Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 9.584426879882812e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0007224082946777344s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.31627368927001953s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.6194968223571777s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0008242130279541016s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.000446319580078125s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.5497207641601562e-05s
INFO | --- Analysis for 0080-3626 took 5.600567579269409s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.9114227294921875e-05s
Availability | VoID file availability check for 土地利用图 took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.291548490524292s
Reputation | Calculation of the PageRank for 土地利用图 took 0.02156543731689453s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.337860107421875e-05s
Believability | Calculation of trust value for 土地利用图 took 1.6689300537109375e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.712920904159546s
Availability | SPARQL endpoint availability check for 113322 took 6.0558319091796875e-05s
Availability | VoID file availability check for 113322 took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for 113322 took 0.2885608673095703s
Reputation | Calculation of the PageRank for 113322 took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for 113322 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.457069396972656e-05s
Believability | Calculation of trust value for 113322 took 1.4543533325195312e-05s
INFO | --- Analysis for 11 took 4.522165536880493s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 9.441375732421875e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2869441509246826s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020999431610107422s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 8.0108642578125e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.430511474609375e-05s
INFO | --- Analysis for 12323 took 2.6676065921783447s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.07147932052612305s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.2886641025543213s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020869970321655273s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.655952453613281e-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.8011679649353027s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.300143003463745s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.2879931926727295s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.792213439941406e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 1.0013580322265625e-05s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.750542163848877s
Availability | SPARQL endpoint availability check for Open Data Web took 5.516767263412476s
Availability | VoID file availability check for Open Data Web took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.29425597190856934s
Reputation | Calculation of the PageRank for Open Data Web took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.7670135498046875e-05s
Believability | Calculation of trust value for Open Data Web took 1.4066696166992188e-05s
INFO | --- Analysis for _data.odw.tw took 12.65079379081726s
Availability | SPARQL endpoint availability check for 土地利用 took 4.38690185546875e-05s
Availability | VoID file availability check for 土地利用 took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2815823554992676s
Reputation | Calculation of the PageRank for 土地利用 took 0.020882606506347656s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.3855438232421875e-05s
Believability | Calculation of trust value for 土地利用 took 1.33514404296875e-05s
INFO | --- Analysis for _data1.odw.tw took 2.6841776371002197s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.553794860839844e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.27680397033691406s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 3.266334533691406e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.5020370483398438e-05s
INFO | --- Analysis for _data2.odw.tw took 4.630538702011108s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.696846008300781e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.30129265785217285s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02023768424987793s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.266334533691406e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.4543533325195312e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 4.027533054351807s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 9.560585021972656e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2821817398071289s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0009517669677734375s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 4.1484832763671875e-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.305037498474121s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 9.226799011230469e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.27526187896728516s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0008294582366943359s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.695487976074219e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 9.059906005859375e-06s
INFO | --- Analysis for A1 took 3.9001853466033936s
Availability | SPARQL endpoint availability check for SummerOlympics took 2.62641978263855s
Availability | VoID file availability check for SummerOlympics took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.2918980121612549s
Reputation | Calculation of the PageRank for SummerOlympics took 0.021770477294921875s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0009441375732421875s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 8.797645568847656e-05s
Believability | Calculation of trust value for SummerOlympics took 1.4543533325195312e-05s
INFO | --- Analysis for abc took 10.107089042663574s
Availability | SPARQL endpoint availability check for Test_m took 9.274482727050781e-05s
Availability | VoID file availability check for Test_m took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Test_m took 0.30058956146240234s
Reputation | Calculation of the PageRank for Test_m took 0.021338224411010742s
Interlinking | Calculation of Degree of Connection for Test_m took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.457069396972656e-05s
Believability | Calculation of trust value for Test_m took 1.4066696166992188e-05s
INFO | --- Analysis for ABC took 2.711550712585449s
Availability | SPARQL endpoint availability check for my intro took 8.96453857421875e-05s
Availability | VoID file availability check for my intro took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for my intro took 0.3095524311065674s
Reputation | Calculation of the PageRank for my intro took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for my intro took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for my intro took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for my intro took 3.647804260253906e-05s
Believability | Calculation of trust value for my intro took 1.5974044799804688e-05s
INFO | --- Analysis for abhay_intro took 2.8464221954345703s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.09853792190551758s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.28403449058532715s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02017688751220703s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010561943054199219s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for abs-linked-data took 2.9288129806518555s
Availability | SPARQL endpoint availability check for AcadOnto took 4.363059997558594e-05s
Availability | VoID file availability check for AcadOnto took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.28822922706604004s
Reputation | Calculation of the PageRank for AcadOnto took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.409385681152344e-05s
Believability | Calculation of trust value for AcadOnto took 1.3828277587890625e-05s
INFO | --- Analysis for acadonto took 3.217510461807251s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.63076138496399s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.3063826560974121s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020560026168823242s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.1961669921875e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.5299530029296875e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.059906005859375e-06s
INFO | --- Analysis for acorn-sat took 37.4927077293396s
Availability | SPARQL endpoint availability check for Addgene took 9.226799011230469e-05s
Availability | VoID file availability check for Addgene took 0.0009157657623291016s
Completeness | Calculation of interlinking completeness for Addgene took 0.31273460388183594s
Reputation | Calculation of the PageRank for Addgene took 0.022066354751586914s
Interlinking | Calculation of Degree of Connection for Addgene took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.863739013671875e-05s
Believability | Calculation of trust value for Addgene took 1.4781951904296875e-05s
INFO | --- Analysis for addgene took 16.21691870689392s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.744529724121094e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.31609272956848145s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 0.00010609626770019531s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.5497207641601562e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 10.094853639602661s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.48468732833862305s
Availability | VoID file availability check for AEMET metereological dataset took 0.0012984275817871094s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.28961706161499023s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.839897155761719e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.4066696166992188e-05s
INFO | --- Analysis for aemet took 5.064646482467651s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.04011249542236328s
Availability | VoID file availability check for AgriNepalData took 0.0002961158752441406s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2846534252166748s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020993947982788086s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.367134094238281e-05s
Believability | Calculation of trust value for AgriNepalData took 1.239776611328125e-05s
INFO | --- Analysis for agrinepaldata took 2.69148588180542s
Availability | SPARQL endpoint availability check for AGRIS took 262.24935030937195s
Availability | VoID file availability check for AGRIS took 0.0007927417755126953s
Completeness | Calculation of interlinking completeness for AGRIS took 0.3466358184814453s
Reputation | Calculation of the PageRank for AGRIS took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.987022399902344e-05s
Believability | Calculation of trust value for AGRIS took 1.239776611328125e-05s
INFO | --- Analysis for agris took 561.6973407268524s
Availability | SPARQL endpoint availability check for AGROVOC took 0.23670148849487305s
Availability | VoID file availability check for AGROVOC took 0.0006582736968994141s
Extra | Recovery of all triples for AGROVOC took 305.8864321708679s
Performance | Total latancy measurement for AGROVOC took 0.5073590278625488s
Amount of data | Number of triples check for AGROVOC took 300.07623863220215s
Interoperability | New terms check for AGROVOC took 6.592447519302368s
Versatility | Languages check for AGROVOC took 300.1243541240692s
Interpretability | Number of blank nodes check for AGROVOC took 300.09030842781067s
Interpretability | RDF structures check for AGROVOC took 0.18678832054138184s
Versatility | Serialization formats check for AGROVOC took 0.09087324142456055s
Availability | RDF dump link check for AGROVOC took 0.07563495635986328s
License | MR license check for AGROVOC took 0.08922576904296875s
License | HR license check for AGROVOC took 3.3756985664367676s
Amount of data | Number of property check for AGROVOC took 0.08885526657104492s
Understandability | Number of label check for AGROVOC took 300.0694091320038s
Understandability | URI regex check for AGROVOC took 0.28621721267700195s
Understandability | Vocabs check for AGROVOC took 0.07876300811767578s
Verifiability | Authors check for AGROVOC took 0.11672449111938477s
Verifiability | Publishers check for AGROVOC took 0.12220954895019531s
Performance | Throughput check for AGROVOC took 10.36326789855957s
Amount of data | Check the number of entities for AGROVOC took 8.20159912109375e-05s
Verifiability | Contribs. check for AGROVOC took 0.10353446006774902s
Interlinking | sameAs chians check for AGROVOC took 0.11746025085449219s
Interlinking | skos check for AGROVOC took 40.962453842163086s
Interlinking | skos check for AGROVOC took 33.401318311691284s
Timeliness | dataset update frequency check for AGROVOC took 0.19716095924377441s
Currency | Creation date check for AGROVOC took 0.3927419185638428s
Currency | Modification date check for AGROVOC took 0.32927680015563965s
Rep.Conc. | URIs length for AGROVOC took 344.63058257102966s
Interoperability | New vocabularies check for AGROVOC took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.17937064170837402s
Accuracy | Check Empty annotation labels for AGROVOC took 25.260741233825684s
Accuracy | Check White space in annotation for AGROVOC took 3.0296993255615234s
Consistency | Disjoint class check for AGROVOC took 0.08805131912231445s
Consistency | Check Misplaced properties for AGROVOC took 22.664700984954834s
Consistency | Check Ontology hijacking for AGROVOC took 300.13709592819214s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 41.80201530456543s
Conciseness | Check Extensional conciseness for AGROVOC took 0.00019168853759765625s
Conciseness | Check Intensional conciseness for AGROVOC took 0.0887598991394043s
Security | Sign check for AGROVOC took 0.13490629196166992s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.5517010688781738s
Reputation | Calculation of the PageRank for AGROVOC took 0.021534442901611328s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011777877807617188s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.9073486328125e-06s
Believability | Calculation of trust value for AGROVOC took 1.1444091796875e-05s
INFO | --- Analysis for agrovoc took 2956.482110261917s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.4047327041625977s
Availability | VoID file availability check for Analytics India Magazine took 0.0006778240203857422s
Extra | Recovery of all triples for Analytics India Magazine took 3.108001947402954s
Performance | Total latancy measurement for Analytics India Magazine took 2.5864555835723877s
Amount of data | Number of triples check for Analytics India Magazine took 1.0990986824035645s
Versatility | Languages check for Analytics India Magazine took 1.3607439994812012s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.5402979850769043s
Interpretability | RDF structures check for Analytics India Magazine took 1.2696313858032227s
Versatility | Serialization formats check for Analytics India Magazine took 1.2513678073883057s
Availability | RDF dump link check for Analytics India Magazine took 1.1356582641601562s
License | MR license check for Analytics India Magazine took 1.1751058101654053s
License | HR license check for Analytics India Magazine took 1.2432162761688232s
Amount of data | Number of property check for Analytics India Magazine took 1.5452728271484375s
Understandability | Number of label check for Analytics India Magazine took 1.1256637573242188s
Understandability | URI regex check for Analytics India Magazine took 2.468217611312866s
Understandability | Vocabs check for Analytics India Magazine took 1.1731181144714355s
Verifiability | Authors check for Analytics India Magazine took 1.3820486068725586s
Verifiability | Publishers check for Analytics India Magazine took 1.1566047668457031s
Performance | Throughput check for Analytics India Magazine took 15.89271092414856s
Amount of data | Check the number of entities for Analytics India Magazine took 0.00010085105895996094s
Verifiability | Contribs. check for Analytics India Magazine took 1.2942454814910889s
Interlinking | sameAs chians check for Analytics India Magazine took 1.079115629196167s
Interlinking | skos check for Analytics India Magazine took 1.0813381671905518s
Interlinking | skos check for Analytics India Magazine took 0.13953852653503418s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.3691704273223877s
Currency | Creation date check for Analytics India Magazine took 2.0887210369110107s
Currency | Modification date check for Analytics India Magazine took 3.3896729946136475s
Rep.Conc. | URIs length for Analytics India Magazine took 2.430271863937378s
Interoperability | New vocabularies check for Analytics India Magazine took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.2742955684661865s
Consistency | Disjoint class check for Analytics India Magazine took 1.7922930717468262s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.2652795314788818s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.9412460327148438s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.0001533031463623047s
Security | Sign check for Analytics India Magazine took 1.4021635055541992s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.3001210689544678s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0009679794311523438s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 1.430511474609375e-06s
Believability | Calculation of trust value for Analytics India Magazine took 9.5367431640625e-06s
INFO | --- Analysis for AIM took 96.6233139038086s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 0.00021314620971679688s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.28746581077575684s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.504753112792969e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.3828277587890625e-05s
INFO | --- Analysis for AISHE took 2.631396532058716s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.57763671875e-05s
Availability | VoID file availability check for  equipment ontology took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.3029801845550537s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02244424819946289s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for  equipment ontology took 1.4066696166992188e-05s
INFO | --- Analysis for akash took 2.659410238265991s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 262.8999650478363s
Availability | VoID file availability check for aliada-scanbit-net took 0.000766754150390625s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.39592623710632324s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02124190330505371s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00013637542724609375s
Believability | Calculation of trust value for aliada-scanbit-net took 1.4066696166992188e-05s
INFO | --- Analysis for aliada-scanbit-net took 1454.4306304454803s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.7802212238311768s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006697177886962891s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 137.7743375301361s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7138607501983643s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.3870463371276855s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.660900592803955s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.021550655365s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.5698304176330566s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8927795886993408s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.7108278274536133s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6853194236755371s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5753638744354248s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5699725151062012s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 32.0236701965332s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.572904109954834s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7697644233703613s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1041185855865479s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5780572891235352s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6315524578094482s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5676078796386719s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.805314064025879s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 3.9577484130859375e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5471892356872559s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5782356262207031s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6250181198120117s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6021549701690674s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5710902214050293s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.8785169124603271s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.126049280166626s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 52.513386964797974s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.6418876647949219s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5756618976593018s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6540024280548096s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.7166335582733154s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 36.41157364845276s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.1169354915618896s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.7941606044769287s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.5921986103057861s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.48825740814209s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 9.082335472106934s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 34.90513253211975s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.5966660976409912s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.527819871902466s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.746776819229126s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8434042930603027s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5411114692687988s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 14604.21639418602s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.6760103702545166s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.022299766540527344s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 7.033348083496094e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.654594421386719e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 2.0198919773101807s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.0251998901367188e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 15358.795161008835s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.39925694465637207s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.3113260269165039s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020631074905395508s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.0531158447265625e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.4066696166992188e-05s
INFO | --- Analysis for alpino-rdf took 4.177117347717285s
Availability | SPARQL endpoint availability check for AAT-atawil took 5.626678466796875e-05s
Availability | VoID file availability check for AAT-atawil took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.304978609085083s
Reputation | Calculation of the PageRank for AAT-atawil took 0.022353172302246094s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.24249267578125e-05s
Believability | Calculation of trust value for AAT-atawil took 1.1444091796875e-05s
INFO | --- Analysis for Altawil took 2.817498207092285s
Availability | SPARQL endpoint availability check for Amer Nejma took 8.749961853027344e-05s
Availability | VoID file availability check for Amer Nejma took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.2928493022918701s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.266334533691406e-05s
Believability | Calculation of trust value for Amer Nejma took 1.2874603271484375e-05s
INFO | --- Analysis for Amer_Nejma took 2.6653149127960205s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.8110389709472656s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.29116058349609375s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.02079916000366211s
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.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.179115295410156e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.33514404296875e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 4.231647729873657s
Availability | SPARQL endpoint availability check for Anime Dataset took 0.00010180473327636719s
Availability | VoID file availability check for Anime Dataset took 0.0008058547973632812s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.27661871910095215s
Reputation | Calculation of the PageRank for Anime Dataset took 0.02154994010925293s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.504753112792969e-05s
Believability | Calculation of trust value for Anime Dataset took 1.0967254638671875e-05s
INFO | --- Analysis for Anime took 3.887868642807007s
Availability | SPARQL endpoint availability check for ANNO took 4.482269287109375e-05s
Availability | VoID file availability check for ANNO took 0.0006883144378662109s
Completeness | Calculation of interlinking completeness for ANNO took 0.3165605068206787s
Reputation | Calculation of the PageRank for ANNO took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for ANNO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.695487976074219e-05s
Believability | Calculation of trust value for ANNO took 1.5020370483398438e-05s
INFO | --- Analysis for anno took 8.210920095443726s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 8.821487426757812e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.316267728805542s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 8.535385131835938e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.5020370483398438e-05s
INFO | --- Analysis for AntiqueCarsCollection took 4.415712118148804s
Availability | SPARQL endpoint availability check for apache took 4.482269287109375e-05s
Availability | VoID file availability check for apache took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for apache took 0.2890446186065674s
Reputation | Calculation of the PageRank for apache took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for apache took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for apache took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for apache took 5.602836608886719e-05s
Believability | Calculation of trust value for apache took 1.3828277587890625e-05s
INFO | --- Analysis for apache took 3.675628185272217s
Availability | SPARQL endpoint availability check for Apertium RDF took 0.000118255615234375s
Availability | VoID file availability check for Apertium RDF took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.300098180770874s
Reputation | Calculation of the PageRank for Apertium RDF took 0.022379636764526367s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.76837158203125e-05s
Believability | Calculation of trust value for Apertium RDF took 1.5497207641601562e-05s
INFO | --- Analysis for apertium-rdf took 6.0998146533966064s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 9.012222290039062e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0014925003051757812s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2793161869049072s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 5.245208740234375e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.4066696166992188e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 6.028919696807861s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 9.274482727050781e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.3393402099609375s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.5497207641601562e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 5.960374593734741s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 9.322166442871094e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.3166053295135498s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.02087688446044922s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.5020370483398438e-05s
INFO | --- Analysis for apertium-rdf-en-es took 6.203306436538696s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.76837158203125e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.3053898811340332s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020941972732543945s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 5.030632019042969e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.5020370483398438e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 5.968466520309448s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 6.198883056640625e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0003597736358642578s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2766880989074707s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0008652210235595703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 5.316734313964844e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.8363916873931885s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.3087427616119385s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020968198776245117s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 5.1021575927734375e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 5.8821752071380615s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 9.1552734375e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0012421607971191406s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.3405017852783203s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.021889209747314453s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 5.054473876953125e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 5.94234299659729s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 9.512901306152344e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.28396177291870117s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.52587890625e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.915406703948975s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.553794860839844e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0008208751678466797s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.30851030349731445s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.021904706954956055s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0010063648223876953s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 5.650520324707031e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.4781951904296875e-05s
INFO | --- Analysis for apertium-rdf-es-an took 5.838424205780029s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 9.560585021972656e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.2841336727142334s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.02124500274658203s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 5.880560398101807s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 6.175041198730469e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.3125607967376709s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.02125716209411621s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 5.1021575927734375e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.0013580322265625e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 28.82661747932434s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 9.1552734375e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.2956705093383789s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.022145509719848633s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.001074075698852539s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 7.295608520507812e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 5.967009544372559s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 9.226799011230469e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.28049683570861816s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.887580871582031e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.5020370483398438e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 5.794483661651611s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.887580871582031e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.30616092681884766s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0008544921875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 5.364418029785156e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 9.5367431640625e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.837929725646973s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 8.916854858398438e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.3291330337524414s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 5.626678466796875e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 5.961188554763794s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.649162292480469e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.296583890914917s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.887580871582031e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.4543533325195312e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 5.933481931686401s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.57763671875e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.2963225841522217s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 5.030632019042969e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.430511474609375e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.9239935874938965s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.601478576660156e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.28024721145629883s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020955801010131836s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.9591064453125e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.430511474609375e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 5.982109785079956s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 9.584426879882812e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0007648468017578125s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.30359768867492676s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.023581266403198242s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0008726119995117188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 5.412101745605469e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.85907506942749s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2917816638946533s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.021420001983642578s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 5.078315734863281e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.4543533325195312e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 6.07379674911499s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 0.00010275840759277344s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006899833679199219s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.30149364471435547s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02091503143310547s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 5.1021575927734375e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.621246337890625e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 6.384309530258179s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 9.107589721679688e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.3157682418823242s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.0208737850189209s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 5.2928924560546875e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.761371612548828s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 0.6902487277984619s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.0006422996520996094s
Extra | Recovery of all triples for AragoDBpedia - aragon open data took 3.0575709342956543s
Performance | Total latancy measurement for AragoDBpedia - aragon open data took 1.9277269840240479s
Amount of data | Number of triples check for AragoDBpedia - aragon open data took 0.7615270614624023s
Interoperability | New terms check for AragoDBpedia - aragon open data took 2.238466262817383s
Versatility | Languages check for AragoDBpedia - aragon open data took 60.46538424491882s
Interpretability | Number of blank nodes check for AragoDBpedia - aragon open data took 4.1172661781311035s
Security | Check HTTPS for AragoDBpedia - aragon open data took 0.24885773658752441s
Interpretability | RDF structures check for AragoDBpedia - aragon open data took 0.6358187198638916s
Versatility | Serialization formats check for AragoDBpedia - aragon open data took 0.9077374935150146s
Availability | RDF dump link check for AragoDBpedia - aragon open data took 0.4258689880371094s
License | MR license check for AragoDBpedia - aragon open data took 0.5654950141906738s
License | HR license check for AragoDBpedia - aragon open data took 5.634857892990112s
Amount of data | Number of property check for AragoDBpedia - aragon open data took 0.4360380172729492s
Understandability | Number of label check for AragoDBpedia - aragon open data took 0.5044102668762207s
Understandability | URI regex check for AragoDBpedia - aragon open data took 0.8956549167633057s
Understandability | Vocabs check for AragoDBpedia - aragon open data took 0.4671151638031006s
Verifiability | Authors check for AragoDBpedia - aragon open data took 0.4680180549621582s
Verifiability | Publishers check for AragoDBpedia - aragon open data took 0.41771674156188965s
Performance | Throughput check for AragoDBpedia - aragon open data took 11.782729625701904s
Amount of data | Check the number of entities for AragoDBpedia - aragon open data took 7.390975952148438e-05s
Verifiability | Contribs. check for AragoDBpedia - aragon open data took 0.5356569290161133s
Interlinking | sameAs chians check for AragoDBpedia - aragon open data took 0.43956947326660156s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.555192232131958s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.37288475036621094s
Timeliness | dataset update frequency check for AragoDBpedia - aragon open data took 0.4831092357635498s
Currency | Creation date check for AragoDBpedia - aragon open data took 1.3474044799804688s
Currency | Modification date check for AragoDBpedia - aragon open data took 0.43073201179504395s
Rep.Conc. | URIs length for AragoDBpedia - aragon open data took 5.988778591156006s
Interoperability | New vocabularies check for AragoDBpedia - aragon open data took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for AragoDBpedia - aragon open data took 0.43091654777526855s
Accuracy | Check Functional Property for AragoDBpedia - aragon open data took 0.46207594871520996s
Accuracy | Check Inverse Functional Property for AragoDBpedia - aragon open data took 0.47269344329833984s
Accuracy | Check Empty annotation labels for AragoDBpedia - aragon open data took 1.390967845916748s
Accuracy | Check White space in annotation for AragoDBpedia - aragon open data took 0.030588626861572266s
Accuracy | Check Datatype consistency for AragoDBpedia - aragon open data took 0.029184579849243164s
Consistency | Disjoint class check for AragoDBpedia - aragon open data took 0.4372732639312744s
Consistency | Check Misplaced properties for AragoDBpedia - aragon open data took 4.463545083999634s
Consistency | Misplaced classes for AragoDBpedia - aragon open data took 0.5923843383789062s
Consistency | Check Ontology hijacking for AragoDBpedia - aragon open data took 2.7994635105133057s
Consistency | Check Invalid usage of undefined classes for AragoDBpedia - aragon open data took 1.4480807781219482s
Consistency | Check Invalid usage of undefined properties for AragoDBpedia - aragon open data took 5.311052083969116s
Conciseness | Check Extensional conciseness for AragoDBpedia - aragon open data took 0.03265547752380371s
Conciseness | Check Intensional conciseness for AragoDBpedia - aragon open data took 0.6685366630554199s
Security | Sign check for AragoDBpedia - aragon open data took 0.5402727127075195s
Availability | Check URIs Dereferenciability for AragoDBpedia - aragon open data took 3361.128833055496s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 0.6933877468109131s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.02156972885131836s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 5.6743621826171875e-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.0251998901367188e-05s
INFO | --- Analysis for aragodbpedia took 3644.3327498435974s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.468849420547485s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.3128213882446289s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 9.369850158691406e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.430511474609375e-05s
INFO | --- Analysis for archiveshub-linkeddata took 83.46114134788513s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.797453880310059s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.2907836437225342s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020929813385009766s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.552436828613281e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 3.0040740966796875e-05s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 21.047649145126343s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.8885364532470703s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.30158495903015137s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.0531158447265625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.4543533325195312e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.903931140899658s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.9114227294921875e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.31142210960388184s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010967254638671875s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.0251998901367188e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 14.328124523162842s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.649162292480469e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0003380775451660156s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.31196165084838867s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.021595239639282227s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010848045349121094s
Believability | Calculation of trust value for Arthroscopy community took 1.4066696166992188e-05s
INFO | --- Analysis for arthroscopy took 29.50861406326294s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.7620978355407715s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0004398822784423828s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 36.65926718711853s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 1.379096508026123s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.16209697723389s
Interoperability | New terms check for Wikidata entry for Art × Science International took 2.13503098487854s
Versatility | Languages check for Wikidata entry for Art × Science International took 65.16614747047424s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.1725344657898s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.2660341262817383s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.18728852272033691s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.1936955451965332s
License | MR license check for Wikidata entry for Art × Science International took 0.22270894050598145s
License | HR license check for Wikidata entry for Art × Science International took 65.15957903862s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.66837477684021s
Understandability | Number of label check for Wikidata entry for Art × Science International took 65.17132544517517s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.3731200695037842s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.18474769592285156s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.18659543991088867s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.2005462646484375s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 8.821487426757812e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.3259117603302002s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 19.99129867553711s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.18375086784362793s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.21263456344604492s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.2388002872467041s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.39362001419067383s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.48537135124206543s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 45.22596859931946s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.19073224067687988s
Accuracy | Check Empty annotation labels for Wikidata entry for Art × Science International took 14.3452308177948s
Accuracy | Check White space in annotation for Wikidata entry for Art × Science International took 2.702011823654175s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.727874755859375s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.1820216178894043s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 11.561090230941772s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 8.988874912261963s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 62.04844093322754s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 43.945767641067505s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.9035732746124268s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.8671133518218994s
Security | Sign check for Wikidata entry for Art × Science International took 0.18230462074279785s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 9.256414890289307s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.35601115226745605s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.02268671989440918s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 2.6464462280273438e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.5735626220703125e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 2.6226043701171875e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 9.298324584960938e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 1043.3455607891083s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 2.898444890975952s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.29888319969177246s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0213010311126709s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.036064147949219e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.4066696166992188e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 11.816450595855713s
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.162569284439087s
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.0005586147308349609s
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.3126490116119385s
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.02072429656982422s
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.0007340908050537109s
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.296966552734375e-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.1920928955078125e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 10.705050706863403s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.160308837890625s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.29816389083862305s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.021094083786010742s
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.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.5367431640625e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 11.657948732376099s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.1708569526672363s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.30266833305358887s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020751953125s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.7206878662109375e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.2636184692382812e-05s
INFO | --- Analysis for ASCDC-CRB took 13.352250814437866s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.1663787364959717s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.31243133544921875s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.02084827423095703s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.00010061264038085938s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0251998901367188e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.141072988510132s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.1806905269622803s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.29253530502319336s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 4.6253204345703125e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC-DQOT took 11.947745084762573s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.1787490844726562s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.303438663482666s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.821487426757812e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.24855923652649s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 2.8878836631774902s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.30835652351379395s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.022959232330322266s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0011599063873291016s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 0.00011038780212402344s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.5497207641601562e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 14.313755512237549s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.1568315029144287s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007224082946777344s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.2997403144836426s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.02143239974975586s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.459785461425781e-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.0251998901367188e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.025042295455933s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.1813454627990723s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.3182101249694824s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.841255187988281e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.261872291564941s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.5655195713043213s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.29065775871276855s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.021004199981689453s
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.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.1975250244140625e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.5020370483398438e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 15.240689039230347s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.192295789718628s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.28751373291015625s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02108001708984375s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0011811256408691406s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.00011086463928222656s
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.841102600097656s
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.16382098197937s
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.0006759166717529297s
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.3271472454071045s
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.02099919319152832s
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.0007832050323486328s
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.96453857421875e-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.047284126281738s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.185303211212158s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.30846595764160156s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.863739013671875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.3113021850585938e-05s
INFO | --- Analysis for ASCDC_-_DNB took 10.626784563064575s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 5.054473876953125e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2878141403198242s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.02082681655883789s
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.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.581710815429688e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.4066696166992188e-05s
INFO | --- Analysis for asit took 7.701444864273071s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 5.888938903808594e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0007224082946777344s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.3030064105987549s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.021312475204467773s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.982948303222656e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 9.5367431640625e-06s
INFO | --- Analysis for asjp took 4.9543139934539795s
Availability | SPARQL endpoint availability check for ASN:US took 2.338024377822876s
Availability | VoID file availability check for ASN:US took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2843935489654541s
Reputation | Calculation of the PageRank for ASN:US took 0.021167278289794922s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.319450378417969e-05s
Believability | Calculation of trust value for ASN:US took 1.049041748046875e-05s
INFO | --- Analysis for asn-us took 12.937904596328735s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 9.1552734375e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.00039577484130859375s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.2884228229522705s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02107405662536621s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007476806640625s
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 1.0013580322265625e-05s
INFO | --- Analysis for aspire-mmu took 4.995479345321655s
Availability | SPARQL endpoint availability check for associations took 4.5299530029296875e-05s
Availability | VoID file availability check for associations took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for associations took 0.3033924102783203s
Reputation | Calculation of the PageRank for associations took 0.020990371704101562s
Interlinking | Calculation of Degree of Connection for associations took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for associations took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for associations took 8.034706115722656e-05s
Believability | Calculation of trust value for associations took 1.430511474609375e-05s
INFO | --- Analysis for associations took 7.446749687194824s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 5.078315734863281e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.3132474422454834s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.021591901779174805s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 0.00010824203491210938s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.4781951904296875e-05s
INFO | --- Analysis for athelia-rfid took 6.031449317932129s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.6197710037231445s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.30756187438964844s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.022098302841186523s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.001100301742553711s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 7.987022399902344e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.4781951904296875e-05s
INFO | --- Analysis for AugustiniConfessiones took 4.388359069824219s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.4691343307495117s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.28860926628112793s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02076888084411621s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.703636169433594e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.3828277587890625e-05s
INFO | --- Analysis for austrian_ski_racers took 3.845754384994507s
Availability | SPARQL endpoint availability check for AVsOnto took 9.226799011230469e-05s
Availability | VoID file availability check for AVsOnto took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.2981913089752197s
Reputation | Calculation of the PageRank for AVsOnto took 0.021723270416259766s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.218650817871094e-05s
Believability | Calculation of trust value for AVsOnto took 1.3828277587890625e-05s
INFO | --- Analysis for AVsOnto took 3.576308012008667s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.44806647300720215s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005669593811035156s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 186.36278438568115s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5080630779266357s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10098242759705s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 232.84655833244324s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.05087065696716s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.07987666130066s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2266073226928711s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24555277824401855s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2466273307800293s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10211706161499023s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 42.49755907058716s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10420966148376s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17963886260986328s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.07994532585144s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.35207223892211914s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13056182861328125s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15461087226867676s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09173297882080078s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.52175259590149s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.20159912109375e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.08844494819641113s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.03637862205505s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15860915184020996s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1369032859802246s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14394378662109375s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4458582401275635s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2527353763580322s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1450.289814710617s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14440011978149414s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.627803087234497s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.271284818649292s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.989049434661865s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1268453598022461s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.29599809646606s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 26.113023042678833s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.1682305335998535s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.6783866882324s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.850764751434326s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24535489082336426s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0621166229248047s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.8220696449279785s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0221707820892334s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.9073486328125e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.152557373046875e-06s
INFO | --- Analysis for b3kat took 5014.811309576035s
Availability | SPARQL endpoint availability check for BabelNet took 0.4428107738494873s
Availability | VoID file availability check for BabelNet took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for BabelNet took 0.3089461326599121s
Reputation | Calculation of the PageRank for BabelNet took 0.021081924438476562s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00019049644470214844s
Believability | Calculation of trust value for BabelNet took 1.5497207641601562e-05s
INFO | --- Analysis for babelnet took 4.699151277542114s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 9.250640869140625e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.30506443977355957s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020848989486694336s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.314018249511719e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.4543533325195312e-05s
INFO | --- Analysis for Bacevicius.lt took 2.671726942062378s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5047652721405029s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0011594295501708984s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.2912943363189697s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.021839380264282227s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.792213439941406e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.4781951904296875e-05s
INFO | --- Analysis for bag took 4.33926248550415s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.520789623260498s
Availability | VoID file availability check for 红色经典歌曲 took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2972269058227539s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02084946632385254s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.647804260253906e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.3589859008789062e-05s
INFO | --- Analysis for baixue took 3.2512621879577637s
Availability | SPARQL endpoint availability check for baixue composer took 5.7220458984375e-05s
Availability | VoID file availability check for baixue composer took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for baixue composer took 0.3065006732940674s
Reputation | Calculation of the PageRank for baixue composer took 0.021016597747802734s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.24249267578125e-05s
Believability | Calculation of trust value for baixue composer took 1.3113021850585938e-05s
INFO | --- Analysis for baixue_composer took 3.1676690578460693s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.560585021972656e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.3014247417449951s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02118229866027832s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.647804260253906e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.4543533325195312e-05s
INFO | --- Analysis for baixue_imagery took 3.1977715492248535s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.465217590332031e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.3356151580810547s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02190542221069336s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.695487976074219e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.430511474609375e-05s
INFO | --- Analysis for baixue_imagery1 took 4.130383729934692s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.601478576660156e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007364749908447266s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.3158903121948242s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0008809566497802734s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.2874603271484375e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.188652276992798s
Availability | SPARQL endpoint availability check for BBC Music took 0.5794966220855713s
Availability | VoID file availability check for BBC Music took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for BBC Music took 0.3006761074066162s
Reputation | Calculation of the PageRank for BBC Music took 0.020938396453857422s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00013446807861328125s
Believability | Calculation of trust value for BBC Music took 1.430511474609375e-05s
INFO | --- Analysis for bbc-music took 4.0639259815216064s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.3161654472351074s
Availability | VoID file availability check for BBC Programmes took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.28011202812194824s
Reputation | Calculation of the PageRank for BBC Programmes took 0.022180557250976562s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0008101463317871094s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00011467933654785156s
Believability | Calculation of trust value for BBC Programmes took 1.621246337890625e-05s
INFO | --- Analysis for bbc-programmes took 12.380683660507202s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.2750720977783203s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.3118278980255127s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02185201644897461s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.0001087188720703125s
Believability | Calculation of trust value for BBC Wildlife Finder took 9.5367431640625e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.768265008926392s
Availability | SPARQL endpoint availability check for BBOP took 9.679794311523438e-05s
Availability | VoID file availability check for BBOP took 0.0009300708770751953s
Completeness | Calculation of interlinking completeness for BBOP took 0.3020360469818115s
Reputation | Calculation of the PageRank for BBOP took 0.020883798599243164s
Interlinking | Calculation of Degree of Connection for BBOP took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.528594970703125e-05s
Believability | Calculation of trust value for BBOP took 9.775161743164062e-06s
INFO | --- Analysis for bbop-selected took 20.755742073059082s
Availability | SPARQL endpoint availability check for Bdgp took 1.072277307510376s
Availability | VoID file availability check for Bdgp took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Bdgp took 0.28391170501708984s
Reputation | Calculation of the PageRank for Bdgp took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0010685920715332031s
Interlinking | Calculation of Clustering coefficient for Bdgp took 4.506111145019531e-05s
Believability | Calculation of trust value for Bdgp took 1.52587890625e-05s
INFO | --- Analysis for bdgp took 5.219807863235474s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.696846008300781e-05s
Availability | VoID file availability check for Bendev Junior took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.28881025314331055s
Reputation | Calculation of the PageRank for Bendev Junior took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.218650817871094e-05s
Believability | Calculation of trust value for Bendev Junior took 1.5020370483398438e-05s
INFO | --- Analysis for bendevoficial took 3.3399510383605957s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 8.253479480743408s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0007290840148925781s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.31291842460632324s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.486343383789062e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 1.049041748046875e-05s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 21.87237572669983s
Availability | SPARQL endpoint availability check for berlios took 8.893013000488281e-05s
Availability | VoID file availability check for berlios took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for berlios took 0.2918980121612549s
Reputation | Calculation of the PageRank for berlios took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for berlios took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for berlios took 9.5367431640625e-05s
Believability | Calculation of trust value for berlios took 1.3589859008789062e-05s
INFO | --- Analysis for berlios took 3.054810047149658s
Availability | SPARQL endpoint availability check for Between Our Worlds took 8.869171142578125e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.37351036071777344s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.961822509765625e-05s
Believability | Calculation of trust value for Between Our Worlds took 9.5367431640625e-06s
INFO | --- Analysis for betweenourworlds took 9.283025979995728s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.10422968864440918s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.297454833984375s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.022156238555908203s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.036064147949219e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for bfs-linked-data took 2.8840768337249756s
Availability | SPARQL endpoint availability check for BibBase took 0.21106529235839844s
Availability | VoID file availability check for BibBase took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for BibBase took 0.3104844093322754s
Reputation | Calculation of the PageRank for BibBase took 0.021997451782226562s
Interlinking | Calculation of Degree of Connection for BibBase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.918212890625e-05s
Believability | Calculation of trust value for BibBase took 1.239776611328125e-05s
INFO | --- Analysis for bibbase took 2.9846107959747314s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 8.797645568847656e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.2843668460845947s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.021047353744506836s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00010967254638671875s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.4543533325195312e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 10.56259274482727s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 9.679794311523438e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.3081974983215332s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.021634340286254883s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00013875961303710938s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 9.775161743164062e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 9.26080584526062s
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.0007381439208984375s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.32161831855773926s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.02202296257019043s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 4.553794860839844e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.5020370483398438e-05s
INFO | --- Analysis for BibSonomy took 10.912365913391113s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.458427429199219e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0007319450378417969s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.3084721565246582s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.023043394088745117s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.7670135498046875e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.3828277587890625e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 7.91728663444519s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 5.173683166503906e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.28548145294189453s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.409385681152344e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.3828277587890625e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.9637715816497803s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.895568609237671s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006132125854492188s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 19.476893186569214s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5284442901611328s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 46.79135203361511s
Interoperability | New terms check for Bio2RDF::Affymetrix took 42.46343731880188s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.12261772155762s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.14563727378845215s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.9731326103210449s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.21439051628112793s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.463869571685791s
License | MR license check for Bio2RDF::Affymetrix took 0.4572563171386719s
License | HR license check for Bio2RDF::Affymetrix took 60.095943450927734s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.1470322608947754s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.759649753570557s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.3814563751220703s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.13288640975952148s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.13703083992004395s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.12520503997802734s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.645419359207153s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 81.88903141021729s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.4546854496002197s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.24930286407470703s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.6930356025695801s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.1835641860961914s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.11593818664550781s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.24721503257751465s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.23869609832763672s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 108.16680860519409s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 13.849905729293823s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.30672407150268555s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15704083442687988s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12749600410461426s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.952435493469238s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8998773097991943s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.677778959274292s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.29739952087402344s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.23088526725769s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.3408780097961426s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.2426652908325195s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.4330878257751465s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.52347779273987s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7089815139770508s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3538081645965576s
Security | Sign check for Bio2RDF::Affymetrix took 0.12804293632507324s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 11.20870041847229s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.3887979984283447s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.02198195457458496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010037422180175781s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 13.321330785751343s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1044.6067733764648s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5148754119873047s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0006165504455566406s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.310440063476562s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2481036186218262s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 46.54615378379822s
Interoperability | New terms check for Bio2RDF::Biomodels took 43.148682832717896s
Versatility | Languages check for Bio2RDF::Biomodels took 60.25537419319153s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2809605598449707s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.15747785568237305s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.39261937141418457s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.3246042728424072s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.5045173168182373s
License | MR license check for Bio2RDF::Biomodels took 0.5262773036956787s
License | HR license check for Bio2RDF::Biomodels took 60.26688241958618s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.2822592258453369s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.380869388580322s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5835835933685303s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2525660991668701s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.27492666244506836s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.2573432922363281s
Performance | Throughput check for Bio2RDF::Biomodels took 11.06120753288269s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 86.48966884613037s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 1.4194493293762207s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.3662416934967041s
Interlinking | skos check for Bio2RDF::Biomodels took 0.7285525798797607s
Interlinking | skos check for Bio2RDF::Biomodels took 0.3558504581451416s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.25849366188049316s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5302424430847168s
Currency | Modification date check for Bio2RDF::Biomodels took 0.49493932723999023s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 110.87162733078003s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 14.191851615905762s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.4687511920928955s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.29084157943725586s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2806274890899658s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.3896403312683105s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.9081263542175293s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.7005929946899414s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.40961122512817383s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.27229452133179s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.538470983505249s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 7.279311418533325s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.4246547222137451s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.66731095314026s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7032468318939209s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.4607877731323242s
Security | Sign check for Bio2RDF::Biomodels took 0.28662919998168945s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 9.655017852783203s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.5472414493560791s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00012302398681640625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 13.428136825561523s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.52587890625e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1057.950998544693s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.4656345844268799s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006494522094726562s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 19.011861324310303s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.278653860092163s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 44.84157848358154s
Interoperability | New terms check for Bio2RDF::Bioportal took 42.21275091171265s
Versatility | Languages check for Bio2RDF::Bioportal took 60.265812158584595s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2570459842681885s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.14568376541137695s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.35994720458984375s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.30742383003234863s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.334707021713257s
License | MR license check for Bio2RDF::Bioportal took 0.46139979362487793s
License | HR license check for Bio2RDF::Bioportal took 60.249308347702026s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2623913288116455s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.481109619140625s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5938074588775635s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.25277256965637207s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.27004384994506836s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.2529280185699463s
Performance | Throughput check for Bio2RDF::Bioportal took 10.609153032302856s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 85.99396300315857s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.6203694343566895s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.27715516090393066s
Interlinking | skos check for Bio2RDF::Bioportal took 0.841090202331543s
Interlinking | skos check for Bio2RDF::Bioportal took 0.3639085292816162s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.2486252784729004s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5074982643127441s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5249981880187988s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 111.96915769577026s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 14.259580373764038s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.44069790840148926s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.26743555068969727s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.276303768157959s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.947307586669922s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8977375030517578s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6945085525512695s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.398357629776001s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.39326047897339s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4597034454345703s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.22149133682251s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.4164364337921143s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.68735074996948s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7294468879699707s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.41554689407348633s
Security | Sign check for Bio2RDF::Bioportal took 0.272017240524292s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 10.416479110717773s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.4673149585723877s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00042510032653808594s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 15.131735563278198s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1069.0937430858612s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.13910818099975586s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0003657341003417969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.4102513790130615s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 6.699562072753906e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-chembl took 17.03793692588806s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.46880102157592773s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006587505340576172s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 18.950694799423218s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2609868049621582s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 46.59181046485901s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 42.98660445213318s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.24522614479065s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.27086758613586426s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.15651917457580566s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.44678544998168945s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.32450079917907715s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.182701826095581s
License | MR license check for Bio2RDF::Clinicaltrials took 0.6175117492675781s
License | HR license check for Bio2RDF::Clinicaltrials took 60.258116245269775s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.2584502696990967s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 9.701911687850952s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.6151354312896729s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.26108551025390625s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.25682544708251953s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.24810171127319336s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.133212804794312s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 82.3800880908966s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.9528303146362305s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.3396165370941162s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.740386962890625s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3434734344482422s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.28384923934936523s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5393056869506836s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5560774803161621s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 112.00519323348999s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 14.938842058181763s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.3977646827697754s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2723429203033447s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.28237271308898926s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.940988302230835s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.9048473834991455s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6769313812255859s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.4183971881866455s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.45090365409851s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.446265935897827s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.812704801559448s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.4256253242492676s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.675199031829834s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7126753330230713s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.4504244327545166s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.27891969680786133s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 18.065900325775146s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.512528657913208s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020885229110717773s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 6.341934204101562e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 13.80944037437439s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.5497207641601562e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1064.5244815349579s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.48816871643066406s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0006728172302246094s
Extra | Recovery of all triples for Bio2RDF::Ctd took 20.587331771850586s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2955656051635742s
Amount of data | Number of triples check for Bio2RDF::Ctd took 47.94757914543152s
Interoperability | New terms check for Bio2RDF::Ctd took 42.5398895740509s
Versatility | Languages check for Bio2RDF::Ctd took 60.24735426902771s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.26931166648864746s
Security | Check HTTPS for Bio2RDF::Ctd took 0.15605545043945312s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.588310956954956s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.31779932975769043s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.4615743160247803s
License | MR license check for Bio2RDF::Ctd took 0.5533511638641357s
License | HR license check for Bio2RDF::Ctd took 60.23819947242737s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.25696659088134766s
Understandability | Number of label check for Bio2RDF::Ctd took 9.652944326400757s
Understandability | URI regex check for Bio2RDF::Ctd took 0.6096072196960449s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.24843358993530273s
Verifiability | Authors check for Bio2RDF::Ctd took 0.24677562713623047s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.2590930461883545s
Performance | Throughput check for Bio2RDF::Ctd took 11.503278017044067s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 84.81983256340027s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.9775397777557373s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.38782405853271484s
Interlinking | skos check for Bio2RDF::Ctd took 0.8454926013946533s
Interlinking | skos check for Bio2RDF::Ctd took 0.41294002532958984s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2892177104949951s
Currency | Creation date check for Bio2RDF::Ctd took 0.5293319225311279s
Currency | Modification date check for Bio2RDF::Ctd took 0.5013542175292969s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 109.44044709205627s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 13.781526565551758s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4322779178619385s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.29061269760131836s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2825045585632324s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 6.66011643409729s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8989534378051758s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6791694164276123s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.40738749504089355s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.76332807540894s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.479620933532715s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.866472959518433s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.436537504196167s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.68426728248596s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7109260559082031s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.4258689880371094s
Security | Sign check for Bio2RDF::Ctd took 0.2945973873138428s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 12.956695318222046s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.36703920364379883s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.0209352970123291s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 7.43865966796875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 13.734497308731079s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.0251998901367188e-05s
INFO | --- Analysis for bio2rdf-ctd took 1070.895637512207s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 9.059906005859375e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.2734675407409668s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.021410465240478516s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.364418029785156e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-dataset took 2.954118490219116s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.46484804153442383s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0006043910980224609s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 18.411978483200073s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.251288652420044s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 46.01277542114258s
Interoperability | New terms check for Bio2RDF::Dbsnp took 41.54399275779724s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.24304437637329s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.25979065895080566s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.1466670036315918s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.702204704284668s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.292773962020874s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.317047119140625s
License | MR license check for Bio2RDF::Dbsnp took 0.4615824222564697s
License | HR license check for Bio2RDF::Dbsnp took 60.25729990005493s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2729218006134033s
Understandability | Number of label check for Bio2RDF::Dbsnp took 9.381793737411499s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5846331119537354s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.2332909107208252s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2539942264556885s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.25246119499206543s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.887034177780151s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 82.41833353042603s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.6339817047119141s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3559386730194092s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.6857907772064209s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.3413825035095215s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.24600601196289062s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.510779857635498s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5133578777313232s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 109.3634877204895s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 14.678861856460571s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.40894627571105957s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.28261351585388184s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.26753711700439453s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.6016151905059814s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.9016735553741455s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6789834499359131s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.5040738582611084s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.22309708595276s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.503488540649414s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.297034740447998s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.4386780261993408s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.65855264663696s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7112178802490234s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.4581143856048584s
Security | Sign check for Bio2RDF::Dbsnp took 0.27659177780151367s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 9.919792652130127s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.5054638385772705s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.021076202392578125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.295608520507812e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 13.368786334991455s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.5020370483398438e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1044.0701396465302s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.47803807258605957s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006253719329833984s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 18.8575439453125s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.252516746520996s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 45.28032946586609s
Interoperability | New terms check for Bio2RDF::Drugbank took 40.521910429000854s
Versatility | Languages check for Bio2RDF::Drugbank took 60.2467474937439s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.26375508308410645s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.14676856994628906s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.38730359077453613s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3398141860961914s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.357074737548828s
License | MR license check for Bio2RDF::Drugbank took 0.47196483612060547s
License | HR license check for Bio2RDF::Drugbank took 60.24883246421814s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2731001377105713s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.245146989822388s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5756309032440186s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.26579928398132324s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.26322174072265625s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2646493911743164s
Performance | Throughput check for Bio2RDF::Drugbank took 10.671462059020996s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 86.68625593185425s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.6197354793548584s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.36394667625427246s
Interlinking | skos check for Bio2RDF::Drugbank took 0.7789609432220459s
Interlinking | skos check for Bio2RDF::Drugbank took 0.3605690002441406s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2512855529785156s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5294568538665771s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5048785209655762s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 108.50142288208008s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 11.675258874893188s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4171326160430908s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.27838706970214844s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.26271533966064453s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 6.887571811676025s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.9103872776031494s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.7015738487243652s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.42766761779785156s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.67242407798767s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.4568979740142822s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 7.606689453125s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.4361438751220703s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.69015693664551s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7360806465148926s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.48017239570617676s
Security | Sign check for Bio2RDF::Drugbank took 0.2722315788269043s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 10.317227363586426s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.6156706809997559s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.021319150924682617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0008349418640136719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00012087821960449219s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 11.686729431152344s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1047.8474390506744s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 1.2603404521942139s
Availability | VoID file availability check for Bio2RDF::Genage took 0.000469207763671875s
Extra | Recovery of all triples for Bio2RDF::Genage took 19.48174214363098s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.3142271041870117s
Amount of data | Number of triples check for Bio2RDF::Genage took 45.51159620285034s
Interoperability | New terms check for Bio2RDF::Genage took 42.271669149398804s
Versatility | Languages check for Bio2RDF::Genage took 60.250200510025024s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2612133026123047s
Security | Check HTTPS for Bio2RDF::Genage took 0.15981125831604004s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.5281665325164795s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.30993032455444336s
Availability | RDF dump link check for Bio2RDF::Genage took 2.4272658824920654s
License | MR license check for Bio2RDF::Genage took 0.5636379718780518s
License | HR license check for Bio2RDF::Genage took 60.25828957557678s
Amount of data | Number of property check for Bio2RDF::Genage took 0.2714688777923584s
Understandability | Number of label check for Bio2RDF::Genage took 10.052548170089722s
Understandability | URI regex check for Bio2RDF::Genage took 0.5725555419921875s
Understandability | Vocabs check for Bio2RDF::Genage took 0.28177523612976074s
Verifiability | Authors check for Bio2RDF::Genage took 0.2603030204772949s
Verifiability | Publishers check for Bio2RDF::Genage took 0.26180410385131836s
Performance | Throughput check for Bio2RDF::Genage took 11.419995546340942s
Amount of data | Check the number of entities for Bio2RDF::Genage took 86.2652428150177s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.6142213344573975s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.35685157775878906s
Interlinking | skos check for Bio2RDF::Genage took 0.7821950912475586s
Interlinking | skos check for Bio2RDF::Genage took 0.3454151153564453s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2684450149536133s
Currency | Creation date check for Bio2RDF::Genage took 0.5106239318847656s
Currency | Modification date check for Bio2RDF::Genage took 0.5150296688079834s
Rep.Conc. | URIs length for Bio2RDF::Genage took 109.02380895614624s
Interoperability | New vocabularies check for Bio2RDF::Genage took 14.277620315551758s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4375448226928711s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.264193058013916s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.29483723640441895s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.4997992515563965s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.9068281650543213s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6876609325408936s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.40343165397644043s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.96999096870422s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.455059289932251s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.8196306228637695s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.4307713508605957s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.69285035133362s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7256402969360352s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.43393421173095703s
Security | Sign check for Bio2RDF::Genage took 0.28511619567871094s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 9.90491533279419s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.4862048625946045s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.021680355072021484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 13.518290519714355s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.4781951904296875e-05s
INFO | --- Analysis for bio2rdf-genage took 1055.196557044983s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.48259425163269043s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006508827209472656s
Extra | Recovery of all triples for Bio2RDF::Gendr took 19.10454273223877s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.3242216110229492s
Amount of data | Number of triples check for Bio2RDF::Gendr took 45.20194745063782s
Interoperability | New terms check for Bio2RDF::Gendr took 41.073731899261475s
Versatility | Languages check for Bio2RDF::Gendr took 60.24721145629883s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2811551094055176s
Security | Check HTTPS for Bio2RDF::Gendr took 0.1570267677307129s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.6640763282775879s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.32173967361450195s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.380051374435425s
License | MR license check for Bio2RDF::Gendr took 0.48839354515075684s
License | HR license check for Bio2RDF::Gendr took 60.24006247520447s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.27234792709350586s
Understandability | Number of label check for Bio2RDF::Gendr took 9.590751886367798s
Understandability | URI regex check for Bio2RDF::Gendr took 0.6071789264678955s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.25525593757629395s
Verifiability | Authors check for Bio2RDF::Gendr took 0.2527740001678467s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2721104621887207s
Performance | Throughput check for Bio2RDF::Gendr took 11.157479524612427s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 85.80987882614136s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.5692970752716064s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.3428840637207031s
Interlinking | skos check for Bio2RDF::Gendr took 0.7426931858062744s
Interlinking | skos check for Bio2RDF::Gendr took 0.356781005859375s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.26633167266845703s
Currency | Creation date check for Bio2RDF::Gendr took 0.5207619667053223s
Currency | Modification date check for Bio2RDF::Gendr took 0.5330100059509277s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 108.09308815002441s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 12.113136053085327s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.42860984802246094s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2987546920776367s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.27600646018981934s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.133873224258423s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.9007925987243652s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6850063800811768s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.39061880111694336s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.38678336143494s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.4491732120513916s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.882344484329224s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.4249382019042969s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.678508281707764s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7319631576538086s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.47074151039123535s
Security | Sign check for Bio2RDF::Gendr took 0.2735176086425781s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 11.213950395584106s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.3276188373565674s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02089238166809082s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 7.200241088867188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 12.94809889793396s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.4781951904296875e-05s
INFO | --- Analysis for bio2rdf-gendr took 1048.8960003852844s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.4799926280975342s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0007190704345703125s
Extra | Recovery of all triples for Bio2RDF::Goa took 18.545204162597656s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2770602703094482s
Amount of data | Number of triples check for Bio2RDF::Goa took 45.16283297538757s
Interoperability | New terms check for Bio2RDF::Goa took 40.27554535865784s
Versatility | Languages check for Bio2RDF::Goa took 60.24891114234924s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.26305556297302246s
Security | Check HTTPS for Bio2RDF::Goa took 0.16807246208190918s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.4276413917541504s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.3165428638458252s
Availability | RDF dump link check for Bio2RDF::Goa took 2.5011892318725586s
License | MR license check for Bio2RDF::Goa took 0.4931304454803467s
License | HR license check for Bio2RDF::Goa took 60.246084213256836s
Amount of data | Number of property check for Bio2RDF::Goa took 0.297576904296875s
Understandability | Number of label check for Bio2RDF::Goa took 9.93151330947876s
Understandability | URI regex check for Bio2RDF::Goa took 0.5706424713134766s
Understandability | Vocabs check for Bio2RDF::Goa took 0.26668787002563477s
Verifiability | Authors check for Bio2RDF::Goa took 0.28099632263183594s
Verifiability | Publishers check for Bio2RDF::Goa took 0.26014137268066406s
Performance | Throughput check for Bio2RDF::Goa took 10.665888786315918s
Amount of data | Check the number of entities for Bio2RDF::Goa took 88.1109344959259s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.5675206184387207s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3494126796722412s
Interlinking | skos check for Bio2RDF::Goa took 0.7279431819915771s
Interlinking | skos check for Bio2RDF::Goa took 0.37212300300598145s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.25040531158447266s
Currency | Creation date check for Bio2RDF::Goa took 0.5136382579803467s
Currency | Modification date check for Bio2RDF::Goa took 0.5407416820526123s
Rep.Conc. | URIs length for Bio2RDF::Goa took 109.73548173904419s
Interoperability | New vocabularies check for Bio2RDF::Goa took 11.370985507965088s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.45683717727661133s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.30182504653930664s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.27197718620300293s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.17926287651062s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.9094078540802002s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.7108192443847656s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4258749485015869s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.45697164535522s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.512176752090454s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.685851097106934s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.4202594757080078s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.66834044456482s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7510225772857666s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.4378695487976074s
Security | Sign check for Bio2RDF::Goa took 0.267622709274292s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 12.387391805648804s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.5189073085784912s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.021646976470947266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0009741783142089844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 7.987022399902344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 10.492251634597778s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-goa took 1055.9769878387451s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.4839754104614258s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006909370422363281s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 19.53534698486328s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2758851051330566s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 45.30666375160217s
Interoperability | New terms check for Bio2RDF::Hgnc took 40.76933789253235s
Versatility | Languages check for Bio2RDF::Hgnc took 60.23915386199951s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.27994251251220703s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.1575489044189453s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.647369384765625s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.3256711959838867s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.315429449081421s
License | MR license check for Bio2RDF::Hgnc took 0.4220468997955322s
License | HR license check for Bio2RDF::Hgnc took 60.256908655166626s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2739522457122803s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.621215343475342s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.58734130859375s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.280956506729126s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.3049001693725586s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.255415678024292s
Performance | Throughput check for Bio2RDF::Hgnc took 11.024128198623657s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 88.62093424797058s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.5953958034515381s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.35968565940856934s
Interlinking | skos check for Bio2RDF::Hgnc took 0.8138494491577148s
Interlinking | skos check for Bio2RDF::Hgnc took 0.33480286598205566s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.27446627616882324s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5488462448120117s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5131120681762695s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 111.01479029655457s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 13.82629108428955s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.4505035877227783s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2659323215484619s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2809321880340576s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.712802171707153s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.9049694538116455s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.7031614780426025s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4134864807128906s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.5986340045929s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.5366508960723877s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.549155235290527s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.4443233013153076s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.67126703262329s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7504234313964844s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4321131706237793s
Security | Sign check for Bio2RDF::Hgnc took 0.28882813453674316s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 10.49940538406372s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.6231861114501953s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.021136999130249023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00012350082397460938s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 13.957979202270508s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.5974044799804688e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1066.3364374637604s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.4784214496612549s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006124973297119141s
Extra | Recovery of all triples for Bio2RDF::Homologene took 19.5085768699646s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2881171703338623s
Amount of data | Number of triples check for Bio2RDF::Homologene took 46.664170265197754s
Interoperability | New terms check for Bio2RDF::Homologene took 42.63957333564758s
Versatility | Languages check for Bio2RDF::Homologene took 60.23891019821167s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.2784154415130615s
Security | Check HTTPS for Bio2RDF::Homologene took 0.14627695083618164s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.5510709285736084s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.3418910503387451s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.2170259952545166s
License | MR license check for Bio2RDF::Homologene took 0.50935959815979s
License | HR license check for Bio2RDF::Homologene took 60.24947738647461s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.2590498924255371s
Understandability | Number of label check for Bio2RDF::Homologene took 10.372075319290161s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5931739807128906s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.25154542922973633s
Verifiability | Authors check for Bio2RDF::Homologene took 0.26784825325012207s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.27358436584472656s
Performance | Throughput check for Bio2RDF::Homologene took 11.12221097946167s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 89.8927834033966s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.5907096862792969s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.3540334701538086s
Interlinking | skos check for Bio2RDF::Homologene took 0.736757755279541s
Interlinking | skos check for Bio2RDF::Homologene took 0.36106133460998535s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.26813292503356934s
Currency | Creation date check for Bio2RDF::Homologene took 0.4975757598876953s
Currency | Modification date check for Bio2RDF::Homologene took 0.5013377666473389s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 110.36822009086609s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 14.113835096359253s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4487628936767578s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2830815315246582s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.25850653648376465s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.398901462554932s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.9044091701507568s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.7040412425994873s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.4186224937438965s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.47049474716187s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.4827897548675537s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.34335994720459s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.424898624420166s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.69006967544556s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7567408084869385s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.41594767570495605s
Security | Sign check for Bio2RDF::Homologene took 0.2868659496307373s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 9.910788536071777s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.5146427154541016s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.841255187988281e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 15.362613201141357s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.4543533325195312e-05s
INFO | --- Analysis for bio2rdf-homologene took 1064.0496344566345s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.46851229667663574s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006513595581054688s
Extra | Recovery of all triples for Bio2RDF::Interpro took 19.891828060150146s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2509465217590332s
Amount of data | Number of triples check for Bio2RDF::Interpro took 45.37387800216675s
Interoperability | New terms check for Bio2RDF::Interpro took 42.23205780982971s
Versatility | Languages check for Bio2RDF::Interpro took 60.23943543434143s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2780909538269043s
Security | Check HTTPS for Bio2RDF::Interpro took 0.14390993118286133s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.5834536552429199s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.329359769821167s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.4084060192108154s
License | MR license check for Bio2RDF::Interpro took 0.5732583999633789s
License | HR license check for Bio2RDF::Interpro took 60.26156735420227s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2758326530456543s
Understandability | Number of label check for Bio2RDF::Interpro took 10.336302995681763s
Understandability | URI regex check for Bio2RDF::Interpro took 0.6111257076263428s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2834608554840088s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2507190704345703s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.27837705612182617s
Performance | Throughput check for Bio2RDF::Interpro took 11.161811828613281s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 88.8240966796875s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.720048189163208s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.37004876136779785s
Interlinking | skos check for Bio2RDF::Interpro took 0.7661521434783936s
Interlinking | skos check for Bio2RDF::Interpro took 0.359234094619751s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2730884552001953s
Currency | Creation date check for Bio2RDF::Interpro took 0.512305498123169s
Currency | Modification date check for Bio2RDF::Interpro took 0.5116527080535889s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 109.81142616271973s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 14.339778661727905s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.4291098117828369s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2816646099090576s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2766885757446289s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.644117116928101s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.9039065837860107s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.7071702480316162s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.36417365074157715s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.53361964225769s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.511397361755371s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.45502233505249s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.448782205581665s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.65782046318054s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7479231357574463s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.43735551834106445s
Security | Sign check for Bio2RDF::Interpro took 0.2795228958129883s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 11.178640842437744s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.3469548225402832s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.021239042282104492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010371208190917969s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 14.358255386352539s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-interpro took 1062.7377092838287s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.1333773136138916s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.44464540481567383s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02129054069519043s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 9.250640869140625e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-iproclass took 16.748446464538574s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.4955618381500244s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006780624389648438s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 19.2139790058136s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.202610969543457s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 44.88905668258667s
Interoperability | New terms check for Bio2RDF::Irefindex took 43.10124182701111s
Versatility | Languages check for Bio2RDF::Irefindex took 60.25481057167053s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.25200581550598145s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.15575551986694336s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.6197588443756104s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.33681702613830566s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.31449818611145s
License | MR license check for Bio2RDF::Irefindex took 0.4232649803161621s
License | HR license check for Bio2RDF::Irefindex took 60.25247001647949s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2615182399749756s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.76767086982727s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.617668867111206s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.26022911071777344s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.24318265914916992s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2590773105621338s
Performance | Throughput check for Bio2RDF::Irefindex took 11.086634874343872s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 87.28950548171997s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6123225688934326s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3577578067779541s
Interlinking | skos check for Bio2RDF::Irefindex took 0.7859454154968262s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3418238162994385s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2650730609893799s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5247697830200195s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5239241123199463s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 109.69805717468262s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 12.846988439559937s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.4317972660064697s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2521185874938965s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.27507519721984863s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.650941371917725s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.90346360206604s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6840050220489502s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.41635870933532715s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.06475377082825s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.4455831050872803s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 7.06496000289917s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.4377567768096924s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.67610502243042s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7087123394012451s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.447127103805542s
Security | Sign check for Bio2RDF::Irefindex took 0.27706432342529297s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 9.545667886734009s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.4755556583404541s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02095794677734375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.440017700195312e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 15.550846338272095s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.52587890625e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1053.7818377017975s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.1415419578552246s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.31412649154663086s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.314018249511719e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 9.692298889160156s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.46735095977783203s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0006239414215087891s
Extra | Recovery of all triples for Bio2RDF::Lsr took 18.96161437034607s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2877070903778076s
Amount of data | Number of triples check for Bio2RDF::Lsr took 45.888566970825195s
Interoperability | New terms check for Bio2RDF::Lsr took 41.643943548202515s
Versatility | Languages check for Bio2RDF::Lsr took 60.25922918319702s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.26801538467407227s
Security | Check HTTPS for Bio2RDF::Lsr took 0.17081117630004883s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.6299822330474854s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3584444522857666s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.190768241882324s
License | MR license check for Bio2RDF::Lsr took 0.4377577304840088s
License | HR license check for Bio2RDF::Lsr took 60.26623821258545s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2655634880065918s
Understandability | Number of label check for Bio2RDF::Lsr took 10.184535264968872s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5535740852355957s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.25389647483825684s
Verifiability | Authors check for Bio2RDF::Lsr took 0.26873016357421875s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.2763187885284424s
Performance | Throughput check for Bio2RDF::Lsr took 11.28040361404419s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 84.42268824577332s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.5932083129882812s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3570890426635742s
Interlinking | skos check for Bio2RDF::Lsr took 0.7673578262329102s
Interlinking | skos check for Bio2RDF::Lsr took 0.3497278690338135s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.27390050888061523s
Currency | Creation date check for Bio2RDF::Lsr took 0.543647289276123s
Currency | Modification date check for Bio2RDF::Lsr took 0.5259439945220947s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 109.07290959358215s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 13.886608362197876s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.438892126083374s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.25891613960266113s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2927556037902832s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.356242418289185s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.9092667102813721s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.7027883529663086s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.28913354873657227s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.10445809364319s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.4826011657714844s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.73013973236084s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.4402289390563965s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.70344018936157s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7522571086883545s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.4606654644012451s
Security | Sign check for Bio2RDF::Lsr took 0.28367018699645996s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 10.459216833114624s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.6213252544403076s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02126598358154297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.078315734863281e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 13.896891593933105s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.4781951904296875e-05s
INFO | --- Analysis for bio2rdf-lsr took 1053.614202260971s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.4969053268432617s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0012993812561035156s
Extra | Recovery of all triples for Bio2RDF::Mesh took 20.709668397903442s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2736289501190186s
Amount of data | Number of triples check for Bio2RDF::Mesh took 45.872668743133545s
Interoperability | New terms check for Bio2RDF::Mesh took 43.99058961868286s
Versatility | Languages check for Bio2RDF::Mesh took 60.26328110694885s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.27179503440856934s
Security | Check HTTPS for Bio2RDF::Mesh took 0.14545416831970215s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.8337385654449463s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.31606292724609375s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.250688314437866s
License | MR license check for Bio2RDF::Mesh took 0.5387957096099854s
License | HR license check for Bio2RDF::Mesh took 60.26096034049988s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2662668228149414s
Understandability | Number of label check for Bio2RDF::Mesh took 9.967674970626831s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5631275177001953s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.2570209503173828s
Verifiability | Authors check for Bio2RDF::Mesh took 0.2747645378112793s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.262775182723999s
Performance | Throughput check for Bio2RDF::Mesh took 11.044180154800415s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 84.341468334198s
Verifiability | Contribs. check for Bio2RDF::Mesh took 1.4106147289276123s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.35506296157836914s
Interlinking | skos check for Bio2RDF::Mesh took 0.796668291091919s
Interlinking | skos check for Bio2RDF::Mesh took 0.35376954078674316s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.2819666862487793s
Currency | Creation date check for Bio2RDF::Mesh took 0.5237569808959961s
Currency | Modification date check for Bio2RDF::Mesh took 0.5574262142181396s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 109.11547470092773s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 14.293201923370361s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.7002921104431152s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.27115559577941895s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2851235866546631s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.304924964904785s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.9034779071807861s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6871049404144287s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.3959219455718994s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.42092108726501s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.4876277446746826s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.526001214981079s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.4309935569763184s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.7039155960083s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7066371440887451s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.4339473247528076s
Security | Sign check for Bio2RDF::Mesh took 0.2830972671508789s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 9.917948246002197s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.5075645446777344s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020997047424316406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 8.344650268554688e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 14.159053564071655s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-mesh took 1059.1406013965607s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.5033724308013916s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006048679351806641s
Extra | Recovery of all triples for Bio2RDF::Mgi took 19.69181489944458s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.320882797241211s
Amount of data | Number of triples check for Bio2RDF::Mgi took 45.57431674003601s
Interoperability | New terms check for Bio2RDF::Mgi took 40.85474181175232s
Versatility | Languages check for Bio2RDF::Mgi took 60.270313024520874s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.2588791847229004s
Security | Check HTTPS for Bio2RDF::Mgi took 0.15641474723815918s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.450439453125s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.33068394660949707s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.366917610168457s
License | MR license check for Bio2RDF::Mgi took 0.43491363525390625s
License | HR license check for Bio2RDF::Mgi took 60.25926065444946s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.2739903926849365s
Understandability | Number of label check for Bio2RDF::Mgi took 9.400669574737549s
Understandability | URI regex check for Bio2RDF::Mgi took 0.6091828346252441s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.2563037872314453s
Verifiability | Authors check for Bio2RDF::Mgi took 0.27071189880371094s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.24883031845092773s
Performance | Throughput check for Bio2RDF::Mgi took 10.59329891204834s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 88.00660157203674s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.6050164699554443s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.38297224044799805s
Interlinking | skos check for Bio2RDF::Mgi took 0.9264187812805176s
Interlinking | skos check for Bio2RDF::Mgi took 0.3677408695220947s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.269010066986084s
Currency | Creation date check for Bio2RDF::Mgi took 0.5317318439483643s
Currency | Modification date check for Bio2RDF::Mgi took 0.5104706287384033s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 110.58793091773987s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 14.037841081619263s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.4292259216308594s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2909843921661377s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2967979907989502s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.058782577514648s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.9041554927825928s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.7073562145233154s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.4080948829650879s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.31720542907715s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4978134632110596s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.300906419754028s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.4247362613677979s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.65403938293457s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7393407821655273s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.4082036018371582s
Security | Sign check for Bio2RDF::Mgi took 0.2905144691467285s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 11.260713338851929s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.4076845645904541s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.021010637283325195s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 0.000102996826171875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 13.906962871551514s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-mgi took 1061.103238582611s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.48041868209838867s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0007150173187255859s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 19.11046028137207s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2739968299865723s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 46.27744245529175s
Interoperability | New terms check for Bio2RDF::Ncbigene took 42.71398615837097s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.247472524642944s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2817037105560303s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.15742850303649902s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.3537163734436035s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3177525997161865s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.272494077682495s
License | MR license check for Bio2RDF::Ncbigene took 0.5609579086303711s
License | HR license check for Bio2RDF::Ncbigene took 60.23160743713379s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.25391149520874023s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.72753357887268s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.597374439239502s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.260988712310791s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2706925868988037s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2453911304473877s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.288292646408081s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 86.80798530578613s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.6252033710479736s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3564903736114502s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.7029845714569092s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3488149642944336s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.26834869384765625s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5107035636901855s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5107736587524414s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 109.34289503097534s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 13.570261001586914s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4048142433166504s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2733793258666992s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.2807283401489258s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.172529220581055s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.9053919315338135s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6853222846984863s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.4582970142364502s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.65559697151184s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.528197765350342s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.20147967338562s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.4286837577819824s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.70482516288757s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.732649564743042s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.4592399597167969s
Security | Sign check for Bio2RDF::Ncbigene took 0.26398396492004395s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 9.688157081604004s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.42763805389404297s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.02091240882873535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012826919555664062s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 13.502544403076172s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.811981201171875e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1056.522362947464s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.48456907272338867s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0007374286651611328s
Extra | Recovery of all triples for Bio2RDF::Ndc took 19.57152557373047s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2953567504882812s
Amount of data | Number of triples check for Bio2RDF::Ndc took 45.71389555931091s
Interoperability | New terms check for Bio2RDF::Ndc took 41.11963081359863s
Versatility | Languages check for Bio2RDF::Ndc took 60.24873924255371s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2763793468475342s
Security | Check HTTPS for Bio2RDF::Ndc took 0.1593315601348877s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.7958576679229736s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.330125093460083s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.375460386276245s
License | MR license check for Bio2RDF::Ndc took 0.4993767738342285s
License | HR license check for Bio2RDF::Ndc took 60.242934465408325s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.44068336486816406s
Understandability | Number of label check for Bio2RDF::Ndc took 10.062156200408936s
Understandability | URI regex check for Bio2RDF::Ndc took 0.6791036128997803s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2681565284729004s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2798020839691162s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.271899938583374s
Performance | Throughput check for Bio2RDF::Ndc took 10.824388027191162s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 88.12859749794006s
Verifiability | Contribs. check for Bio2RDF::Ndc took 2.17598032951355s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.3658273220062256s
Interlinking | skos check for Bio2RDF::Ndc took 0.7590689659118652s
Interlinking | skos check for Bio2RDF::Ndc took 0.34961819648742676s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.28452277183532715s
Currency | Creation date check for Bio2RDF::Ndc took 0.534949541091919s
Currency | Modification date check for Bio2RDF::Ndc took 0.5199713706970215s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 111.96687006950378s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 13.786173582077026s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.452103853225708s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2749919891357422s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2711493968963623s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.805455684661865s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8981564044952393s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6981313228607178s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.3970048427581787s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.51488971710205s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.504645347595215s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.506079912185669s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.439619541168213s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.69362926483154s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7514729499816895s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.4492526054382324s
Security | Sign check for Bio2RDF::Ndc took 0.26763367652893066s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 10.391594409942627s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.5844833850860596s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 14.69365668296814s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.5735626220703125e-05s
INFO | --- Analysis for bio2rdf-ndc took 1063.5586981773376s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.15974807739257812s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.28893542289733887s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02099776268005371s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.695487976074219e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.4781951904296875e-05s
INFO | --- Analysis for bio2rdf-nextprot took 3.6558408737182617s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.4750337600708008s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0007696151733398438s
Extra | Recovery of all triples for Bio2RDF::Omim took 20.010523557662964s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2607944011688232s
Amount of data | Number of triples check for Bio2RDF::Omim took 46.254804611206055s
Interoperability | New terms check for Bio2RDF::Omim took 42.90248703956604s
Versatility | Languages check for Bio2RDF::Omim took 60.261035442352295s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2685697078704834s
Security | Check HTTPS for Bio2RDF::Omim took 0.16808295249938965s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.5975568294525146s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.33907032012939453s
Availability | RDF dump link check for Bio2RDF::Omim took 2.253666639328003s
License | MR license check for Bio2RDF::Omim took 0.4953014850616455s
License | HR license check for Bio2RDF::Omim took 60.252652406692505s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2749602794647217s
Understandability | Number of label check for Bio2RDF::Omim took 9.966249465942383s
Understandability | URI regex check for Bio2RDF::Omim took 0.5967926979064941s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2694122791290283s
Verifiability | Authors check for Bio2RDF::Omim took 0.261472225189209s
Verifiability | Publishers check for Bio2RDF::Omim took 0.2619354724884033s
Performance | Throughput check for Bio2RDF::Omim took 10.860952377319336s
Amount of data | Check the number of entities for Bio2RDF::Omim took 83.9390881061554s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.6056694984436035s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3481740951538086s
Interlinking | skos check for Bio2RDF::Omim took 0.7221949100494385s
Interlinking | skos check for Bio2RDF::Omim took 0.3661487102508545s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.25414013862609863s
Currency | Creation date check for Bio2RDF::Omim took 0.509824275970459s
Currency | Modification date check for Bio2RDF::Omim took 0.49756407737731934s
Rep.Conc. | URIs length for Bio2RDF::Omim took 107.35544061660767s
Interoperability | New vocabularies check for Bio2RDF::Omim took 14.854600429534912s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4284539222717285s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.26653313636779785s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.248213529586792s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 7.058716535568237s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.9014451503753662s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6862163543701172s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.3922717571258545s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.70469975471497s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.5044291019439697s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.453044652938843s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.4301626682281494s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.67777729034424s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.722661018371582s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.43854236602783203s
Security | Sign check for Bio2RDF::Omim took 0.28203725814819336s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 9.914470195770264s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.49043703079223633s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.021085023880004883s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0008456707000732422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.0001442432403564453s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 13.476029396057129s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-omim took 1046.5648713111877s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 9.036064147949219e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.3186323642730713s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.100799560546875e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.4781951904296875e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 3.0283849239349365s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.4685213565826416s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0006296634674072266s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.399545192718506s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2763645648956299s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 46.035415172576904s
Interoperability | New terms check for Bio2RDF::Orphanet took 44.72369980812073s
Versatility | Languages check for Bio2RDF::Orphanet took 60.25644564628601s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.27072691917419434s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.15718793869018555s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.5426883697509766s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.31316542625427246s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.2374391555786133s
License | MR license check for Bio2RDF::Orphanet took 0.6171159744262695s
License | HR license check for Bio2RDF::Orphanet took 60.25743246078491s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.27469563484191895s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.755533456802368s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.6051158905029297s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.2557816505432129s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.24443650245666504s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.253009557723999s
Performance | Throughput check for Bio2RDF::Orphanet took 11.088591575622559s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 85.11666655540466s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.7481405735015869s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.33475685119628906s
Interlinking | skos check for Bio2RDF::Orphanet took 0.70865797996521s
Interlinking | skos check for Bio2RDF::Orphanet took 0.33158254623413086s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.26157689094543457s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5176596641540527s
Currency | Modification date check for Bio2RDF::Orphanet took 0.49599123001098633s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 111.36138224601746s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 59.78731679916382s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.39639735221862793s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2606840133666992s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.25841617584228516s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.509257555007935s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8993217945098877s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6908652782440186s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.3926849365234375s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.10158610343933s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.4280710220336914s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.449732065200806s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.437385082244873s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.671388149261475s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7224352359771729s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.6714417934417725s
Security | Sign check for Bio2RDF::Orphanet took 0.26976919174194336s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 11.069276809692383s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.37066006660461426s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02095961570739746s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.916854858398438e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 30.898132801055908s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1118.7338917255402s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.13565945625305176s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.2830212116241455s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.8623809814453125e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.041514158248901s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.4517545700073242s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0006256103515625s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 18.75476598739624s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.1668601036071777s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 45.59000539779663s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 41.45568346977234s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.23448705673218s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.26045727729797363s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.1486964225769043s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.5073299407958984s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.37993550300598145s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 1.9574310779571533s
License | MR license check for Bio2RDF::Pharmgkb took 0.4722123146057129s
License | HR license check for Bio2RDF::Pharmgkb took 60.2312753200531s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.3544197082519531s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.173532962799072s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5462331771850586s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.2511413097381592s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.25304174423217773s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.2457871437072754s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.6275794506073s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 84.95934009552002s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.5424079895019531s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.3880283832550049s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.7607705593109131s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.3273742198944092s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2504541873931885s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.4795246124267578s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.4760873317718506s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 108.16700315475464s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 56.341421604156494s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.39904117584228516s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.26262354850769043s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.2512550354003906s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.651798486709595s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.9132528305053711s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.7044715881347656s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.381289005279541s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.86587452888489s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4844069480895996s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.900853157043457s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.435481309890747s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.65579438209534s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7273051738739014s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.5754261016845703s
Security | Sign check for Bio2RDF::Pharmgkb took 0.26253414154052734s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 23.870136737823486s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.4046785831451416s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020824432373046875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.605552673339844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 12.860091924667358s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.4781951904296875e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1102.2272534370422s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.45021820068359375s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0006940364837646484s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 19.184930562973022s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.1597890853881836s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 45.937761306762695s
Interoperability | New terms check for Bio2RDF::Pubmed took 40.81545400619507s
Versatility | Languages check for Bio2RDF::Pubmed took 60.252063035964966s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2679622173309326s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.14560818672180176s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.37067174911499023s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.3068673610687256s
Availability | RDF dump link check for Bio2RDF::Pubmed took 1.9003775119781494s
License | MR license check for Bio2RDF::Pubmed took 0.48372626304626465s
License | HR license check for Bio2RDF::Pubmed took 60.23346209526062s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.24944448471069336s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.831422567367554s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5439267158508301s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.23887085914611816s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.24495792388916016s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.24154257774353027s
Performance | Throughput check for Bio2RDF::Pubmed took 11.662750482559204s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 86.92105793952942s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.5669877529144287s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.25507545471191406s
Interlinking | skos check for Bio2RDF::Pubmed took 0.9484870433807373s
Interlinking | skos check for Bio2RDF::Pubmed took 0.33373546600341797s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2435150146484375s
Currency | Creation date check for Bio2RDF::Pubmed took 0.47838521003723145s
Currency | Modification date check for Bio2RDF::Pubmed took 0.48110055923461914s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 111.24129128456116s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 12.930065393447876s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.3986191749572754s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.26262807846069336s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2680389881134033s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.012052059173584s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.9038746356964111s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6936357021331787s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.4234476089477539s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.50694060325623s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.4706764221191406s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.347248315811157s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.4474773406982422s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.67204189300537s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7126548290252686s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.4276711940765381s
Security | Sign check for Bio2RDF::Pubmed took 0.2722318172454834s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 19.48642373085022s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.5251514911651611s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.021149873733520508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00013828277587890625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 12.704467058181763s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.0251998901367188e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1053.0974702835083s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.13553380966186523s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.262897253036499s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.021349191665649414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 8.678436279296875e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.4781951904296875e-05s
INFO | --- Analysis for bio2rdf-sabiork took 8.63916563987732s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.44669365882873535s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0005812644958496094s
Extra | Recovery of all triples for Bio2RDF::Sgd took 19.046679973602295s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.1818699836730957s
Amount of data | Number of triples check for Bio2RDF::Sgd took 45.125805377960205s
Interoperability | New terms check for Bio2RDF::Sgd took 42.09680771827698s
Versatility | Languages check for Bio2RDF::Sgd took 60.23304271697998s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.2537727355957031s
Security | Check HTTPS for Bio2RDF::Sgd took 0.14621901512145996s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.5021622180938721s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.3024015426635742s
Availability | RDF dump link check for Bio2RDF::Sgd took 1.8235454559326172s
License | MR license check for Bio2RDF::Sgd took 0.46100950241088867s
License | HR license check for Bio2RDF::Sgd took 60.229886054992676s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.25154542922973633s
Understandability | Number of label check for Bio2RDF::Sgd took 9.935627937316895s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5426623821258545s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.24120831489562988s
Verifiability | Authors check for Bio2RDF::Sgd took 0.24670743942260742s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.23865509033203125s
Performance | Throughput check for Bio2RDF::Sgd took 11.532912254333496s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 86.47775721549988s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.5757529735565186s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3374056816101074s
Interlinking | skos check for Bio2RDF::Sgd took 0.7613821029663086s
Interlinking | skos check for Bio2RDF::Sgd took 0.33634352684020996s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.24605369567871094s
Currency | Creation date check for Bio2RDF::Sgd took 0.4744114875793457s
Currency | Modification date check for Bio2RDF::Sgd took 0.4842696189880371s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 109.86269855499268s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 12.759329795837402s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.39870285987854004s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2615242004394531s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2578926086425781s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.978407621383667s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.9028658866882324s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.697221040725708s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.29009580612182617s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 64.85486912727356s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.4397780895233154s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.927521228790283s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.4477295875549316s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.67895245552063s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7275419235229492s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.40727686882019043s
Security | Sign check for Bio2RDF::Sgd took 0.2481062412261963s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 9.578892469406128s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.44502997398376465s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020976781845092773s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0008249282836914062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011968612670898438s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 13.408584117889404s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.5020370483398438e-05s
INFO | --- Analysis for bio2rdf-sgd took 1043.7321648597717s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 6.461143493652344e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.25983166694641113s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.981590270996094e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 2.7825846672058105s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.4463231563568115s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0005202293395996094s
Extra | Recovery of all triples for Bio2RDF::Sider took 18.973902225494385s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.1813256740570068s
Amount of data | Number of triples check for Bio2RDF::Sider took 45.10904359817505s
Interoperability | New terms check for Bio2RDF::Sider took 40.90636873245239s
Versatility | Languages check for Bio2RDF::Sider took 60.23187017440796s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.24954748153686523s
Security | Check HTTPS for Bio2RDF::Sider took 0.1471855640411377s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.5826380252838135s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3458254337310791s
Availability | RDF dump link check for Bio2RDF::Sider took 1.9003045558929443s
License | MR license check for Bio2RDF::Sider took 0.48709845542907715s
License | HR license check for Bio2RDF::Sider took 60.23359036445618s
Amount of data | Number of property check for Bio2RDF::Sider took 0.24443960189819336s
Understandability | Number of label check for Bio2RDF::Sider took 10.077052354812622s
Understandability | URI regex check for Bio2RDF::Sider took 0.5425760746002197s
Understandability | Vocabs check for Bio2RDF::Sider took 0.23810815811157227s
Verifiability | Authors check for Bio2RDF::Sider took 0.24498939514160156s
Verifiability | Publishers check for Bio2RDF::Sider took 0.24164795875549316s
Performance | Throughput check for Bio2RDF::Sider took 11.700571775436401s
Amount of data | Check the number of entities for Bio2RDF::Sider took 84.79183530807495s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.5644309520721436s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.25498485565185547s
Interlinking | skos check for Bio2RDF::Sider took 0.7511224746704102s
Interlinking | skos check for Bio2RDF::Sider took 0.33144092559814453s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.24920129776000977s
Currency | Creation date check for Bio2RDF::Sider took 0.4805796146392822s
Currency | Modification date check for Bio2RDF::Sider took 0.4745199680328369s
Rep.Conc. | URIs length for Bio2RDF::Sider took 107.69050717353821s
Interoperability | New vocabularies check for Bio2RDF::Sider took 11.53819751739502s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.39653468132019043s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.26640844345092773s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.23523974418640137s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.475656747817993s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.9028027057647705s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6841168403625488s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.3787350654602051s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.43421769142151s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.4623818397521973s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.757399559020996s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.4474754333496094s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.67176270484924s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7130975723266602s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.41767001152038574s
Security | Sign check for Bio2RDF::Sider took 0.25223445892333984s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 11.101417779922485s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.3057441711425781s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.021088123321533203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 12.538691282272339s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-sider took 1042.6146748065948s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 9.1552734375e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.2777984142303467s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020328998565673828s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 5.1975250244140625e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-taxon took 2.735300302505493s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.4451792240142822s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006234645843505859s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.77943706512451s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.17020583152771s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 47.970662117004395s
Interoperability | New terms check for Bio2RDF::Taxonomy took 42.44894456863403s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.22986674308777s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2536935806274414s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.14902162551879883s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.6206533908843994s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.30040907859802246s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 1.9352476596832275s
License | MR license check for Bio2RDF::Taxonomy took 0.5775618553161621s
License | HR license check for Bio2RDF::Taxonomy took 60.22908639907837s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.24486303329467773s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.618557691574097s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5423295497894287s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2339944839477539s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.24456787109375s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.24178218841552734s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.672398805618286s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 84.75861477851868s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.5730130672454834s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.3509480953216553s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.9100759029388428s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.3323221206665039s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.24791669845581055s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.48375535011291504s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.4810519218444824s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 109.34334182739258s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 12.235426187515259s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4051845073699951s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2587258815765381s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.26435422897338867s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.769079208374023s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.9084274768829346s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.7015383243560791s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.4094245433807373s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.63499975204468s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.4549694061279297s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.636393308639526s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.4528393745422363s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.66722083091736s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.742913007736206s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.409104585647583s
Security | Sign check for Bio2RDF::Taxonomy took 0.2519419193267822s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 9.650926351547241s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.4546208381652832s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.021300792694091797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00011754035949707031s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 12.635668754577637s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1051.4191296100616s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.1358025074005127s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.2750673294067383s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 4.458427429199219e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 15.859804391860962s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.4478020668029785s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006470680236816406s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 19.44078826904297s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.160438060760498s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.674147605895996s
Interoperability | New terms check for Bio2RDF::Wormbase took 42.84379768371582s
Versatility | Languages check for Bio2RDF::Wormbase took 60.23056125640869s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.25336122512817383s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.14781498908996582s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.40837860107421875s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.32082414627075195s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.019397497177124s
License | MR license check for Bio2RDF::Wormbase took 0.5166542530059814s
License | HR license check for Bio2RDF::Wormbase took 60.23391914367676s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.2395765781402588s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.551373958587646s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5455977916717529s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.24017715454101562s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.24726057052612305s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.24173283576965332s
Performance | Throughput check for Bio2RDF::Wormbase took 11.715630769729614s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 84.47973728179932s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.5657370090484619s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.3468503952026367s
Interlinking | skos check for Bio2RDF::Wormbase took 0.8015997409820557s
Interlinking | skos check for Bio2RDF::Wormbase took 0.33544230461120605s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.2514634132385254s
Currency | Creation date check for Bio2RDF::Wormbase took 0.4804365634918213s
Currency | Modification date check for Bio2RDF::Wormbase took 0.47510528564453125s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 110.03340125083923s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 14.060264587402344s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.4017188549041748s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2674899101257324s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2636094093322754s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.774454593658447s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.9052622318267822s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6851625442504883s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.41533565521240234s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.09023356437683s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.466421127319336s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.399559497833252s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.4417529106140137s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.689260482788086s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7132411003112793s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.406207799911499s
Security | Sign check for Bio2RDF::Wormbase took 0.2682368755340576s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 9.964696407318115s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.4718897342681885s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.021062612533569336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.511543273925781e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 13.579918146133423s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.4543533325195312e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1047.7200908660889s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.24109411239624023s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.2783236503601074s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.869171142578125e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 9.298324584960938e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 2.711077928543091s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.649162292480469e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.26892614364624023s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0008289813995361328s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.601478576660156e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.430511474609375e-05s
INFO | --- Analysis for biolod-pdb took 7.215334415435791s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.5624194145202637s
Availability | VoID file availability check for BioModels RDF took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.27217817306518555s
Reputation | Calculation of the PageRank for BioModels RDF took 0.02090620994567871s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.410743713378906e-05s
Believability | Calculation of trust value for BioModels RDF took 1.4781951904296875e-05s
INFO | --- Analysis for biomodels-rdf took 3.6668174266815186s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.818695306777954s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007610321044921875s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2753574848175049s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020827531814575195s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.719329833984375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.3589859008789062e-05s
INFO | --- Analysis for Biop took 5.6132354736328125s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.410743713378906e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.26430654525756836s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02075052261352539s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.601478576660156e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.3828277587890625e-05s
INFO | --- Analysis for Bioportal took 2.5592734813690186s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.553794860839844e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2778773307800293s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020880460739135742s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006442070007324219s
Believability | Calculation of trust value for Amphibian gross anatomy took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-aao took 4.641807556152344s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 0.00010967254638671875s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.27462196350097656s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020780086517333984s
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.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00033354759216308594s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-aba took 4.104915380477905s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0007352828979492188s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.28234291076660156s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015785694122314453s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-acgt took 4.267715930938721s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.5299530029296875e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0007364749908447266s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.27443432807922363s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.021708011627197266s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.000362396240234375s
Believability | Calculation of trust value for Animal natural history and life history took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-adw took 4.024106979370117s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.2576594352722168s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004911422729492188s
Believability | Calculation of trust value for Anatomical Entity Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-aeo took 4.003544092178345s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.001379251480102539s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.27315664291381836s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.021181583404541016s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.001007080078125s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-aero took 3.9071762561798096s
Availability | SPARQL endpoint availability check for AI/RHEUM took 9.202957153320312e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.2785007953643799s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.021348237991333008s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004372596740722656s
Believability | Calculation of trust value for AI/RHEUM took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-air took 4.001288175582886s
Availability | SPARQL endpoint availability check for Amino Acid took 0.00019550323486328125s
Availability | VoID file availability check for Amino Acid took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.276961088180542s
Reputation | Calculation of the PageRank for Amino Acid took 0.020644187927246094s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002760887145996094s
Believability | Calculation of trust value for Amino Acid took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-amino-acid took 3.906080722808838s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.26517343521118164s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.02081775665283203s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002956390380859375s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-apo took 4.00629997253418s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 8.916854858398438e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2681872844696045s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020747900009155273s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00024008750915527344s
Believability | Calculation of trust value for African Traditional Medicine took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-atmo took 4.102184772491455s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.410743713378906e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2693650722503662s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020711421966552734s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.202957153320312e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ato took 4.006091356277466s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.27731776237487793s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013082027435302734s
Believability | Calculation of trust value for BioAssay Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bao took 4.25368857383728s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 5.626678466796875e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.26793670654296875s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0004029273986816406s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 4.171899795532227s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0007104873657226562s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.28172922134399414s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02111220359802246s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.00033473968505859375s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bcgo took 4.013257741928101s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.2781710624694824s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.02099013328552246s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014650821685791016s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-bdo took 4.033869028091431s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 5.888938903808594e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.25934553146362305s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.021009445190429688s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005123615264892578s
Believability | Calculation of trust value for Basic Formal Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-bfo took 3.8806941509246826s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.38690185546875e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.26630163192749023s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007734298706054688s
Believability | Calculation of trust value for Bleeding History Phenotype took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-bho took 3.8747599124908447s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.2743830680847168s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004553794860839844s
Believability | Calculation of trust value for Bilateria anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-bila took 4.054831266403198s
Availability | SPARQL endpoint availability check for BIRNLex took 4.696846008300781e-05s
Availability | VoID file availability check for BIRNLex took 0.0007870197296142578s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.2696199417114258s
Reputation | Calculation of the PageRank for BIRNLex took 0.02150750160217285s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014994144439697266s
Believability | Calculation of trust value for BIRNLex took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-birnlex took 4.02121639251709s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.863739013671875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.26749634742736816s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020854711532592773s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007524490356445312s
Believability | Calculation of trust value for Gene Regulation Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-bootstrep took 4.0412681102752686s
Availability | SPARQL endpoint availability check for BioPAX took 6.198883056640625e-05s
Availability | VoID file availability check for BioPAX took 0.00042319297790527344s
Completeness | Calculation of interlinking completeness for BioPAX took 0.27562952041625977s
Reputation | Calculation of the PageRank for BioPAX took 0.021019458770751953s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00011396408081054688s
Believability | Calculation of trust value for BioPAX took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bp took 3.907209873199463s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0008213520050048828s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.26523923873901367s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.00033283233642578125s
Believability | Calculation of trust value for Biomedical Resource Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 3.9005417823791504s
Availability | SPARQL endpoint availability check for Spatial Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0007777214050292969s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.27794599533081055s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.02106475830078125s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00023674964904785156s
Believability | Calculation of trust value for Spatial Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-bspo took 3.840945243835449s
Availability | SPARQL endpoint availability check for BioTop took 9.393692016601562e-05s
Availability | VoID file availability check for BioTop took 0.0007805824279785156s
Completeness | Calculation of interlinking completeness for BioTop took 0.275606632232666s
Reputation | Calculation of the PageRank for BioTop took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for BioTop took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.00066375732421875s
Believability | Calculation of trust value for BioTop took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-bt took 4.167577266693115s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 0.00010180473327636719s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.26940321922302246s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020717620849609375s
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.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0009303092956542969s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bto took 3.9119338989257812s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 0.00013208389282226562s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3130607604980469s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020961999893188477s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018587112426757812s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-canco took 4.433776140213013s
Availability | SPARQL endpoint availability check for CAO took 9.322166442871094e-05s
Availability | VoID file availability check for CAO took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for CAO took 0.2762434482574463s
Reputation | Calculation of the PageRank for CAO took 0.021334409713745117s
Interlinking | Calculation of Degree of Connection for CAO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006120204925537109s
Believability | Calculation of trust value for CAO took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-cao took 3.8548221588134766s
Availability | SPARQL endpoint availability check for CareLex took 9.179115295410156e-05s
Availability | VoID file availability check for CareLex took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for CareLex took 0.2641134262084961s
Reputation | Calculation of the PageRank for CareLex took 0.021134614944458008s
Interlinking | Calculation of Degree of Connection for CareLex took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.8650970458984375e-05s
Believability | Calculation of trust value for CareLex took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-carelex took 3.891934871673584s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 5.173683166503906e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2771596908569336s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02090930938720703s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008301734924316406s
Believability | Calculation of trust value for Cell Cycle Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-cco took 3.7823703289031982s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.26555967330932617s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002658367156982422s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-cdao took 4.000191688537598s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 0.00011134147644042969s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0007472038269042969s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2682344913482666s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020991086959838867s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008127689361572266s
Believability | Calculation of trust value for Chemical entities of biological interest took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-chebi took 3.981464385986328s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 8.821487426757812e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.2648196220397949s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002791881561279297s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-chem2bio2owl took 4.025311470031738s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 9.393692016601562e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.26761937141418457s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02109694480895996s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007982254028320312s
Believability | Calculation of trust value for Chemical Information Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-cheminf took 3.83717942237854s
Availability | SPARQL endpoint availability check for Cell type took 0.00012493133544921875s
Availability | VoID file availability check for Cell type took 0.0007600784301757812s
Completeness | Calculation of interlinking completeness for Cell type took 0.2658257484436035s
Reputation | Calculation of the PageRank for Cell type took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for Cell type took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.000392913818359375s
Believability | Calculation of trust value for Cell type took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cl took 3.8136236667633057s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.2769463062286377s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.021398067474365234s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0010783672332763672s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0009448528289794922s
Believability | Calculation of trust value for Cell Line Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-clo took 5.054847478866577s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2671964168548584s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.021269559860229492s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0009396076202392578s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00022077560424804688s
Believability | Calculation of trust value for Clinical Measurement Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-cmo took 3.963601589202881s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.27350950241088867s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.022104740142822266s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002224445343017578s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-cno took 3.899667739868164s
Availability | SPARQL endpoint availability check for Wheat trait took 9.012222290039062e-05s
Availability | VoID file availability check for Wheat trait took 0.0008409023284912109s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.27368736267089844s
Reputation | Calculation of the PageRank for Wheat trait took 0.021060466766357422s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 6.556510925292969e-05s
Believability | Calculation of trust value for Wheat trait took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-co_wheat took 3.9559857845306396s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.696846008300781e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.2683448791503906s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02301645278930664s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00034689903259277344s
Believability | Calculation of trust value for Cognitive Atlas took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cogat took 3.8492634296417236s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0006737709045410156s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2778890132904053s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0008137226104736328s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cogpo took 4.153174638748169s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 9.226799011230469e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.29283571243286133s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00044989585876464844s
Believability | Calculation of trust value for Current Procedural Terminology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-cpt took 3.9338717460632324s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 8.726119995117188e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0010979175567626953s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.32267260551452637s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.021535873413085938s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.001829385757446289s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-csp took 4.392394304275513s
Availability | SPARQL endpoint availability check for COSTART took 4.887580871582031e-05s
Availability | VoID file availability check for COSTART took 0.0008502006530761719s
Completeness | Calculation of interlinking completeness for COSTART took 0.2778506278991699s
Reputation | Calculation of the PageRank for COSTART took 0.021318435668945312s
Interlinking | Calculation of Degree of Connection for COSTART took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for COSTART took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0010533332824707031s
Believability | Calculation of trust value for COSTART took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-cst took 4.016347408294678s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 7.390975952148438e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.26738691329956055s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.021270751953125s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005402565002441406s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ctcae took 4.090761661529541s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 9.274482727050781e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.27904462814331055s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020906448364257812s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004940032958984375s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ctx took 4.039856672286987s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.315376281738281e-05s
Availability | VoID file availability check for Dendritic cell took 0.0007717609405517578s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.2730696201324463s
Reputation | Calculation of the PageRank for Dendritic cell took 0.021771669387817383s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00032210350036621094s
Believability | Calculation of trust value for Dendritic cell took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-dc_cl took 3.915710210800171s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.601478576660156e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0007803440093994141s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.26802968978881836s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02308177947998047s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0008130073547363281s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 0.00011992454528808594s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ddanat took 4.1419525146484375s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 5.1021575927734375e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.287553071975708s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02088189125061035s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009801387786865234s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ddi took 4.032793045043945s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.26793432235717773s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.021258831024169922s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 0.00010609626770019531s
Believability | Calculation of trust value for Diagnostic Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-diagnosticont took 4.022647857666016s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.26978135108947754s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020743370056152344s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001690387725830078s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 3.9495954513549805s
Availability | SPARQL endpoint availability check for Human disease ontology took 9.441375732421875e-05s
Availability | VoID file availability check for Human disease ontology took 0.0007517337799072266s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.26267385482788086s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020856380462646484s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006425380706787109s
Believability | Calculation of trust value for Human disease ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-doid took 3.9518327713012695s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2721576690673828s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.021495580673217773s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008220672607421875s
Believability | Calculation of trust value for Electrocardiography Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-ecg took 3.953258752822876s
Availability | SPARQL endpoint availability check for Evidence codes took 4.792213439941406e-05s
Availability | VoID file availability check for Evidence codes took 0.0008392333984375s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.26636743545532227s
Reputation | Calculation of the PageRank for Evidence codes took 0.020882606506347656s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.743171691894531e-05s
Believability | Calculation of trust value for Evidence codes took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-eco took 4.062665224075317s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 9.34600830078125e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3150343894958496s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.001779317855834961s
Believability | Calculation of trust value for Experimental Factor Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-efo took 4.543410301208496s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 8.821487426757812e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.27314090728759766s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02133655548095703s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.001180410385131836s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ehda took 3.963257074356079s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 8.988380432128906e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.27040958404541016s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.02090597152709961s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007920265197753906s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ehdaa took 4.151934385299683s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 9.250640869140625e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0008585453033447266s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.27402544021606445s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.02207493782043457s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0008687973022460938s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0006189346313476562s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ehdaa2 took 3.97607684135437s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.482269287109375e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0008339881896972656s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.2675817012786865s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.02109670639038086s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0011470317840576172s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 4.4345855712890625e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-emap took 3.837625026702881s
Availability | SPARQL endpoint availability check for Environment Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Environment Ontology took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.2802395820617676s
Reputation | Calculation of the PageRank for Environment Ontology took 0.021247148513793945s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0004515647888183594s
Believability | Calculation of trust value for Environment Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-envo took 3.9522597789764404s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 9.202957153320312e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2748384475708008s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.03211474418640137s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.001630544662475586s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0005035400390625s
Believability | Calculation of trust value for Plant environmental conditions took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-eo took 3.9879603385925293s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 9.131431579589844e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.2691051959991455s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.022593021392822266s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012693405151367188s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ep took 4.001185178756714s
Availability | SPARQL endpoint availability check for Epilepsy took 7.176399230957031e-05s
Availability | VoID file availability check for Epilepsy took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2664670944213867s
Reputation | Calculation of the PageRank for Epilepsy took 0.020847082138061523s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0008013248443603516s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001430511474609375s
Believability | Calculation of trust value for Epilepsy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-epileponto took 4.017588376998901s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.482269287109375e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.27697229385375977s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.0211637020111084s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0012061595916748047s
Believability | Calculation of trust value for eagle-i research resource ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ero took 4.072380304336548s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 5.340576171875e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.26251697540283203s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020797252655029297s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.001132965087890625s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0013892650604248047s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ev took 3.951056957244873s
Availability | SPARQL endpoint availability check for ExO took 9.107589721679688e-05s
Availability | VoID file availability check for ExO took 0.0007827281951904297s
Completeness | Calculation of interlinking completeness for ExO took 0.2804107666015625s
Reputation | Calculation of the PageRank for ExO took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for ExO took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00027370452880859375s
Believability | Calculation of trust value for ExO took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-exo took 4.152242183685303s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.506111145019531e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2678542137145996s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.021136760711669922s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00012493133544921875s
Believability | Calculation of trust value for Fungal gross anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-fao took 4.026298999786377s
Availability | SPARQL endpoint availability check for Biological imaging methods took 9.417533874511719e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.26823902130126953s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00019884109497070312s
Believability | Calculation of trust value for Biological imaging methods took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-fbbi took 4.030874967575073s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 0.00011014938354492188s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.27794599533081055s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.022513389587402344s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006513595581054688s
Believability | Calculation of trust value for Drosophila gross anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-fbbt took 3.9472904205322266s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.506111145019531e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.27428507804870605s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.00045800209045410156s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-fbcv took 4.048878908157349s
Availability | SPARQL endpoint availability check for Drosophila development took 9.274482727050781e-05s
Availability | VoID file availability check for Drosophila development took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2687528133392334s
Reputation | Calculation of the PageRank for Drosophila development took 0.02156662940979004s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.863739013671875e-05s
Believability | Calculation of trust value for Drosophila development took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-fbdv took 4.0164947509765625s
Availability | SPARQL endpoint availability check for Fly taxonomy took 5.555152893066406e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2868502140045166s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.026174545288085938s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.00045013427734375s
Believability | Calculation of trust value for Fly taxonomy took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-fbsp took 4.040658473968506s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.363059997558594e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0007166862487792969s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2727982997894287s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.02088475227355957s
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.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022745132446289062s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-fda-meddevice took 3.9859542846679688s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.26311588287353516s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.0206296443939209s
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.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00041747093200683594s
Believability | Calculation of trust value for Family Health History Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fhho took 3.9951300621032715s
Availability | SPARQL endpoint availability check for Influenza Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.3504350185394287s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.021361589431762695s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0009598731994628906s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0011720657348632812s
Believability | Calculation of trust value for Influenza Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-flu took 4.060042381286621s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 9.059906005859375e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.27867984771728516s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.023068666458129883s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 7.128715515136719e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-fma took 4.170551061630249s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.000720977783203125s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.27266621589660645s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001430511474609375s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-fypo took 4.123751401901245s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 9.298324584960938e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.27358531951904297s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02153301239013672s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.775161743164062e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-geospecies took 3.9510672092437744s
Availability | SPARQL endpoint availability check for General Formal Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.28870272636413574s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.021351099014282227s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0001773834228515625s
Believability | Calculation of trust value for General Formal Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-gfo took 4.093942642211914s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 6.461143493652344e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2734816074371338s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020748376846313477s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.000606536865234375s
Believability | Calculation of trust value for General Formal Ontology: Biology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-gfo-bio took 3.821096181869507s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 8.797645568847656e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2747161388397217s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008711814880371094s
Believability | Calculation of trust value for Gene Ontology Extension took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-go_x1 took 3.8826887607574463s
Availability | SPARQL endpoint availability check for Gene Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Gene Ontology took 0.0008194446563720703s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2736992835998535s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008528232574462891s
Believability | Calculation of trust value for Gene Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-go_x2 took 4.006811618804932s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 9.036064147949219e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.27321767807006836s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.0215761661529541s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.337860107421875e-05s
Believability | Calculation of trust value for Cereal Plant Development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-gro took 3.896043300628662s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 9.059906005859375e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2724781036376953s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.02245640754699707s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004792213439941406s
Believability | Calculation of trust value for Cereal plant gross anatomy took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-gro_x1 took 3.919647455215454s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 5.698204040527344e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0008630752563476562s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2670767307281494s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.021117687225341797s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007803440093994141s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-gro_x2 took 3.9548683166503906s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.26641845703125s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02243328094482422s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005648136138916016s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hao took 3.9172003269195557s
Availability | SPARQL endpoint availability check for HCPCS took 8.940696716308594e-05s
Availability | VoID file availability check for HCPCS took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for HCPCS took 0.27312207221984863s
Reputation | Calculation of the PageRank for HCPCS took 0.02200007438659668s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00022554397583007812s
Believability | Calculation of trust value for HCPCS took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-hcpcs took 3.9091122150421143s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.506111145019531e-05s
Availability | VoID file availability check for Health Level Seven took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.26569390296936035s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02080678939819336s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012748241424560547s
Believability | Calculation of trust value for Health Level Seven took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hl7 took 3.8008179664611816s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.4345855712890625e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2734336853027344s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00035381317138671875s
Believability | Calculation of trust value for HEALTH_INDICATORS took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-hlth_indics took 3.8682515621185303s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.26781535148620605s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.021311044692993164s
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.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.7670135498046875e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-hom took 3.928065538406372s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 9.34600830078125e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0013039112091064453s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.27385640144348145s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.02241373062133789s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0008807182312011719s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.743171691894531e-05s
Believability | Calculation of trust value for HOM-HARVARD took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-hom_harvard took 3.880721092224121s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.2678861618041992s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.0222017765045166s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006458759307861328s
Believability | Calculation of trust value for Human Phenotype Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-hp_x1 took 3.785559892654419s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.26787590980529785s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020982980728149414s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010528564453125s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-hpio took 3.9949939250946045s
Availability | SPARQL endpoint availability check for HUGO took 9.322166442871094e-05s
Availability | VoID file availability check for HUGO took 0.0008051395416259766s
Completeness | Calculation of interlinking completeness for HUGO took 0.2666323184967041s
Reputation | Calculation of the PageRank for HUGO took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for HUGO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.463859558105469e-05s
Believability | Calculation of trust value for HUGO took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-hugo took 3.9389755725860596s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 9.822845458984375e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0007524490356445312s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.26511526107788086s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.021022319793701172s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006668567657470703s
Believability | Calculation of trust value for Information Artifact Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-iao took 4.070302963256836s
Availability | SPARQL endpoint availability check for ICD10 took 9.059906005859375e-05s
Availability | VoID file availability check for ICD10 took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for ICD10 took 0.27860093116760254s
Reputation | Calculation of the PageRank for ICD10 took 0.02052593231201172s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008516311645507812s
Believability | Calculation of trust value for ICD10 took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-icd10 took 4.129906177520752s
Availability | SPARQL endpoint availability check for ICD10CM took 6.580352783203125e-05s
Availability | VoID file availability check for ICD10CM took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.26938676834106445s
Reputation | Calculation of the PageRank for ICD10CM took 0.020912647247314453s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006520748138427734s
Believability | Calculation of trust value for ICD10CM took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icd10cm took 3.9942469596862793s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.5299530029296875e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.2651379108428955s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.02064204216003418s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00015306472778320312s
Believability | Calculation of trust value for ICD-10-PCS took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-icd10pcs took 3.9436376094818115s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 9.250640869140625e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.27393031120300293s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.02747058868408203s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0009589195251464844s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0008656978607177734s
Believability | Calculation of trust value for International Classification of Diseases took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-icd9cm took 4.07532811164856s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.601478576660156e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.2682225704193115s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.021122217178344727s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.000827789306640625s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0005033016204833984s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-icf_x1 took 4.184123277664185s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 0.00011515617370605469s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.2863426208496094s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02094888687133789s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0013000965118408203s
Believability | Calculation of trust value for International Classification for Nursing Practice took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-icnp took 4.055402994155884s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.38690185546875e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0007557868957519531s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.2675614356994629s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.021496295928955078s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00047516822814941406s
Believability | Calculation of trust value for International Classification of Primary Care took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-icpc took 3.8756117820739746s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 0.00015616416931152344s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0007224082946777344s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2761423587799072s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020747900009155273s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0009183883666992188s
Believability | Calculation of trust value for ICPC-2 PLUS took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-icpc2p took 3.9566903114318848s
Availability | SPARQL endpoint availability check for ICPS Network took 9.131431579589844e-05s
Availability | VoID file availability check for ICPS Network took 0.0008218288421630859s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.277529239654541s
Reputation | Calculation of the PageRank for ICPS Network took 0.021572589874267578s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00023746490478515625s
Believability | Calculation of trust value for ICPS Network took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-icps took 4.058201789855957s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.26944828033447266s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.022544145584106445s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008389949798583984s
Believability | Calculation of trust value for Infectious Disease Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ido took 3.91196870803833s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0007545948028564453s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.263775110244751s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011470317840576172s
Believability | Calculation of trust value for Brucellosis Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-idobru took 3.8874001502990723s
Availability | SPARQL endpoint availability check for Malaria Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2756819725036621s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.02133345603942871s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013709068298339844s
Believability | Calculation of trust value for Malaria Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-idomal took 3.8141393661499023s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.38690185546875e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.27020835876464844s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003142356872558594s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-iev took 3.8747501373291016s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 9.059906005859375e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0008218288421630859s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.26740574836730957s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00015592575073242188s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-imgt took 4.09902548789978s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 0.00016736984252929688s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2989523410797119s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005249977111816406s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-imr took 4.2580885887146s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 9.822845458984375e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.264629602432251s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.0225222110748291s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008406639099121094s
Believability | Calculation of trust value for Interaction Network Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-ino took 4.055058479309082s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.458427429199219e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2653331756591797s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.361701965332031e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-invertebrata took 3.989675521850586s
Availability | SPARQL endpoint availability check for IxnO took 6.127357482910156e-05s
Availability | VoID file availability check for IxnO took 0.0007948875427246094s
Completeness | Calculation of interlinking completeness for IxnO took 0.274399995803833s
Reputation | Calculation of the PageRank for IxnO took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for IxnO took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00019550323486328125s
Believability | Calculation of trust value for IxnO took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ixno took 4.025957822799683s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.57763671875e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.27115941047668457s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0004019737243652344s
Believability | Calculation of trust value for SysMO-JERM took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-jerm took 4.629616022109985s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.2651941776275635s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.021215200424194336s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0010292530059814453s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 4.0531158447265625e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-kisao took 3.86025333404541s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.6253204345703125e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0007805824279785156s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2589898109436035s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.02085590362548828s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00022649765014648438s
Believability | Calculation of trust value for Loggerhead nesting took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-lhn took 4.044816493988037s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Lipid Ontology took 0.00041222572326660156s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.2680792808532715s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020885467529296875s
Believability | Calculation of trust value for Lipid Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-lipro took 3.8980555534362793s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.5299530029296875e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0003886222839355469s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.31522154808044434s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020855426788330078s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018625259399414062s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-lnc took 4.338653564453125s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 7.987022399902344e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2657456398010254s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006496906280517578s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ma took 3.7609481811523438s
Availability | SPARQL endpoint availability check for Multiple alignment took 8.630752563476562e-05s
Availability | VoID file availability check for Multiple alignment took 0.001440286636352539s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.274627685546875s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020972013473510742s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002231597900390625s
Believability | Calculation of trust value for Multiple alignment took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mao took 3.8616943359375s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.506111145019531e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0007512569427490234s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.26697325706481934s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007290840148925781s
Believability | Calculation of trust value for Minimal anatomical terminology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-mat took 3.8149068355560303s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.363059997558594e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.28136634826660156s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.023041248321533203s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.00046563148498535156s
Believability | Calculation of trust value for Breast tissue cell lines took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-mcbcc took 4.0820441246032715s
Availability | SPARQL endpoint availability check for Cell line ontology took 9.298324584960938e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26531982421875s
Reputation | Calculation of the PageRank for Cell line ontology took 0.022270917892456055s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007700920104980469s
Believability | Calculation of trust value for Cell line ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mccl took 3.841348648071289s
Availability | SPARQL endpoint availability check for Cell line ontology took 9.131431579589844e-05s
Availability | VoID file availability check for Cell line ontology took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2694511413574219s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021434783935546875s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014469623565673828s
Believability | Calculation of trust value for Cell line ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 3.788816213607788s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.363059997558594e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0008296966552734375s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.26654791831970215s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002453327178955078s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mcv took 3.8674116134643555s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.673004150390625e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2693145275115967s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.022346019744873047s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001919269561767578s
Believability | Calculation of trust value for Master Drug Data Base took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mddb took 3.9165074825286865s
Availability | SPARQL endpoint availability check for MedDRA took 4.696846008300781e-05s
Availability | VoID file availability check for MedDRA took 0.0007603168487548828s
Completeness | Calculation of interlinking completeness for MedDRA took 0.27524828910827637s
Reputation | Calculation of the PageRank for MedDRA took 0.021500825881958008s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011687278747558594s
Believability | Calculation of trust value for MedDRA took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mdr took 4.001890420913696s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 0.00010776519775390625s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.27552223205566406s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02176070213317871s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009286403656005859s
Believability | Calculation of trust value for MedlinePlus Health Topics took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-medlineplus took 3.8369228839874268s
Availability | SPARQL endpoint availability check for MeGO took 9.036064147949219e-05s
Availability | VoID file availability check for MeGO took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for MeGO took 0.27300000190734863s
Reputation | Calculation of the PageRank for MeGO took 0.02165961265563965s
Interlinking | Calculation of Degree of Connection for MeGO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00015687942504882812s
Believability | Calculation of trust value for MeGO took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mego took 3.9174516201019287s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.5299530029296875e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.321063756942749s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.021134376525878906s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0019297599792480469s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mesh-owl took 4.6231911182403564s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 9.369850158691406e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.26908302307128906s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020915746688842773s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006444454193115234s
Believability | Calculation of trust value for Mental Functioning Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mf took 4.0622663497924805s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 0.00013780593872070312s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.27157068252563477s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020817995071411133s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005724430084228516s
Believability | Calculation of trust value for Medaka fish anatomy and development took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-mfo took 3.7990524768829346s
Availability | SPARQL endpoint availability check for Emotion Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2731621265411377s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.02112579345703125s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.00078582763671875s
Believability | Calculation of trust value for Emotion Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mfoem took 4.019749402999878s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2712383270263672s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00011801719665527344s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mhc took 3.869133949279785s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.458427429199219e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2663545608520508s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.021074533462524414s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006709098815917969s
Believability | Calculation of trust value for Protein-protein interaction took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mi took 3.9251794815063477s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 0.00010919570922851562s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2637462615966797s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007266998291015625s
Believability | Calculation of trust value for Mosquito insecticide resistance took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-miro took 3.9391517639160156s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0007808208465576172s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.2670300006866455s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00013709068298339844s
Believability | Calculation of trust value for Measurement Method Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mmo took 4.072402238845825s
Availability | SPARQL endpoint availability check for MGED Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for MGED Ontology took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.26563143730163574s
Reputation | Calculation of the PageRank for MGED Ontology took 0.021816492080688477s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0011749267578125s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0005095005035400391s
Believability | Calculation of trust value for MGED Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mo took 4.069845676422119s
Availability | SPARQL endpoint availability check for Protein modification took 0.00011086463928222656s
Availability | VoID file availability check for Protein modification took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2735621929168701s
Reputation | Calculation of the PageRank for Protein modification took 0.021871566772460938s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002288818359375s
Believability | Calculation of trust value for Protein modification took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mod took 4.031824588775635s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 9.1552734375e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.275134801864624s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006988048553466797s
Believability | Calculation of trust value for Mammalian phenotype took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mp took 4.1336729526519775s
Availability | SPARQL endpoint availability check for Mouse pathology took 0.00010991096496582031s
Availability | VoID file availability check for Mouse pathology took 0.0004127025604248047s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.2799184322357178s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004982948303222656s
Believability | Calculation of trust value for Mouse pathology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-mpath took 3.943098783493042s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.291534423828125e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.26795530319213867s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003733634948730469s
Believability | Calculation of trust value for Mass spectrometry took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ms took 3.792642116546631s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 9.107589721679688e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.32274532318115234s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020885705947875977s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0019512176513671875s
Believability | Calculation of trust value for Medical Subject Headings took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-msh took 4.402114629745483s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 9.608268737792969e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2739074230194092s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00018095970153808594s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-mthch took 3.974400043487549s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.27354884147644043s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.02126145362854004s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008337497711181641s
Believability | Calculation of trust value for Natural Products Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-natpro took 3.9186484813690186s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.5299530029296875e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2698094844818115s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.021348953247070312s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0009179115295410156s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0009391307830810547s
Believability | Calculation of trust value for NCBI organismal classification took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-ncbitaxon took 3.8281490802764893s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 9.72747802734375e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.31359052658081055s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.002016782760620117s
Believability | Calculation of trust value for NCI Thesaurus took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ncit took 4.429854393005371s
Availability | SPARQL endpoint availability check for National Drug Data File took 9.608268737792969e-05s
Availability | VoID file availability check for National Drug Data File took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.26462292671203613s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006926059722900391s
Believability | Calculation of trust value for National Drug Data File took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nddf took 4.040784120559692s
Availability | SPARQL endpoint availability check for National Drug File took 4.410743713378906e-05s
Availability | VoID file availability check for National Drug File took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2749142646789551s
Reputation | Calculation of the PageRank for National Drug File took 0.02187657356262207s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.001295328140258789s
Believability | Calculation of trust value for National Drug File took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-ndfrt took 4.00355076789856s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 9.107589721679688e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.2786107063293457s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011777877807617188s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-nemo_x1 took 4.001657009124756s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.3401956558227539s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0007045269012451172s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-neomark took 4.4151976108551025s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.2827930450439453s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020717382431030273s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.0001289844512939453s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-neomarkontology took 3.966527223587036s
Availability | SPARQL endpoint availability check for NIFSTD took 0.00010967254638671875s
Availability | VoID file availability check for NIFSTD took 0.0007548332214355469s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.3187081813812256s
Reputation | Calculation of the PageRank for NIFSTD took 0.021420717239379883s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.002005338668823242s
Believability | Calculation of trust value for NIFSTD took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-nif took 4.519078254699707s
Availability | SPARQL endpoint availability check for NIF Cell took 9.012222290039062e-05s
Availability | VoID file availability check for NIF Cell took 0.00042724609375s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.27454590797424316s
Reputation | Calculation of the PageRank for NIF Cell took 0.020846128463745117s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013723373413085938s
Believability | Calculation of trust value for NIF Cell took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-nif_cell took 4.045527219772339s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.7206878662109375e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.26926589012145996s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.001432180404663086s
Believability | Calculation of trust value for NIF Dysfunction took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-nif_dysfunction took 4.23935866355896s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.26843762397766113s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.0208737850189209s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005857944488525391s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nigo took 4.061429023742676s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 9.036064147949219e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.26212501525878906s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005698204040527344s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-nmr took 3.9177932739257812s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2748587131500244s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.021821022033691406s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0008485317230224609s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00013494491577148438s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-nonrctontology took 4.009095191955566s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0008060932159423828s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.26700735092163086s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.02090597152709961s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0010404586791992188s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0013577938079833984s
Believability | Calculation of trust value for NanoParticle Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-npo took 3.999107837677002s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2841475009918213s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02089238166809082s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007355213165283203s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-oae took 4.057544708251953s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 5.817413330078125e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.2673830986022949s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0015137195587158203s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-obi took 3.960700511932373s
Availability | SPARQL endpoint availability check for OBOE took 0.00010704994201660156s
Availability | VoID file availability check for OBOE took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for OBOE took 0.27845287322998047s
Reputation | Calculation of the PageRank for OBOE took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for OBOE took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00013756752014160156s
Believability | Calculation of trust value for OBOE took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-oboe took 4.046949625015259s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.291534423828125e-05s
Availability | VoID file availability check for OBOE SBC took 0.0008168220520019531s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.27961087226867676s
Reputation | Calculation of the PageRank for OBOE SBC took 0.021253108978271484s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008077621459960938s
Believability | Calculation of trust value for OBOE SBC took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-oboe-sbc took 4.161755323410034s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 5.078315734863281e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0007579326629638672s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.28157663345336914s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.021320104598999023s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0006372928619384766s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-ocre took 3.9668729305267334s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 0.00010609626770019531s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.27683138847351074s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008742809295654297s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-odgi took 3.991530179977417s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.839897155761719e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0007052421569824219s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2645530700683594s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.021467924118041992s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0012254714965820312s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0010502338409423828s
Believability | Calculation of trust value for Ontology for Genetic Interval took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ogi took 4.101311206817627s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.27285313606262207s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.02082991600036621s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0003204345703125s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ogmd took 3.97182297706604s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.6253204345703125e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.2687661647796631s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.02061319351196289s
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.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006947517395019531s
Believability | Calculation of trust value for Ontology for General Medical Science took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ogms took 3.808255672454834s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.482269287109375e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.26684141159057617s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011887550354003906s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-omim took 3.8456037044525146s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 9.226799011230469e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0007779598236083984s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.2706296443939209s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.00039458274841308594s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-omit took 3.967355966567993s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 9.274482727050781e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.26827311515808105s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02086019515991211s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006010532379150391s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-omrse took 2.4341397285461426s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2682352066040039s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02085566520690918s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007994174957275391s
Believability | Calculation of trust value for Ontology of Data Mining took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-ontodm took 4.124576807022095s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.506111145019531e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0007603168487548828s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.2692265510559082s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.021111011505126953s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002613067626953125s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ontodt took 4.119817018508911s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.7206878662109375e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2687389850616455s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006079673767089844s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-ontoorpha took 4.040194749832153s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 0.00010132789611816406s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.27553272247314453s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020576000213623047s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009171962738037109s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-opl took 4.1485278606414795s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.553794860839844e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.27719688415527344s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0009701251983642578s
Believability | Calculation of trust value for Phenotypic quality took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-pato took 3.9611384868621826s
Availability | SPARQL endpoint availability check for Physician Data Query took 9.179115295410156e-05s
Availability | VoID file availability check for Physician Data Query took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.26911330223083496s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020797252655029297s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008347034454345703s
Believability | Calculation of trust value for Physician Data Query took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pdq took 4.09941029548645s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 5.555152893066406e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2692534923553467s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020796775817871094s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008330345153808594s
Believability | Calculation of trust value for Pediatric Terminology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-pedterm took 3.969020366668701s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.2725644111633301s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.02172255516052246s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0002090930938720703s
Believability | Calculation of trust value for Parasite Experiment Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-peo took 3.8012430667877197s
Availability | SPARQL endpoint availability check for PHARE took 5.5789947509765625e-05s
Availability | VoID file availability check for PHARE took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for PHARE took 0.26579928398132324s
Reputation | Calculation of the PageRank for PHARE took 0.020726919174194336s
Interlinking | Calculation of Degree of Connection for PHARE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PHARE took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.000652313232421875s
Believability | Calculation of trust value for PHARE took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-phare took 4.036610126495361s
Availability | SPARQL endpoint availability check for PKO_Re took 4.482269287109375e-05s
Availability | VoID file availability check for PKO_Re took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2690696716308594s
Reputation | Calculation of the PageRank for PKO_Re took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00021505355834960938s
Believability | Calculation of trust value for PKO_Re took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-pko took 4.063952922821045s
Availability | SPARQL endpoint availability check for PMA 2010 took 0.0001533031463623047s
Availability | VoID file availability check for PMA 2010 took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2842371463775635s
Reputation | Calculation of the PageRank for PMA 2010 took 0.022203922271728516s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0010080337524414062s
Believability | Calculation of trust value for PMA 2010 took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-pma took 3.9619598388671875s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.291534423828125e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2687339782714844s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001690387725830078s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pmr took 4.026952028274536s
Availability | SPARQL endpoint availability check for Plant Anatomy took 8.749961853027344e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.27393579483032227s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020753860473632812s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0004258155822753906s
Believability | Calculation of trust value for Plant Anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-po took 4.0101237297058105s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 9.1552734375e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0007796287536621094s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.27706122398376465s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02211594581604004s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.937980651855469e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-po_x1 took 4.0028297901153564s
Availability | SPARQL endpoint availability check for Plant Ontology took 0.00010228157043457031s
Availability | VoID file availability check for Plant Ontology took 0.0007870197296142578s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.26676106452941895s
Reputation | Calculation of the PageRank for Plant Ontology took 0.021249055862426758s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004496574401855469s
Believability | Calculation of trust value for Plant Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-po_x2 took 3.9723832607269287s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.601478576660156e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0008263587951660156s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2679007053375244s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006787776947021484s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-pr took 4.079869508743286s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 9.34600830078125e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2638857364654541s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02157282829284668s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002791881561279297s
Believability | Calculation of trust value for Proteomics data and process provenance took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-propreo took 4.327859163284302s
Availability | SPARQL endpoint availability check for Pathway ontology took 0.00012350082397460938s
Availability | VoID file availability check for Pathway ontology took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.2769443988800049s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00013256072998046875s
Believability | Calculation of trust value for Pathway ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-pw took 4.099669694900513s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.26699376106262207s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020727157592773438s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-qibo took 4.154696941375732s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 9.679794311523438e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3158223628997803s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020793914794921875s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0018374919891357422s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-rcd took 4.488385200500488s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0007715225219726562s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2684669494628906s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00014472007751464844s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-rctontology took 3.896524429321289s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.28061413764953613s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02099752426147461s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.918212890625e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-repo took 3.9799554347991943s
Availability | SPARQL endpoint availability check for Physico-chemical process took 8.893013000488281e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.2766742706298828s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020844459533691406s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.000209808349609375s
Believability | Calculation of trust value for Physico-chemical process took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-rex took 4.0195112228393555s
Availability | SPARQL endpoint availability check for RadLex took 9.059906005859375e-05s
Availability | VoID file availability check for RadLex took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for RadLex took 0.2679939270019531s
Reputation | Calculation of the PageRank for RadLex took 0.022387266159057617s
Interlinking | Calculation of Degree of Connection for RadLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015316009521484375s
Believability | Calculation of trust value for RadLex took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rid took 3.866877317428589s
Availability | SPARQL endpoint availability check for RNA ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for RNA ontology took 0.0007827281951904297s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.27202725410461426s
Reputation | Calculation of the PageRank for RNA ontology took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005502700805664062s
Believability | Calculation of trust value for RNA ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rnao took 3.9459962844848633s
Availability | SPARQL endpoint availability check for Role Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Role Ontology took 0.0007977485656738281s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2726290225982666s
Reputation | Calculation of the PageRank for Role Ontology took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00021576881408691406s
Believability | Calculation of trust value for Role Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-roleo took 3.721855878829956s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 9.131431579589844e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.26514363288879395s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001800060272216797s
Believability | Calculation of trust value for Rat Strain Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-rs took 4.1117002964019775s
Availability | SPARQL endpoint availability check for RxNORM took 0.00010251998901367188s
Availability | VoID file availability check for RxNORM took 0.0008313655853271484s
Completeness | Calculation of interlinking completeness for RxNORM took 0.27288079261779785s
Reputation | Calculation of the PageRank for RxNORM took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006132125854492188s
Believability | Calculation of trust value for RxNORM took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rxnorm took 3.9870445728302s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.649162292480469e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.27576422691345215s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020998716354370117s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010390281677246094s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sao took 4.067840099334717s
Availability | SPARQL endpoint availability check for Systems Biology took 9.226799011230469e-05s
Availability | VoID file availability check for Systems Biology took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.27353787422180176s
Reputation | Calculation of the PageRank for Systems Biology took 0.020905733108520508s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004825592041015625s
Believability | Calculation of trust value for Systems Biology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-sbo took 3.9809818267822266s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.26661133766174316s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02127242088317871s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010943412780761719s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-sbro took 4.1345391273498535s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.3087735176086426s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013251304626464844s
Believability | Calculation of trust value for Sleep Domain Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sdo took 3.9245872497558594s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 5.245208740234375e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.27141475677490234s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003533363342285156s
Believability | Calculation of trust value for Sample processing and separation techniques took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sep took 4.0046820640563965s
Availability | SPARQL endpoint availability check for Student Health Record took 4.458427429199219e-05s
Availability | VoID file availability check for Student Health Record took 0.0007822513580322266s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.26554322242736816s
Reputation | Calculation of the PageRank for Student Health Record took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.00044727325439453125s
Believability | Calculation of trust value for Student Health Record took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-shr took 3.7094454765319824s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 6.604194641113281e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.26953768730163574s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.001270294189453125s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sio took 4.589451789855957s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 8.96453857421875e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0008082389831542969s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.26523733139038086s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.021838903427124023s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00021457672119140625s
Believability | Calculation of trust value for Situation-Based Access Control took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sitbac took 4.0306103229522705s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.458427429199219e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.33109188079833984s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019497871398925781s
Believability | Calculation of trust value for SNOMED Clinical Terms took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-snomedct took 4.577967405319214s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.839897155761719e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.26674890518188477s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006864070892333984s
Believability | Calculation of trust value for SNP-Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-snpo took 3.8473763465881348s
Availability | SPARQL endpoint availability check for Sequence types and features took 9.107589721679688e-05s
Availability | VoID file availability check for Sequence types and features took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2682676315307617s
Reputation | Calculation of the PageRank for Sequence types and features took 0.021749019622802734s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0006127357482910156s
Believability | Calculation of trust value for Sequence types and features took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-so_x1 took 3.9758927822113037s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 9.179115295410156e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.31171560287475586s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.02126765251159668s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015799999237060547s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sopharm took 4.432044982910156s
Availability | SPARQL endpoint availability check for SoyOntology took 0.00010514259338378906s
Availability | VoID file availability check for SoyOntology took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.279721736907959s
Reputation | Calculation of the PageRank for SoyOntology took 0.021060943603515625s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00013637542724609375s
Believability | Calculation of trust value for SoyOntology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-soy took 3.9937455654144287s
Availability | SPARQL endpoint availability check for Spider Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.27480411529541016s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003581047058105469s
Believability | Calculation of trust value for Spider Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-spd took 3.990255117416382s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.00078582763671875s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.26865148544311523s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00028634071350097656s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-spto took 4.135555982589722s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.2682664394378662s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.021228790283203125s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00047707557678222656s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-sso took 3.8635549545288086s
Availability | SPARQL endpoint availability check for Software Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Software Ontology took 0.0007863044738769531s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.30525851249694824s
Reputation | Calculation of the PageRank for Software Ontology took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004119873046875s
Believability | Calculation of trust value for Software Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-swo took 4.0902111530303955s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 8.96453857421875e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.000827789306640625s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.345350980758667s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00026106834411621094s
Believability | Calculation of trust value for Tick gross anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-tads took 4.094449996948242s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0007803440093994141s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.2747673988342285s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0009253025054931641s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-tao took 3.9853057861328125s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 0.00011944770812988281s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2665832042694092s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.441375732421875e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-taxrank took 4.775514841079712s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 7.319450378417969e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.26754045486450195s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.022022724151611328s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007276535034179688s
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 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-teddy took 3.795964002609253s
Availability | SPARQL endpoint availability check for Time Event Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Time Event Ontology took 0.00080108642578125s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.27298617362976074s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020931720733642578s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008425712585449219s
Believability | Calculation of trust value for Time Event Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-teo took 4.122973680496216s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 8.821487426757812e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.27204060554504395s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020903587341308594s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00042438507080078125s
Believability | Calculation of trust value for Mosquito gross anatomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-tgma took 4.038661479949951s
Availability | SPARQL endpoint availability check for thesaurus took 5.888938903808594e-05s
Availability | VoID file availability check for thesaurus took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for thesaurus took 0.27518272399902344s
Reputation | Calculation of the PageRank for thesaurus took 0.0217435359954834s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.271766662597656e-05s
Believability | Calculation of trust value for thesaurus took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-thesaurus took 4.0347676277160645s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.363059997558594e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.26662516593933105s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02118229866027832s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00040459632873535156s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 3.8399288654327393s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2866401672363281s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008499622344970703s
Believability | Calculation of trust value for Translational Medicine Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-tmo took 3.9236996173858643s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2725403308868408s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020865440368652344s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00019693374633789062s
Believability | Calculation of trust value for Plant Trait Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-to took 4.009315490722656s
Availability | SPARQL endpoint availability check for TOK_Ontology took 0.00012564659118652344s
Availability | VoID file availability check for TOK_Ontology took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2751035690307617s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020917654037475586s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00019931793212890625s
Believability | Calculation of trust value for TOK_Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-tok took 4.0596747398376465s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 9.250640869140625e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.27658534049987793s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020919084548950195s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.0002300739288330078s
Believability | Calculation of trust value for Teleost taxonomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-tto took 4.069216012954712s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.259594202041626s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.02102828025817871s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010726451873779297s
Believability | Calculation of trust value for Uber anatomy ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-uberon took 3.948925018310547s
Availability | SPARQL endpoint availability check for Units Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for Units Ontology took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.27344751358032227s
Reputation | Calculation of the PageRank for Units Ontology took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002338886260986328s
Believability | Calculation of trust value for Units Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-unitsontology took 4.1234776973724365s
Availability | SPARQL endpoint availability check for Units of measurement took 9.1552734375e-05s
Availability | VoID file availability check for Units of measurement took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.27210307121276855s
Reputation | Calculation of the PageRank for Units of measurement took 0.020884275436401367s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0003037452697753906s
Believability | Calculation of trust value for Units of measurement took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-uo took 4.006386041641235s
Availability | SPARQL endpoint availability check for VANDF took 9.179115295410156e-05s
Availability | VoID file availability check for VANDF took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for VANDF took 0.2766082286834717s
Reputation | Calculation of the PageRank for VANDF took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for VANDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007219314575195312s
Believability | Calculation of trust value for VANDF took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-vandf took 4.196848630905151s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 9.560585021972656e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.000736236572265625s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2684636116027832s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020745038986206055s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004296302795410156s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-vao took 4.0059449672698975s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 9.250640869140625e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.27570009231567383s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020622968673706055s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006518363952636719s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vhog took 3.9847943782806396s
Availability | SPARQL endpoint availability check for VIVO took 4.5299530029296875e-05s
Availability | VoID file availability check for VIVO took 0.0007886886596679688s
Completeness | Calculation of interlinking completeness for VIVO took 0.275118350982666s
Reputation | Calculation of the PageRank for VIVO took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for VIVO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0008695125579833984s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003712177276611328s
Believability | Calculation of trust value for VIVO took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-vivo took 4.0599524974823s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.27109622955322266s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.021050691604614258s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0013217926025390625s
Believability | Calculation of trust value for Vaccine Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-vo took 4.113527059555054s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.28343868255615234s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.021234750747680664s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.0002117156982421875s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-vt took 3.873647689819336s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 9.226799011230469e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2691359519958496s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.021939754486083984s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005180835723876953s
Believability | Calculation of trust value for C. elegans gross anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-wbbt took 4.047839879989624s
Availability | SPARQL endpoint availability check for C. elegans development took 9.083747863769531e-05s
Availability | VoID file availability check for C. elegans development took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.26873779296875s
Reputation | Calculation of the PageRank for C. elegans development took 0.020919322967529297s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0008056163787841797s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 5.7220458984375e-05s
Believability | Calculation of trust value for C. elegans development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-wbls took 3.8757786750793457s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 9.012222290039062e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0007929801940917969s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.27421140670776367s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.02080392837524414s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 0.00010037422180175781s
Believability | Calculation of trust value for C. elegans phenotype took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-wbphenotype took 3.984748125076294s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 5.221366882324219e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2685737609863281s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.021479129791259766s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006113052368164062s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-who took 4.038934230804443s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 9.441375732421875e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2772667407989502s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0007507801055908203s
Believability | Calculation of trust value for Xenopus anatomy and development took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-xao took 4.159873008728027s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 9.679794311523438e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.2691049575805664s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00024008750915527344s
Believability | Calculation of trust value for Experimental Conditions Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-xco took 4.090967178344727s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 9.274482727050781e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.2682528495788574s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.02331233024597168s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002777576446533203s
Believability | Calculation of trust value for Yeast phenotypes took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ypo took 3.8930656909942627s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 0.00011277198791503906s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.26593446731567383s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02059197425842285s
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.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007746219635009766s
Believability | Calculation of trust value for Zebrafish anatomy and development took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-zfa took 3.867562770843506s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.696846008300781e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.2757382392883301s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.021378040313720703s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0008261203765869141s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.933906555175781e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.430511474609375e-05s
INFO | --- Analysis for Bioportal_link took 3.4226372241973877s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.4016532897949219s
Availability | VoID file availability check for BioSamples RDF took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.26851367950439453s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020897626876831055s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.933906555175781e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.1920928955078125e-05s
INFO | --- Analysis for biosamples-rdf took 3.453099250793457s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.23467397689819336s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2710838317871094s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.021042585372924805s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00012636184692382812s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.3589859008789062e-05s
INFO | --- Analysis for bis-linked-data took 2.6989948749542236s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.392333984375e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2703273296356201s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.1961669921875e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.4781951904296875e-05s
INFO | --- Analysis for bll-thesaurus took 3.4852523803710938s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.1558499336242676s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.2689988613128662s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02062225341796875s
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.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 7.367134094238281e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.52587890625e-05s
INFO | --- Analysis for bluk-bnb took 12.171082258224487s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.280681848526001s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006761550903320312s
Extra | Recovery of all triples for Thesaurus BNCF took 47.804415702819824s
Performance | Total latancy measurement for Thesaurus BNCF took 0.5210585594177246s
Amount of data | Number of triples check for Thesaurus BNCF took 0.5811223983764648s
Interoperability | New terms check for Thesaurus BNCF took 1.5736041069030762s
Versatility | Languages check for Thesaurus BNCF took 6.844278812408447s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.7845644950866699s
Security | Check HTTPS for Thesaurus BNCF took 0.0764317512512207s
Interpretability | RDF structures check for Thesaurus BNCF took 0.10808968544006348s
Versatility | Serialization formats check for Thesaurus BNCF took 0.1047523021697998s
Availability | RDF dump link check for Thesaurus BNCF took 0.10269308090209961s
License | MR license check for Thesaurus BNCF took 0.10287046432495117s
License | HR license check for Thesaurus BNCF took 0.16985392570495605s
Amount of data | Number of property check for Thesaurus BNCF took 0.10609602928161621s
Understandability | Number of label check for Thesaurus BNCF took 0.2492992877960205s
Understandability | URI regex check for Thesaurus BNCF took 0.20994234085083008s
Understandability | Vocabs check for Thesaurus BNCF took 0.10309576988220215s
Verifiability | Authors check for Thesaurus BNCF took 0.10677695274353027s
Verifiability | Publishers check for Thesaurus BNCF took 0.10303997993469238s
Performance | Throughput check for Thesaurus BNCF took 10.185281753540039s
Amount of data | Check the number of entities for Thesaurus BNCF took 3.170967102050781e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.10112309455871582s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.09980988502502441s
Interlinking | skos check for Thesaurus BNCF took 0.14325332641601562s
Interlinking | skos check for Thesaurus BNCF took 0.12467527389526367s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.1017904281616211s
Currency | Creation date check for Thesaurus BNCF took 0.21390485763549805s
Currency | Modification date check for Thesaurus BNCF took 0.20363950729370117s
Rep.Conc. | URIs length for Thesaurus BNCF took 27.375101566314697s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.10673308372497559s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.1041862964630127s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.10279536247253418s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 13.986908674240112s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.501490592956543s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 4.040729284286499s
Consistency | Disjoint class check for Thesaurus BNCF took 0.10208320617675781s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.7936127185821533s
Consistency | Misplaced classes for Thesaurus BNCF took 6.895458221435547s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.961142301559448s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.6947393417358398s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.4008378982543945s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4553513526916504s
Security | Sign check for Thesaurus BNCF took 0.1022491455078125s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.868797779083252s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.34139323234558105s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.021181821823120117s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 8.893013000488281e-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.430511474609375e-05s
INFO | --- Analysis for bncf-ns took 188.23770427703857s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.631096363067627s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006833076477050781s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.280569076538086s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6634001731872559s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.9154462814331055s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.1199188232421875s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.199554681777954s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.9870569705963135s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2646796703338623s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4158954620361328s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4422316551208496s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4216315746307373s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5393002033233643s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.22765111923218s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3400993347167969s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8989219665527344s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6970653533935547s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.41628384590148926s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4633927345275879s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35022568702697754s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.741253852844238s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.534027099609375e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33101415634155273s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.376251220703125s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3595271110534668s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3532400131225586s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4537770748138428s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7118091583251953s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.359403133392334s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.54387640953064s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3240213394165039s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.282956600189209s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3312416076660156s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7066102027893066s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030761241912841797s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03108835220336914s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3320045471191406s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.557551622390747s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4564056396484375s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.5248165130615234s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9457793235778809s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.287423133850098s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03248286247253418s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39894747734069824s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3448777198791504s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.33583927154541s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.30021142959594727s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02149796485900879s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 9.5367431640625e-07s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4781951904296875e-05s
INFO | --- Analysis for bpr took 383.36870312690735s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 9.965896606445312e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.26455092430114746s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02078557014465332s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.343292236328125e-05s
Believability | Calculation of trust value for Brazilian Politicians took 1.0967254638671875e-05s
INFO | --- Analysis for brazilian-politicians took 2.484771728515625s
Availability | SPARQL endpoint availability check for Bricklink took 1.5422022342681885s
Availability | VoID file availability check for Bricklink took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Bricklink took 0.26734256744384766s
Reputation | Calculation of the PageRank for Bricklink took 0.021030902862548828s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.62939453125e-05s
Believability | Calculation of trust value for Bricklink took 1.239776611328125e-05s
INFO | --- Analysis for bricklink took 15.788635492324829s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.332865476608276s
Availability | VoID file availability check for British Museum Collection took 0.0007939338684082031s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2751798629760742s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.62396240234375e-05s
Believability | Calculation of trust value for British Museum Collection took 1.4781951904296875e-05s
INFO | --- Analysis for british-museum-collection took 72.86915230751038s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.458427429199219e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.2756023406982422s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020711898803710938s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.5299530029296875e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.3828277587890625e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.521890163421631s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.22878265380859375s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006082057952880859s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 11.583423376083374s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.5645334720611572s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.9989628791809082s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.959496021270752s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.944545269012451s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.8899717330932617s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11669278144836426s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11533880233764648s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1136014461517334s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11344575881958008s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 22.341716051101685s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11319375038146973s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1734316349029541s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.22671031951904297s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11388802528381348s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11401772499084473s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11427807807922363s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.212916851043701s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.00011038780212402344s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11418271064758301s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11385798454284668s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11359119415283203s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1136922836303711s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12210750579833984s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.22786402702331543s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2272200584411621s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.4871187210083s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11668562889099121s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11279630661010742s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11313080787658691s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.3434560298919678s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2491135597229004s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.70106053352356s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11453413963317871s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.0150601863861084s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.548225164413452s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.4015378952026367s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.725210189819336s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.73887038230896s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11249470710754395s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3420.2918157577515s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.6590924263000488s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.02155470848083496s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.723403930664062e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.9073486328125e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0013580322265625e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3532.1784040927887s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.209580659866333s
Availability | VoID file availability check for business.data.gov.uk took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.27376317977905273s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.53131103515625e-05s
Believability | Calculation of trust value for business.data.gov.uk took 1.0728836059570312e-05s
INFO | --- Analysis for business-data-gov-uk took 2.7949929237365723s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.5602359771728516s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0007598400115966797s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 6.769058704376221s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.386873722076416s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.5845005512237549s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.8694031238555908s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 60.27636218070984s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.8718409538269043s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.17340397834777832s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.6063392162322998s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 1.306311845779419s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.34085559844970703s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.7840282917022705s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 28.38012981414795s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3946523666381836s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 3.231818914413452s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.6930642127990723s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.2891561985015869s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.3843655586242676s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.27881669998168945s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.197438955307007s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.295608520507812e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.5359063148498535s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3308131694793701s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.45728325843811035s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.27952075004577637s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.4687778949737549s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.860753059387207s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.657203197479248s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 5.619636535644531s
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.4117867946624756s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.42617011070251465s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5263721942901611s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 2.5283286571502686s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03405904769897461s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.029989957809448242s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.512941837310791s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.5419590473175049s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.36746764183044434s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 4.729451894760132s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.4324500560760498s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.5754573345184326s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03413677215576172s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.5869479179382324s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 1.9310965538024902s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 11.439600706100464s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.2714509963989258s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.021218299865722656s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0010309219360351562s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 7.295608520507812e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.049041748046875e-05s
INFO | --- Analysis for BVMC took 249.13301062583923s
Availability | SPARQL endpoint availability check for cablegate took 1.5051093101501465s
Availability | VoID file availability check for cablegate took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for cablegate took 0.2721891403198242s
Reputation | Calculation of the PageRank for cablegate took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for cablegate took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for cablegate took 7.2479248046875e-05s
Believability | Calculation of trust value for cablegate took 9.298324584960938e-06s
INFO | --- Analysis for cablegate took 16.07533359527588s
Availability | SPARQL endpoint availability check for Calames took 4.649162292480469e-05s
Availability | VoID file availability check for Calames took 0.00038170814514160156s
Completeness | Calculation of interlinking completeness for Calames took 0.2706749439239502s
Reputation | Calculation of the PageRank for Calames took 0.020849943161010742s
Interlinking | Calculation of Degree of Connection for Calames took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Calames took 4.0531158447265625e-05s
Believability | Calculation of trust value for Calames took 1.3828277587890625e-05s
INFO | --- Analysis for calames took 3.967254638671875s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.3674948215484619s
Availability | VoID file availability check for CaLiGraph took 0.0005381107330322266s
Extra | Recovery of all triples for CaLiGraph took 1.1178510189056396s
Performance | Total latancy measurement for CaLiGraph took 1.0764079093933105s
Amount of data | Number of triples check for CaLiGraph took 13.591258525848389s
Interoperability | New terms check for CaLiGraph took 2.2443809509277344s
Versatility | Languages check for CaLiGraph took 60.28219556808472s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2391512393951416s
Security | Check HTTPS for CaLiGraph took 0.12763643264770508s
Interpretability | RDF structures check for CaLiGraph took 0.24130535125732422s
Versatility | Serialization formats check for CaLiGraph took 0.24081873893737793s
Availability | RDF dump link check for CaLiGraph took 0.23287630081176758s
License | MR license check for CaLiGraph took 0.23882627487182617s
License | HR license check for CaLiGraph took 60.292171001434326s
Amount of data | Number of property check for CaLiGraph took 0.24350357055664062s
Understandability | Number of label check for CaLiGraph took 3.278658866882324s
Understandability | URI regex check for CaLiGraph took 0.4666709899902344s
Understandability | Vocabs check for CaLiGraph took 0.23359155654907227s
Verifiability | Authors check for CaLiGraph took 0.23743820190429688s
Verifiability | Publishers check for CaLiGraph took 0.23424434661865234s
Performance | Throughput check for CaLiGraph took 10.5942063331604s
Amount of data | Check the number of entities for CaLiGraph took 0.019839048385620117s
Verifiability | Contribs. check for CaLiGraph took 0.23822784423828125s
Interlinking | sameAs chians check for CaLiGraph took 0.643526554107666s
Interlinking | skos check for CaLiGraph took 0.24017071723937988s
Interlinking | skos check for CaLiGraph took 0.21201372146606445s
Timeliness | dataset update frequency check for CaLiGraph took 0.2401437759399414s
Currency | Creation date check for CaLiGraph took 0.4755587577819824s
Currency | Modification date check for CaLiGraph took 0.47672271728515625s
Rep.Conc. | URIs length for CaLiGraph took 60.96434187889099s
Interoperability | New vocabularies check for CaLiGraph took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.23427748680114746s
Accuracy | Check Functional Property for CaLiGraph took 0.23453307151794434s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.23487544059753418s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5370800495147705s
Accuracy | Check White space in annotation for CaLiGraph took 0.026488542556762695s
Accuracy | Check Datatype consistency for CaLiGraph took 0.053389787673950195s
Consistency | Disjoint class check for CaLiGraph took 0.23598241806030273s
Consistency | Check Misplaced properties for CaLiGraph took 60.866897106170654s
Consistency | Misplaced classes for CaLiGraph took 0.4692714214324951s
Consistency | Check Ontology hijacking for CaLiGraph took 2.085568904876709s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.4336621761322021s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.72114014625549s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.037459373474121094s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4312727451324463s
Security | Sign check for CaLiGraph took 0.24039840698242188s
Availability | Check URIs Dereferenciability for CaLiGraph took 9.540903091430664s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.3077208995819092s
Reputation | Calculation of the PageRank for CaLiGraph took 0.024634838104248047s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0008213520050048828s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 4.410743713378906e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 9.5367431640625e-06s
INFO | --- Analysis for CaLiGraph took 1370.065289258957s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.24045443534851074s
Availability | VoID file availability check for CaLiGraph took 0.00039696693420410156s
Extra | Recovery of all triples for CaLiGraph took 1.1303255558013916s
Performance | Total latancy measurement for CaLiGraph took 1.0676145553588867s
Amount of data | Number of triples check for CaLiGraph took 13.602035760879517s
Interoperability | New terms check for CaLiGraph took 2.0288987159729004s
Versatility | Languages check for CaLiGraph took 60.27420520782471s
Interpretability | Number of blank nodes check for CaLiGraph took 0.23366785049438477s
Security | Check HTTPS for CaLiGraph took 0.1266942024230957s
Interpretability | RDF structures check for CaLiGraph took 0.2363734245300293s
Versatility | Serialization formats check for CaLiGraph took 0.24096417427062988s
Availability | RDF dump link check for CaLiGraph took 0.23784279823303223s
License | MR license check for CaLiGraph took 0.23693132400512695s
License | HR license check for CaLiGraph took 60.26441478729248s
Amount of data | Number of property check for CaLiGraph took 0.23988986015319824s
Understandability | Number of label check for CaLiGraph took 3.2116518020629883s
Understandability | URI regex check for CaLiGraph took 0.48740673065185547s
Understandability | Vocabs check for CaLiGraph took 0.23558878898620605s
Verifiability | Authors check for CaLiGraph took 0.24044561386108398s
Verifiability | Publishers check for CaLiGraph took 0.2359614372253418s
Performance | Throughput check for CaLiGraph took 10.665639638900757s
Amount of data | Check the number of entities for CaLiGraph took 0.016440391540527344s
Verifiability | Contribs. check for CaLiGraph took 0.24112677574157715s
Interlinking | sameAs chians check for CaLiGraph took 0.643639087677002s
Interlinking | skos check for CaLiGraph took 0.2380826473236084s
Interlinking | skos check for CaLiGraph took 0.21318697929382324s
Timeliness | dataset update frequency check for CaLiGraph took 0.2385237216949463s
Currency | Creation date check for CaLiGraph took 0.47037267684936523s
Currency | Modification date check for CaLiGraph took 0.47057557106018066s
Rep.Conc. | URIs length for CaLiGraph took 60.94958806037903s
Interoperability | New vocabularies check for CaLiGraph took 5.4836273193359375e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.23674464225769043s
Accuracy | Check Functional Property for CaLiGraph took 0.2361900806427002s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.23481297492980957s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5359320640563965s
Accuracy | Check White space in annotation for CaLiGraph took 0.026339292526245117s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05010342597961426s
Consistency | Disjoint class check for CaLiGraph took 0.2393505573272705s
Consistency | Check Misplaced properties for CaLiGraph took 61.00606679916382s
Consistency | Misplaced classes for CaLiGraph took 0.46165919303894043s
Consistency | Check Ontology hijacking for CaLiGraph took 2.060100555419922s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.4138579368591309s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.67551302909851s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.030807971954345703s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.429229736328125s
Security | Sign check for CaLiGraph took 0.23653745651245117s
Availability | Check URIs Dereferenciability for CaLiGraph took 10.043410062789917s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.4464297294616699s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02107691764831543s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.891654968261719e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.9073486328125e-06s
Believability | Calculation of trust value for CaLiGraph took 6.67572021484375e-06s
INFO | --- Analysis for caligraph took 1369.867841243744s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.05608034133911133s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.26079344749450684s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020834684371948242s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.170967102050781e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 4.76837158203125e-06s
INFO | --- Analysis for cap-italy-rdf took 2.547259569168091s
Availability | SPARQL endpoint availability check for person took 8.7738037109375e-05s
Availability | VoID file availability check for person took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for person took 0.2662034034729004s
Reputation | Calculation of the PageRank for person took 0.02074289321899414s
Interlinking | Calculation of Degree of Connection for person took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for person took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for person took 3.075599670410156e-05s
Believability | Calculation of trust value for person took 1.0013580322265625e-05s
INFO | --- Analysis for card took 2.4268605709075928s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 9.369850158691406e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2697477340698242s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020912885665893555s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.1484832763671875e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.9486212730407715s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.2111818790435791s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.2632162570953369s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.022480249404907227s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 3.838539123535156e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 9.298324584960938e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2.6930675506591797s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.696846008300781e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0003223419189453125s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.26438117027282715s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020816564559936523s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00012445449829101562s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.3828277587890625e-05s
INFO | --- Analysis for ce4r took 31.189234018325806s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4128894805908203s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005407333374023438s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.0318753719329834s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7253892421722412s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18822932243347168s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.5769352912902832s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 23.248671770095825s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1755833625793457s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3230557441711426s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1603395938873291s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15210270881652832s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5530767440795898s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7437891960144043s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14832615852355957s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7846729755401611s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.40108323097229004s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16737079620361328s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3461453914642334s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3953864574432373s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.935827016830444s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.653236389160156e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2248997688293457s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20702242851257324s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 1.244476079940796s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14882659912109375s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1612250804901123s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6768894195556641s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4082043170928955s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 1.3630669116973877s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17594671249389648s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.23532772064208984s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.19953560829162598s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6075563430786133s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.029544353485107422s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.027866125106811523s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21130800247192383s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 0.7332713603973389s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.8092851638793945s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.288170576095581s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.5332186222076416s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03342866897583008s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.20493555068969727s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14656901359558105s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2770.6282629966736s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.6196510791778564s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.458427429199219e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.1920928955078125e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.3113021850585938e-05s
INFO | --- Analysis for ceo took 2857.7811436653137s
Availability | SPARQL endpoint availability check for Chat Game corpus took 0.00011181831359863281s
Availability | VoID file availability check for Chat Game corpus took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.272186279296875s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.022721290588378906s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.6716461181640625e-05s
Believability | Calculation of trust value for Chat Game corpus took 9.775161743164062e-06s
INFO | --- Analysis for chat-game-corpus took 12.551357746124268s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 8.726119995117188e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008122920989990234s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.2799050807952881s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02112579345703125s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.340576171875e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.0013580322265625e-05s
INFO | --- Analysis for chem2bio2rdf took 133.09556484222412s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5472652912139893s
Availability | VoID file availability check for ChEMBL RDF took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.26666712760925293s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02121424674987793s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.76837158203125e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.0013580322265625e-05s
INFO | --- Analysis for chembl-rdf took 3.6173999309539795s
Availability | SPARQL endpoint availability check for chemdb  dataset took 0.7714383602142334s
Availability | VoID file availability check for chemdb  dataset took 0.00028586387634277344s
Extra | Recovery of all triples for chemdb  dataset took 4.8512654304504395s
Performance | Total latancy measurement for chemdb  dataset took 2.464142322540283s
Amount of data | Number of triples check for chemdb  dataset took 0.530780553817749s
Interoperability | New terms check for chemdb  dataset took 3.383314847946167s
Versatility | Languages check for chemdb  dataset took 22.249043703079224s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5101919174194336s
Interpretability | RDF structures check for chemdb  dataset took 0.5960485935211182s
Versatility | Serialization formats check for chemdb  dataset took 0.569467306137085s
Availability | RDF dump link check for chemdb  dataset took 0.49418115615844727s
License | MR license check for chemdb  dataset took 0.6987907886505127s
License | HR license check for chemdb  dataset took 3.1789278984069824s
Amount of data | Number of property check for chemdb  dataset took 0.525073766708374s
Understandability | Number of label check for chemdb  dataset took 0.9854228496551514s
Understandability | URI regex check for chemdb  dataset took 1.0618774890899658s
Understandability | Vocabs check for chemdb  dataset took 0.5157938003540039s
Verifiability | Authors check for chemdb  dataset took 0.559783935546875s
Verifiability | Publishers check for chemdb  dataset took 0.5258862972259521s
Performance | Throughput check for chemdb  dataset took 14.609341382980347s
Amount of data | Check the number of entities for chemdb  dataset took 0.00010561943054199219s
Verifiability | Contribs. check for chemdb  dataset took 0.5081474781036377s
Interlinking | sameAs chians check for chemdb  dataset took 0.5646557807922363s
Interlinking | skos check for chemdb  dataset took 0.6131970882415771s
Interlinking | skos check for chemdb  dataset took 0.49286484718322754s
Timeliness | dataset update frequency check for chemdb  dataset took 0.5017573833465576s
Currency | Creation date check for chemdb  dataset took 1.0155484676361084s
Currency | Modification date check for chemdb  dataset took 0.998687744140625s
Rep.Conc. | URIs length for chemdb  dataset took 2.889749765396118s
Interoperability | New vocabularies check for chemdb  dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5058307647705078s
Accuracy | Check Functional Property for chemdb  dataset took 0.561499834060669s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.5411276817321777s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.2076168060302734s
Accuracy | Check White space in annotation for chemdb  dataset took 0.03061366081237793s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03352808952331543s
Consistency | Disjoint class check for chemdb  dataset took 0.4896509647369385s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2053933143615723s
Consistency | Misplaced classes for chemdb  dataset took 0.6057548522949219s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.4277708530426025s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.3206596374511719s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.0263164043426514s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03330254554748535s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5189847946166992s
Security | Sign check for chemdb  dataset took 0.6051750183105469s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2463.99587726593s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.4716336727142334s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.021906614303588867s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.033348083496094e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb  dataset took 1.1920928955078125e-05s
INFO | --- Analysis for chemdb-basicInfo took 4624.222394227982s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5162031650543213s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0005357265472412109s
Extra | Recovery of all triples for chemdb estimated properties dataset took 6.053615093231201s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.4548354148864746s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5293731689453125s
Interoperability | New terms check for chemdb estimated properties dataset took 3.4124972820281982s
Versatility | Languages check for chemdb estimated properties dataset took 22.409460306167603s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5146725177764893s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5129361152648926s
Versatility | Serialization formats check for chemdb estimated properties dataset took 0.5132355690002441s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.48529696464538574s
License | MR license check for chemdb estimated properties dataset took 0.4851248264312744s
License | HR license check for chemdb estimated properties dataset took 3.058757781982422s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5128061771392822s
Understandability | Number of label check for chemdb estimated properties dataset took 0.5207195281982422s
Understandability | URI regex check for chemdb estimated properties dataset took 0.9691298007965088s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.4849972724914551s
Verifiability | Authors check for chemdb estimated properties dataset took 0.485001802444458s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.4835026264190674s
Performance | Throughput check for chemdb estimated properties dataset took 14.616063833236694s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 7.271766662597656e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.4941215515136719s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.5081238746643066s
Interlinking | skos check for chemdb estimated properties dataset took 0.49206113815307617s
Interlinking | skos check for chemdb estimated properties dataset took 0.48449277877807617s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.48429393768310547s
Currency | Creation date check for chemdb estimated properties dataset took 1.0009033679962158s
Currency | Modification date check for chemdb estimated properties dataset took 1.0004234313964844s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 2.887052059173584s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.4959537982940674s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.5079820156097412s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.4918498992919922s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 2.1208250522613525s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.04037737846374512s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03356766700744629s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.4960939884185791s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2058629989624023s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6121871471405029s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.384143590927124s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.2786915302276611s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.9795715808868408s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03707289695739746s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5071229934692383s
Security | Sign check for chemdb estimated properties dataset took 0.48201537132263184s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2450.782649040222s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.45661163330078125s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.021749258041381836s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 5.5789947509765625e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.0251998901367188e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 4598.977092266083s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.505925178527832s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0003139972686767578s
Extra | Recovery of all triples for chemdb phase transition dataset took 4.863945484161377s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.4555306434631348s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5377764701843262s
Interoperability | New terms check for chemdb phase transition dataset took 3.3949365615844727s
Versatility | Languages check for chemdb phase transition dataset took 22.98092246055603s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5142581462860107s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5255069732666016s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.902594804763794s
Availability | RDF dump link check for chemdb phase transition dataset took 0.6555287837982178s
License | MR license check for chemdb phase transition dataset took 1.4941048622131348s
License | HR license check for chemdb phase transition dataset took 3.433748722076416s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5109584331512451s
Understandability | Number of label check for chemdb phase transition dataset took 2.4773871898651123s
Understandability | URI regex check for chemdb phase transition dataset took 1.1305384635925293s
Understandability | Vocabs check for chemdb phase transition dataset took 0.5497171878814697s
Verifiability | Authors check for chemdb phase transition dataset took 0.5680375099182129s
Verifiability | Publishers check for chemdb phase transition dataset took 0.5399341583251953s
Performance | Throughput check for chemdb phase transition dataset took 14.185497999191284s
Amount of data | Check the number of entities for chemdb phase transition dataset took 6.413459777832031e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.5445206165313721s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.589946985244751s
Interlinking | skos check for chemdb phase transition dataset took 0.7092211246490479s
Interlinking | skos check for chemdb phase transition dataset took 0.49170970916748047s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.5571889877319336s
Currency | Creation date check for chemdb phase transition dataset took 1.074693202972412s
Currency | Modification date check for chemdb phase transition dataset took 1.0084381103515625s
Rep.Conc. | URIs length for chemdb phase transition dataset took 2.88767409324646s
Interoperability | New vocabularies check for chemdb phase transition dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.48464465141296387s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.5523881912231445s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.5352323055267334s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 2.1755592823028564s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.030988454818725586s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.033370018005371094s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.5383598804473877s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2026629447937012s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.5911564826965332s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.3697564601898193s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.282055139541626s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 1.9754133224487305s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03329014778137207s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5120322704315186s
Security | Sign check for chemdb phase transition dataset took 0.7397556304931641s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2452.1686050891876s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.46835899353027344s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.02117133140563965s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.9604644775390625e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-phaseTransition took 4589.267920255661s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5116217136383057s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.00027251243591308594s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 13.16623854637146s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.452080011367798s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5325689315795898s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.9122002124786377s
Versatility | Languages check for chemdb thermochemistry dataset took 23.16894841194153s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5107479095458984s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5111253261566162s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.5086650848388672s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.4826085567474365s
License | MR license check for chemdb thermochemistry dataset took 0.48624444007873535s
License | HR license check for chemdb thermochemistry dataset took 3.1584973335266113s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5223731994628906s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.5205059051513672s
Understandability | URI regex check for chemdb thermochemistry dataset took 0.9680836200714111s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.4856290817260742s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.6319875717163086s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.49326324462890625s
Performance | Throughput check for chemdb thermochemistry dataset took 14.605700969696045s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 6.914138793945312e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.49265289306640625s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.5107259750366211s
Interlinking | skos check for chemdb thermochemistry dataset took 0.4934678077697754s
Interlinking | skos check for chemdb thermochemistry dataset took 0.49856138229370117s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.5811209678649902s
Currency | Creation date check for chemdb thermochemistry dataset took 1.0118422508239746s
Currency | Modification date check for chemdb thermochemistry dataset took 0.9993491172790527s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.3528072834014893s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.49460315704345703s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.5077002048492432s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.48249387741088867s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 2.835141181945801s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.031013965606689453s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03641200065612793s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.49732351303100586s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2057909965515137s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6155204772949219s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.888428211212158s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.3194022178649902s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.018688440322876s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.036058902740478516s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5199203491210938s
Security | Sign check for chemdb thermochemistry dataset took 0.48972058296203613s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2454.6988286972046s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.47585153579711914s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.02239704132080078s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.389617919921875e-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.0013580322265625e-05s
INFO | --- Analysis for chemdb-thermochemistry took 4603.092429161072s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 9.083747863769531e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.2668280601501465s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.021094083786010742s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 9.775161743164062e-06s
INFO | --- Analysis for chempedia-rdf took 9.312632322311401s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.172325134277344e-05s
Availability | VoID file availability check for Chiman Maru took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.2627568244934082s
Reputation | Calculation of the PageRank for Chiman Maru took 0.02323174476623535s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.24249267578125e-05s
Believability | Calculation of trust value for Chiman Maru took 1.049041748046875e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.4007816314697266s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.97493052482605s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.27800512313842773s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.3855438232421875e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.3828277587890625e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 799.0053834915161s
Availability | SPARQL endpoint availability check for Chronicling America took 4.649162292480469e-05s
Availability | VoID file availability check for Chronicling America took 0.0003082752227783203s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.275127649307251s
Reputation | Calculation of the PageRank for Chronicling America took 0.020993947982788086s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010061264038085938s
Believability | Calculation of trust value for Chronicling America took 1.0251998901367188e-05s
INFO | --- Analysis for chronicling-america took 10.591122388839722s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 7.824202537536621s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006716251373291016s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 83.07105350494385s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.527848243713379s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 1.413658857345581s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.162320375442505s
Versatility | Languages check for Cultural Heritage Thesaurus took 7.743654727935791s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 1.9248342514038086s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.28805017471313477s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.3222942352294922s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 5.5677649974823s
License | MR license check for Cultural Heritage Thesaurus took 0.3079354763031006s
License | HR license check for Cultural Heritage Thesaurus took 0.7966246604919434s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.301525354385376s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.46639585494995117s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5766589641571045s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.279038667678833s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.2944955825805664s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.3237600326538086s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.772138833999634s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 3.266334533691406e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.28891563415527344s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.32047367095947266s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.31014060974121094s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.4208524227142334s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.344346284866333s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.7307534217834473s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.7008829116821289s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 32.180705070495605s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 0.8006727695465088s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.3313586711883545s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.32819080352783203s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.28178906440734863s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 6.663467645645142s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.2257072925567627s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.31232142448425293s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 3.090134620666504s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.32668399810791016s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 7.788820505142212s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 4.272942781448364s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00014209747314453125s
Security | Sign check for Cultural Heritage Thesaurus took 0.3161895275115967s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 391.26487827301025s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.36315202713012695s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.029788732528686523s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 9.799003601074219e-05s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.7536134719848633s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for cht took 609.2249858379364s
Availability | SPARQL endpoint availability check for ciard-ring took 8.654594421386719e-05s
Availability | VoID file availability check for ciard-ring took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2748732566833496s
Reputation | Calculation of the PageRank for ciard-ring took 0.02094435691833496s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.744529724121094e-05s
Believability | Calculation of trust value for ciard-ring took 1.33514404296875e-05s
INFO | --- Analysis for ciard-ring took 10.410608053207397s
Availability | SPARQL endpoint availability check for Cine Figure took 4.38690185546875e-05s
Availability | VoID file availability check for Cine Figure took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.2859952449798584s
Reputation | Calculation of the PageRank for Cine Figure took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.482269287109375e-05s
Believability | Calculation of trust value for Cine Figure took 7.867813110351562e-06s
INFO | --- Analysis for Cine_Figure took 2.66336727142334s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 2.477512836456299s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.3089900016784668s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.0219573974609375s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.57763671875e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 11.633172988891602s
Availability | SPARQL endpoint availability check for CIPFA took 8.702278137207031e-05s
Availability | VoID file availability check for CIPFA took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for CIPFA took 0.3065927028656006s
Reputation | Calculation of the PageRank for CIPFA took 0.020810365676879883s
Interlinking | Calculation of Degree of Connection for CIPFA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.6716461181640625e-05s
Believability | Calculation of trust value for CIPFA took 9.059906005859375e-06s
INFO | --- Analysis for cipfa took 2.884864091873169s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.0438494682312s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0007638931274414062s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.3045380115509033s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0003943443298339844s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.2636184692382812e-05s
INFO | --- Analysis for ckan took 262.85321974754333s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5982034206390381s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.3012523651123047s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.021477222442626953s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.62396240234375e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for CLaSSES took 4.445531368255615s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.291534423828125e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2945821285247803s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 2.9802322387695312e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.33514404296875e-05s
INFO | --- Analysis for classical_temples took 4.785401821136475s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.1986610889434814s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2935206890106201s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020258665084838867s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.559226989746094e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 9.5367431640625e-06s
INFO | --- Analysis for clean-energy-data-reegle took 5.712870121002197s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.410743713378906e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2874166965484619s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02133631706237793s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.605552673339844e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.1920928955078125e-05s
INFO | --- Analysis for clld-afbo took 3.766247272491455s
Availability | SPARQL endpoint availability check for CLLD-APICS took 8.487701416015625e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.27696943283081055s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.021888256072998047s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.891654968261719e-05s
Believability | Calculation of trust value for CLLD-APICS took 9.5367431640625e-06s
INFO | --- Analysis for clld-apics took 3.9481654167175293s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 0.00010347366333007812s
Availability | VoID file availability check for CLLD-EWAVE took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.2848672866821289s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.02104783058166504s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.933906555175781e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 9.5367431640625e-06s
INFO | --- Analysis for clld-ewave took 3.6788482666015625s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.2438507080078125e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2885775566101074s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.022898197174072266s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.655952453613281e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.0251998901367188e-05s
INFO | --- Analysis for clld-glottolog took 4.019608497619629s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.4345855712890625e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.2892730236053467s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.02199244499206543s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.368492126464844e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.3113021850585938e-05s
INFO | --- Analysis for clld-phoible took 3.754744052886963s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.487701416015625e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.3291740417480469s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.02254509925842285s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.700920104980469e-05s
Believability | Calculation of trust value for CLLD-SAILS took 9.059906005859375e-06s
INFO | --- Analysis for clld-sails took 3.847792863845825s
Availability | SPARQL endpoint availability check for CLLD-WALS took 8.797645568847656e-05s
Availability | VoID file availability check for CLLD-WALS took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2893989086151123s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020860910415649414s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 7.987022399902344e-05s
Believability | Calculation of trust value for CLLD-WALS took 9.298324584960938e-06s
INFO | --- Analysis for clld-wals took 3.975897789001465s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 9.298324584960938e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.29796552658081055s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.021076440811157227s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.82012939453125e-05s
Believability | Calculation of trust value for CLLD-WOLD took 9.298324584960938e-06s
INFO | --- Analysis for clld-wold took 3.832794666290283s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.2598381042480469s
Availability | VoID file availability check for Cooperation Databank took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.27691149711608887s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.021963834762573242s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.790855407714844e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.2636184692382812e-05s
INFO | --- Analysis for CoDa took 3.160404920578003s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.056532382965088s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.299837589263916s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.022553682327270508s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.24249267578125e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 8.344650268554688e-06s
INFO | --- Analysis for coins-openuplabs took 3.753908157348633s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.4450178146362305s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.27463769912719727s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.021049022674560547s
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.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.559226989746094e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.049041748046875e-05s
INFO | --- Analysis for CoLChina_sp2000 took 7.51579737663269s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.20108509063720703s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.29743313789367676s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02113199234008789s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.124641418457031e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.3113021850585938e-05s
INFO | --- Analysis for colinda took 2.9488797187805176s
Availability | SPARQL endpoint availability check for CN  2012 took 25.26487922668457s
Availability | VoID file availability check for CN  2012 took 0.0007634162902832031s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.3549790382385254s
Reputation | Calculation of the PageRank for CN  2012 took 0.021052122116088867s
Interlinking | Calculation of Degree of Connection for CN  2012 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.5299530029296875e-05s
Believability | Calculation of trust value for CN  2012 took 4.5299530029296875e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 124.70790672302246s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.40659499168395996s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.27309250831604004s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 9.775161743164062e-06s
INFO | --- Analysis for CompHistSem took 4.096215724945068s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 1.782339334487915s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.29768967628479004s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.022518157958984375s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.695487976074219e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.2874603271484375e-05s
INFO | --- Analysis for comsode-d3-2 took 7.2847466468811035s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 0.00010275840759277344s
Availability | VoID file availability check for 2011 US Congress People took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2781484127044678s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.021559715270996094s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.463859558105469e-05s
Believability | Calculation of trust value for 2011 US Congress People took 7.62939453125e-06s
INFO | --- Analysis for congresspeople took 3.276034116744995s
Availability | SPARQL endpoint availability check for MIMO took 0.2789039611816406s
Availability | VoID file availability check for MIMO took 0.0007944107055664062s
Completeness | Calculation of interlinking completeness for MIMO took 0.32415246963500977s
Reputation | Calculation of the PageRank for MIMO took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for MIMO took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.3113021850585938e-05s
Believability | Calculation of trust value for MIMO took 1.239776611328125e-05s
INFO | --- Analysis for CONNECTED took 3.954258680343628s
Availability | SPARQL endpoint availability check for Copyright Free Music took 8.869171142578125e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.2793412208557129s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020233631134033203s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.9802322387695312e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.1920928955078125e-05s
INFO | --- Analysis for Copyright_Free_Music took 3.7183098793029785s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 9.202957153320312e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.35048651695251465s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020356178283691406s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.651878356933594e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.0728836059570312e-05s
INFO | --- Analysis for copyrighttermbank took 35.047990798950195s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.8438959121704102s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0007748603820800781s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.31129002571105957s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020381450653076172s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.647804260253906e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.239776611328125e-05s
INFO | --- Analysis for core took 6.972998857498169s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.5635547637939453s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005183219909667969s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 105.63599109649658s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 1.0657610893249512s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.277478694915771s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.059309244155884s
Versatility | Languages check for Corine linked dataset @PSNC took 300.1726908683777s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.2709927558898926s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.4030318260192871s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 10.586589574813843s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.36452674865722656s
License | MR license check for Corine linked dataset @PSNC took 0.9100968837738037s
License | HR license check for Corine linked dataset @PSNC took 300.2484004497528s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.21119141578674316s
Understandability | Number of label check for Corine linked dataset @PSNC took 3.6033689975738525s
Understandability | URI regex check for Corine linked dataset @PSNC took 1.342249870300293s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.6754703521728516s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.21353697776794434s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.23498177528381348s
Performance | Throughput check for Corine linked dataset @PSNC took 11.41366195678711s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 6.866455078125e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.2202603816986084s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.2957143783569336s
Interlinking | skos check for Corine linked dataset @PSNC took 0.5103905200958252s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4866800308227539s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.402169704437256s
Currency | Creation date check for Corine linked dataset @PSNC took 0.48513007164001465s
Currency | Modification date check for Corine linked dataset @PSNC took 0.28049135208129883s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 151.01038098335266s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.20976972579956055s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.4759383201599121s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.5176723003387451s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 36.96373677253723s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6892776489257812s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.579887628555298s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.2007768154144287s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 85.73972392082214s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.455764770507812s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 34.299391984939575s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.4160616397857666s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 87.03847551345825s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.8174729347229004s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.5506324768066406s
Security | Sign check for Corine linked dataset @PSNC took 1.9715800285339355s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 10.285097122192383s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.43906545639038086s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for Corine_linked_dataset took 2259.4149916172028s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 0.00010061264038085938s
Availability | VoID file availability check for Cornetto1.2 took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.2807950973510742s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02247333526611328s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 6.008148193359375e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.049041748046875e-05s
INFO | --- Analysis for cornetto took 13.203494548797607s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.1639420986175537s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005881786346435547s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 204.38000774383545s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6089973449707031s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 99.00449895858765s
Interoperability | New terms check for Corporate Body Named Authority List  took 57.66194438934326s
Versatility | Languages check for Corporate Body Named Authority List  took 300.026558637619s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 15.845545768737793s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.31971025466918945s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.6544194221496582s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 4.312721490859985s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.2201097011566162s
License | MR license check for Corporate Body Named Authority List  took 0.41690969467163086s
License | HR license check for Corporate Body Named Authority List  took 300.0553319454193s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.18728899955749512s
Understandability | Number of label check for Corporate Body Named Authority List  took 2.161085605621338s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.35548996925354004s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.09140348434448242s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.19370245933532715s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.2627573013305664s
Performance | Throughput check for Corporate Body Named Authority List  took 10.517853498458862s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 0.00011157989501953125s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.12066817283630371s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 6.5774760246276855s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3322932720184326s
Interlinking | skos check for Corporate Body Named Authority List  took 0.37200427055358887s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.2979705333709717s
Currency | Creation date check for Corporate Body Named Authority List  took 0.707791805267334s
Currency | Modification date check for Corporate Body Named Authority List  took 0.17325544357299805s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 410.5863630771637s
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.1687760353088379s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.18409347534179688s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.16981744766235352s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 39.6299467086792s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.2251274585723877s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6384804248809814s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.19727635383605957s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.4461028575897s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.44747519493103s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 35.830512285232544s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.643925666809082s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.40707635879517s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.137206554412842s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.38014864921569824s
Security | Sign check for Corporate Body Named Authority List  took 0.4527933597564697s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 11.254299402236938s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.8419196605682373s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.022429943084716797s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 6.151199340820312e-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 8.106231689453125e-06s
INFO | --- Analysis for corporate-body took 14925.470603227615s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.6444985866546631s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0007395744323730469s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.29979920387268066s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020958662033081055s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 4.553794860839844e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.33514404296875e-05s
INFO | --- Analysis for CorpusFibonacci took 4.3564064502716064s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.14342021942138672s
Availability | VoID file availability check for Country Name Authority List took 0.00039124488830566406s
Extra | Recovery of all triples for Country Name Authority List took 186.53742718696594s
Performance | Total latancy measurement for Country Name Authority List took 0.5915496349334717s
Amount of data | Number of triples check for Country Name Authority List took 40.00868630409241s
Interoperability | New terms check for Country Name Authority List took 58.63937282562256s
Versatility | Languages check for Country Name Authority List took 300.062162399292s
Interpretability | Number of blank nodes check for Country Name Authority List took 14.696143388748169s
Security | Check HTTPS for Country Name Authority List took 0.3449060916900635s
Interpretability | RDF structures check for Country Name Authority List took 0.3674609661102295s
Versatility | Serialization formats check for Country Name Authority List took 3.375157356262207s
Availability | RDF dump link check for Country Name Authority List took 0.22925806045532227s
License | MR license check for Country Name Authority List took 0.5587317943572998s
License | HR license check for Country Name Authority List took 300.09700989723206s
Amount of data | Number of property check for Country Name Authority List took 0.24121737480163574s
Understandability | Number of label check for Country Name Authority List took 1.519247055053711s
Understandability | URI regex check for Country Name Authority List took 0.3912498950958252s
Understandability | Vocabs check for Country Name Authority List took 0.10349750518798828s
Verifiability | Authors check for Country Name Authority List took 0.20509934425354004s
Verifiability | Publishers check for Country Name Authority List took 0.19639277458190918s
Performance | Throughput check for Country Name Authority List took 10.981354713439941s
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.18940162658691406s
Interlinking | sameAs chians check for Country Name Authority List took 6.4582600593566895s
Interlinking | skos check for Country Name Authority List took 0.17126965522766113s
Interlinking | skos check for Country Name Authority List took 0.4558126926422119s
Timeliness | dataset update frequency check for Country Name Authority List took 0.4282515048980713s
Currency | Creation date check for Country Name Authority List took 0.4483497142791748s
Currency | Modification date check for Country Name Authority List took 0.15001559257507324s
Rep.Conc. | URIs length for Country Name Authority List took 409.6363980770111s
Interoperability | New vocabularies check for Country Name Authority List took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.44943690299987793s
Accuracy | Check Functional Property for Country Name Authority List took 0.1988837718963623s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.15685749053955078s
Accuracy | Check Empty annotation labels for Country Name Authority List took 40.76351284980774s
Accuracy | Check White space in annotation for Country Name Authority List took 3.1957950592041016s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6461803913116455s
Consistency | Disjoint class check for Country Name Authority List took 0.16367530822753906s
Consistency | Check Misplaced properties for Country Name Authority List took 300.416472196579s
Consistency | Misplaced classes for Country Name Authority List took 8.619858980178833s
Consistency | Check Ontology hijacking for Country Name Authority List took 36.18203520774841s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.758720874786377s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.555545091629s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.157870054244995s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.4233856201171875s
Security | Sign check for Country Name Authority List took 0.7240302562713623s
Availability | Check URIs Dereferenciability for Country Name Authority List took 11.490012168884277s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.3221149444580078s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.021203994750976562s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 2.1457672119140625e-06s
Believability | Calculation of trust value for Country Name Authority List took 1.33514404296875e-05s
INFO | --- Analysis for country-authority-list took 15191.714750051498s
Availability | SPARQL endpoint availability check for Courts thesaurus took 4.601478576660156e-05s
Availability | VoID file availability check for Courts thesaurus took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.3440523147583008s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.02178668975830078s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.081031799316406e-05s
Believability | Calculation of trust value for Courts thesaurus took 5.9604644775390625e-06s
INFO | --- Analysis for courts-thesaurus took 3.283933639526367s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.0001010894775390625s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.3028717041015625s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.021033763885498047s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.177757263183594e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.0967254638671875e-05s
INFO | --- Analysis for Covid-on-the-Web took 3.4222962856292725s
Availability | SPARQL endpoint availability check for CPA 2008 took 8.535385131835938e-05s
Availability | VoID file availability check for CPA 2008 took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.30619215965270996s
Reputation | Calculation of the PageRank for CPA 2008 took 0.020743846893310547s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.695487976074219e-05s
Believability | Calculation of trust value for CPA 2008 took 1.2159347534179688e-05s
INFO | --- Analysis for cpa-2008 took 3.336596727371216s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 3.886222839355469e-05s
Availability | VoID file availability check for Cooperative Patent Classification took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.28685975074768066s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02105545997619629s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 3.647804260253906e-05s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.3589859008789062e-05s
INFO | --- Analysis for CPC took 3.274203300476074s
Availability | SPARQL endpoint availability check for CPC 2008 took 4.7206878662109375e-05s
Availability | VoID file availability check for CPC 2008 took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.2954990863800049s
Reputation | Calculation of the PageRank for CPC 2008 took 0.022411584854125977s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.220008850097656e-05s
Believability | Calculation of trust value for CPC 2008 took 1.2159347534179688e-05s
INFO | --- Analysis for cpc-2008 took 3.25868558883667s
Availability | SPARQL endpoint availability check for CPV  2003 took 8.296966552734375e-05s
Availability | VoID file availability check for CPV  2003 took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.28418850898742676s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02118968963623047s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.8623809814453125e-05s
Believability | Calculation of trust value for CPV  2003 took 6.67572021484375e-06s
INFO | --- Analysis for cpv-2003 took 3.2283644676208496s
Availability | SPARQL endpoint availability check for CPV 2008 took 4.601478576660156e-05s
Availability | VoID file availability check for CPV 2008 took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.27856922149658203s
Reputation | Calculation of the PageRank for CPV 2008 took 0.02294182777404785s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.982948303222656e-05s
Believability | Calculation of trust value for CPV 2008 took 1.049041748046875e-05s
INFO | --- Analysis for cpv-2008 took 3.224548101425171s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 8.416175842285156e-05s
Availability | VoID file availability check for crowdsourcing-fb took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.2606837749481201s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.02119302749633789s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.029273986816406e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 8.58306884765625e-06s
INFO | --- Analysis for crowdsourcing-fb took 3.2030982971191406s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 4.267692565917969e-05s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.34152746200561523s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.8160552978515625e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 1.239776611328125e-05s
INFO | --- Analysis for ctic-public-dataset took 3.5661139488220215s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 2.6321628093719482s
Availability | VoID file availability check for CulturaLinkedData took 0.0004734992980957031s
Extra | Recovery of all triples for CulturaLinkedData took 142.78587865829468s
Performance | Total latancy measurement for CulturaLinkedData took 2.6537911891937256s
Amount of data | Number of triples check for CulturaLinkedData took 0.7260870933532715s
Interoperability | New terms check for CulturaLinkedData took 4.071446180343628s
Versatility | Languages check for CulturaLinkedData took 63.76579999923706s
Interpretability | Number of blank nodes check for CulturaLinkedData took 0.2244105339050293s
Interpretability | RDF structures check for CulturaLinkedData took 2.364175796508789s
Versatility | Serialization formats check for CulturaLinkedData took 2.3059890270233154s
Availability | RDF dump link check for CulturaLinkedData took 2.102259397506714s
License | MR license check for CulturaLinkedData took 0.7368438243865967s
License | HR license check for CulturaLinkedData took 61.92887210845947s
Amount of data | Number of property check for CulturaLinkedData took 0.196854829788208s
Understandability | Number of label check for CulturaLinkedData took 1.0940990447998047s
Understandability | URI regex check for CulturaLinkedData took 0.5898034572601318s
Understandability | Vocabs check for CulturaLinkedData took 2.0050220489501953s
Verifiability | Authors check for CulturaLinkedData took 0.3038148880004883s
Verifiability | Publishers check for CulturaLinkedData took 2.0175719261169434s
Performance | Throughput check for CulturaLinkedData took 21.68640422821045s
Amount of data | Check the number of entities for CulturaLinkedData took 7.653236389160156e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.27440476417541504s
Interlinking | sameAs chians check for CulturaLinkedData took 2.1459460258483887s
Interlinking | skos check for CulturaLinkedData took 2.286128044128418s
Interlinking | skos check for CulturaLinkedData took 2.0145294666290283s
Timeliness | dataset update frequency check for CulturaLinkedData took 2.1478374004364014s
Currency | Creation date check for CulturaLinkedData took 2.29620099067688s
Currency | Modification date check for CulturaLinkedData took 0.3700735569000244s
Rep.Conc. | URIs length for CulturaLinkedData took 52.384140729904175s
Interoperability | New vocabularies check for CulturaLinkedData took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.18195796012878418s
Accuracy | Check Functional Property for CulturaLinkedData took 1.937387466430664s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.1877593994140625s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 46.38500356674194s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6230270862579346s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.292626142501831s
Consistency | Disjoint class check for CulturaLinkedData took 0.20240187644958496s
Consistency | Check Misplaced properties for CulturaLinkedData took 9.918715238571167s
Consistency | Misplaced classes for CulturaLinkedData took 4.203101634979248s
Consistency | Check Ontology hijacking for CulturaLinkedData took 41.20453214645386s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3106751441955566s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 11.213589668273926s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.4210538864135742s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 2.0579304695129395s
Security | Sign check for CulturaLinkedData took 0.8893096446990967s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 10.037552118301392s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.38945841789245605s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.0213623046875s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 3.814697265625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.33514404296875e-05s
INFO | --- Analysis for culturalinkeddata took 626.0226902961731s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 4.029273986816406e-05s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0002167224884033203s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.31584739685058594s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 6.198883056640625e-06s
INFO | --- Analysis for cz-ares-or took 3.3998100757598877s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.100799560546875e-05s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.27763938903808594s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02079606056213379s
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.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.600120544433594e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.7220458984375e-06s
INFO | --- Analysis for cz-ares-rzp took 3.276517152786255s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 6.771087646484375e-05s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0002167224884033203s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.28059816360473633s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.02042412757873535s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.3855438232421875e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 6.67572021484375e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.2056310176849365s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 3.981590270996094e-05s
Availability | VoID file availability check for Integrated pollution registry took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.26710033416748047s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.7670135498046875e-05s
Believability | Calculation of trust value for Integrated pollution registry took 6.4373016357421875e-06s
INFO | --- Analysis for cz-cenia-pollution took 3.136033773422241s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 4.1484832763671875e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.2979891300201416s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.743171691894531e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 6.4373016357421875e-06s
INFO | --- Analysis for cz-contracts took 3.743664026260376s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.20998024940490723s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2828700542449951s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.62396240234375e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ctia-bans took 5.147522687911987s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10882782936096191s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0009257793426513672s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.2830667495727539s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.6716461181640625e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 9.5367431640625e-06s
INFO | --- Analysis for cz-ctia-confiscations took 3.002933979034424s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11725282669067383s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.3710777759552002s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.021638154983520508s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.457069396972656e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 8.821487426757812e-06s
INFO | --- Analysis for cz-ctia-focus took 3.26621675491333s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.1152191162109375s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0010957717895507812s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2745084762573242s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.02100682258605957s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.2438507080078125e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-inspections took 3.016047477722168s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.11315608024597168s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0008003711700439453s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2803933620452881s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.4809112548828125e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 8.821487426757812e-06s
INFO | --- Analysis for cz-ctia-sanctions took 4.6336891651153564s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.20905709266662598s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.3182511329650879s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.743171691894531e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 9.059906005859375e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 3.226288318634033s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.10656881332397461s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0007848739624023438s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.29128575325012207s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020612001419067383s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.5762786865234375e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 9.059906005859375e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 3.12528395652771s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.6031539440155029s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.27904462814331055s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.7423856258392334s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.35120177268981934s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.30736494064331055s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.2438507080078125e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.633397102355957s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.39569902420043945s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.290740966796875s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.790855407714844e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0013580322265625e-05s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.5917327404022217s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.33446669578552246s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2873203754425049s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.021482467651367188s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0010266304016113281s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.8160552978515625e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.4395062923431396s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.3590102195739746s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.3051881790161133s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.022518157958984375s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.625164031982422s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3551201820373535s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007836818695068359s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.30060315132141113s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.504753112792969e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 8.58306884765625e-06s
INFO | --- Analysis for cz-czso-regions took 3.326249361038208s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3493540287017822s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.00039696693420410156s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.30120277404785156s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.02164006233215332s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.5055935382843018s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.4015188217163086s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.280015230178833s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020829439163208008s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.1961669921875e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.5811235904693604s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.37212705612182617s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2918703556060791s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.0233156681060791s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.6814775466918945s
Availability | SPARQL endpoint availability check for ATC groups took 0.11220741271972656s
Availability | VoID file availability check for ATC groups took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for ATC groups took 0.3101463317871094s
Reputation | Calculation of the PageRank for ATC groups took 0.0225830078125s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.62939453125e-05s
Believability | Calculation of trust value for ATC groups took 1.1682510375976562e-05s
INFO | --- Analysis for cz-eh-1-atc took 3.0276036262512207s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.12065291404724121s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.28797173500061035s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.022211313247680664s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.790855407714844e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 8.821487426757812e-06s
INFO | --- Analysis for cz-fulfillments took 3.117366313934326s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.0470888614654541s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.28806328773498535s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.023147106170654297s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.8160552978515625e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 9.298324584960938e-06s
INFO | --- Analysis for cz-ic took 3.530698299407959s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.12993788719177246s
Availability | VoID file availability check for List of Czech data boxes took 0.0006465911865234375s
Extra | Recovery of all triples for List of Czech data boxes took 142.834881067276s
Performance | Total latancy measurement for List of Czech data boxes took 0.5981330871582031s
Amount of data | Number of triples check for List of Czech data boxes took 10.830770492553711s
Interoperability | New terms check for List of Czech data boxes took 10.486510753631592s
Versatility | Languages check for List of Czech data boxes took 300.1832983493805s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.4397304058074951s
Interpretability | RDF structures check for List of Czech data boxes took 0.12778091430664062s
Versatility | Serialization formats check for List of Czech data boxes took 0.20449137687683105s
Availability | RDF dump link check for List of Czech data boxes took 17.443031311035156s
License | MR license check for List of Czech data boxes took 0.4973595142364502s
License | HR license check for List of Czech data boxes took 52.876776456832886s
Amount of data | Number of property check for List of Czech data boxes took 0.12431669235229492s
Understandability | Number of label check for List of Czech data boxes took 1.685487985610962s
Understandability | URI regex check for List of Czech data boxes took 0.4580698013305664s
Understandability | Vocabs check for List of Czech data boxes took 0.12362003326416016s
Verifiability | Authors check for List of Czech data boxes took 0.13152265548706055s
Verifiability | Publishers check for List of Czech data boxes took 0.12453365325927734s
Performance | Throughput check for List of Czech data boxes took 10.73453688621521s
Amount of data | Check the number of entities for List of Czech data boxes took 3.1587281227111816s
Verifiability | Contribs. check for List of Czech data boxes took 0.1283416748046875s
Interlinking | sameAs chians check for List of Czech data boxes took 0.42010498046875s
Interlinking | skos check for List of Czech data boxes took 0.19201898574829102s
Interlinking | skos check for List of Czech data boxes took 0.1066439151763916s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.22935223579406738s
Currency | Creation date check for List of Czech data boxes took 0.2560431957244873s
Currency | Modification date check for List of Czech data boxes took 0.12298941612243652s
Rep.Conc. | URIs length for List of Czech data boxes took 109.95987701416016s
Interoperability | New vocabularies check for List of Czech data boxes took 47.228609800338745s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.38306522369384766s
Accuracy | Check Functional Property for List of Czech data boxes took 0.1810905933380127s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.15704011917114258s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 30.111488103866577s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.077800750732422s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.617067575454712s
Consistency | Disjoint class check for List of Czech data boxes took 0.11054062843322754s
Consistency | Check Misplaced properties for List of Czech data boxes took 66.72445344924927s
Consistency | Misplaced classes for List of Czech data boxes took 7.585024833679199s
Consistency | Check Ontology hijacking for List of Czech data boxes took 30.126689434051514s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.3706510066986084s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 61.29805278778076s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.684633731842041s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.39353013038635254s
Security | Sign check for List of Czech data boxes took 0.14230012893676758s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 395.8403215408325s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.505303144454956s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.021240949630737305s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 43.83905625343323s
Believability | Calculation of trust value for List of Czech data boxes took 9.5367431640625e-06s
INFO | --- Analysis for cz-list-of-databoxes took 1700.487791776657s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12415766716003418s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.00034427642822265625s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 140.41847610473633s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6643307209014893s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.596934795379639s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.717650175094604s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1520802974701s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.2452921867370605s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1382157802581787s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.19791126251220703s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 14.977272272109985s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5109741687774658s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 55.34362840652466s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12351036071777344s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.7347691059112549s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.579216718673706s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1373462677001953s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13628482818603516s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12153005599975586s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.77725100517273s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.207090377807617s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1087806224822998s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.45656633377075195s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12142515182495117s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1388554573059082s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13771748542785645s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.22755074501037598s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11753559112548828s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 109.44222116470337s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 49.955960750579834s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4354979991912842s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.22277259826660156s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.172135591506958s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.426337718963623s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.105118751525879s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6736319065093994s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11486101150512695s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 66.7851722240448s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.8234007358551025s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 32.485246419906616s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3790984153747559s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 61.4553484916687s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.7074899673461914s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.36493372917175293s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12592077255249023s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 390.4465243816376s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6427388191223145s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.021323204040527344s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 32.39523959159851s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.5367431640625e-06s
INFO | --- Analysis for cz-nace took 1685.0591859817505s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.31333279609680176s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0006256103515625s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.1 took 412.54039883613586s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8092715740203857s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7633876800537109s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.3808586597442627s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.1 took 300.2254626750946s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8054101467132568s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.8159010410308838s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.376765489578247s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3925185203552246s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8966407775878906s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.3737075328826904s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.1754920482635498s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.40191650390625s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.5107517242431641s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.23591232299804688s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.483661413192749s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2969014644622803s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.1 took 10.638337135314941s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.866455078125e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2240922451019287s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2137007713317871s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4205455780029297s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.16812944412231445s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.4809300899505615s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.6781454086303711s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.436511754989624s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.1 took 86.73404598236084s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.1625652313232422s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2810811996459961s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.30408215522766113s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.1 took 70.44071388244629s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.453603506088257s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.641066074371338s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.224714994430542s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.9740593433380127s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.110835075378418s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.1 took 71.13272953033447s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.7787859439849854s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.235827445983887s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.212716817855835s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.23925089836120605s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.805584192276001s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.1 took 950.3784985542297s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7418115139007568s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.021365642547607422s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.00011897087097167969s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.1 took 4.291534423828125e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.049041748046875e-05s
INFO | --- Analysis for cz-nkod took 23677.390784740448s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.168137788772583s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0007765293121337891s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.33381152153015137s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.021366596221923828s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.790855407714844e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 9.059906005859375e-06s
INFO | --- Analysis for cz-orders took 3.2080633640289307s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.1909465789794922s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0006744861602783203s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 143.53044199943542s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.556746244430542s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.681489944458008s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.75580382347107s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.14127254486084s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.3836605548858643s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.13282132148742676s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.1768050193786621s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 15.246397733688354s
License | MR license check for Institutions of public power of the Czech Republic took 0.6021835803985596s
License | HR license check for Institutions of public power of the Czech Republic took 54.51636624336243s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.1381978988647461s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.5706212520599365s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.5390877723693848s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.12405562400817871s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.13020753860473633s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.11542725563049316s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.81340503692627s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.084486722946167s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.14376401901245117s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.41750311851501465s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.20581889152526855s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.11497187614440918s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.24987506866455078s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.24744892120361328s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.11179280281066895s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 109.85820627212524s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 37.20355725288391s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.3789784908294678s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.22043418884277344s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.24582123756408691s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 31.491312265396118s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0618529319763184s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.6108694076538086s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.11627817153930664s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 66.3468668460846s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.574800491333008s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 31.417434692382812s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.3712067604064941s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 60.94022870063782s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.6960866451263428s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.3593153953552246s
Security | Sign check for Institutions of public power of the Czech Republic took 0.17175936698913574s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 391.3866901397705s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.42862367630004883s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.020574092864990234s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 46.009084701538086s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-ovm took 1692.2796664237976s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.10840606689453125s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.3050193786621094s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.021938085556030273s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-ovm-agendas took 4.096193790435791s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2001492977142334s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006160736083984375s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 58.68023729324341s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5635907649993896s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 19.19048500061035s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 33.36545157432556s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.1752669811249s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14689350128173828s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.3592185974121094s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11851358413696289s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7808036804199219s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12815022468566895s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11535143852233887s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11603498458862305s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.8925635814666748s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.22626066207885742s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11723494529724121s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10928964614868164s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11364459991455078s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.46070909500122s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.033348083496094e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11470818519592285s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11546826362609863s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1385941505432129s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11354947090148926s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11751961708068848s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.21731209754943848s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1270434856414795s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 221.9640142917633s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1760237216949463s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12097287178039551s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12099695205688477s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 13.333884000778198s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.2011899948120117s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.6250457763671875s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11915016174316406s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 168.1654691696167s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.424956321716309s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 17.402183532714844s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.389374017715454s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 169.5398609638214s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.9650468826293945s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.25267815589904785s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12792277336120605s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.030239820480347s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6085278987884521s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.021364450454711914s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 4.76837158203125e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ruian took 1454.5566020011902s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7446944713592529s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.3031120300292969s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.022077560424804688s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.152557373046875e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 4.27524471282959s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.495471715927124s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.2785012722015381s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020561695098876953s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 7.62939453125e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.8909049034118652s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.5095694065093994s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.2849617004394531s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.02129077911376953s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 2.956390380859375e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 9.059906005859375e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.908968210220337s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.12011981010437012s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.32782554626464844s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.021273136138916016s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.266334533691406e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.2159347534179688e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.1543455123901367s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.11556744575500488s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2851285934448242s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020913124084472656s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.218650817871094e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 3.0914969444274902s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11703753471374512s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.3008906841278076s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.647804260253906e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.2636184692382812e-05s
INFO | --- Analysis for cz-sidc-drugs took 3.086648941040039s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.20002031326293945s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.00077056884765625s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 143.99173307418823s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.607306718826294s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.718671083450317s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.928282976150513s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1646785736084s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.4214980602264404s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.13473129272460938s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.17721080780029297s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 15.523503541946411s
License | MR license check for Summary types of Czech institutions of public power took 0.12569737434387207s
License | HR license check for Summary types of Czech institutions of public power took 52.61817693710327s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.10710382461547852s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.313446044921875s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.3659679889678955s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.1333789825439453s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.1135246753692627s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.10896658897399902s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.725512981414795s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.207289218902588s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.13883686065673828s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.4255695343017578s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.20703649520874023s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.1184835433959961s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.25071167945861816s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.25458669662475586s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.12988519668579102s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 110.31878542900085s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 42.048694133758545s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.3660011291503906s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.25952649116516113s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.24179983139038086s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 30.99005126953125s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.0906193256378174s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6322824954986572s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.12798833847045898s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 67.36069679260254s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.626418828964233s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 30.721847534179688s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.355238914489746s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 61.275474309921265s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.7021305561065674s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.3993706703186035s
Security | Sign check for Summary types of Czech institutions of public power took 0.16430997848510742s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 395.063364982605s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.6849398612976074s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02245044708251953s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 9.179115295410156e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 31.992990255355835s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 9.5367431640625e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 1686.5481007099152s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.11549639701843262s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.3018760681152344s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02285170555114746s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.838539123535156e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 3.212023973464966s
Availability | SPARQL endpoint availability check for State funding providers took 0.1049642562866211s
Availability | VoID file availability check for State funding providers took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for State funding providers took 0.28948497772216797s
Reputation | Calculation of the PageRank for State funding providers took 0.0218505859375s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.124641418457031e-05s
Believability | Calculation of trust value for State funding providers took 7.867813110351562e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.0187785625457764s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.10789108276367188s
Availability | VoID file availability check for Organizations active in R&D took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.2990245819091797s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.021282196044921875s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.0531158447265625e-05s
Believability | Calculation of trust value for Organizations active in R&D took 7.867813110351562e-06s
INFO | --- Analysis for cz-vavai-organizations took 3.3144493103027344s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.11288857460021973s
Availability | VoID file availability check for R&D Programmes took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.30040431022644043s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020483016967773438s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.2438507080078125e-05s
Believability | Calculation of trust value for R&D Programmes took 7.867813110351562e-06s
INFO | --- Analysis for cz-vavai-programmes took 3.2861225605010986s
Availability | SPARQL endpoint availability check for R&D Projects took 0.11033773422241211s
Availability | VoID file availability check for R&D Projects took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.30520081520080566s
Reputation | Calculation of the PageRank for R&D Projects took 0.0209195613861084s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.315376281738281e-05s
Believability | Calculation of trust value for R&D Projects took 9.5367431640625e-06s
INFO | --- Analysis for cz-vavai-projects took 3.182450532913208s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10836386680603027s
Availability | VoID file availability check for Institutional research plans took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.2688724994659424s
Reputation | Calculation of the PageRank for Institutional research plans took 0.021280527114868164s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.076957702636719e-05s
Believability | Calculation of trust value for Institutional research plans took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-research-plans took 3.1826581954956055s
Availability | SPARQL endpoint availability check for Results of R&D took 0.11632657051086426s
Availability | VoID file availability check for Results of R&D took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.30019378662109375s
Reputation | Calculation of the PageRank for Results of R&D took 0.02088165283203125s
Interlinking | Calculation of Degree of Connection for Results of R&D took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.220008850097656e-05s
Believability | Calculation of trust value for Results of R&D took 7.867813110351562e-06s
INFO | --- Analysis for cz-vavai-results took 3.129471778869629s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.11239457130432129s
Availability | VoID file availability check for Tenders in R&D took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.29761290550231934s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.021212100982666016s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.172325134277344e-05s
Believability | Calculation of trust value for Tenders in R&D took 9.5367431640625e-06s
INFO | --- Analysis for cz-vavai-tenders took 3.1007769107818604s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 9.274482727050781e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.2867448329925537s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.0212554931640625s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.409385681152344e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.0013580322265625e-05s
INFO | --- Analysis for czech_addresses took 4.316654682159424s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.614415168762207s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.2808725833892822s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.021004199981689453s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 9.775161743164062e-06s
INFO | --- Analysis for DanteLatinLoanwords took 4.358684539794922s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.40355467796325684s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006666183471679688s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 141.51713299751282s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0307397842407227s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 12.71270203590393s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.169014930725098s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.28127479553223s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.23493528366088867s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.13276195526123047s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.9126513004302979s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.2546656131744385s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2183372974395752s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.2555091381072998s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.32865309715271s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.34282541275024414s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.3095941543579102s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.4701087474822998s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.24189329147338867s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.5009534358978271s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 1.669416904449463s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.28852915763855s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 8.058547973632812e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.22438931465148926s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.5497231483459473s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.49993348121643066s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.5154967308044434s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.25609803199768066s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 3.189650774002075s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 2.7571725845336914s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 86.52328276634216s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.23626303672790527s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3690640926361084s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3903975486755371s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 44.67558240890503s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.1875715255737305s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.6552820205688477s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.45897364616394043s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.422884225845337s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.48413634300232s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 40.66836881637573s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.4952340126037598s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 22.942287921905518s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8770995140075684s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2502760887145996s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.25768589973449707s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 9.253047943115234s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.397707462310791s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02096271514892578s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014209747314453125s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.6689300537109375e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.0251998901367188e-05s
INFO | --- Analysis for data-bnf-fr took 858.2195057868958s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.43892836570739746s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.27967190742492676s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02091526985168457s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.890296936035156e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 9.775161743164062e-06s
INFO | --- Analysis for data-cnr-it took 4.016233682632446s
Availability | SPARQL endpoint availability check for Data.gov took 1.6733627319335938s
Availability | VoID file availability check for Data.gov took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Data.gov took 0.29003262519836426s
Reputation | Calculation of the PageRank for Data.gov took 0.021007299423217773s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Data.gov took 4.220008850097656e-05s
Believability | Calculation of trust value for Data.gov took 8.344650268554688e-06s
INFO | --- Analysis for data-gov took 19.081681966781616s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.06505370140075684s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.2805640697479248s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.05718994140625e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 8.821487426757812e-06s
INFO | --- Analysis for data-gov-ie took 2.83955979347229s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 8.797645568847656e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.28658580780029297s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.0208432674407959s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.2479248046875e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 8.58306884765625e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.7435302734375s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 11.201498985290527s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.3031423091888428s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02106618881225586s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.270408630371094e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.0967254638671875e-05s
INFO | --- Analysis for data-hnm-hu took 144.35022711753845s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.14493680000305176s
Availability | VoID file availability check for Climb Dataincubator took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.296292781829834s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02113652229309082s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.62939453125e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.0967254638671875e-05s
INFO | --- Analysis for data-incubator-climb took 2.9257161617279053s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.124641418457031e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2898736000061035s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.021152257919311523s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.298324584960938e-05s
Believability | Calculation of trust value for Discogs in RDF took 1.049041748046875e-05s
INFO | --- Analysis for data-incubator-discogs took 4.766887664794922s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.07030606269836426s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.29169416427612305s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.02226543426513672s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.412101745605469e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 8.344650268554688e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.441741943359375s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.05429434776306152s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.29674816131591797s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.021576404571533203s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 9.512901306152344e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 9.775161743164062e-06s
INFO | --- Analysis for data-incubator-moseley took 8.578184127807617s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.05683398246765137s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.31711268424987793s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.021097183227539062s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.012222290039062e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 9.775161743164062e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.791954278945923s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 4.3207361698150635s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.30399227142333984s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02118825912475586s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.368492126464844e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 8.344650268554688e-06s
INFO | --- Analysis for data-incubator-nasa took 10.495162725448608s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.06550908088684082s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2767186164855957s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020426273345947266s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.557868957519531e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.049041748046875e-05s
INFO | --- Analysis for data-incubator-our-airports took 2.766606330871582s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.06378173828125s
Availability | VoID file availability check for Pokedex data in RDF took 0.0003581047058105469s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.3282618522644043s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.021195650100708008s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.179115295410156e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.1682510375976562e-05s
INFO | --- Analysis for data-incubator-pokedex took 3.6437671184539795s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.07240509986877441s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.33938169479370117s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.022035598754882812s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.869171142578125e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.049041748046875e-05s
INFO | --- Analysis for data-incubator-smcjournals took 2.8483572006225586s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.28687381744384766s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0005948543548583984s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 16.283381462097168s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.0029358863830566s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 18.286645650863647s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.523770809173584s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.189733266830444s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.140264749526978s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.2768287658691406s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.1830286979675293s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.20967411994934082s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.13045239448547363s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.38561320304870605s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.154664993286133s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.39594531059265137s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 26.331022262573242s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.795496940612793s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.22518396377563477s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.21616673469543457s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.5398390293121338s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 23.64780330657959s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.534027099609375e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.18280339241027832s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.9584710597991943s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2513844966888428s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.49617481231689453s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.17349982261657715s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.41745972633361816s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.6763119697570801s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 31.05837655067444s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 295.6602404117584s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.1655576229095459s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.16487860679626465s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.12935829162597656s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 14.564100980758667s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.989774227142334s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.082976341247559s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.18883180618286133s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.5118370056152344s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 7.882950782775879s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 7.788116931915283s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.438551664352417s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 2.1878485679626465s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.937488317489624s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.44481587409973145s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.1281125545501709s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.1520824432373047s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.4103701114654541s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.021059036254882812s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.52587890625e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 201.77858471870422s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 8.106231689453125e-06s
INFO | --- Analysis for data-open-ac-uk took 977.0914723873138s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8320486545562744s
Availability | VoID file availability check for Persée in RDF took 0.0008034706115722656s
Extra | Recovery of all triples for Persée in RDF took 1.1603004932403564s
Performance | Total latancy measurement for Persée in RDF took 0.6320285797119141s
Amount of data | Number of triples check for Persée in RDF took 0.7026474475860596s
Interoperability | New terms check for Persée in RDF took 1.902360200881958s
Versatility | Languages check for Persée in RDF took 118.28057265281677s
Interpretability | Number of blank nodes check for Persée in RDF took 0.3949928283691406s
Interpretability | RDF structures check for Persée in RDF took 0.6976101398468018s
Versatility | Serialization formats check for Persée in RDF took 0.9564383029937744s
Availability | RDF dump link check for Persée in RDF took 0.3308873176574707s
License | MR license check for Persée in RDF took 1.3124144077301025s
License | HR license check for Persée in RDF took 39.2530996799469s
Amount of data | Number of property check for Persée in RDF took 0.15324091911315918s
Understandability | Number of label check for Persée in RDF took 1.8565661907196045s
Understandability | URI regex check for Persée in RDF took 0.8913657665252686s
Understandability | Vocabs check for Persée in RDF took 0.4368734359741211s
Verifiability | Authors check for Persée in RDF took 0.15362977981567383s
Verifiability | Publishers check for Persée in RDF took 0.13233613967895508s
Performance | Throughput check for Persée in RDF took 10.602336406707764s
Amount of data | Check the number of entities for Persée in RDF took 0.00011157989501953125s
Verifiability | Contribs. check for Persée in RDF took 0.14662766456604004s
Interlinking | sameAs chians check for Persée in RDF took 0.18170428276062012s
Interlinking | skos check for Persée in RDF took 0.7361385822296143s
Interlinking | skos check for Persée in RDF took 0.13116955757141113s
Timeliness | dataset update frequency check for Persée in RDF took 0.7441682815551758s
Currency | Creation date check for Persée in RDF took 0.5716478824615479s
Currency | Modification date check for Persée in RDF took 0.2738382816314697s
Rep.Conc. | URIs length for Persée in RDF took 3.5609068870544434s
Interoperability | New vocabularies check for Persée in RDF took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.1168515682220459s
Accuracy | Check Functional Property for Persée in RDF took 0.1314990520477295s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.15036678314208984s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.5639898777008057s
Accuracy | Check White space in annotation for Persée in RDF took 0.03988075256347656s
Accuracy | Check Datatype consistency for Persée in RDF took 0.02727794647216797s
Consistency | Disjoint class check for Persée in RDF took 0.33803653717041016s
Consistency | Check Misplaced properties for Persée in RDF took 2.6420459747314453s
Consistency | Misplaced classes for Persée in RDF took 0.2186577320098877s
Consistency | Check Ontology hijacking for Persée in RDF took 1.8293342590332031s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.3434865474700928s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.9199464321136475s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03386425971984863s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.11659884452819824s
Security | Sign check for Persée in RDF took 0.8134706020355225s
Availability | Check URIs Dereferenciability for Persée in RDF took 1460.4813668727875s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.7630767822265625s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020747661590576172s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00011754035949707031s
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.1682510375976562e-05s
INFO | --- Analysis for data-persee-fr took 1698.7642226219177s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.220545768737793s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.3022298812866211s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011277198791503906s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 6.198883056640625e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.388763189315796s
Availability | SPARQL endpoint availability check for Open Data Web took 12.62514042854309s
Availability | VoID file availability check for Open Data Web took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2788574695587158s
Reputation | Calculation of the PageRank for Open Data Web took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 2.9087066650390625e-05s
Believability | Calculation of trust value for Open Data Web took 6.198883056640625e-06s
INFO | --- Analysis for data.odw.tw took 34.1681649684906s
Availability | SPARQL endpoint availability check for datahub took 5.173683166503906e-05s
Availability | VoID file availability check for datahub took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for datahub took 0.3006112575531006s
Reputation | Calculation of the PageRank for datahub took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for datahub took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for datahub took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for datahub took 4.6253204345703125e-05s
Believability | Calculation of trust value for datahub took 7.867813110351562e-06s
INFO | --- Analysis for datahub took 4.418635129928589s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.723629713058472s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.3024897575378418s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.7670135498046875e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.0728836059570312e-05s
INFO | --- Analysis for datahub-kr-datamap took 13.412208318710327s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3856229782104492s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.28018736839294434s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.200241088867188e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.2636184692382812e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.437885522842407s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.26855206489563s
Availability | VoID file availability check for datos-artium-org took 0.0007925033569335938s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.29747724533081055s
Reputation | Calculation of the PageRank for datos-artium-org took 0.02082991600036621s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011801719665527344s
Believability | Calculation of trust value for datos-artium-org took 1.239776611328125e-05s
INFO | --- Analysis for datos-artium-org took 165.12059473991394s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.801344871520996s
Availability | VoID file availability check for Datos.bcn.cl took 0.0008668899536132812s
Extra | Recovery of all triples for Datos.bcn.cl took 25.18330407142639s
Performance | Total latancy measurement for Datos.bcn.cl took 6.103990316390991s
Amount of data | Number of triples check for Datos.bcn.cl took 4.546816825866699s
Interoperability | New terms check for Datos.bcn.cl took 3.7672677040100098s
Versatility | Languages check for Datos.bcn.cl took 294.9124655723572s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.2527968883514404s
Security | Check HTTPS for Datos.bcn.cl took 0.7227005958557129s
Interpretability | RDF structures check for Datos.bcn.cl took 1.3182532787322998s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2181143760681152s
Availability | RDF dump link check for Datos.bcn.cl took 1.204554796218872s
License | MR license check for Datos.bcn.cl took 1.2223243713378906s
License | HR license check for Datos.bcn.cl took 28.369173765182495s
Amount of data | Number of property check for Datos.bcn.cl took 1.2542388439178467s
Understandability | Number of label check for Datos.bcn.cl took 1.4451653957366943s
Understandability | URI regex check for Datos.bcn.cl took 2.4334232807159424s
Understandability | Vocabs check for Datos.bcn.cl took 1.249781847000122s
Verifiability | Authors check for Datos.bcn.cl took 1.1885666847229004s
Verifiability | Publishers check for Datos.bcn.cl took 1.219759225845337s
Performance | Throughput check for Datos.bcn.cl took 12.195953130722046s
Amount of data | Check the number of entities for Datos.bcn.cl took 8.034706115722656e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2470667362213135s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2181527614593506s
Interlinking | skos check for Datos.bcn.cl took 1.2092866897583008s
Interlinking | skos check for Datos.bcn.cl took 1.2195427417755127s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2219789028167725s
Currency | Creation date check for Datos.bcn.cl took 2.44561767578125s
Currency | Modification date check for Datos.bcn.cl took 1.2167303562164307s
Rep.Conc. | URIs length for Datos.bcn.cl took 19.95565152168274s
Interoperability | New vocabularies check for Datos.bcn.cl took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2038311958312988s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.2657115459442139s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.1973464488983154s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 23.739535570144653s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.3244969844818115s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.26764392852783203s
Consistency | Disjoint class check for Datos.bcn.cl took 1.261415958404541s
Consistency | Check Misplaced properties for Datos.bcn.cl took 8.356654405593872s
Consistency | Misplaced classes for Datos.bcn.cl took 2.098154306411743s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 19.64708662033081s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.3403749465942383s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.365805387496948s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.30291128158569336s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.4314911365509033s
Security | Sign check for Datos.bcn.cl took 1.225597858428955s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 7705.370805025101s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.8738734722137451s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.022195816040039062s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.939338684082031e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.9073486328125e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 9.298324584960938e-06s
INFO | --- Analysis for datos-bcn-cl took 8812.583169937134s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.6118178367614746s
Availability | VoID file availability check for datos.bne.es took 0.0007319450378417969s
Extra | Recovery of all triples for datos.bne.es took 131.43165469169617s
Performance | Total latancy measurement for datos.bne.es took 5.069690942764282s
Amount of data | Number of triples check for datos.bne.es took 0.8711647987365723s
Interoperability | New terms check for datos.bne.es took 2.3439393043518066s
Versatility | Languages check for datos.bne.es took 62.55768847465515s
Interpretability | Number of blank nodes check for datos.bne.es took 0.3088874816894531s
Security | Check HTTPS for datos.bne.es took 0.19598674774169922s
Interpretability | RDF structures check for datos.bne.es took 2.448547840118408s
Versatility | Serialization formats check for datos.bne.es took 2.513138771057129s
Availability | RDF dump link check for datos.bne.es took 0.4032571315765381s
License | MR license check for datos.bne.es took 2.711923837661743s
License | HR license check for datos.bne.es took 60.59520936012268s
Amount of data | Number of property check for datos.bne.es took 0.3128318786621094s
Understandability | Number of label check for datos.bne.es took 3.0438969135284424s
Understandability | URI regex check for datos.bne.es took 2.563641309738159s
Understandability | Vocabs check for datos.bne.es took 0.3709430694580078s
Verifiability | Authors check for datos.bne.es took 0.41872477531433105s
Verifiability | Publishers check for datos.bne.es took 2.1035516262054443s
Performance | Throughput check for datos.bne.es took 23.757097721099854s
Amount of data | Check the number of entities for datos.bne.es took 3.981590270996094e-05s
Verifiability | Contribs. check for datos.bne.es took 0.37392425537109375s
Interlinking | sameAs chians check for datos.bne.es took 2.3550896644592285s
Interlinking | skos check for datos.bne.es took 2.464928388595581s
Interlinking | skos check for datos.bne.es took 2.092632532119751s
Timeliness | dataset update frequency check for datos.bne.es took 0.4462862014770508s
Currency | Creation date check for datos.bne.es took 0.6892099380493164s
Currency | Modification date check for datos.bne.es took 0.6376152038574219s
Rep.Conc. | URIs length for datos.bne.es took 53.60823082923889s
Interoperability | New vocabularies check for datos.bne.es took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.31931543350219727s
Accuracy | Check Functional Property for datos.bne.es took 0.315504789352417s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.30060434341430664s
Accuracy | Check Empty annotation labels for datos.bne.es took 44.34682655334473s
Accuracy | Check White space in annotation for datos.bne.es took 1.6251277923583984s
Accuracy | Check Datatype consistency for datos.bne.es took 1.3209950923919678s
Consistency | Disjoint class check for datos.bne.es took 0.3303642272949219s
Consistency | Check Misplaced properties for datos.bne.es took 10.398728847503662s
Consistency | Misplaced classes for datos.bne.es took 6.127174139022827s
Consistency | Check Ontology hijacking for datos.bne.es took 44.08088207244873s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.2783279418945312s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 9.406788349151611s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.4024426937103271s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.31967854499816895s
Security | Sign check for datos.bne.es took 2.815171241760254s
Availability | Check URIs Dereferenciability for datos.bne.es took 10.170874118804932s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.40322422981262207s
Reputation | Calculation of the PageRank for datos.bne.es took 0.02123403549194336s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011515617370605469s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 1.9073486328125e-06s
Believability | Calculation of trust value for datos.bne.es took 1.1920928955078125e-05s
INFO | --- Analysis for datos-bne-es took 645.8300266265869s
Availability | SPARQL endpoint availability check for dbacademic took 0.06639528274536133s
Availability | VoID file availability check for dbacademic took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for dbacademic took 0.3158450126647949s
Reputation | Calculation of the PageRank for dbacademic took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for dbacademic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for dbacademic took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.0279159545898438e-05s
Believability | Calculation of trust value for dbacademic took 7.867813110351562e-06s
INFO | --- Analysis for dbacademic took 2.974168300628662s
Availability | SPARQL endpoint availability check for DBkWik took 0.22934842109680176s
Availability | VoID file availability check for DBkWik took 0.0006506443023681641s
Extra | Recovery of all triples for DBkWik took 1.872067928314209s
Performance | Total latancy measurement for DBkWik took 0.5186262130737305s
Amount of data | Number of triples check for DBkWik took 5.123868465423584s
Interoperability | New terms check for DBkWik took 2.1180334091186523s
Versatility | Languages check for DBkWik took 61.68231987953186s
Interpretability | Number of blank nodes check for DBkWik took 0.12623143196105957s
Interpretability | RDF structures check for DBkWik took 0.30721569061279297s
Versatility | Serialization formats check for DBkWik took 0.3045518398284912s
Availability | RDF dump link check for DBkWik took 3.2459325790405273s
License | MR license check for DBkWik took 0.32507967948913574s
License | HR license check for DBkWik took 61.53676652908325s
Amount of data | Number of property check for DBkWik took 0.33331727981567383s
Understandability | Number of label check for DBkWik took 2.317068576812744s
Understandability | URI regex check for DBkWik took 0.3161170482635498s
Understandability | Vocabs check for DBkWik took 0.1445298194885254s
Verifiability | Authors check for DBkWik took 0.13027429580688477s
Verifiability | Publishers check for DBkWik took 0.10233688354492188s
Performance | Throughput check for DBkWik took 10.619681358337402s
Amount of data | Check the number of entities for DBkWik took 0.00011515617370605469s
Verifiability | Contribs. check for DBkWik took 0.1282026767730713s
Interlinking | sameAs chians check for DBkWik took 0.4535250663757324s
Interlinking | skos check for DBkWik took 0.5432517528533936s
Interlinking | skos check for DBkWik took 0.1066286563873291s
Timeliness | dataset update frequency check for DBkWik took 0.25126099586486816s
Currency | Creation date check for DBkWik took 0.5413744449615479s
Currency | Modification date check for DBkWik took 0.23845791816711426s
Rep.Conc. | URIs length for DBkWik took 11.31701397895813s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.1413416862487793s
Accuracy | Check Functional Property for DBkWik took 0.32285380363464355s
Accuracy | Check Inverse Functional Property for DBkWik took 0.2800421714782715s
Accuracy | Check Empty annotation labels for DBkWik took 0.7827565670013428s
Accuracy | Check White space in annotation for DBkWik took 0.023739337921142578s
Accuracy | Check Datatype consistency for DBkWik took 0.037133216857910156s
Consistency | Disjoint class check for DBkWik took 0.13830351829528809s
Consistency | Check Misplaced properties for DBkWik took 11.73654556274414s
Consistency | Misplaced classes for DBkWik took 0.6373226642608643s
Consistency | Check Ontology hijacking for DBkWik took 1.8271307945251465s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.2660582065582275s
Consistency | Check Invalid usage of undefined properties for DBkWik took 12.76133131980896s
Conciseness | Check Extensional conciseness for DBkWik took 0.03284263610839844s
Conciseness | Check Intensional conciseness for DBkWik took 0.7646224498748779s
Security | Sign check for DBkWik took 0.2751157283782959s
Availability | Check URIs Dereferenciability for DBkWik took 9.894727230072021s
Completeness | Calculation of interlinking completeness for DBkWik took 0.4229848384857178s
Reputation | Calculation of the PageRank for DBkWik took 0.02109813690185547s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.319450378417969e-05s
Believability | Calculation of trust value for DBkWik took 1.2636184692382812e-05s
INFO | --- Analysis for dbkwik took 1390.762886762619s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 8.940696716308594e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.32276153564453125s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.021230697631835938s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00010633468627929688s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.3113021850585938e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 4.653927564620972s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.42993736267089844s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0005981922149658203s
Extra | Recovery of all triples for dblp Knowledge Graph took 7.298924207687378s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.8581013679504395s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.1477189064025879s
Interoperability | New terms check for dblp Knowledge Graph took 1.7850010395050049s
Versatility | Languages check for dblp Knowledge Graph took 0.20240426063537598s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 5.853182315826416s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.18976116180419922s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.20868802070617676s
Availability | RDF dump link check for dblp Knowledge Graph took 0.17131257057189941s
License | MR license check for dblp Knowledge Graph took 0.1708388328552246s
License | HR license check for dblp Knowledge Graph took 30.146446704864502s
Amount of data | Number of property check for dblp Knowledge Graph took 0.19377923011779785s
Understandability | Number of label check for dblp Knowledge Graph took 0.4609358310699463s
Understandability | URI regex check for dblp Knowledge Graph took 0.28604626655578613s
Understandability | Vocabs check for dblp Knowledge Graph took 0.14018535614013672s
Verifiability | Authors check for dblp Knowledge Graph took 0.16286706924438477s
Verifiability | Publishers check for dblp Knowledge Graph took 0.1756148338317871s
Performance | Throughput check for dblp Knowledge Graph took 10.858465433120728s
Amount of data | Check the number of entities for dblp Knowledge Graph took 7.82012939453125e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.1574254035949707s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.20879435539245605s
Interlinking | skos check for dblp Knowledge Graph took 0.15568876266479492s
Interlinking | skos check for dblp Knowledge Graph took 0.1465613842010498s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.18828797340393066s
Currency | Creation date check for dblp Knowledge Graph took 0.29059863090515137s
Currency | Modification date check for dblp Knowledge Graph took 0.3127725124359131s
Rep.Conc. | URIs length for dblp Knowledge Graph took 15.183152914047241s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.13272976875305176s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.15636467933654785s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.14904403686523438s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 7.087505340576172s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.1294960975646973s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.057722568511963s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.15589427947998047s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.31761693954467773s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 6.073007106781006s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 18323.039840221405s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 3.929107666015625s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.799072027206421s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.18304920196533203s
Security | Sign check for dblp Knowledge Graph took 0.13408279418945312s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 4.176088809967041s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.8668453693389893s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020953655242919922s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.7881393432617188e-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.0728836059570312e-05s
INFO | --- Analysis for dblp-kg took 18487.981731653214s
Availability | SPARQL endpoint availability check for DBnary took 0.3220372200012207s
Availability | VoID file availability check for DBnary took 0.0005190372467041016s
Extra | Recovery of all triples for DBnary took 1.151172399520874s
Performance | Total latancy measurement for DBnary took 0.39731907844543457s
Amount of data | Number of triples check for DBnary took 1.2135865688323975s
Interoperability | New terms check for DBnary took 3.6995444297790527s
Versatility | Languages check for DBnary took 61.47627663612366s
Interpretability | Number of blank nodes check for DBnary took 4.973325967788696s
Security | Check HTTPS for DBnary took 0.18668818473815918s
Interpretability | RDF structures check for DBnary took 0.278397798538208s
Versatility | Serialization formats check for DBnary took 0.3630661964416504s
Availability | RDF dump link check for DBnary took 0.18110918998718262s
License | MR license check for DBnary took 0.48374462127685547s
License | HR license check for DBnary took 61.16526913642883s
Amount of data | Number of property check for DBnary took 0.10825538635253906s
Understandability | Number of label check for DBnary took 0.582909345626831s
Understandability | URI regex check for DBnary took 0.15452075004577637s
Understandability | Vocabs check for DBnary took 0.17269420623779297s
Verifiability | Authors check for DBnary took 0.0705864429473877s
Verifiability | Publishers check for DBnary took 0.08275985717773438s
Performance | Throughput check for DBnary took 10.499183893203735s
Amount of data | Check the number of entities for DBnary took 7.867813110351562e-05s
Verifiability | Contribs. check for DBnary took 0.06665658950805664s
Interlinking | sameAs chians check for DBnary took 0.1204373836517334s
Interlinking | skos check for DBnary took 0.1852884292602539s
Interlinking | skos check for DBnary took 0.0656278133392334s
Timeliness | dataset update frequency check for DBnary took 0.15819478034973145s
Currency | Creation date check for DBnary took 0.17023468017578125s
Currency | Modification date check for DBnary took 0.17470026016235352s
Rep.Conc. | URIs length for DBnary took 11.249415636062622s
Interoperability | New vocabularies check for DBnary took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBnary took 0.10497379302978516s
Accuracy | Check Functional Property for DBnary took 0.21051883697509766s
Accuracy | Check Inverse Functional Property for DBnary took 0.16638660430908203s
Accuracy | Check Empty annotation labels for DBnary took 0.4237031936645508s
Accuracy | Check White space in annotation for DBnary took 0.030518054962158203s
Accuracy | Check Datatype consistency for DBnary took 0.028974294662475586s
Consistency | Disjoint class check for DBnary took 0.11372184753417969s
Consistency | Check Misplaced properties for DBnary took 8.77647614479065s
Consistency | Misplaced classes for DBnary took 0.24117255210876465s
Consistency | Check Ontology hijacking for DBnary took 1.8747248649597168s
Consistency | Check Invalid usage of undefined classes for DBnary took 1.502918004989624s
Consistency | Check Invalid usage of undefined properties for DBnary took 10.093111276626587s
Conciseness | Check Extensional conciseness for DBnary took 0.03985142707824707s
Conciseness | Check Intensional conciseness for DBnary took 0.1844470500946045s
Security | Sign check for DBnary took 0.14157795906066895s
Availability | Check URIs Dereferenciability for DBnary took 10.708858489990234s
Completeness | Calculation of interlinking completeness for DBnary took 0.3030846118927002s
Reputation | Calculation of the PageRank for DBnary took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for DBnary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBnary took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for DBnary took 6.580352783203125e-05s
Interoperability | Check the re-using of existing vocabs for DBnary took 1.430511474609375e-06s
Believability | Calculation of trust value for DBnary took 1.2159347534179688e-05s
INFO | --- Analysis for dbnary took 304.8286588191986s
Availability | SPARQL endpoint availability check for DBpedia took 0.938748836517334s
Availability | VoID file availability check for DBpedia took 0.0006730556488037109s
Extra | Recovery of all triples for DBpedia took 2.9106132984161377s
Performance | Total latancy measurement for DBpedia took 2.8125219345092773s
Amount of data | Number of triples check for DBpedia took 0.9974124431610107s
Interoperability | New terms check for DBpedia took 6.286766529083252s
Versatility | Languages check for DBpedia took 31.624248027801514s
Interpretability | Number of blank nodes check for DBpedia took 0.5669867992401123s
Security | Check HTTPS for DBpedia took 0.3350996971130371s
Interpretability | RDF structures check for DBpedia took 0.7111668586730957s
Versatility | Serialization formats check for DBpedia took 0.6798832416534424s
Availability | RDF dump link check for DBpedia took 0.5791807174682617s
License | MR license check for DBpedia took 1.2599647045135498s
License | HR license check for DBpedia took 31.13885998725891s
Amount of data | Number of property check for DBpedia took 1.6358203887939453s
Understandability | Number of label check for DBpedia took 5.549899339675903s
Understandability | URI regex check for DBpedia took 1.162790298461914s
Understandability | Vocabs check for DBpedia took 0.6721432209014893s
Verifiability | Authors check for DBpedia took 0.6846141815185547s
Verifiability | Publishers check for DBpedia took 0.5352609157562256s
Performance | Throughput check for DBpedia took 11.240586280822754s
Amount of data | Check the number of entities for DBpedia took 7.176399230957031e-05s
Verifiability | Contribs. check for DBpedia took 0.5921812057495117s
Interlinking | sameAs chians check for DBpedia took 8.58983850479126s
Interlinking | skos check for DBpedia took 1.1056909561157227s
Interlinking | skos check for DBpedia took 0.5443675518035889s
Timeliness | dataset update frequency check for DBpedia took 0.6357390880584717s
Currency | Creation date check for DBpedia took 1.1602559089660645s
Currency | Modification date check for DBpedia took 1.6464276313781738s
Rep.Conc. | URIs length for DBpedia took 37.26555681228638s
Interoperability | New vocabularies check for DBpedia took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 4.149357080459595s
Accuracy | Check Functional Property for DBpedia took 0.6167721748352051s
Accuracy | Check Inverse Functional Property for DBpedia took 0.5861897468566895s
Accuracy | Check Empty annotation labels for DBpedia took 2.0047194957733154s
Accuracy | Check White space in annotation for DBpedia took 0.03009963035583496s
Accuracy | Check Datatype consistency for DBpedia took 0.027556896209716797s
Consistency | Disjoint class check for DBpedia took 1.1507012844085693s
Consistency | Check Misplaced properties for DBpedia took 32.960082054138184s
Consistency | Misplaced classes for DBpedia took 3.0273327827453613s
Consistency | Check Ontology hijacking for DBpedia took 2.8737900257110596s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.2714242935180664s
Consistency | Check Invalid usage of undefined properties for DBpedia took 2.7679615020751953s
Conciseness | Check Extensional conciseness for DBpedia took 0.03306913375854492s
Conciseness | Check Intensional conciseness for DBpedia took 1.92020583152771s
Security | Sign check for DBpedia took 0.5695257186889648s
Availability | Check URIs Dereferenciability for DBpedia took 4810.2071142196655s
Completeness | Calculation of interlinking completeness for DBpedia took 0.960237979888916s
Reputation | Calculation of the PageRank for DBpedia took 0.021524906158447266s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009012222290039062s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.9073486328125e-06s
Believability | Calculation of trust value for DBpedia took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia took 7367.64363193512s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.3392181396484375e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0003542900085449219s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.31722164154052734s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.02092123031616211s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.842613220214844e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 7.428908586502075s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.174389600753784s
Availability | VoID file availability check for DBpedia Commons took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.3243677616119385s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.914138793945312e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-commons took 16.507718086242676s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.3723759651184082s
Availability | VoID file availability check for DBpedia in Greek took 0.0002655982971191406s
Extra | Recovery of all triples for DBpedia in Greek took 1.1248540878295898s
Performance | Total latancy measurement for DBpedia in Greek took 1.1492104530334473s
Amount of data | Number of triples check for DBpedia in Greek took 0.26514220237731934s
Interoperability | New terms check for DBpedia in Greek took 1.7256042957305908s
Versatility | Languages check for DBpedia in Greek took 12.654793739318848s
Interpretability | Number of blank nodes check for DBpedia in Greek took 0.2570955753326416s
Security | Check HTTPS for DBpedia in Greek took 0.14028596878051758s
Interpretability | RDF structures check for DBpedia in Greek took 0.3037552833557129s
Versatility | Serialization formats check for DBpedia in Greek took 0.2725954055786133s
Availability | RDF dump link check for DBpedia in Greek took 0.2463517189025879s
License | MR license check for DBpedia in Greek took 0.2943291664123535s
License | HR license check for DBpedia in Greek took 2.6917078495025635s
Amount of data | Number of property check for DBpedia in Greek took 0.23645973205566406s
Understandability | Number of label check for DBpedia in Greek took 0.3205275535583496s
Understandability | URI regex check for DBpedia in Greek took 0.5011091232299805s
Understandability | Vocabs check for DBpedia in Greek took 0.22727656364440918s
Verifiability | Authors check for DBpedia in Greek took 0.23502445220947266s
Verifiability | Publishers check for DBpedia in Greek took 0.23321270942687988s
Performance | Throughput check for DBpedia in Greek took 11.54049825668335s
Amount of data | Check the number of entities for DBpedia in Greek took 3.24249267578125e-05s
Verifiability | Contribs. check for DBpedia in Greek took 0.27840161323547363s
Interlinking | sameAs chians check for DBpedia in Greek took 0.26100611686706543s
Interlinking | skos check for DBpedia in Greek took 0.3968191146850586s
Interlinking | skos check for DBpedia in Greek took 0.2212374210357666s
Timeliness | dataset update frequency check for DBpedia in Greek took 0.320889949798584s
Currency | Creation date check for DBpedia in Greek took 0.4829709529876709s
Currency | Modification date check for DBpedia in Greek took 0.49513673782348633s
Rep.Conc. | URIs length for DBpedia in Greek took 1.2921442985534668s
Interoperability | New vocabularies check for DBpedia in Greek took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Greek took 0.23308873176574707s
Accuracy | Check Functional Property for DBpedia in Greek took 0.2761690616607666s
Accuracy | Check Inverse Functional Property for DBpedia in Greek took 0.2645399570465088s
Consistency | Disjoint class check for DBpedia in Greek took 0.2368018627166748s
Consistency | Check Misplaced properties for DBpedia in Greek took 1.006791114807129s
Consistency | Check Ontology hijacking for DBpedia in Greek took 0.42565345764160156s
Consistency | Check Invalid usage of undefined properties for DBpedia in Greek took 2.033769130706787s
Conciseness | Check Extensional conciseness for DBpedia in Greek took 0.00013780593872070312s
Security | Sign check for DBpedia in Greek took 0.2760648727416992s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.2827775478363037s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.021137714385986328s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0001971721649169922s
Interoperability | Check the re-using of existing vocabs for DBpedia in Greek took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia in Greek took 4.0531158447265625e-06s
INFO | --- Analysis for dbpedia-el took 123.15089702606201s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 30.348828554153442s
Availability | VoID file availability check for DBpedia in Spanish took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.27488207817077637s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010418891906738281s
Believability | Calculation of trust value for DBpedia in Spanish took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-es took 83.96213960647583s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.3954875469207764s
Availability | VoID file availability check for DBpedia in Basque took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.2818465232849121s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020296812057495117s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 2.9087066650390625e-05s
Believability | Calculation of trust value for DBpedia in Basque took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-eu took 7.353298664093018s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.1671278476715088s
Availability | VoID file availability check for DBpedia in French took 0.0005140304565429688s
Extra | Recovery of all triples for DBpedia in French took 82.59310364723206s
Performance | Total latancy measurement for DBpedia in French took 0.446347713470459s
Amount of data | Number of triples check for DBpedia in French took 1.9458723068237305s
Interoperability | New terms check for DBpedia in French took 2.1020596027374268s
Versatility | Languages check for DBpedia in French took 300.08871722221375s
Interpretability | Number of blank nodes check for DBpedia in French took 0.16578912734985352s
Security | Check HTTPS for DBpedia in French took 0.20360779762268066s
Interpretability | RDF structures check for DBpedia in French took 0.5769650936126709s
Versatility | Serialization formats check for DBpedia in French took 0.35428738594055176s
Availability | RDF dump link check for DBpedia in French took 6.759968519210815s
License | MR license check for DBpedia in French took 1.2859373092651367s
License | HR license check for DBpedia in French took 74.40279865264893s
Amount of data | Number of property check for DBpedia in French took 0.1674962043762207s
Understandability | Number of label check for DBpedia in French took 1.7481460571289062s
Understandability | URI regex check for DBpedia in French took 0.27306175231933594s
Understandability | Vocabs check for DBpedia in French took 0.13169050216674805s
Verifiability | Authors check for DBpedia in French took 0.206984281539917s
Verifiability | Publishers check for DBpedia in French took 0.12103819847106934s
Performance | Throughput check for DBpedia in French took 10.463672161102295s
Amount of data | Check the number of entities for DBpedia in French took 2.188581943511963s
Verifiability | Contribs. check for DBpedia in French took 0.13578248023986816s
Interlinking | sameAs chians check for DBpedia in French took 0.32282042503356934s
Interlinking | skos check for DBpedia in French took 0.22835016250610352s
Interlinking | skos check for DBpedia in French took 0.07420206069946289s
Timeliness | dataset update frequency check for DBpedia in French took 0.2699713706970215s
Currency | Creation date check for DBpedia in French took 0.22007155418395996s
Currency | Modification date check for DBpedia in French took 0.19484925270080566s
Rep.Conc. | URIs length for DBpedia in French took 36.63680720329285s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.1157984733581543s
Accuracy | Check Functional Property for DBpedia in French took 0.12923526763916016s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.10942912101745605s
Accuracy | Check Empty annotation labels for DBpedia in French took 25.98359227180481s
Accuracy | Check White space in annotation for DBpedia in French took 3.1040093898773193s
Accuracy | Check Datatype consistency for DBpedia in French took 2.6650197505950928s
Consistency | Disjoint class check for DBpedia in French took 0.1647486686706543s
Consistency | Check Misplaced properties for DBpedia in French took 7.167331218719482s
Consistency | Misplaced classes for DBpedia in French took 9.340411186218262s
Consistency | Check Ontology hijacking for DBpedia in French took 22.057584285736084s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.3372461795806885s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 7.601815462112427s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.1080732345581055s
Conciseness | Check Intensional conciseness for DBpedia in French took 2.0952060222625732s
Security | Sign check for DBpedia in French took 0.12250471115112305s
Availability | Check URIs Dereferenciability for DBpedia in French took 2049.659097671509s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.7571992874145508s
Reputation | Calculation of the PageRank for DBpedia in French took 0.02398991584777832s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 6.604194641113281e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.0002162456512451172s
Believability | Calculation of trust value for DBpedia in French took 1.3828277587890625e-05s
INFO | --- Analysis for dbpedia-fr took 2851.125829935074s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 2.0894789695739746s
Availability | VoID file availability check for DBpedia in Japanese took 4.402774333953857s
Extra | Recovery of all triples for DBpedia in Japanese took 5.95974588394165s
Performance | Total latancy measurement for DBpedia in Japanese took 7.190657138824463s
Amount of data | Number of triples check for DBpedia in Japanese took 27.5472092628479s
Interoperability | New terms check for DBpedia in Japanese took 18.727064847946167s
Versatility | Languages check for DBpedia in Japanese took 1.4401400089263916s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.4277827739715576s
Security | Check HTTPS for DBpedia in Japanese took 0.8652122020721436s
Interpretability | RDF structures check for DBpedia in Japanese took 1.4954767227172852s
Versatility | Serialization formats check for DBpedia in Japanese took 1.4774651527404785s
Availability | RDF dump link check for DBpedia in Japanese took 1.4445297718048096s
License | MR license check for DBpedia in Japanese took 1.485123634338379s
License | HR license check for DBpedia in Japanese took 61.433351039886475s
Amount of data | Number of property check for DBpedia in Japanese took 1.4692130088806152s
Understandability | Number of label check for DBpedia in Japanese took 8.188527345657349s
Understandability | URI regex check for DBpedia in Japanese took 2.8967318534851074s
Understandability | Vocabs check for DBpedia in Japanese took 1.4347929954528809s
Verifiability | Authors check for DBpedia in Japanese took 1.4786522388458252s
Verifiability | Publishers check for DBpedia in Japanese took 1.4408352375030518s
Performance | Throughput check for DBpedia in Japanese took 14.385652780532837s
Amount of data | Check the number of entities for DBpedia in Japanese took 0.00011086463928222656s
Verifiability | Contribs. check for DBpedia in Japanese took 1.4553465843200684s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.999201774597168s
Interlinking | skos check for DBpedia in Japanese took 1.452479362487793s
Interlinking | skos check for DBpedia in Japanese took 1.434351921081543s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.452040433883667s
Currency | Creation date check for DBpedia in Japanese took 2.8974385261535645s
Currency | Modification date check for DBpedia in Japanese took 2.874887228012085s
Rep.Conc. | URIs length for DBpedia in Japanese took 110.26571464538574s
Interoperability | New vocabularies check for DBpedia in Japanese took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.4403293132781982s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.4593400955200195s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.4655628204345703s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 3.0883591175079346s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.02647089958190918s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.027767181396484375s
Consistency | Disjoint class check for DBpedia in Japanese took 1.5874226093292236s
Consistency | Check Misplaced properties for DBpedia in Japanese took 94.33079218864441s
Consistency | Misplaced classes for DBpedia in Japanese took 3.1997461318969727s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.501970291137695s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.3461191654205322s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 94.19322228431702s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03351593017578125s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.770042896270752s
Security | Sign check for DBpedia in Japanese took 1.4687910079956055s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 9.335655450820923s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.3637669086456299s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.021025896072387695s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 6.389617919921875e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010418891906738281s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia-ja took 1030.099301815033s
Availability | SPARQL endpoint availability check for dbpedia lite took 9.083747863769531e-05s
Availability | VoID file availability check for dbpedia lite took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.3077390193939209s
Reputation | Calculation of the PageRank for dbpedia lite took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.799003601074219e-05s
Believability | Calculation of trust value for dbpedia lite took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-lite took 6.349710941314697s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.23398566246032715s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.3203094005584717s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02216362953186035s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001621246337890625s
Believability | Calculation of trust value for DBpedia in Dutch took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-nl took 3.4620187282562256s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 4.446996212005615s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.30714941024780273s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.021402835845947266s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.130073547363281e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia-pt took 17.029802799224854s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.1961669921875e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.27921128273010254s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.021724462509155273s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.771087646484375e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.3113021850585938e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.997876405715942s
Availability | SPARQL endpoint availability check for DBTropes took 8.940696716308594e-05s
Availability | VoID file availability check for DBTropes took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for DBTropes took 0.3132045269012451s
Reputation | Calculation of the PageRank for DBTropes took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.012222290039062e-05s
Believability | Calculation of trust value for DBTropes took 1.2159347534179688e-05s
INFO | --- Analysis for dbtropes took 3.4435267448425293s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.315376281738281e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.27858662605285645s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.078315734863281e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.2636184692382812e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 3.177700996398926s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 8.96453857421875e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.2793240547180176s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020348548889160156s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.1948089599609375e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.1920928955078125e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 2.9036507606506348s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.6212053298950195s
Availability | VoID file availability check for DBTune.org/classical took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.26653218269348145s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 8.153915405273438e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.5020370483398438e-05s
INFO | --- Analysis for dbtune-classical took 9.099439144134521s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.553711891174316s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0008502006530761719s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2974517345428467s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020254850387573242s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.271766662597656e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.0728836059570312e-05s
INFO | --- Analysis for dbtune-john-peel-sessions took 11.00624942779541s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.616838216781616s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0008327960968017578s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.33189821243286133s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020893573760986328s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.914138793945312e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.33514404296875e-05s
INFO | --- Analysis for dbtune-magnatune took 9.978955745697021s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 0.1427936553955078s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005245208740234375s
Extra | Recovery of all triples for DBTune.org Musicbrainz D2R Server took 32.14012002944946s
Performance | Total latancy measurement for DBTune.org Musicbrainz D2R Server took 0.6059820652008057s
Amount of data | Number of triples check for DBTune.org Musicbrainz D2R Server took 0.7609469890594482s
Interoperability | New terms check for DBTune.org Musicbrainz D2R Server took 1.6338322162628174s
Versatility | Languages check for DBTune.org Musicbrainz D2R Server took 1.321333408355713s
Interpretability | Number of blank nodes check for DBTune.org Musicbrainz D2R Server took 0.7610452175140381s
Interpretability | RDF structures check for DBTune.org Musicbrainz D2R Server took 0.12790656089782715s
Versatility | Serialization formats check for DBTune.org Musicbrainz D2R Server took 0.13437533378601074s
Availability | RDF dump link check for DBTune.org Musicbrainz D2R Server took 0.092010498046875s
License | MR license check for DBTune.org Musicbrainz D2R Server took 0.0931704044342041s
License | HR license check for DBTune.org Musicbrainz D2R Server took 4.098618268966675s
Amount of data | Number of property check for DBTune.org Musicbrainz D2R Server took 0.12748980522155762s
Understandability | Number of label check for DBTune.org Musicbrainz D2R Server took 0.25785112380981445s
Understandability | URI regex check for DBTune.org Musicbrainz D2R Server took 0.18355655670166016s
Understandability | Vocabs check for DBTune.org Musicbrainz D2R Server took 0.09434700012207031s
Verifiability | Authors check for DBTune.org Musicbrainz D2R Server took 0.1005551815032959s
Verifiability | Publishers check for DBTune.org Musicbrainz D2R Server took 0.09246468544006348s
Performance | Throughput check for DBTune.org Musicbrainz D2R Server took 10.748297691345215s
Amount of data | Check the number of entities for DBTune.org Musicbrainz D2R Server took 9.226799011230469e-05s
Verifiability | Contribs. check for DBTune.org Musicbrainz D2R Server took 0.09998655319213867s
Interlinking | sameAs chians check for DBTune.org Musicbrainz D2R Server took 0.1609814167022705s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.0924067497253418s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.09201478958129883s
Timeliness | dataset update frequency check for DBTune.org Musicbrainz D2R Server took 0.09386730194091797s
Currency | Creation date check for DBTune.org Musicbrainz D2R Server took 0.22125458717346191s
Currency | Modification date check for DBTune.org Musicbrainz D2R Server took 0.20462417602539062s
Rep.Conc. | URIs length for DBTune.org Musicbrainz D2R Server took 8.95946216583252s
Interoperability | New vocabularies check for DBTune.org Musicbrainz D2R Server took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for DBTune.org Musicbrainz D2R Server took 0.12587785720825195s
Accuracy | Check Functional Property for DBTune.org Musicbrainz D2R Server took 0.09119534492492676s
Accuracy | Check Inverse Functional Property for DBTune.org Musicbrainz D2R Server took 0.08406925201416016s
Accuracy | Check Empty annotation labels for DBTune.org Musicbrainz D2R Server took 1.8850529193878174s
Accuracy | Check White space in annotation for DBTune.org Musicbrainz D2R Server took 0.09262347221374512s
Accuracy | Check Datatype consistency for DBTune.org Musicbrainz D2R Server took 1.1449236869812012s
Consistency | Disjoint class check for DBTune.org Musicbrainz D2R Server took 0.09219026565551758s
Consistency | Check Misplaced properties for DBTune.org Musicbrainz D2R Server took 1.1950125694274902s
Consistency | Check Ontology hijacking for DBTune.org Musicbrainz D2R Server took 3.910304069519043s
Consistency | Check Invalid usage of undefined classes for DBTune.org Musicbrainz D2R Server took 1.3429052829742432s
Consistency | Check Invalid usage of undefined properties for DBTune.org Musicbrainz D2R Server took 2.191922426223755s
Conciseness | Check Extensional conciseness for DBTune.org Musicbrainz D2R Server took 0.6344742774963379s
Security | Sign check for DBTune.org Musicbrainz D2R Server took 0.09207820892333984s
Availability | Check URIs Dereferenciability for DBTune.org Musicbrainz D2R Server took 1357.8462450504303s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.5270516872406006s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.021870851516723633s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00012159347534179688s
Interoperability | Check the re-using of existing vocabs for DBTune.org Musicbrainz D2R Server took 1.430511474609375e-06s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.33514404296875e-05s
INFO | --- Analysis for dbtune-musicbrainz took 1462.7088243961334s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.3419978618621826s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.2922937870025635s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.4836273193359375e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.1444091796875e-05s
INFO | --- Analysis for dbtune-myspace took 3.293724298477173s
Availability | SPARQL endpoint availability check for data.dcs took 4.1484832763671875e-05s
Availability | VoID file availability check for data.dcs took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for data.dcs took 0.29032278060913086s
Reputation | Calculation of the PageRank for data.dcs took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for data.dcs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for data.dcs took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.246566772460938e-05s
Believability | Calculation of trust value for data.dcs took 1.3589859008789062e-05s
INFO | --- Analysis for dcs-sheffield took 2.8908185958862305s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 9.226799011230469e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2808387279510498s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.00543212890625e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 8.344650268554688e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.648423433303833s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.363059997558594e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.28191375732421875s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.38690185546875e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.1205673217773438e-05s
INFO | --- Analysis for debian-package-tracking-system took 4.1441330909729s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.1961669921875e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.3334071636199951s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020735502243041992s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.4332275390625e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.049041748046875e-05s
INFO | --- Analysis for desaparecidos took 3.0761804580688477s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.38690185546875e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.3050971031188965s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00010466575622558594s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.3113021850585938e-05s
INFO | --- Analysis for deustoentrepreneurship took 4.417119026184082s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 0.00011515617370605469s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.2844557762145996s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00011134147644042969s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.0967254638671875e-05s
INFO | --- Analysis for deustotech took 4.75980019569397s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.4882450103759766s
Availability | VoID file availability check for Deutsche Biographie took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.2809746265411377s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.695487976074219e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.3589859008789062e-05s
INFO | --- Analysis for deutsche-biographie took 4.567224502563477s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 8.678436279296875e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2770085334777832s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020125627517700195s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.030632019042969e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 9.5367431640625e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.686063766479492s
Availability | SPARQL endpoint availability check for dev8d took 9.012222290039062e-05s
Availability | VoID file availability check for dev8d took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for dev8d took 0.2923851013183594s
Reputation | Calculation of the PageRank for dev8d took 0.021343708038330078s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.914138793945312e-05s
Believability | Calculation of trust value for dev8d took 1.0013580322265625e-05s
INFO | --- Analysis for dev8d took 3.9257161617279053s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.292166471481323s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.28169918060302734s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.021971464157104492s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 4.982948303222656e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.3828277587890625e-05s
INFO | --- Analysis for dewey_decimal_classification took 93.14997792243958s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.2438507080078125e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.35176825523376465s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.021044015884399414s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.62396240234375e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 9.775161743164062e-06s
INFO | --- Analysis for DHSVM took 201.4894621372223s
Availability | SPARQL endpoint availability check for Diavgeia took 8.654594421386719e-05s
Availability | VoID file availability check for Diavgeia took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.27359843254089355s
Reputation | Calculation of the PageRank for Diavgeia took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.678436279296875e-05s
Believability | Calculation of trust value for Diavgeia took 4.76837158203125e-06s
INFO | --- Analysis for diavgeia took 6.055664539337158s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.4345855712890625e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.33474135398864746s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011610984802246094s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for didactalia took 9.74857473373413s
Availability | SPARQL endpoint availability check for DisGeNET took 1.7902517318725586s
Availability | VoID file availability check for DisGeNET took 0.0003478527069091797s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.3294408321380615s
Reputation | Calculation of the PageRank for DisGeNET took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.0001552104949951172s
Believability | Calculation of trust value for DisGeNET took 6.4373016357421875e-06s
INFO | --- Analysis for disgenet took 8.134134531021118s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.696846008300781e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2783501148223877s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02087712287902832s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.2901763916015625e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.2636184692382812e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 6.3981523513793945s
Availability | SPARQL endpoint availability check for DM2E took 9.1552734375e-05s
Availability | VoID file availability check for DM2E took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for DM2E took 0.30916309356689453s
Reputation | Calculation of the PageRank for DM2E took 0.021753787994384766s
Interlinking | Calculation of Degree of Connection for DM2E took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DM2E took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00010991096496582031s
Believability | Calculation of trust value for DM2E took 1.1920928955078125e-05s
INFO | --- Analysis for dm2e took 3.570563793182373s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 8.893013000488281e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.3332786560058594s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015020370483398438s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.0967254638671875e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 7.871148586273193s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 8.630752563476562e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.2960951328277588s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.02223038673400879s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.890296936035156e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 8.58306884765625e-06s
INFO | --- Analysis for doi took 7.775819301605225s
Availability | SPARQL endpoint availability check for Driggu Florentino took 9.274482727050781e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.3101310729980469s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020700931549072266s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.8371810913085938e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.239776611328125e-05s
INFO | --- Analysis for Driggu took 3.81541109085083s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 2.0221240520477295s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0003216266632080078s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.31221604347229004s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.5762786865234375e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.33514404296875e-05s
INFO | --- Analysis for drug-data-hifm took 17.887913465499878s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 272.16598868370056s
Availability | VoID file availability check for MetaLex Document Server took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.32079339027404785s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.5762786865234375e-05s
Believability | Calculation of trust value for MetaLex Document Server took 9.775161743164062e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.6094422340393s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.343893051147461s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0008256435394287109s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.30982160568237305s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020821809768676758s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.8623809814453125e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.3589859008789062e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 14.902240514755249s
Availability | SPARQL endpoint availability check for DWS-Group took 5.245208740234375e-05s
Availability | VoID file availability check for DWS-Group took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.28893446922302246s
Reputation | Calculation of the PageRank for DWS-Group took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for DWS-Group took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010180473327636719s
Believability | Calculation of trust value for DWS-Group took 1.239776611328125e-05s
INFO | --- Analysis for dws-group took 2.806884288787842s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 8.559226989746094e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.33144569396972656s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.02157878875732422s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.170967102050781e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.0728836059570312e-05s
INFO | --- Analysis for E1 took 4.521853446960449s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.09254693984985352s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.2936546802520752s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020786523818969727s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0009942054748535156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00014400482177734375s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-alaska took 2.8086130619049072s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.04195976257324219s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.28844332695007324s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020831823348999023s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.1021575927734375e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-cau took 2.854701280593872s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.0669093132019043s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.33946704864501953s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02065443992614746s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.175041198730469e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.8414525985717773s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.0421142578125s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0003986358642578125s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.29755735397338867s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.703636169433594e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-cdrewu took 2.7682080268859863s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.04370307922363281s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.3147871494293213s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02197861671447754s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0011112689971923828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00017571449279785156s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-dartmouth took 2.7949798107147217s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04882454872131348s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2756035327911377s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.020594358444213867s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.416175842285156e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i-famu took 2.818394660949707s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.05631875991821289s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.28736209869384766s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020864009857177734s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012874603271484375s
Believability | Calculation of trust value for eagle-i @ Harvard University took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i-harvard took 2.8399319648742676s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.04039788246154785s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.3390634059906006s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001270771026611328s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 8.821487426757812e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.848904848098755s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.03952646255493164s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.28931117057800293s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.437301635742188e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-howard took 2.7770192623138428s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.03520679473876953s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.31682276725769043s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.29425048828125e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.7969918251037598s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.04641294479370117s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.4257206916809082s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011610984802246094s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-jsu took 2.9064600467681885s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.035671234130859375s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.33921027183532715s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.838539123535156e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-meharry took 2.8240761756896973s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.040433645248413086s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2846038341522217s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010180473327636719s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-montana took 2.8749189376831055s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.03919672966003418s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.4725825786590576s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.022565126419067383s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.751319885253906e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-msm took 3.007216691970825s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.04717898368835449s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2705538272857666s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.021068811416625977s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0008542537689208984s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00013971328735351562s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.769651174545288s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.06950116157531738s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.27825427055358887s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020594358444213867s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 7.367134094238281e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-psm took 2.7548465728759766s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.06933712959289551s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.3178987503051758s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.413459777832031e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-tsu took 2.8290183544158936s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.06766796112060547s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2868175506591797s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.02227044105529785s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.389617919921875e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-tuskegee took 2.9368507862091064s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.04397726058959961s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.48583054542541504s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.021178245544433594s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010061264038085938s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 9.5367431640625e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.9867517948150635s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04022049903869629s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2948160171508789s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.028493881225585938s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0013158321380615234s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00017499923706054688s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-upr took 2.754591941833496s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.04891610145568848s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.000986337661743164s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.29815006256103516s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.02529144287109375s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.008148193359375e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-utep took 2.7815184593200684s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.04926919937133789s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00042629241943359375s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.3054630756378174s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.022572755813598633s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.937980651855469e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-utsa took 2.7660036087036133s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.17653131484985352s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.293255090713501s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.021866321563720703s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 0.00011849403381347656s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 2.8574018478393555s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.057089805603027344s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0003135204315185547s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.2698655128479004s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.295608520507812e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-xula took 2.718221426010132s
Availability | SPARQL endpoint availability check for Emergency situation took 0.6150801181793213s
Availability | VoID file availability check for Emergency situation took 0.0003421306610107422s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.3009216785430908s
Reputation | Calculation of the PageRank for Emergency situation took 0.02088475227355957s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.649162292480469e-05s
Believability | Calculation of trust value for Emergency situation took 4.5299530029296875e-06s
INFO | --- Analysis for Earthquake took 3.8173303604125977s
Availability | SPARQL endpoint availability check for ESO took 0.47556495666503906s
Availability | VoID file availability check for ESO took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for ESO took 0.3285183906555176s
Reputation | Calculation of the PageRank for ESO took 0.022566795349121094s
Interlinking | Calculation of Degree of Connection for ESO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ESO took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for ESO took 8.344650268554688e-05s
Believability | Calculation of trust value for ESO took 1.2159347534179688e-05s
INFO | --- Analysis for Earthquake_case took 4.633700370788574s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.10649704933166504s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.31168127059936523s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.02111077308654785s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010037422180175781s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for ecb-linked-data took 2.9986140727996826s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 9.244526624679565s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.31522130966186523s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.337860107421875e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 8.821487426757812e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 21.22717571258545s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.7351388931274414s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.30224013328552246s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.890296936035156e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 7.108842372894287s
Availability | SPARQL endpoint availability check for ECLAP took 20.78802752494812s
Availability | VoID file availability check for ECLAP took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for ECLAP took 0.2845323085784912s
Reputation | Calculation of the PageRank for ECLAP took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for ECLAP took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ECLAP took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.62396240234375e-05s
Believability | Calculation of trust value for ECLAP took 1.1682510375976562e-05s
INFO | --- Analysis for eclap took 53.686630964279175s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.506111145019531e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.2672414779663086s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.2636184692382812e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.3589859008789062e-05s
INFO | --- Analysis for ECNU-GISer took 4.654194116592407s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 8.916854858398438e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.27889037132263184s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.021386384963989258s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.459785461425781e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.2636184692382812e-05s
INFO | --- Analysis for ecs took 2.8100290298461914s
Availability | SPARQL endpoint availability check for Edublogs took 4.839897155761719e-05s
Availability | VoID file availability check for Edublogs took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for Edublogs took 0.3205273151397705s
Reputation | Calculation of the PageRank for Edublogs took 0.021485567092895508s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.72747802734375e-05s
Believability | Calculation of trust value for Edublogs took 1.2874603271484375e-05s
INFO | --- Analysis for edublogs took 3.6301662921905518s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.5826067924499512s
Availability | VoID file availability check for education.data.gov.uk took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.27178072929382324s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.022653579711914062s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.96453857421875e-05s
Believability | Calculation of trust value for education.data.gov.uk took 1.0251998901367188e-05s
INFO | --- Analysis for education-data-gov-uk took 5.747208833694458s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 391.522198677063s
Availability | VoID file availability check for Educational programs - SISVU took 0.0010037422180175781s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.5293715000152588s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.020912885665893555s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.817413330078125e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.049041748046875e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1319.8869788646698s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.1519525051116943s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.3212699890136719s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.021912336349487305s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.00543212890625e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 1.0013580322265625e-05s
INFO | --- Analysis for eea took 6.486051559448242s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5202434062957764s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.2825953960418701s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.02199554443359375s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0010786056518554688s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 6.413459777832031e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 9.059906005859375e-06s
INFO | --- Analysis for eea-rod took 5.598535776138306s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.1663351058959961s
Availability | VoID file availability check for EEA Vocabularies took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.33287715911865234s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 7.987022399902344e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.1920928955078125e-05s
INFO | --- Analysis for eea-vocabularies took 5.3955442905426025s
Availability | SPARQL endpoint availability check for E-Government Ontology took 30.228400945663452s
Availability | VoID file availability check for E-Government Ontology took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.34447288513183594s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.022162914276123047s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 2.9087066650390625e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for EGovOntology took 43.83471465110779s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5851376056671143s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005986690521240234s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.373342514038086s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2390825748443604s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7077856063842773s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9077460765838623s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.31728768348694s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.440608739852905s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5773394107818604s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7835824489593506s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24879837036132812s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4234480857849121s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.121906757354736s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2614884376525879s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4746592044830322s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6824681758880615s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.31912994384765625s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.40416955947875977s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26145052909851074s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.071103811264038s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 7.128715515136719e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3340120315551758s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2618706226348877s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.42957425117492676s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2638845443725586s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.30179810523986816s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.941469669342041s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24189090728759766s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.998572111129761s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2364335060119629s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.34991979598999023s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.36881470680236816s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3798327445983887s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030990123748779297s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.027979135513305664s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2452075481414795s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.228801012039185s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4192650318145752s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.2684998512268066s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2686614990234375s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.143712997436523s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03446698188781738s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5052211284637451s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5820157527923584s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3296.590697288513s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9289689064025879s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.021657705307006836s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.5789947509765625e-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.1682510375976562e-05s
INFO | --- Analysis for ei2a took 3535.075360774994s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 8.988380432128906e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2930471897125244s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010824203491210938s
Believability | Calculation of trust value for EIONET RDF Data took 8.106231689453125e-06s
INFO | --- Analysis for eionet-rdf took 3.3012287616729736s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 0.0001049041748046875s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.2865273952484131s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.021863937377929688s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.0517578125e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.3113021850585938e-05s
INFO | --- Analysis for ElgooG_ took 2.634817361831665s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.178553104400635s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.3089475631713867s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.02274489402770996s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 8.368492126464844e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.0967254638671875e-05s
INFO | --- Analysis for elviajero took 25.195124626159668s
Availability | SPARQL endpoint availability check for EMN took 8.96453857421875e-05s
Availability | VoID file availability check for EMN took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for EMN took 0.32640933990478516s
Reputation | Calculation of the PageRank for EMN took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for EMN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for EMN took 4.0531158447265625e-05s
Believability | Calculation of trust value for EMN took 1.5020370483398438e-05s
INFO | --- Analysis for emn took 2.9626922607421875s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.506111145019531e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.28899359703063965s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02254629135131836s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.054473876953125e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 9.5367431640625e-06s
INFO | --- Analysis for enakting-co2emission took 2.7688145637512207s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 9.965896606445312e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0012063980102539062s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.27601099014282227s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.0226898193359375s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.076957702636719e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for enakting-crime took 2.796496629714966s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.38690185546875e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.2655055522918701s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.022371292114257812s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.6716461181640625e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 7.867813110351562e-06s
INFO | --- Analysis for enakting-energy took 2.641160011291504s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 8.869171142578125e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.3257288932800293s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.131431579589844e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-mortality took 2.790010452270508s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 8.487701416015625e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.302112340927124s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020874738693237305s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.719329833984375e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 8.106231689453125e-06s
INFO | --- Analysis for enakting-nhs took 2.746958017349243s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 8.702278137207031e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2879664897918701s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.02078080177307129s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.3882598876953125e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 8.106231689453125e-06s
INFO | --- Analysis for enakting-population took 2.7459139823913574s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.7891535758972168s
Availability | VoID file availability check for English Heritage Periods List took 0.0008084774017333984s
Extra | Recovery of all triples for English Heritage Periods List took 0.321216344833374s
Performance | Total latancy measurement for English Heritage Periods List took 1.5782966613769531s
Amount of data | Number of triples check for English Heritage Periods List took 0.492919921875s
Versatility | Languages check for English Heritage Periods List took 0.2663414478302002s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.46343469619750977s
Security | Check HTTPS for English Heritage Periods List took 0.22516250610351562s
Interpretability | RDF structures check for English Heritage Periods List took 0.33893728256225586s
Versatility | Serialization formats check for English Heritage Periods List took 0.42957568168640137s
Availability | RDF dump link check for English Heritage Periods List took 0.3658421039581299s
License | MR license check for English Heritage Periods List took 0.40421152114868164s
License | HR license check for English Heritage Periods List took 0.3330879211425781s
Amount of data | Number of property check for English Heritage Periods List took 0.36283183097839355s
Understandability | Number of label check for English Heritage Periods List took 0.43676090240478516s
Understandability | URI regex check for English Heritage Periods List took 0.6979568004608154s
Understandability | Vocabs check for English Heritage Periods List took 0.3734910488128662s
Verifiability | Authors check for English Heritage Periods List took 0.40354228019714355s
Verifiability | Publishers check for English Heritage Periods List took 0.34963488578796387s
Performance | Throughput check for English Heritage Periods List took 12.261111497879028s
Amount of data | Check the number of entities for English Heritage Periods List took 7.963180541992188e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.33734846115112305s
Interlinking | sameAs chians check for English Heritage Periods List took 0.3355393409729004s
Interlinking | skos check for English Heritage Periods List took 0.36675453186035156s
Interlinking | skos check for English Heritage Periods List took 0.3288125991821289s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.3875699043273926s
Currency | Creation date check for English Heritage Periods List took 0.6190550327301025s
Currency | Modification date check for English Heritage Periods List took 0.634688138961792s
Rep.Conc. | URIs length for English Heritage Periods List took 0.6340174674987793s
Interoperability | New vocabularies check for English Heritage Periods List took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.4134645462036133s
Accuracy | Check Functional Property for English Heritage Periods List took 0.29482126235961914s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.34214186668395996s
Consistency | Disjoint class check for English Heritage Periods List took 0.3078029155731201s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.324171781539917s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6096341609954834s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00014257431030273438s
Security | Sign check for English Heritage Periods List took 0.3317267894744873s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.3010523319244385s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.021413803100585938s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 9.5367431640625e-07s
Believability | Calculation of trust value for English Heritage Periods List took 1.0967254638671875e-05s
INFO | --- Analysis for english-heritage-periods-list took 53.22681403160095s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.5916457176208496s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0006482601165771484s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.1275558471679688s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.09236478805542s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.9057478904724121s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.6666696071624756s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.4423506259918213s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.18133783340454s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.18454670906066895s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.42827630043029785s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.2285623550415039s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 55.21303367614746s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.33333730697631836s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.233381032943726s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.14515042304992676s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.2737593650817871s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.2960357666015625s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.572622537612915s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.24445295333862305s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.32863306999206543s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.853564262390137s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 7.128715515136719e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.17728257179260254s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.39289116859436035s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.29812049865722656s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.22428679466247559s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.16702771186828613s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.5018348693847656s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.4705977439880371s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 2.8608334064483643s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.1476612091064453s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.15215134620666504s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 1.2138304710388184s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.33447718620300293s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 1.961226224899292s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 2.160132646560669s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.5628328323364258s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.00014066696166992188s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.6416060924530029s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.250598669052124s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.3603787422180176s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 4.267692565917969e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.430511474609375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 8.106231689453125e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 286.39013051986694s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.16411399841308594s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0003345012664794922s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.1536052227020264s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.9057013988494873s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.13265490531921387s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.5243034362792969s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.3428928852081299s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.26041078567505s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.21607661247253418s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.2244715690612793s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.277407169342041s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 55.11442446708679s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.13883519172668457s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.265318393707275s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.2289268970489502s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.24655413627624512s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.4482302665710449s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.24111437797546387s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.23675060272216797s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.606942892074585s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.493572473526001s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 4.458427429199219e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.212921142578125s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.14366507530212402s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.2240006923675537s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.16511058807373047s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.12494874000549316s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.3711690902709961s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.21819138526916504s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.466831922531128s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 6.699562072753906e-05s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.13741683959960938s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.14812159538269043s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.1336815357208252s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.13222026824951172s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.48607444763183594s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.1010568141937256s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.6556568145751953s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.0001652240753173828s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.34075403213500977s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.23632311820983887s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.3052945137023926s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.933906555175781e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.430511474609375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 9.298324584960938e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 274.05880856513977s
Availability | SPARQL endpoint availability check for English WordNet took 0.00012922286987304688s
Availability | VoID file availability check for English WordNet took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for English WordNet took 0.28346920013427734s
Reputation | Calculation of the PageRank for English WordNet took 0.02213764190673828s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.457069396972656e-05s
Believability | Calculation of trust value for English WordNet took 9.5367431640625e-06s
INFO | --- Analysis for english-wordnet took 3.422386884689331s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.09166526794433594s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.27696943283081055s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.021175622940063477s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 9.250640869140625e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.049041748046875e-05s
INFO | --- Analysis for enipedia took 2.8794538974761963s
Availability | SPARQL endpoint availability check for Enslaved.org took 9.083747863769531e-05s
Availability | VoID file availability check for Enslaved.org took 0.0007891654968261719s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.32198166847229004s
Reputation | Calculation of the PageRank for Enslaved.org took 0.021677017211914062s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.600120544433594e-05s
Believability | Calculation of trust value for Enslaved.org took 1.33514404296875e-05s
INFO | --- Analysis for enslaved.org took 5.017053842544556s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.4053175449371338s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.29886484146118164s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.02084493637084961s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.14984130859375e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 5.4836273193359375e-06s
INFO | --- Analysis for entice-graph took 3.269313335418701s
Availability | SPARQL endpoint availability check for Entrez Gene took 9.036064147949219e-05s
Availability | VoID file availability check for Entrez Gene took 0.0009179115295410156s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.3019106388092041s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.600120544433594e-05s
Believability | Calculation of trust value for Entrez Gene took 1.3589859008789062e-05s
INFO | --- Analysis for entrez_gene took 27.41991925239563s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0820293426513672s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.2955749034881592s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.02232503890991211s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.984306335449219e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 5.9604644775390625e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 12.10856556892395s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.31594419479370117s
Availability | VoID file availability check for environment.data.gov.uk took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.28015995025634766s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.02255558967590332s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.7206878662109375e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.675983190536499s
Availability | SPARQL endpoint availability check for EARTh took 270.77001905441284s
Availability | VoID file availability check for EARTh took 0.00079345703125s
Completeness | Calculation of interlinking completeness for EARTh took 0.31902170181274414s
Reputation | Calculation of the PageRank for EARTh took 0.02098679542541504s
Interlinking | Calculation of Degree of Connection for EARTh took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010371208190917969s
Believability | Calculation of trust value for EARTh took 1.2636184692382812e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 562.3210327625275s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.5801968574523926s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0004894733428955078s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 114.35662627220154s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.9470686912536621s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.37614393234253s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.170764207839966s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.2277262210846s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.4065165519714355s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.3660726547241211s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 9.259641647338867s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.41198039054870605s
License | MR license check for Micka (EO metadata) @PSNC took 0.8884496688842773s
License | HR license check for Micka (EO metadata) @PSNC took 300.22849106788635s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.2134685516357422s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 3.005232572555542s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 1.1569781303405762s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.6427326202392578s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.22243285179138184s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.24368929862976074s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.556888103485107s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 8.20159912109375e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.21984577178955078s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.20798015594482422s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.5087306499481201s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.43947911262512207s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 6.6682984828948975s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.46193504333496094s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.2484583854675293s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 151.2210874557495s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.20672082901000977s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.5103878974914551s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.5334897041320801s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 36.64823007583618s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.67728853225708s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.632361650466919s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.2000126838684082s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 86.26297354698181s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.355316638946533s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 32.21022939682007s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.3262355327606201s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 87.05539631843567s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.7953975200653076s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5285112857818604s
Security | Sign check for Micka (EO metadata) @PSNC took 1.6301438808441162s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 9.320285558700562s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.501274824142456s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.02249002456665039s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for EO_metadata took 2260.8598957061768s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.6253204345703125e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0007781982421875s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.33747220039367676s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.02048182487487793s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.2901763916015625e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 1.0967254638671875e-05s
INFO | --- Analysis for EOKP-Datasets took 3.6122210025787354s
Availability | SPARQL endpoint availability check for EPA-CDR took 0.00012874603271484375s
Availability | VoID file availability check for EPA-CDR took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.2993330955505371s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.4809112548828125e-05s
Believability | Calculation of trust value for EPA-CDR took 8.344650268554688e-06s
INFO | --- Analysis for epa-cdr took 8.014975786209106s
Availability | SPARQL endpoint availability check for EPA-FRS took 8.511543273925781e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.301128625869751s
Reputation | Calculation of the PageRank for EPA-FRS took 0.021883249282836914s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.033348083496094e-05s
Believability | Calculation of trust value for EPA-FRS took 8.106231689453125e-06s
INFO | --- Analysis for epa-frs took 6.266767978668213s
Availability | SPARQL endpoint availability check for EPA-RCRA took 8.869171142578125e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.3189890384674072s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.218650817871094e-05s
Believability | Calculation of trust value for EPA-RCRA took 9.059906005859375e-06s
INFO | --- Analysis for epa-rcra took 6.428196668624878s
Availability | SPARQL endpoint availability check for EPA-SRS took 8.797645568847656e-05s
Availability | VoID file availability check for EPA-SRS took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.3324110507965088s
Reputation | Calculation of the PageRank for EPA-SRS took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.295608520507812e-05s
Believability | Calculation of trust value for EPA-SRS took 7.3909759521484375e-06s
INFO | --- Analysis for epa-srs took 9.376107931137085s
Availability | SPARQL endpoint availability check for EPA-TRI took 8.797645568847656e-05s
Availability | VoID file availability check for EPA-TRI took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2953181266784668s
Reputation | Calculation of the PageRank for EPA-TRI took 0.02202129364013672s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.24249267578125e-05s
Believability | Calculation of trust value for EPA-TRI took 9.5367431640625e-06s
INFO | --- Analysis for epa-tri took 6.229656457901001s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.04594230651855469s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.32335877418518066s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020632266998291016s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001277923583984375s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.932633399963379s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.49248838424682617s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.27568864822387695s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.02068161964416504s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.0108642578125e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.239776611328125e-05s
INFO | --- Analysis for eprtr took 3.896228313446045s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.5481674671173096s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0005364418029785156s
Extra | Recovery of all triples for Railway Infrastructure KG took 57.01612734794617s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.0993494987487793s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.26638150215148926s
Interoperability | New terms check for Railway Infrastructure KG took 1.7299695014953613s
Versatility | Languages check for Railway Infrastructure KG took 75.87992024421692s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.28755617141723633s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.5570094585418701s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.2474963665008545s
Availability | RDF dump link check for Railway Infrastructure KG took 0.22977495193481445s
License | MR license check for Railway Infrastructure KG took 0.298464298248291s
License | HR license check for Railway Infrastructure KG took 65.7443482875824s
Amount of data | Number of property check for Railway Infrastructure KG took 0.25756263732910156s
Understandability | Number of label check for Railway Infrastructure KG took 0.5311458110809326s
Understandability | URI regex check for Railway Infrastructure KG took 0.49469804763793945s
Understandability | Vocabs check for Railway Infrastructure KG took 0.26604318618774414s
Verifiability | Authors check for Railway Infrastructure KG took 0.3865818977355957s
Verifiability | Publishers check for Railway Infrastructure KG took 0.20681357383728027s
Performance | Throughput check for Railway Infrastructure KG took 11.25077509880066s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.25569605827331543s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.21109986305236816s
Interlinking | skos check for Railway Infrastructure KG took 0.28180527687072754s
Interlinking | skos check for Railway Infrastructure KG took 0.2463364601135254s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.238478422164917s
Currency | Creation date check for Railway Infrastructure KG took 0.5213413238525391s
Currency | Modification date check for Railway Infrastructure KG took 0.24430322647094727s
Rep.Conc. | URIs length for Railway Infrastructure KG took 23.009801864624023s
Interoperability | New vocabularies check for Railway Infrastructure KG took 27.40876841545105s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.21098589897155762s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.26918983459472656s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.24957776069641113s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 13.738573789596558s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 2.604965925216675s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.645413637161255s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.30751609802246094s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 1.7073044776916504s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.4990394115448s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 18.203826904296875s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.4827141761779785s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 2.8716979026794434s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 2.9864397048950195s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.356978178024292s
Security | Sign check for Railway Infrastructure KG took 0.45871520042419434s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2373.1065480709076s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.54693603515625s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.022718191146850586s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 9.226799011230469e-05s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 28.50043749809265s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.3828277587890625e-05s
INFO | --- Analysis for ERAKG took 2832.6433935165405s
Availability | SPARQL endpoint availability check for reg took 8.96453857421875e-05s
Availability | VoID file availability check for reg took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for reg took 0.2842831611633301s
Reputation | Calculation of the PageRank for reg took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for reg took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for reg took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for reg took 1.1920928955078125e-05s
Believability | Calculation of trust value for reg took 1.239776611328125e-05s
INFO | --- Analysis for erg took 2.7083399295806885s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.5299472808837891s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.3013274669647217s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.24249267578125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 9.298324584960938e-06s
INFO | --- Analysis for es-msssi-drug-prices took 3.51084041595459s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 6.723403930664062e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.3184692859649658s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.022602081298828125s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.845329284667969e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 9.5367431640625e-06s
INFO | --- Analysis for esd-standards took 4.459815502166748s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 9.322166442871094e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.2897334098815918s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.022481441497802734s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.414817810058594e-05s
Believability | Calculation of trust value for ESD-Toolkit took 8.344650268554688e-06s
INFO | --- Analysis for esd-toolkit took 3.673973798751831s
Availability | SPARQL endpoint availability check for Dataset Esis took 9.226799011230469e-05s
Availability | VoID file availability check for Dataset Esis took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.272444486618042s
Reputation | Calculation of the PageRank for Dataset Esis took 0.021053075790405273s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.1948089599609375e-05s
Believability | Calculation of trust value for Dataset Esis took 1.0013580322265625e-05s
INFO | --- Analysis for esislearning took 3.158478021621704s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 9.107589721679688e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.27720189094543457s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.02185988426208496s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.24249267578125e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 9.5367431640625e-06s
INFO | --- Analysis for ESV took 4.397152662277222s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.5898351669311523s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.289872407913208s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.021045207977294922s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.340186595916748s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 9.581647396087646s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.000640869140625s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.29663848876953125s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020831823348999023s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.653236389160156e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.3828277587890625e-05s
INFO | --- Analysis for eu-agencies-bodies took 23.882809162139893s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 8.630752563476562e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.30213260650634766s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.022084712982177734s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.390975952148438e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 7.867813110351562e-06s
INFO | --- Analysis for eu-institutions took 9.123193502426147s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.498852014541626s
Availability | VoID file availability check for EU Parliament Media Library took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.3298990726470947s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020916461944580078s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.743171691894531e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 8.106231689453125e-06s
INFO | --- Analysis for eu-parliament-media took 10.450483083724976s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.361175775527954s
Availability | VoID file availability check for EU Who Is Who took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2802894115447998s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.02083301544189453s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.7670135498046875e-05s
Believability | Calculation of trust value for EU Who Is Who took 7.62939453125e-06s
INFO | --- Analysis for eu-who-is-who took 15.891252040863037s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.3864827156066895s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.2893195152282715s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.021863698959350586s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.291534423828125e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for eumida-linked-data took 13.354337453842163s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.375931978225708s
Availability | VoID file availability check for European Nature Information System took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.29584431648254395s
Reputation | Calculation of the PageRank for European Nature Information System took 0.021228313446044922s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010585784912109375s
Believability | Calculation of trust value for European Nature Information System took 1.049041748046875e-05s
INFO | --- Analysis for eunis took 4.702517509460449s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 7.939146518707275s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0007734298706054688s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.2962963581085205s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.022446393966674805s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.390975952148438e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.0013580322265625e-05s
INFO | --- Analysis for eur-lex-rdf took 20.825689554214478s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.4200410842895508s
Availability | VoID file availability check for Standard Eurobarometer took 0.0007627010345458984s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.28643798828125s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.02135610580444336s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.363059997558594e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 8.344650268554688e-06s
INFO | --- Analysis for eurobarometer-standard took 12.285302639007568s
Availability | SPARQL endpoint availability check for European Election Results took 1.544806957244873s
Availability | VoID file availability check for European Election Results took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2892792224884033s
Reputation | Calculation of the PageRank for European Election Results took 0.020946741104125977s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.8623809814453125e-05s
Believability | Calculation of trust value for European Election Results took 9.775161743164062e-06s
INFO | --- Analysis for european-election-results took 13.11649751663208s
Availability | SPARQL endpoint availability check for EPO patents took 0.47435808181762695s
Availability | VoID file availability check for EPO patents took 0.0006082057952880859s
Extra | Recovery of all triples for EPO patents took 27.588971614837646s
Performance | Total latancy measurement for EPO patents took 1.0781261920928955s
Amount of data | Number of triples check for EPO patents took 90.19961833953857s
Versatility | Languages check for EPO patents took 100.30230712890625s
Interpretability | Number of blank nodes check for EPO patents took 90.30563712120056s
Interpretability | RDF structures check for EPO patents took 0.3948678970336914s
Versatility | Serialization formats check for EPO patents took 0.24057960510253906s
Availability | RDF dump link check for EPO patents took 0.27702879905700684s
License | MR license check for EPO patents took 0.2672758102416992s
License | HR license check for EPO patents took 90.2180426120758s
Amount of data | Number of property check for EPO patents took 0.2757697105407715s
Understandability | Number of label check for EPO patents took 90.16273260116577s
Understandability | URI regex check for EPO patents took 0.5989141464233398s
Understandability | Vocabs check for EPO patents took 0.23174571990966797s
Verifiability | Authors check for EPO patents took 0.250354528427124s
Verifiability | Publishers check for EPO patents took 0.312938928604126s
Performance | Throughput check for EPO patents took 11.137139320373535s
Amount of data | Check the number of entities for EPO patents took 7.390975952148438e-05s
Verifiability | Contribs. check for EPO patents took 0.21459412574768066s
Interlinking | sameAs chians check for EPO patents took 0.20806407928466797s
Interlinking | skos check for EPO patents took 0.2749941349029541s
Interlinking | skos check for EPO patents took 0.15323257446289062s
Timeliness | dataset update frequency check for EPO patents took 0.20021986961364746s
Currency | Creation date check for EPO patents took 0.4183075428009033s
Currency | Modification date check for EPO patents took 0.368135929107666s
Rep.Conc. | URIs length for EPO patents took 134.81236720085144s
Interoperability | New vocabularies check for EPO patents took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.20649123191833496s
Accuracy | Check Empty annotation labels for EPO patents took 20.963411569595337s
Accuracy | Check White space in annotation for EPO patents took 3.020916223526001s
Accuracy | Check Datatype consistency for EPO patents took 4.8549888134002686s
Consistency | Disjoint class check for EPO patents took 0.2824416160583496s
Consistency | Check Misplaced properties for EPO patents took 100.3812198638916s
Consistency | Check Ontology hijacking for EPO patents took 23.328583002090454s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.573075294494629s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.58046889305115s
Conciseness | Check Extensional conciseness for EPO patents took 2.903695821762085s
Conciseness | Check Intensional conciseness for EPO patents took 0.3955717086791992s
Security | Sign check for EPO patents took 0.2612879276275635s
Availability | Check URIs Dereferenciability for EPO patents took 1.782850742340088s
Completeness | Calculation of interlinking completeness for EPO patents took 0.7022223472595215s
Reputation | Calculation of the PageRank for EPO patents took 0.021659135818481445s
Interlinking | Calculation of Degree of Connection for EPO patents took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.9073486328125e-06s
Believability | Calculation of trust value for EPO patents took 1.0251998901367188e-05s
INFO | --- Analysis for European_Patent_Information took 1199.3657548427582s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 9.059906005859375e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.3739020824432373s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02113199234008789s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 0.00010466575622558594s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 9.059906005859375e-06s
INFO | --- Analysis for europeana-lod-v1 took 7.872015714645386s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.4080190658569336s
Availability | VoID file availability check for Europeana SPARQL took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.2849586009979248s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.863739013671875e-05s
Believability | Calculation of trust value for Europeana SPARQL took 8.106231689453125e-06s
INFO | --- Analysis for europeana-sparql took 6.537737607955933s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.08968687057495117s
Availability | VoID file availability check for EuroSentiment took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.3924415111541748s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02238297462463379s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.886222839355469e-05s
Believability | Calculation of trust value for EuroSentiment took 1.2636184692382812e-05s
INFO | --- Analysis for eurosentiment took 3.662423610687256s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 8.630752563476562e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.29662418365478516s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.021999120712280273s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.963180541992188e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 8.344650268554688e-06s
INFO | --- Analysis for eurostat-rdf took 12.641952991485596s
Availability | SPARQL endpoint availability check for EuroVoc took 0.17132329940795898s
Availability | VoID file availability check for EuroVoc took 0.0006592273712158203s
Extra | Recovery of all triples for EuroVoc took 183.0851595401764s
Performance | Total latancy measurement for EuroVoc took 0.626807451248169s
Amount of data | Number of triples check for EuroVoc took 42.79630255699158s
Interoperability | New terms check for EuroVoc took 57.430211782455444s
Versatility | Languages check for EuroVoc took 300.15394735336304s
Interpretability | Number of blank nodes check for EuroVoc took 15.624069452285767s
Security | Check HTTPS for EuroVoc took 0.36696386337280273s
Interpretability | RDF structures check for EuroVoc took 0.45062708854675293s
Versatility | Serialization formats check for EuroVoc took 3.7640633583068848s
Availability | RDF dump link check for EuroVoc took 0.19908547401428223s
License | MR license check for EuroVoc took 0.4538760185241699s
License | HR license check for EuroVoc took 300.0606393814087s
Amount of data | Number of property check for EuroVoc took 0.15808343887329102s
Understandability | Number of label check for EuroVoc took 1.517474889755249s
Understandability | URI regex check for EuroVoc took 0.4005286693572998s
Understandability | Vocabs check for EuroVoc took 0.10314297676086426s
Verifiability | Authors check for EuroVoc took 0.1093590259552002s
Verifiability | Publishers check for EuroVoc took 0.17879056930541992s
Performance | Throughput check for EuroVoc took 10.815218687057495s
Amount of data | Check the number of entities for EuroVoc took 3.123283386230469e-05s
Verifiability | Contribs. check for EuroVoc took 0.19628167152404785s
Interlinking | sameAs chians check for EuroVoc took 6.491267204284668s
Interlinking | skos check for EuroVoc took 0.1936321258544922s
Interlinking | skos check for EuroVoc took 0.13581013679504395s
Timeliness | dataset update frequency check for EuroVoc took 0.2891981601715088s
Currency | Creation date check for EuroVoc took 0.2874479293823242s
Currency | Modification date check for EuroVoc took 0.1362307071685791s
Rep.Conc. | URIs length for EuroVoc took 404.60761404037476s
Interoperability | New vocabularies check for EuroVoc took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.19054794311523438s
Accuracy | Check Functional Property for EuroVoc took 0.19739651679992676s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.16947603225708008s
Accuracy | Check Empty annotation labels for EuroVoc took 40.51034355163574s
Accuracy | Check White space in annotation for EuroVoc took 3.1906063556671143s
Accuracy | Check Datatype consistency for EuroVoc took 2.6177568435668945s
Consistency | Disjoint class check for EuroVoc took 0.16892385482788086s
Consistency | Check Misplaced properties for EuroVoc took 300.407808303833s
Consistency | Misplaced classes for EuroVoc took 8.423704862594604s
Consistency | Check Ontology hijacking for EuroVoc took 43.71455407142639s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.6731376647949219s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.45211815834045s
Conciseness | Check Extensional conciseness for EuroVoc took 3.0847039222717285s
Conciseness | Check Intensional conciseness for EuroVoc took 0.3500351905822754s
Security | Sign check for EuroVoc took 0.12961173057556152s
Availability | Check URIs Dereferenciability for EuroVoc took 11.40931248664856s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.7216026782989502s
Reputation | Calculation of the PageRank for EuroVoc took 0.021109342575073242s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 7.963180541992188e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.9073486328125e-06s
Believability | Calculation of trust value for EuroVoc took 9.5367431640625e-06s
INFO | --- Analysis for eurovoc took 15008.410455226898s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 0.00016069412231445312s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.30910563468933105s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 3.147125244140625e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.553794860839844e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 5.0067901611328125e-06s
INFO | --- Analysis for euskadi-farmacias took 5.442331552505493s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.6785321235656738s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.30472898483276367s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.0217282772064209s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.337860107421875e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.2874603271484375e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.473840713500977s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.5620570182800293s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0008680820465087891s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.278688907623291s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.021775245666503906s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 8.893013000488281e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 7.3909759521484375e-06s
INFO | --- Analysis for eutc-productions took 7.991358518600464s
Availability | SPARQL endpoint availability check for EventMedia took 0.3968539237976074s
Availability | VoID file availability check for EventMedia took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for EventMedia took 0.2830061912536621s
Reputation | Calculation of the PageRank for EventMedia took 0.02062201499938965s
Interlinking | Calculation of Degree of Connection for EventMedia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EventMedia took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010728836059570312s
Believability | Calculation of trust value for EventMedia took 1.049041748046875e-05s
INFO | --- Analysis for event-media took 19.761147260665894s
Availability | SPARQL endpoint availability check for EventKG took 8.440017700195312e-05s
Availability | VoID file availability check for EventKG took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for EventKG took 0.3291788101196289s
Reputation | Calculation of the PageRank for EventKG took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for EventKG took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EventKG took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.153915405273438e-05s
Believability | Calculation of trust value for EventKG took 1.2159347534179688e-05s
INFO | --- Analysis for eventkg took 4.993445158004761s
Availability | SPARQL endpoint availability check for Eventseer took 7.520427942276001s
Availability | VoID file availability check for Eventseer took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Eventseer took 0.30298781394958496s
Reputation | Calculation of the PageRank for Eventseer took 0.022467613220214844s
Interlinking | Calculation of Degree of Connection for Eventseer took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Eventseer took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.553794860839844e-05s
Believability | Calculation of trust value for Eventseer took 1.0251998901367188e-05s
INFO | --- Analysis for eventseer took 10.32627248764038s
Availability | SPARQL endpoint availability check for Face Link took 4.2438507080078125e-05s
Availability | VoID file availability check for Face Link took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Face Link took 0.2918064594268799s
Reputation | Calculation of the PageRank for Face Link took 0.021280765533447266s
Interlinking | Calculation of Degree of Connection for Face Link took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Face Link took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.170967102050781e-05s
Believability | Calculation of trust value for Face Link took 1.4543533325195312e-05s
INFO | --- Analysis for Face_Link took 2.6095402240753174s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5926511287689209s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0005464553833007812s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 125.62877440452576s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9588930606842041s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.171845197677612s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.131854772567749s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2632451057434s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.3408937454223633s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.35853147506713867s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.748327016830444s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.40369534492492676s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9412393569946289s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2001848220825s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22174501419067383s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.4924097061157227s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.188826084136963s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6126506328582764s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21062827110290527s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22997641563415527s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.369967222213745s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.677078247070312e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18126606941223145s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22399568557739258s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.48953747749328613s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4290585517883301s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.975567102432251s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.49593496322631836s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.263779878616333s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 151.44322967529297s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21077179908752441s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4490330219268799s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.45510411262512207s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 38.911189556121826s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6973705291748047s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6808695793151855s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19347882270812988s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 86.21302080154419s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.394275903701782s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 30.83844017982483s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3924691677093506s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 86.99104833602905s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.814225673675537s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5230517387390137s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4044296741485596s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.31569528579712s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5246257781982422s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.02146625518798828s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.435943603515625e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0728836059570312e-05s
INFO | --- Analysis for FADN_(2019) took 2278.7495019435883s
Availability | SPARQL endpoint availability check for FAMEData took 8.797645568847656e-05s
Availability | VoID file availability check for FAMEData took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for FAMEData took 0.3124864101409912s
Reputation | Calculation of the PageRank for FAMEData took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.266334533691406e-05s
Believability | Calculation of trust value for FAMEData took 1.1444091796875e-05s
INFO | --- Analysis for famedata took 7.783265590667725s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.2786097526550293s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00010037422180175781s
Believability | Calculation of trust value for FAO geopolitical ontology took 8.58306884765625e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 111.53879284858704s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.24851632118225098s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.28801679611206055s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.584426879882812e-05s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for fao-linked-data took 2.9186527729034424s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 8.96453857421875e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.2979624271392822s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.075599670410156e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.0967254638671875e-05s
INFO | --- Analysis for FAO_species took 2.7110788822174072s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.625919103622437s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.33947134017944336s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.021462440490722656s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.1484832763671875e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.2159347534179688e-05s
INFO | --- Analysis for farmbio-chembl took 72.16525268554688s
Availability | SPARQL endpoint availability check for I4.0-Onto took 8.797645568847656e-05s
Availability | VoID file availability check for I4.0-Onto took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.27396440505981445s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.02093648910522461s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 2.765655517578125e-05s
Believability | Calculation of trust value for I4.0-Onto took 2.1457672119140625e-05s
INFO | --- Analysis for fatimazahra took 2.762303113937378s
Availability | SPARQL endpoint availability check for FHIR STU3 took 8.869171142578125e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.2982931137084961s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020885229110717773s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.8848648071289062e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.0967254638671875e-05s
INFO | --- Analysis for FHIR_STU3 took 3.029129981994629s
Availability | SPARQL endpoint availability check for FiESTA took 8.559226989746094e-05s
Availability | VoID file availability check for FiESTA took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for FiESTA took 0.3105051517486572s
Reputation | Calculation of the PageRank for FiESTA took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.838539123535156e-05s
Believability | Calculation of trust value for FiESTA took 1.2159347534179688e-05s
INFO | --- Analysis for fiesta took 12.911993503570557s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 8.702278137207031e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.30075955390930176s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.022101402282714844s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.9087066650390625e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1444091796875e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.694406270980835s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 8.726119995117188e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.295149564743042s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.021318674087524414s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.009506225585938e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 8.344650268554688e-06s
INFO | --- Analysis for finnish-municipalities took 3.6970126628875732s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.19697117805480957s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0005977153778076172s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 120.54076290130615s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.9639546871185303s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 8.843710899353027s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.05863642692566s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.2427108287811s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 1.8609058856964111s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.2122058868408203s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 8.956397533416748s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.1763613224029541s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.1935276985168457s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.1881697177887s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.19378924369812012s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 1.185509204864502s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 1.272871732711792s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.19287443161010742s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.21193146705627441s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.24057388305664062s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.474767684936523s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 7.43865966796875e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.1804184913635254s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.19595813751220703s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4363689422607422s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4135110378265381s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 5.325694799423218s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.4885697364807129s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.2129523754119873s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 150.49038171768188s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.17596960067749023s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.19086813926696777s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.19659781455993652s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 34.17045521736145s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.693126916885376s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.6455256938934326s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.21681857109069824s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 86.05616450309753s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.359393835067749s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 31.258276224136353s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.326406717300415s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 86.7555775642395s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.819455146789551s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.4956536293029785s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.20933055877685547s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 10.246005773544312s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 20.445199728012085s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.021924734115600586s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 5.817413330078125e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2296.1770391464233s
Availability | SPARQL endpoint availability check for Fishes of Texas took 8.940696716308594e-05s
Availability | VoID file availability check for Fishes of Texas took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.31608128547668457s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.153915405273438e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.0728836059570312e-05s
INFO | --- Analysis for fishes-of-texas took 3.2606263160705566s
Availability | SPARQL endpoint availability check for flickr? wrappr took 9.179115295410156e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.27332472801208496s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.023293495178222656s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.012222290039062e-05s
Believability | Calculation of trust value for flickr? wrappr took 1.1205673217773438e-05s
INFO | --- Analysis for flickr-wrappr took 3.8694770336151123s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.267692565917969e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.2794051170349121s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.02071213722229004s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.0040740966796875e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.2874603271484375e-05s
INFO | --- Analysis for FLUS took 7.949656963348389s
Availability | SPARQL endpoint availability check for Flybase took 1.2345683574676514s
Availability | VoID file availability check for Flybase took 0.0011475086212158203s
Completeness | Calculation of interlinking completeness for Flybase took 0.3047599792480469s
Reputation | Calculation of the PageRank for Flybase took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for Flybase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.4809112548828125e-05s
Believability | Calculation of trust value for Flybase took 1.0967254638671875e-05s
INFO | --- Analysis for flybase took 5.842987298965454s
Availability | SPARQL endpoint availability check for Flyted took 1.0105388164520264s
Availability | VoID file availability check for Flyted took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Flyted took 0.3220860958099365s
Reputation | Calculation of the PageRank for Flyted took 0.02083897590637207s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Flyted took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.0279159545898438e-05s
Believability | Calculation of trust value for Flyted took 1.0251998901367188e-05s
INFO | --- Analysis for flyted took 5.850926399230957s
Availability | SPARQL endpoint availability check for Foodista took 9.835465431213379s
Availability | VoID file availability check for Foodista took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Foodista took 0.2802257537841797s
Reputation | Calculation of the PageRank for Foodista took 0.02076888084411621s
Interlinking | Calculation of Degree of Connection for Foodista took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.743171691894531e-05s
Believability | Calculation of trust value for Foodista took 1.1920928955078125e-05s
INFO | --- Analysis for foodista took 48.8097083568573s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.17801928520202637s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2860736846923828s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.343292236328125e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.2159347534179688e-05s
INFO | --- Analysis for foodpedia took 2.8262667655944824s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.410743713378906e-05s
Availability | VoID file availability check for FrameBase schema took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.2907071113586426s
Reputation | Calculation of the PageRank for FrameBase schema took 0.020760536193847656s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.363059997558594e-05s
Believability | Calculation of trust value for FrameBase schema took 1.2874603271484375e-05s
INFO | --- Analysis for framebase-schema took 3.3268513679504395s
Availability | SPARQL endpoint availability check for Framester took 0.00010323524475097656s
Availability | VoID file availability check for Framester took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Framester took 0.29225754737854004s
Reputation | Calculation of the PageRank for Framester took 0.022273778915405273s
Interlinking | Calculation of Degree of Connection for Framester took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Framester took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Framester took 8.726119995117188e-05s
Believability | Calculation of trust value for Framester took 9.5367431640625e-06s
INFO | --- Analysis for framester took 3.9518837928771973s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.05903911590576172s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.27652716636657715s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.022383689880371094s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.153915405273438e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for frb-linked-data took 2.733529567718506s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 9.036064147949219e-05s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 0.31485748291015625s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.0002694129943847656s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.239776611328125e-05s
INFO | --- Analysis for freebase took 4.164120435714722s
Availability | SPARQL endpoint availability check for Freeyork took 5.0067901611328125e-05s
Availability | VoID file availability check for Freeyork took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Freeyork took 0.28058290481567383s
Reputation | Calculation of the PageRank for Freeyork took 0.02093338966369629s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010704994201660156s
Believability | Calculation of trust value for Freeyork took 1.0251998901367188e-05s
INFO | --- Analysis for freeyork-org took 3.282017946243286s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7104687690734863s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.3152587413787842s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.022577762603759766s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.534027099609375e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 9.298324584960938e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.7636706829071045s
Availability | SPARQL endpoint availability check for DailyMed took 0.6792478561401367s
Availability | VoID file availability check for DailyMed took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for DailyMed took 0.3428645133972168s
Reputation | Calculation of the PageRank for DailyMed took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.202957153320312e-05s
Believability | Calculation of trust value for DailyMed took 1.2636184692382812e-05s
INFO | --- Analysis for fu-berlin-dailymed took 5.848614931106567s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7115530967712402s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.2994513511657715s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.702278137207031e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.33514404296875e-05s
INFO | --- Analysis for fu-berlin-dblp took 4.648629665374756s
Availability | SPARQL endpoint availability check for Diseasome took 0.6910452842712402s
Availability | VoID file availability check for Diseasome took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Diseasome took 0.3049306869506836s
Reputation | Calculation of the PageRank for Diseasome took 0.020701885223388672s
Interlinking | Calculation of Degree of Connection for Diseasome took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diseasome took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.0001068115234375s
Believability | Calculation of trust value for Diseasome took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-diseasome took 5.781676769256592s
Availability | SPARQL endpoint availability check for DrugBank took 0.6745409965515137s
Availability | VoID file availability check for DrugBank took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for DrugBank took 0.30141496658325195s
Reputation | Calculation of the PageRank for DrugBank took 0.020281314849853516s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011324882507324219s
Believability | Calculation of trust value for DrugBank took 1.3113021850585938e-05s
INFO | --- Analysis for fu-berlin-drugbank took 5.900749444961548s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.6940836906433105s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.301957368850708s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.022222042083740234s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.0279159545898438e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.1682510375976562e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 4.613163948059082s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6927280426025391s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2970881462097168s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.02124643325805664s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.748603820800781e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.767375707626343s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.6808385848999023s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2959287166595459s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020575284957885742s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.224082946777344e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 8.58306884765625e-06s
INFO | --- Analysis for fu-berlin-eures took 4.542052268981934s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6918418407440186s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2790389060974121s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.022256851196289062s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.989738464355469e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 9.775161743164062e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.171952724456787s
Availability | SPARQL endpoint availability check for MediCare took 0.6814377307891846s
Availability | VoID file availability check for MediCare took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for MediCare took 0.32526111602783203s
Reputation | Calculation of the PageRank for MediCare took 0.020993471145629883s
Interlinking | Calculation of Degree of Connection for MediCare took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.315376281738281e-05s
Believability | Calculation of trust value for MediCare took 1.3113021850585938e-05s
INFO | --- Analysis for fu-berlin-medicare took 5.214585542678833s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.6754059791564941s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.30060291290283203s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.605552673339844e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 1.0013580322265625e-05s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.721861124038696s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6728365421295166s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.337066650390625s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020852327346801758s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.274482727050781e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-sider took 5.312121868133545s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.7094876766204834s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2976696491241455s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.915496826171875e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.4066696166992188e-05s
INFO | --- Analysis for fu-berlin-stitch took 4.641616106033325s
Availability | SPARQL endpoint availability check for fvdb took 4.649162292480469e-05s
Availability | VoID file availability check for fvdb took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for fvdb took 0.27825355529785156s
Reputation | Calculation of the PageRank for fvdb took 0.022402524948120117s
Interlinking | Calculation of Degree of Connection for fvdb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.3855438232421875e-05s
Believability | Calculation of trust value for fvdb took 9.298324584960938e-06s
INFO | --- Analysis for fv took 12.683626174926758s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 0.00010609626770019531s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.28840160369873047s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.9802322387695312e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 9.775161743164062e-06s
INFO | --- Analysis for GACS took 3.288645029067993s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.220008850097656e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.2783524990081787s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 3.910064697265625e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.0013580322265625e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.336068391799927s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 8.893013000488281e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.2831547260284424s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00011992454528808594s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.0013580322265625e-05s
INFO | --- Analysis for garnicaplywood took 3.6014811992645264s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.083747863769531e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0003135204315185547s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.3014655113220215s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020799636840820312s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.202957153320312e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 7.867813110351562e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.7895636558532715s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.3186168670654297s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.27685046195983887s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.022658348083496094s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.00010061264038085938s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 9.5367431640625e-06s
INFO | --- Analysis for gemet took 5.148104190826416s
Availability | SPARQL endpoint availability check for gemet-annotated took 8.797645568847656e-05s
Availability | VoID file availability check for gemet-annotated took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.324326753616333s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020991086959838867s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.790855407714844e-05s
Believability | Calculation of trust value for gemet-annotated took 1.3113021850585938e-05s
INFO | --- Analysis for gemet-annotated took 3.4077587127685547s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.8752236366271973s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.34070301055908203s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.9577484130859375e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.049041748046875e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.683551788330078s
Availability | SPARQL endpoint availability check for Super Ontology took 1.4961707592010498s
Availability | VoID file availability check for Super Ontology took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.29801011085510254s
Reputation | Calculation of the PageRank for Super Ontology took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0009677410125732422s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.933906555175781e-05s
Believability | Calculation of trust value for Super Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 5.250627517700195s
Availability | SPARQL endpoint availability check for Geographic detector model took 8.893013000488281e-05s
Availability | VoID file availability check for Geographic detector model took 0.0007736682891845703s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.30350613594055176s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.0517578125e-05s
Believability | Calculation of trust value for Geographic detector model took 1.33514404296875e-05s
INFO | --- Analysis for GeoDetector took 21.87690782546997s
Availability | SPARQL endpoint availability check for geodomainwn took 4.267692565917969e-05s
Availability | VoID file availability check for geodomainwn took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.29510021209716797s
Reputation | Calculation of the PageRank for geodomainwn took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for geodomainwn took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 5.0067901611328125e-05s
Believability | Calculation of trust value for geodomainwn took 1.33514404296875e-05s
INFO | --- Analysis for geodomainwn took 4.1098809242248535s
Availability | SPARQL endpoint availability check for GeoEcuador took 6.961822509765625e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.29395008087158203s
Reputation | Calculation of the PageRank for GeoEcuador took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.604194641113281e-05s
Believability | Calculation of trust value for GeoEcuador took 9.5367431640625e-06s
INFO | --- Analysis for geoecuador took 12.971126794815063s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.1344003677368164s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.38472509384155273s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.02099132537841797s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.104873657226562e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 7.3909759521484375e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 48.1972930431366s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.4702107906341553s
Availability | VoID file availability check for GeoLinkedData took 0.0003821849822998047s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.29634547233581543s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02093195915222168s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 9.274482727050781e-05s
Believability | Calculation of trust value for GeoLinkedData took 5.0067901611328125e-06s
INFO | --- Analysis for geolinkeddata took 4.1731061935424805s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.24869751930236816s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0003654956817626953s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.45591950416565s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.38001465797424316s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.14284276962280273s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.4030566215515137s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.19227933883666992s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.18421387672424316s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.1928255558013916s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.09155964851379395s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.09096002578735352s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06878852844238281s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.10467839241027832s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.8712661266326904s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.1081533432006836s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.1029825210571289s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.13089585304260254s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.09693312644958496s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.06940221786499023s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10383319854736328s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.38499140739441s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 0.00016117095947265625s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06216287612915039s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.061478376388549805s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.09710001945495605s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.07629513740539551s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06980371475219727s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16172266006469727s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16055822372436523s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.3096811771392822s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 2.1348514556884766s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10459160804748535s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06214094161987305s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06086254119873047s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.3176429271697998s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007467031478881836s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.22848248481750488s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.06175088882446289s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.20697617530822754s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5213077068328857s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 2.9017016887664795s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.4211177825927734s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.5821404457092285s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.18068456649780273s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.06804752349853516s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0300793647766113s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.30098605155944824s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.021299123764038086s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.440017700195312e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 3.295529365539551s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 55.77423286437988s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.363059997558594e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.3103654384613037s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004639625549316406s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.0967254638671875e-05s
INFO | --- Analysis for geonames-semantic-web took 3.5241520404815674s
Availability | SPARQL endpoint availability check for Geospatial World  took 9.059906005859375e-05s
Availability | VoID file availability check for Geospatial World  took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.28905534744262695s
Reputation | Calculation of the PageRank for Geospatial World  took 0.022167205810546875s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010442733764648438s
Believability | Calculation of trust value for Geospatial World  took 1.0728836059570312e-05s
INFO | --- Analysis for geospatialworld-net took 3.1708364486694336s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5587220191955566s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.30126523971557617s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.021526813507080078s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.0001347064971923828s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.1205673217773438e-05s
INFO | --- Analysis for geospecies took 5.989660024642944s
Availability | SPARQL endpoint availability check for GeoWordNet took 9.131431579589844e-05s
Availability | VoID file availability check for GeoWordNet took 0.0008263587951660156s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.32621073722839355s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.2928924560546875e-05s
Believability | Calculation of trust value for GeoWordNet took 1.0251998901367188e-05s
INFO | --- Analysis for geowordnet took 7.979718923568726s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.09069442749023438s
Availability | VoID file availability check for German labor law thesaurus took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.28683996200561523s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.022954702377319336s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.963180541992188e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 2.809995651245117s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.3392181396484375e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.279954195022583s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02064967155456543s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.172325134277344e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.0251998901367188e-05s
INFO | --- Analysis for germlex took 3.134767770767212s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.36706995964050293s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.31249451637268066s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.021737098693847656s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.893013000488281e-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.355178356170654s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.417135000228882s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.35287952423095703s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 8.249282836914062e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 9.775161743164062e-06s
INFO | --- Analysis for getty-aat took 16.6584370136261s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.263045310974121s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.3175027370452881s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020301103591918945s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.054473876953125e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.0251998901367188e-05s
INFO | --- Analysis for getty-tgn took 13.423338651657104s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 7.326547384262085s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.34116625785827637s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.075599670410156e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 8.821487426757812e-06s
INFO | --- Analysis for gipuzkoademografia took 31.024399280548096s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 0.00010156631469726562s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.2684361934661865s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02272629737854004s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.457069396972656e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 8.106231689453125e-06s
INFO | --- Analysis for glastonbury-2011 took 6.014273166656494s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 8.797645568847656e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.29784464836120605s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020893096923828125s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 5.078315734863281e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.430511474609375e-05s
INFO | --- Analysis for global-hunger-index-2011 took 3.437375545501709s
Availability | SPARQL endpoint availability check for Glottolog took 0.000110626220703125s
Availability | VoID file availability check for Glottolog took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Glottolog took 0.299102783203125s
Reputation | Calculation of the PageRank for Glottolog took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.507469177246094e-05s
Believability | Calculation of trust value for Glottolog took 1.3113021850585938e-05s
INFO | --- Analysis for glottolog took 6.486133337020874s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 8.96453857421875e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.2927536964416504s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010561943054199219s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.0251998901367188e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 8.571645736694336s
Availability | SPARQL endpoint availability check for 1121 took 8.702278137207031e-05s
Availability | VoID file availability check for 1121 took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for 1121 took 0.2880246639251709s
Reputation | Calculation of the PageRank for 1121 took 0.021143198013305664s
Interlinking | Calculation of Degree of Connection for 1121 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.266334533691406e-05s
Believability | Calculation of trust value for 1121 took 1.0967254638671875e-05s
INFO | --- Analysis for God_ took 3.06048321723938s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.673004150390625e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.29128146171569824s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.340576171875e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.0728836059570312e-05s
INFO | --- Analysis for gold took 4.238312721252441s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 9.822845458984375e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.305706262588501s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.02208876609802246s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 7.82012939453125e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.3828277587890625e-05s
INFO | --- Analysis for googleart-wrapper took 3.0429537296295166s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.10178446769714355s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.28385090827941895s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020452260971069336s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.3855438232421875e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.4066696166992188e-05s
INFO | --- Analysis for govagribus-denmark took 34.89265441894531s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.438861608505249s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.34143757820129395s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020769119262695312s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.440017700195312e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 24.315916538238525s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.6786224842071533s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.3054335117340088s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.021124601364135742s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 9.34600830078125e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 4.76837158203125e-06s
INFO | --- Analysis for govtrack took 10.896523237228394s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 0.00010609626770019531s
Availability | VoID file availability check for greek-administrative-geography took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.3008899688720703s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.021073579788208008s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.365776062011719e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.2159347534179688e-05s
INFO | --- Analysis for greek-administrative-geography took 2.682227849960327s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.15718674659729004s
Availability | VoID file availability check for Greek Wordnet took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.2995767593383789s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.021187305450439453s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.3392181396484375e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.2159347534179688e-05s
INFO | --- Analysis for greek-wordnet took 2.8832039833068848s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2874479293823242s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.00067138671875s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 12.273375988006592s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.638340950012207s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.70023512840271s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 1.603952169418335s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 1.9027667045593262s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5423071384429932s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12723398208618164s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12296175956726074s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12616848945617676s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13296103477478027s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5856468677520752s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1502063274383545s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.24453473091125488s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.26387977600097656s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12499499320983887s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12847304344177246s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1234736442565918s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.96802806854248s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 7.152557373046875e-05s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11576032638549805s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12312746047973633s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1217954158782959s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12221264839172363s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13301539421081543s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.254047155380249s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.247758150100708s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 7.88496208190918s
Interoperability | New vocabularies check for Greek prisons releases Jan 2018 - Dec 2023 took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13132715225219727s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.11966776847839355s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.12733960151672363s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 2.1175320148468018s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.29048681259155273s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.645310163497925s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12301158905029297s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.219282627105713s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 2.8193225860595703s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.2440235614776611s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.679917573928833s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.9357681274414062s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11996889114379883s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 4824.92079782486s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.7813591957092285s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.02093195915222168s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.811981201171875e-05s
Interoperability | Check the re-using of existing vocabs for Greek prisons releases Jan 2018 - Dec 2023 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 1.2636184692382812e-05s
INFO | --- Analysis for greek_prisons_releases took 4904.0279421806335s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.7720921039581299s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.3014957904815674s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02183699607849121s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.700920104980469e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.2159347534179688e-05s
INFO | --- Analysis for greekchildrensartmuseum took 4.736857652664185s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 9.202957153320312e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.2955031394958496s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.021556377410888672s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010466575622558594s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.3589859008789062e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 7.663156747817993s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.4656305313110352s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.2858395576477051s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.649162292480469e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.2159347534179688e-05s
INFO | --- Analysis for grrp took 4.300209283828735s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.2799363136291504s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.2956817150115967s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.67572021484375e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 9.059906005859375e-06s
INFO | --- Analysis for grrt took 4.036459922790527s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.252338171005249s
Availability | VoID file availability check for Geological Timescale took 0.0006787776947021484s
Extra | Recovery of all triples for Geological Timescale took 2.8857150077819824s
Performance | Total latancy measurement for Geological Timescale took 5.0305891036987305s
Amount of data | Number of triples check for Geological Timescale took 1.016160011291504s
Interoperability | New terms check for Geological Timescale took 1.6957080364227295s
Versatility | Languages check for Geological Timescale took 1.1513571739196777s
Interpretability | Number of blank nodes check for Geological Timescale took 1.033893346786499s
Security | Check HTTPS for Geological Timescale took 0.9392859935760498s
Interpretability | RDF structures check for Geological Timescale took 0.977536678314209s
Versatility | Serialization formats check for Geological Timescale took 1.0422208309173584s
Availability | RDF dump link check for Geological Timescale took 1.207716703414917s
License | MR license check for Geological Timescale took 0.9869678020477295s
License | HR license check for Geological Timescale took 1.057945966720581s
Amount of data | Number of property check for Geological Timescale took 0.9946870803833008s
Understandability | Number of label check for Geological Timescale took 1.0384125709533691s
Understandability | URI regex check for Geological Timescale took 1.451509714126587s
Understandability | Vocabs check for Geological Timescale took 0.993455171585083s
Verifiability | Authors check for Geological Timescale took 0.9688565731048584s
Verifiability | Publishers check for Geological Timescale took 0.45339536666870117s
Performance | Throughput check for Geological Timescale took 12.331616163253784s
Amount of data | Check the number of entities for Geological Timescale took 0.022779464721679688s
Verifiability | Contribs. check for Geological Timescale took 0.998035192489624s
Interlinking | sameAs chians check for Geological Timescale took 0.4903581142425537s
Interlinking | skos check for Geological Timescale took 1.0017638206481934s
Interlinking | skos check for Geological Timescale took 0.9558060169219971s
Timeliness | dataset update frequency check for Geological Timescale took 1.0058300495147705s
Currency | Creation date check for Geological Timescale took 2.0322561264038086s
Currency | Modification date check for Geological Timescale took 1.0438241958618164s
Rep.Conc. | URIs length for Geological Timescale took 2.7168071269989014s
Interoperability | New vocabularies check for Geological Timescale took 6.0176262855529785s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.9807417392730713s
Accuracy | Check Functional Property for Geological Timescale took 1.0150916576385498s
Accuracy | Check Inverse Functional Property for Geological Timescale took 1.0240132808685303s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.356938123703003s
Accuracy | Check White space in annotation for Geological Timescale took 0.015918254852294922s
Accuracy | Check Datatype consistency for Geological Timescale took 0.0730283260345459s
Consistency | Disjoint class check for Geological Timescale took 1.075235366821289s
Consistency | Check Misplaced properties for Geological Timescale took 2.0805702209472656s
Consistency | Misplaced classes for Geological Timescale took 1.1305456161499023s
Consistency | Check Ontology hijacking for Geological Timescale took 2.3318123817443848s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.2498242855072021s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.286921262741089s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05218076705932617s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.9460592269897461s
Security | Sign check for Geological Timescale took 1.0462977886199951s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.426893472671509s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.3199491500854492s
Reputation | Calculation of the PageRank for Geological Timescale took 0.02022385597229004s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.772445678710938e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 6.917755126953125s
Believability | Calculation of trust value for Geological Timescale took 1.1682510375976562e-05s
INFO | --- Analysis for GTS took 135.4560432434082s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.27755212783813477s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.020514249801635742s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.3855438232421875e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for GTS-ont took 2.924645185470581s
Availability | SPARQL endpoint availability check for GUTSTOK  took 8.749961853027344e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.2764153480529785s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020864009857177734s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.0517578125e-05s
Believability | Calculation of trust value for GUTSTOK  took 7.867813110351562e-06s
INFO | --- Analysis for Guillaume_Forget took 2.605173110961914s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.38690185546875e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.29584574699401855s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.651878356933594e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.3113021850585938e-05s
INFO | --- Analysis for gutenberg took 8.92104697227478s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 5.125999450683594e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.31809067726135254s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.2901763916015625e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.049041748046875e-05s
INFO | --- Analysis for gwa-ili took 6.048280239105225s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 8.869171142578125e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.34891414642333984s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.02050948143005371s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.552436828613281e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 5.0067901611328125e-06s
INFO | --- Analysis for GWR took 198.0674021244049s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 8.96453857421875e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.34362196922302246s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 4.5299530029296875e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.1205673217773438e-05s
INFO | --- Analysis for HASM took 203.45514941215515s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.290087938308716s
Availability | VoID file availability check for HealthCare Ontology took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.3145182132720947s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.020241975784301758s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.5762786865234375e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for HealthCare_Ontology took 6.5304114818573s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 9.322166442871094e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.2977602481842041s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.02121877670288086s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 5.9604644775390625e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 8.344650268554688e-06s
INFO | --- Analysis for heartfailure took 3.234813928604126s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.672993898391724s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.39278125762939453s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02113485336303711s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.2438507080078125e-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.239776611328125e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 120.11475610733032s
Availability | SPARQL endpoint availability check for Hedatuz took 0.22881603240966797s
Availability | VoID file availability check for Hedatuz took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.3429374694824219s
Reputation | Calculation of the PageRank for Hedatuz took 0.02147674560546875s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.719329833984375e-05s
Believability | Calculation of trust value for Hedatuz took 1.0728836059570312e-05s
INFO | --- Analysis for hedatuz took 3.327491044998169s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.11637163162231445s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.3041365146636963s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012254714965820312s
Believability | Calculation of trust value for Hellenic Fire Brigade took 9.059906005859375e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.9739530086517334s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.025940895080566406s
Availability | VoID file availability check for Hellenic Police took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.3027071952819824s
Reputation | Calculation of the PageRank for Hellenic Police took 0.021802425384521484s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012755393981933594s
Believability | Calculation of trust value for Hellenic Police took 8.821487426757812e-06s
INFO | --- Analysis for hellenic-police took 2.835020065307617s
Availability | SPARQL endpoint availability check for Hermos took 4.410743713378906e-05s
Availability | VoID file availability check for Hermos took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for Hermos took 0.2964048385620117s
Reputation | Calculation of the PageRank for Hermos took 0.021006107330322266s
Interlinking | Calculation of Degree of Connection for Hermos took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hermos took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.9087066650390625e-05s
Believability | Calculation of trust value for Hermos took 1.3589859008789062e-05s
INFO | --- Analysis for Hermos took 3.357349157333374s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.38690185546875e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.30152249336242676s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.9325485229492188e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.3589859008789062e-05s
INFO | --- Analysis for Himanshu_Mahawar took 2.6867284774780273s
Availability | SPARQL endpoint availability check for HITO took 0.43439412117004395s
Availability | VoID file availability check for HITO took 0.0007736682891845703s
Extra | Recovery of all triples for HITO took 1.7799651622772217s
Performance | Total latancy measurement for HITO took 0.9463541507720947s
Amount of data | Number of triples check for HITO took 0.17444729804992676s
Interoperability | New terms check for HITO took 1.4934749603271484s
Versatility | Languages check for HITO took 0.21878790855407715s
Interpretability | Number of blank nodes check for HITO took 0.19771933555603027s
Interpretability | RDF structures check for HITO took 0.20883989334106445s
Versatility | Serialization formats check for HITO took 0.1948990821838379s
Availability | RDF dump link check for HITO took 0.2119598388671875s
License | MR license check for HITO took 0.19310593605041504s
License | HR license check for HITO took 0.2017979621887207s
Amount of data | Number of property check for HITO took 0.19333219528198242s
Understandability | Number of label check for HITO took 0.2121269702911377s
Understandability | URI regex check for HITO took 0.3859837055206299s
Understandability | Vocabs check for HITO took 0.17937207221984863s
Verifiability | Authors check for HITO took 0.19314026832580566s
Verifiability | Publishers check for HITO took 0.2015070915222168s
Performance | Throughput check for HITO took 11.260509967803955s
Amount of data | Check the number of entities for HITO took 8.487701416015625e-05s
Verifiability | Contribs. check for HITO took 0.19481348991394043s
Interlinking | sameAs chians check for HITO took 0.2008967399597168s
Interlinking | skos check for HITO took 0.19214725494384766s
Interlinking | skos check for HITO took 0.1787714958190918s
Timeliness | dataset update frequency check for HITO took 0.20210051536560059s
Currency | Creation date check for HITO took 0.39464521408081055s
Currency | Modification date check for HITO took 0.38114070892333984s
Rep.Conc. | URIs length for HITO took 1.0800368785858154s
Interoperability | New vocabularies check for HITO took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.18931031227111816s
Accuracy | Check Functional Property for HITO took 0.20769023895263672s
Accuracy | Check Inverse Functional Property for HITO took 0.1876373291015625s
Accuracy | Check Empty annotation labels for HITO took 0.48659515380859375s
Accuracy | Check White space in annotation for HITO took 0.013723611831665039s
Accuracy | Check Datatype consistency for HITO took 0.07279324531555176s
Consistency | Disjoint class check for HITO took 0.17900729179382324s
Consistency | Check Misplaced properties for HITO took 0.483975887298584s
Consistency | Misplaced classes for HITO took 0.36466026306152344s
Consistency | Check Ontology hijacking for HITO took 1.7289910316467285s
Consistency | Check Invalid usage of undefined classes for HITO took 1.252664566040039s
Consistency | Check Invalid usage of undefined properties for HITO took 1.48417067527771s
Conciseness | Check Extensional conciseness for HITO took 0.06116676330566406s
Conciseness | Check Intensional conciseness for HITO took 0.1971437931060791s
Security | Sign check for HITO took 0.1983785629272461s
Availability | Check URIs Dereferenciability for HITO took 1727.1119635105133s
Completeness | Calculation of interlinking completeness for HITO took 0.5117025375366211s
Reputation | Calculation of the PageRank for HITO took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for HITO took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for HITO took 8.082389831542969e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.1920928955078125e-06s
Believability | Calculation of trust value for HITO took 1.3589859008789062e-05s
INFO | --- Analysis for hito took 1779.6969425678253s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 13.003667831420898s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.3223862648010254s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02128458023071289s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.528594970703125e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.2159347534179688e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 41.85575604438782s
Availability | SPARQL endpoint availability check for gseg took 9.393692016601562e-05s
Availability | VoID file availability check for gseg took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for gseg took 0.31833577156066895s
Reputation | Calculation of the PageRank for gseg took 0.020624160766601562s
Interlinking | Calculation of Degree of Connection for gseg took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for gseg took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for gseg took 3.0994415283203125e-05s
Believability | Calculation of trust value for gseg took 1.2636184692382812e-05s
INFO | --- Analysis for hongse took 3.511201858520508s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 2.3534622192382812s
Availability | VoID file availability check for COURAGE Dataset took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.26945996284484863s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.2901763916015625e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.3828277587890625e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 6.209225416183472s
Availability | SPARQL endpoint availability check for RoadTrb took 9.1552734375e-05s
Availability | VoID file availability check for RoadTrb took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.27619504928588867s
Reputation | Calculation of the PageRank for RoadTrb took 0.02141737937927246s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.0279159545898438e-05s
Believability | Calculation of trust value for RoadTrb took 9.298324584960938e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.7323415279388428s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 9.655952453613281e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0006883144378662109s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.29952120780944824s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 30.84114146232605s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 8.845329284667969e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.2777891159057617s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.075599670410156e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.33514404296875e-05s
INFO | --- Analysis for http:pakistan.com took 2.6198015213012695s
Availability | SPARQL endpoint availability check for CEDICT took 8.821487426757812e-05s
Availability | VoID file availability check for CEDICT took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for CEDICT took 0.3112623691558838s
Reputation | Calculation of the PageRank for CEDICT took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.0517578125e-05s
Believability | Calculation of trust value for CEDICT took 1.1682510375976562e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.236898899078369s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.329123258590698s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.29314208030700684s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0009293556213378906s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.034706115722656e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.3113021850585938e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 9.780720710754395s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 8.654594421386719e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.2843325138092041s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.021050453186035156s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.0994415283203125e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 9.775161743164062e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 3.3380260467529297s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 9.179115295410156e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.32897424697875977s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.02141118049621582s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.62396240234375e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.2874603271484375e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.6890790462493896s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.363059997558594e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.32781195640563965s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.337860107421875e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.239776611328125e-05s
INFO | --- Analysis for http:www.msm.com took 2.612812042236328s
Availability | SPARQL endpoint availability check for Game Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Game Ontology took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.28930211067199707s
Reputation | Calculation of the PageRank for Game Ontology took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for Game Ontology took 1.5020370483398438e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 3.3028390407562256s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.036064147949219e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.3406333923339844s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.3113021850585938e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.6467347145080566s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.036064147949219e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.27669429779052734s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.023062944412231445s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.0517578125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2874603271484375e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.722834348678589s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00010585784912109375s
Availability | VoID file availability check for Indian Biodiversity took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.28437256813049316s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.147125244140625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0728836059570312e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.615449905395508s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.893013000488281e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.29575490951538086s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.2901763916015625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2874603271484375e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.7564780712127686s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.012222290039062e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2779812812805176s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.022403955459594727s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.170967102050781e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2874603271484375e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.660430669784546s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.553794860839844e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.307513952255249s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.023355960845947266s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.337860107421875e-05s
Believability | Calculation of trust value for Indian Biodiversity took 8.106231689453125e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 4.108213663101196s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.202957153320312e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.30547595024108887s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.1948089599609375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.239776611328125e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.7193350791931152s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 9.179115295410156e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.3131687641143799s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.0279159545898438e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.1920928955078125e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.344010591506958s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.1033024787902832s
Availability | VoID file availability check for Bookkeeping took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.2804534435272217s
Reputation | Calculation of the PageRank for Bookkeeping took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.147125244140625e-05s
Believability | Calculation of trust value for Bookkeeping took 1.0967254638671875e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 4.330831527709961s
Availability | SPARQL endpoint availability check for Legal Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Legal Ontology took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.3106534481048584s
Reputation | Calculation of the PageRank for Legal Ontology took 0.021311521530151367s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.337860107421875e-05s
Believability | Calculation of trust value for Legal Ontology took 1.049041748046875e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 3.395148992538452s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.5299530029296875e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.000743865966796875s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.30991554260253906s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.021800994873046875s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0010750293731689453s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 0.00010204315185546875s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.239776611328125e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 3.115797281265259s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 0.00014543533325195312s
Availability | VoID file availability check for Writer Luigi Usai took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.3008253574371338s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.170967102050781e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.3589859008789062e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.8998405933380127s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.6296467781066895s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.30852413177490234s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010943412780761719s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.6689300537109375e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 3.2525246143341064s
Availability | SPARQL endpoint availability check for IATE RDF took 8.678436279296875e-05s
Availability | VoID file availability check for IATE RDF took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.31274962425231934s
Reputation | Calculation of the PageRank for IATE RDF took 0.02204155921936035s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.743171691894531e-05s
Believability | Calculation of trust value for IATE RDF took 1.1920928955078125e-05s
INFO | --- Analysis for iate-rdf took 2.965740203857422s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.353847503662109s
Availability | VoID file availability check for IATI as Linked Data took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.277240514755249s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.702278137207031e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.3589859008789062e-05s
INFO | --- Analysis for iati-as-linked-data took 14.13354754447937s
Availability | SPARQL endpoint availability check for ICANE took 0.3162229061126709s
Availability | VoID file availability check for ICANE took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for ICANE took 0.3363652229309082s
Reputation | Calculation of the PageRank for ICANE took 0.020778894424438477s
Interlinking | Calculation of Degree of Connection for ICANE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICANE took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.678436279296875e-05s
Believability | Calculation of trust value for ICANE took 9.775161743164062e-06s
INFO | --- Analysis for icane took 3.867036819458008s
Availability | SPARQL endpoint availability check for ichoose took 0.15026617050170898s
Availability | VoID file availability check for ichoose took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for ichoose took 0.2918522357940674s
Reputation | Calculation of the PageRank for ichoose took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for ichoose took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.914138793945312e-05s
Believability | Calculation of trust value for ichoose took 1.2874603271484375e-05s
INFO | --- Analysis for ichoose took 42.80182099342346s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 1.407210350036621s
Availability | VoID file availability check for The Iconology Dataset took 0.0007948875427246094s
Extra | Recovery of all triples for The Iconology Dataset took 4.456415176391602s
Performance | Total latancy measurement for The Iconology Dataset took 0.6610217094421387s
Amount of data | Number of triples check for The Iconology Dataset took 0.21358847618103027s
Interoperability | New terms check for The Iconology Dataset took 1.4551589488983154s
Versatility | Languages check for The Iconology Dataset took 0.5843489170074463s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.20259761810302734s
Interpretability | RDF structures check for The Iconology Dataset took 0.15572094917297363s
Versatility | Serialization formats check for The Iconology Dataset took 0.11727619171142578s
Availability | RDF dump link check for The Iconology Dataset took 0.09044933319091797s
License | MR license check for The Iconology Dataset took 0.12454628944396973s
License | HR license check for The Iconology Dataset took 0.3308131694793701s
Amount of data | Number of property check for The Iconology Dataset took 0.12815070152282715s
Understandability | Number of label check for The Iconology Dataset took 0.1672043800354004s
Understandability | URI regex check for The Iconology Dataset took 0.17370986938476562s
Understandability | Vocabs check for The Iconology Dataset took 0.1287364959716797s
Verifiability | Authors check for The Iconology Dataset took 0.09819698333740234s
Verifiability | Publishers check for The Iconology Dataset took 0.09022021293640137s
Performance | Throughput check for The Iconology Dataset took 10.431545972824097s
Amount of data | Check the number of entities for The Iconology Dataset took 0.00011086463928222656s
Verifiability | Contribs. check for The Iconology Dataset took 0.09361124038696289s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09984254837036133s
Interlinking | skos check for The Iconology Dataset took 0.09309244155883789s
Interlinking | skos check for The Iconology Dataset took 0.09213495254516602s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09080648422241211s
Currency | Creation date check for The Iconology Dataset took 0.18621540069580078s
Currency | Modification date check for The Iconology Dataset took 0.20148229598999023s
Rep.Conc. | URIs length for The Iconology Dataset took 1.4255940914154053s
Interoperability | New vocabularies check for The Iconology Dataset took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08396148681640625s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.26254749298095703s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016487836837768555s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.4372870922088623s
Consistency | Disjoint class check for The Iconology Dataset took 0.07334566116333008s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.14799857139587402s
Consistency | Misplaced classes for The Iconology Dataset took 0.8895666599273682s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.5821208953857422s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.2922403812408447s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.368795394897461s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.30779576301574707s
Security | Sign check for The Iconology Dataset took 0.08258366584777832s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2584.346555709839s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.8184487819671631s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.02121734619140625s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for The Iconology Dataset took 1.0967254638671875e-05s
INFO | --- Analysis for iconology-dataset took 2642.5683555603027s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.38690185546875e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.28361034393310547s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.939338684082031e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 7.3909759521484375e-06s
INFO | --- Analysis for idreffr took 3.78922700881958s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.7086567878723145s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.2658579349517822s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.9591064453125e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 6.9141387939453125e-06s
INFO | --- Analysis for ids took 4.6825110912323s
Availability | SPARQL endpoint availability check for ietflang took 4.363059997558594e-05s
Availability | VoID file availability check for ietflang took 0.0007636547088623047s
Completeness | Calculation of interlinking completeness for ietflang took 0.3073892593383789s
Reputation | Calculation of the PageRank for ietflang took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for ietflang took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for ietflang took 5.0067901611328125e-05s
Believability | Calculation of trust value for ietflang took 7.152557373046875e-06s
INFO | --- Analysis for ietflang took 14.573977947235107s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.5427002906799316s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.3075590133666992s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.021587133407592773s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 9.5367431640625e-06s
INFO | --- Analysis for IGVLL took 4.336237668991089s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.4582054615020752s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0004265308380126953s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.4072175025939941s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9392890930175781s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.20708847045898438s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.4647622108459473s
Versatility | Languages check for 3LGM² IHE Ontology took 0.2069411277770996s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.20885157585144043s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.22406435012817383s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.18575000762939453s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.18851542472839355s
License | MR license check for 3LGM² IHE Ontology took 0.2084200382232666s
License | HR license check for 3LGM² IHE Ontology took 0.21602225303649902s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.21385955810546875s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.20708656311035156s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.4049050807952881s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.19195771217346191s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.18685698509216309s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.19009041786193848s
Performance | Throughput check for 3LGM² IHE Ontology took 11.296271085739136s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 3.838539123535156e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.2002568244934082s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.19786810874938965s
Interlinking | skos check for 3LGM² IHE Ontology took 0.20169281959533691s
Interlinking | skos check for 3LGM² IHE Ontology took 0.18013477325439453s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.1960451602935791s
Currency | Creation date check for 3LGM² IHE Ontology took 0.4073638916015625s
Currency | Modification date check for 3LGM² IHE Ontology took 0.38217973709106445s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.7485837936401367s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.17827916145324707s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.1989302635192871s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.18020200729370117s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3328690528869629s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0016210079193115234s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.04967927932739258s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.17993855476379395s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4521212577819824s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2726163864135742s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.5900886058807373s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.2621519565582275s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.4983532428741455s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.03166556358337402s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.18769049644470215s
Security | Sign check for 3LGM² IHE Ontology took 0.19361162185668945s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 428.49893832206726s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.3938026428222656s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.020826101303100586s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 4.124641418457031e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.1920928955078125e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.239776611328125e-05s
INFO | --- Analysis for IHE took 474.9168245792389s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.3750853538513184s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0006163120269775391s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 5.450985431671143s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 7.335912704467773s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 22.192299842834473s
Interoperability | New terms check for Test Site, LOD Lab 317 took 7.833774566650391s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.47370982170105s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.679020643234253s
Security | Check HTTPS for Test Site, LOD Lab 317 took 0.9755256175994873s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 1.643681287765503s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.6708385944366455s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.5001239776611328s
License | MR license check for Test Site, LOD Lab 317 took 1.5741701126098633s
License | HR license check for Test Site, LOD Lab 317 took 1.9110853672027588s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.5250627994537354s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.7536118030548096s
Understandability | URI regex check for Test Site, LOD Lab 317 took 2.9502627849578857s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.512770414352417s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.6782479286193848s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.4935920238494873s
Performance | Throughput check for Test Site, LOD Lab 317 took 14.749943017959595s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 8.463859558105469e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.4920690059661865s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.4698035717010498s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.5350432395935059s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.5056238174438477s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.5502240657806396s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.026406764984131s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.012603521347046s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 34.31534767150879s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.4906044006347656s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.4785327911376953s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.467134952545166s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 2.971979856491089s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.031935930252075195s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.029073715209960938s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.4778366088867188s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 28.150837182998657s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 1.8389222621917725s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 4.673947095870972s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.3024091720581055s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 24.222100496292114s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.03354024887084961s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.0074527263641357s
Security | Sign check for Test Site, LOD Lab 317 took 1.6518487930297852s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 9.185240983963013s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.47022223472595215s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.021653413772583008s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.457069396972656e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 9.5367431640625e-07s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.239776611328125e-05s
INFO | --- Analysis for iislod-test took 508.39480924606323s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 9.369850158691406e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0004000663757324219s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.33498382568359375s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.7670135498046875e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.1682510375976562e-05s
INFO | --- Analysis for ILUSOC took 17.99057674407959s
Availability | SPARQL endpoint availability check for im@sparql took 7.201114892959595s
Availability | VoID file availability check for im@sparql took 0.0003960132598876953s
Completeness | Calculation of interlinking completeness for im@sparql took 0.28201818466186523s
Reputation | Calculation of the PageRank for im@sparql took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.218650817871094e-05s
Believability | Calculation of trust value for im@sparql took 8.58306884765625e-06s
INFO | --- Analysis for im@sparql took 14.474273443222046s
Availability | SPARQL endpoint availability check for imagery bailingniao took 8.940696716308594e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0003559589385986328s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2861301898956299s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 2.86102294921875e-05s
Believability | Calculation of trust value for imagery bailingniao took 6.9141387939453125e-06s
INFO | --- Analysis for imagery_bailingniao took 3.741814613342285s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1830918788909912s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0003857612609863281s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 19.24978518486023s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.4912467002868652s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.86628246307373s
Interoperability | New terms check for Imagesnippets Image Descriptions took 2.235267400741577s
Versatility | Languages check for Imagesnippets Image Descriptions took 20.43645977973938s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.372917175292969s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.7271604537963867s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.760148286819458s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7522296905517578s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7407364845275879s
License | MR license check for Imagesnippets Image Descriptions took 0.7453930377960205s
License | HR license check for Imagesnippets Image Descriptions took 30.74879550933838s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7343740463256836s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.5992026329040527s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.4746553897857666s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7439281940460205s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7204508781433105s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7158961296081543s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.925108432769775s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 6.866455078125e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7500309944152832s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7370545864105225s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7547128200531006s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7055902481079102s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7594010829925537s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.4054665565490723s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.4755322933197021s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 33.28038287162781s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7148950099945068s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7193059921264648s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7346839904785156s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 11.004695177078247s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.224597215652466s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.283096551895142s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7531569004058838s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.917778015136719s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 4.82390284538269s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.3784804344177246s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.620506763458252s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.974116325378418s
Security | Sign check for Imagesnippets Image Descriptions took 0.7122273445129395s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 11.19235610961914s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.37816500663757324s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020666122436523438s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.703636169433594e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.6689300537109375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.0728836059570312e-05s
INFO | --- Analysis for imagesnippets took 374.4068834781647s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.11095666885375977s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.29865550994873047s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.02033090591430664s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 0.00010466575622558594s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for imf-linked-data took 2.802293062210083s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.172325134277344e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.00021958351135253906s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.3247489929199219s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.239776611328125e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 9.5367431640625e-06s
INFO | --- Analysis for Imtiaz took 2.6481435298919678s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.2438507080078125e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.29596662521362305s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 2.8848648071289062e-05s
Believability | Calculation of trust value for Royalty Free Music took 4.5299530029296875e-06s
INFO | --- Analysis for inaudio.org took 4.077782154083252s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.43688011169433594s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.31888365745544434s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 4.0531158447265625e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 9.775161743164062e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 4.167524099349976s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.00013065338134765625s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.30173158645629883s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.021238088607788086s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010728836059570312s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 1.3589859008789062e-05s
INFO | --- Analysis for ineverycrea took 13.436331987380981s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.606910705566406e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2981095314025879s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020839214324951172s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.393692016601562e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0251998901367188e-05s
INFO | --- Analysis for ineverycrea-argentina took 7.865082740783691s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 270.4746153354645s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.3869640827178955s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02086329460144043s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.295608520507812e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for influence-tracker-dataset took 566.2168312072754s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.696846008300781e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.29016900062561035s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.021323680877685547s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.314018249511719e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 1.33514404296875e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 2.733153820037842s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.1961669921875e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0003554821014404297s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.411163330078125s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00010442733764648438s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 8.821487426757812e-06s
INFO | --- Analysis for interactivemaps-gnoss took 14.911772727966309s
Availability | SPARQL endpoint availability check for intervalue took 0.19738197326660156s
Availability | VoID file availability check for intervalue took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for intervalue took 0.30205345153808594s
Reputation | Calculation of the PageRank for intervalue took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for intervalue took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.914138793945312e-05s
Believability | Calculation of trust value for intervalue took 1.2159347534179688e-05s
INFO | --- Analysis for intervalue took 2.862065315246582s
Availability | SPARQL endpoint availability check for Inztrow took 4.363059997558594e-05s
Availability | VoID file availability check for Inztrow took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Inztrow took 0.28732824325561523s
Reputation | Calculation of the PageRank for Inztrow took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for Inztrow took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Inztrow took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.075599670410156e-05s
Believability | Calculation of trust value for Inztrow took 1.3589859008789062e-05s
INFO | --- Analysis for Inztrow took 3.7929210662841797s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0007328987121582031s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.2872312068939209s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.022396326065063477s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for ipbes took 3.8962860107421875s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.410743713378906e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 5.805221796035767s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.022799015045166016s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 3.147125244140625e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0008368492126464844s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 6.0558319091796875e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.1205673217773438e-05s
INFO | --- Analysis for iptc-newscodes took 2174.397212266922s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.324802875518799s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.31132030487060547s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.021895170211791992s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 0.00010776519775390625s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.1444091796875e-05s
INFO | --- Analysis for iserve took 8.997628450393677s
Availability | SPARQL endpoint availability check for ISIC V4 took 40.18303561210632s
Availability | VoID file availability check for ISIC V4 took 0.0009102821350097656s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.297166109085083s
Reputation | Calculation of the PageRank for ISIC V4 took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.38690185546875e-05s
Believability | Calculation of trust value for ISIC V4 took 9.775161743164062e-06s
INFO | --- Analysis for isic-v4 took 139.1745204925537s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 8.606910705566406e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.31276583671569824s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020994186401367188s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.319450378417969e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 8.821487426757812e-06s
INFO | --- Analysis for isil-dbpedia took 4.54547381401062s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 8.702278137207031e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.3184351921081543s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.719329833984375e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.6927719116210938e-05s
INFO | --- Analysis for iso-639-oasis took 3.5193169116973877s
Availability | SPARQL endpoint availability check for ISOcat took 4.410743713378906e-05s
Availability | VoID file availability check for ISOcat took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for ISOcat took 0.3321714401245117s
Reputation | Calculation of the PageRank for ISOcat took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.580352783203125e-05s
Believability | Calculation of trust value for ISOcat took 1.33514404296875e-05s
INFO | --- Analysis for isocat took 65.266934633255s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 9.036064147949219e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.30245113372802734s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.4809112548828125e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.0251998901367188e-05s
INFO | --- Analysis for isocat-metadata took 5.790302276611328s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9285454750061035s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006630420684814453s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.468768358230591s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2803938388824463s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14025378227233887s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8647849559783936s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.13173317909241s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08473062515258789s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.03505229949951172s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10065507888793945s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09724545478820801s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09218406677246094s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13132739067077637s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.99755549430847s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0985879898071289s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3251962661743164s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3172173500061035s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13489246368408203s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1348719596862793s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08729982376098633s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 11.0565025806427s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.961822509765625e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13114643096923828s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20215201377868652s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.44191932678222656s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.40581178665161133s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13189244270324707s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16817378997802734s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0846104621887207s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 12.78827714920044s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08348608016967773s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08793497085571289s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08703804016113281s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.889392375946045s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31092023849487305s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2704317569732666s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08052206039428711s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.82771635055542s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9097764492034912s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.9255716800689697s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.330322265625s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.078487634658813s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.29993581771850586s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08938074111938477s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09656810760498047s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.3616304397583s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.40821409225463867s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.021071195602416992s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010633468627929688s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.430511474609375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.049041748046875e-05s
INFO | --- Analysis for ispra-lod-place took 445.21975660324097s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.050642967224121094s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.00031304359436035156s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.271704912185669s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.27523255348205566s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.14003396034240723s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.8901896476745605s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 92.02595090866089s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.08893585205078125s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.03310203552246094s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.10373234748840332s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.09873628616333008s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.08691072463989258s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.1474447250366211s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 90.90275740623474s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.08723735809326172s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.3537085056304932s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.30686235427856445s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.1496725082397461s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.14836359024047852s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.08452558517456055s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.411149501800537s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 6.985664367675781e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.1289365291595459s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.2037971019744873s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.44581151008605957s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.41083669662475586s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.1337566375732422s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.17536163330078125s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.08261537551879883s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 12.744365215301514s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.08236122131347656s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.08634090423583984s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.08568620681762695s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.745371103286743s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.31556057929992676s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.2643401622772217s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.07965588569641113s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 8.807656049728394s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9170398712158203s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.8395774364471436s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.324251413345337s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.056577920913696s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.30409884452819824s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.08942270278930664s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.09958481788635254s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.793308973312378s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.4338359832763672s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021334171295166016s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.886222839355469e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 7.867813110351562e-06s
INFO | --- Analysis for ispra-lod-ron took 438.28091645240784s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.7100875377655029s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.2978329658508301s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020889759063720703s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.775161743164062e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 9.775161743164062e-06s
INFO | --- Analysis for issa-agritrop took 4.931684255599976s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 8.96453857421875e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.29721593856811523s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.075599670410156e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 9.775161743164062e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.6494593620300293s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 9.107589721679688e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.31465578079223633s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.022190332412719727s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 4.792213439941406e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.0251998901367188e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 3.086029529571533s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 8.869171142578125e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.29228854179382324s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020865917205810547s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.1948089599609375e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.0728836059570312e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 2.8832390308380127s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.3131396770477295s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.31514763832092285s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020833253860473633s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.988380432128906e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 8.344650268554688e-06s
INFO | --- Analysis for istat-immigration took 4.23881459236145s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.22346234321594238s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.267503023147583s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.266334533691406e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 4.5299530029296875e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.2397663593292236s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.1621735095977783s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.29885077476501465s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.021987199783325195s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.748603820800781e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.2636184692382812e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 3.94586443901062s
Availability | SPARQL endpoint availability check for IWN took 8.726119995117188e-05s
Availability | VoID file availability check for IWN took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for IWN took 0.27781105041503906s
Reputation | Calculation of the PageRank for IWN took 0.021048545837402344s
Interlinking | Calculation of Degree of Connection for IWN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for IWN took 3.8623809814453125e-05s
Believability | Calculation of trust value for IWN took 1.1920928955078125e-05s
INFO | --- Analysis for iwn took 6.1910481452941895s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.675978183746338s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.28833937644958496s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.02211475372314453s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.580352783203125e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.1444091796875e-05s
INFO | --- Analysis for jamendo-dbtune took 10.527970314025879s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 8.869171142578125e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.00109100341796875s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2859928607940674s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.021352052688598633s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.8160552978515625e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.79790997505188s
Availability | SPARQL endpoint availability check for JEL Classification took 9.107589721679688e-05s
Availability | VoID file availability check for JEL Classification took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2761809825897217s
Reputation | Calculation of the PageRank for JEL Classification took 0.021860599517822266s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.147125244140625e-05s
Believability | Calculation of trust value for JEL Classification took 1.1205673217773438e-05s
INFO | --- Analysis for jel-classification took 5.146835803985596s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.150954008102417s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.2811398506164551s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02109217643737793s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.2901763916015625e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.430511474609375e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 7.461795806884766s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 262.24696803092957s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.001486063003540039s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.31833338737487793s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.021101713180541992s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.62939453125e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.239776611328125e-05s
INFO | --- Analysis for jita took 541.1186094284058s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.059204816818237s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.3454558849334717s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.021747827529907227s
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.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.749961853027344e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.33514404296875e-05s
INFO | --- Analysis for john-goodwins-family-tree took 62.92103052139282s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 8.96453857421875e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0011341571807861328s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2808856964111328s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.021440505981445312s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 4.100799560546875e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 1.33514404296875e-05s
INFO | --- Analysis for jp-cos took 4.694119930267334s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 8.869171142578125e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0008349418640136719s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.34363746643066406s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.02096414566040039s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.1961669921875e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.33514404296875e-05s
INFO | --- Analysis for jp-textbook took 4.5885374546051025s
Availability | SPARQL endpoint availability check for JRC-Names took 8.702278137207031e-05s
Availability | VoID file availability check for JRC-Names took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.31157994270324707s
Reputation | Calculation of the PageRank for JRC-Names took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.743171691894531e-05s
Believability | Calculation of trust value for JRC-Names took 1.3589859008789062e-05s
INFO | --- Analysis for jrc-names-ec took 4.918256044387817s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.0967466831207275s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.3267669677734375s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.021024465560913086s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.723403930664062e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 9.775161743164062e-06s
INFO | --- Analysis for jrc-names-mlode took 3.991185426712036s
Availability | SPARQL endpoint availability check for JudaicaLink took 8.606910705566406e-05s
Availability | VoID file availability check for JudaicaLink took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.43976688385009766s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 9.918212890625e-05s
Believability | Calculation of trust value for JudaicaLink took 9.775161743164062e-06s
INFO | --- Analysis for judaicalink took 4.988340139389038s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06310558319091797s
Availability | VoID file availability check for Kallikratis municipalities took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.2724761962890625s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.179115295410156e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 1.049041748046875e-05s
INFO | --- Analysis for kallikratis-municipalities took 2.7440309524536133s
Availability | SPARQL endpoint availability check for EU Soccer League took 8.7738037109375e-05s
Availability | VoID file availability check for EU Soccer League took 0.0013592243194580078s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2952895164489746s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.0040740966796875e-05s
Believability | Calculation of trust value for EU Soccer League took 1.1920928955078125e-05s
INFO | --- Analysis for KG:Course_Submission took 4.714715480804443s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 8.702278137207031e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.3137640953063965s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.021996021270751953s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.1682510375976562e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.3828277587890625e-05s
INFO | --- Analysis for KING took 2.858877420425415s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.482269287109375e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2895808219909668s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.022051095962524414s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.794929504394531e-05s
Believability | Calculation of trust value for Klappstuhlclub took 9.059906005859375e-06s
INFO | --- Analysis for klappstuhlclub took 12.846482515335083s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.873069047927856s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.31844568252563477s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.022033214569091797s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.699562072753906e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.33514404296875e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.668835163116455s
Availability | SPARQL endpoint availability check for Knowledge Forest took 8.606910705566406e-05s
Availability | VoID file availability check for Knowledge Forest took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2958238124847412s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.022014856338500977s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.4809112548828125e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.3113021850585938e-05s
INFO | --- Analysis for KnowledgeFusion took 2.7053771018981934s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 9.202957153320312e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.31536436080932617s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020800113677978516s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.818771362304688e-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.602588653564453s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.649162292480469e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.3199770450592041s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.021481037139892578s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.2901763916015625e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.049041748046875e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.7145988941192627s
Availability | SPARQL endpoint availability check for Informatics Studies took 8.606910705566406e-05s
Availability | VoID file availability check for Informatics Studies took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.29618024826049805s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020247220993041992s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.9325485229492188e-05s
Believability | Calculation of trust value for Informatics Studies took 5.7220458984375e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.239006519317627s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.0743412971496582s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2918245792388916s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020307064056396484s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.6716461181640625e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 5.9604644775390625e-06s
INFO | --- Analysis for kupkb took 10.538281917572021s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 8.37611436843872s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.3018631935119629s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02054119110107422s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.82012939453125e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.3113021850585938e-05s
INFO | --- Analysis for l3s-dblp took 42.781851291656494s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 22.78393244743347s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.3073763847351074s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 7.05718994140625e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for lak-dataset took 66.415531873703s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.2271287441253662s
Availability | VoID file availability check for  Language Name Authority List  took 0.0004820823669433594s
Extra | Recovery of all triples for  Language Name Authority List  took 164.0386393070221s
Performance | Total latancy measurement for  Language Name Authority List  took 0.5984227657318115s
Amount of data | Number of triples check for  Language Name Authority List  took 52.294055461883545s
Interoperability | New terms check for  Language Name Authority List  took 57.628777265548706s
Versatility | Languages check for  Language Name Authority List  took 300.15458631515503s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 77.16162300109863s
Security | Check HTTPS for  Language Name Authority List  took 0.4025113582611084s
Interpretability | RDF structures check for  Language Name Authority List  took 0.5240390300750732s
Versatility | Serialization formats check for  Language Name Authority List  took 2.968533992767334s
Availability | RDF dump link check for  Language Name Authority List  took 0.2389357089996338s
License | MR license check for  Language Name Authority List  took 0.36639833450317383s
License | HR license check for  Language Name Authority List  took 300.02899742126465s
Amount of data | Number of property check for  Language Name Authority List  took 0.9905414581298828s
Understandability | Number of label check for  Language Name Authority List  took 1.7123792171478271s
Understandability | URI regex check for  Language Name Authority List  took 0.39109086990356445s
Understandability | Vocabs check for  Language Name Authority List  took 0.10916733741760254s
Verifiability | Authors check for  Language Name Authority List  took 0.27271485328674316s
Verifiability | Publishers check for  Language Name Authority List  took 0.21635842323303223s
Performance | Throughput check for  Language Name Authority List  took 10.662087678909302s
Amount of data | Check the number of entities for  Language Name Authority List  took 7.319450378417969e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.19199895858764648s
Interlinking | sameAs chians check for  Language Name Authority List  took 6.429894208908081s
Interlinking | skos check for  Language Name Authority List  took 0.3354814052581787s
Interlinking | skos check for  Language Name Authority List  took 0.30360865592956543s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.28957462310791016s
Currency | Creation date check for  Language Name Authority List  took 0.5290460586547852s
Currency | Modification date check for  Language Name Authority List  took 0.22797918319702148s
Rep.Conc. | URIs length for  Language Name Authority List  took 422.48008847236633s
Interoperability | New vocabularies check for  Language Name Authority List  took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.17182517051696777s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.18828964233398438s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.16631150245666504s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 39.369694232940674s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.1856420040130615s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.655264377593994s
Consistency | Disjoint class check for  Language Name Authority List  took 0.17879438400268555s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.3926525115967s
Consistency | Misplaced classes for  Language Name Authority List  took 8.528421640396118s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 72.34608030319214s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.7187271118164062s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.5307319164276s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.1250243186950684s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.3766946792602539s
Security | Sign check for  Language Name Authority List  took 0.4775724411010742s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 11.121845006942749s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 5.768743991851807s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021397113800048828s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.799003601074219e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 2.1457672119140625e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.0967254638671875e-05s
INFO | --- Analysis for language-authority-list took 14935.188022375107s
Availability | SPARQL endpoint availability check for Lark took 384.36776995658875s
Availability | VoID file availability check for Lark took 0.0011754035949707031s
Completeness | Calculation of interlinking completeness for Lark took 0.5212979316711426s
Reputation | Calculation of the PageRank for Lark took 0.021311521530151367s
Interlinking | Calculation of Degree of Connection for Lark took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Lark took 7.82012939453125e-05s
Believability | Calculation of trust value for Lark took 1.1205673217773438e-05s
INFO | --- Analysis for LARK took 1676.1147108078003s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.4976320266723633s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.3242337703704834s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for LASLA took 4.436565399169922s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.548088788986206s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0003898143768310547s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.29439449310302734s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.022294044494628906s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 4.029273986816406e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 4.251507520675659s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.5177035331726074s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.2871253490447998s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.021708965301513672s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for LatinAffectus took 4.3927929401397705s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.5239262580871582s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.27576780319213867s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.124641418457031e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LatinWordnetLiLa took 4.521461248397827s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.220008850097656e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2878124713897705s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.022139787673950195s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011658668518066406s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.33514404296875e-05s
INFO | --- Analysis for lcsh took 7.128296852111816s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.363059997558594e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.2915787696838379s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.082389831542969e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.3589859008789062e-05s
INFO | --- Analysis for lcsubjects took 3.1378350257873535s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 9.974252700805664s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.32041168212890625s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.267692565917969e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.3589859008789062e-05s
INFO | --- Analysis for ldt@library took 38.78310513496399s
Availability | SPARQL endpoint availability check for U ime Legije took 8.96453857421875e-05s
Availability | VoID file availability check for U ime Legije took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.28100109100341797s
Reputation | Calculation of the PageRank for U ime Legije took 0.02115774154663086s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0010864734649658203s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.600120544433594e-05s
Believability | Calculation of trust value for U ime Legije took 1.1682510375976562e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 2.7001607418060303s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.4755115509033203s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0007593631744384766s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.27617979049682617s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.022645235061645508s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.152557373046875e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.2874603271484375e-05s
INFO | --- Analysis for LemmaBank took 4.700712203979492s
Availability | SPARQL endpoint availability check for lemonUby took 8.726119995117188e-05s
Availability | VoID file availability check for lemonUby took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for lemonUby took 0.30878710746765137s
Reputation | Calculation of the PageRank for lemonUby took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.389617919921875e-05s
Believability | Calculation of trust value for lemonUby took 1.2874603271484375e-05s
INFO | --- Analysis for lemonuby took 3.631699800491333s
Availability | SPARQL endpoint availability check for LemonWiktionary took 9.036064147949219e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.27527856826782227s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.02089977264404297s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.600120544433594e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.3828277587890625e-05s
INFO | --- Analysis for lemonwiktionary took 4.611777305603027s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.4644594192504883s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0008072853088378906s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.2741127014160156s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.022438764572143555s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 1.33514404296875e-05s
INFO | --- Analysis for LewisShort took 4.157754182815552s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.0449914932250977s
Availability | VoID file availability check for LEXIN-RDF took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.30602455139160156s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.021847963333129883s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.886222839355469e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.2636184692382812e-05s
INFO | --- Analysis for lexin-rdf took 6.082921266555786s
Availability | SPARQL endpoint availability check for lexinfo took 4.363059997558594e-05s
Availability | VoID file availability check for lexinfo took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for lexinfo took 0.2837717533111572s
Reputation | Calculation of the PageRank for lexinfo took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.893013000488281e-05s
Believability | Calculation of trust value for lexinfo took 1.1920928955078125e-05s
INFO | --- Analysis for lexinfo took 3.0869016647338867s
Availability | SPARQL endpoint availability check for Lexvo took 8.678436279296875e-05s
Availability | VoID file availability check for Lexvo took 0.001201629638671875s
Completeness | Calculation of interlinking completeness for Lexvo took 0.3346283435821533s
Reputation | Calculation of the PageRank for Lexvo took 0.022376298904418945s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017380714416503906s
Believability | Calculation of trust value for Lexvo took 1.1920928955078125e-05s
INFO | --- Analysis for lexvo took 3.7065296173095703s
Availability | SPARQL endpoint availability check for Lexvo.org took 0.00010418891906738281s
Availability | VoID file availability check for Lexvo.org took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.31909823417663574s
Reputation | Calculation of the PageRank for Lexvo.org took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.486343383789062e-05s
Believability | Calculation of trust value for Lexvo.org took 1.2159347534179688e-05s
INFO | --- Analysis for lexvo-org took 2.8219778537750244s
Availability | SPARQL endpoint availability check for LIBRIS took 0.39126110076904297s
Availability | VoID file availability check for LIBRIS took 0.0007479190826416016s
Extra | Recovery of all triples for LIBRIS took 6.282984972000122s
Performance | Total latancy measurement for LIBRIS took 0.7295918464660645s
Amount of data | Number of triples check for LIBRIS took 24.6863796710968s
Interoperability | New terms check for LIBRIS took 17.356082439422607s
Versatility | Languages check for LIBRIS took 0.20336246490478516s
Interpretability | Number of blank nodes check for LIBRIS took 300.09332633018494s
Security | Check HTTPS for LIBRIS took 0.33795762062072754s
Interpretability | RDF structures check for LIBRIS took 0.2551841735839844s
Versatility | Serialization formats check for LIBRIS took 0.21898412704467773s
Availability | RDF dump link check for LIBRIS took 0.13584589958190918s
License | MR license check for LIBRIS took 0.16776537895202637s
License | HR license check for LIBRIS took 0.14725995063781738s
Amount of data | Number of property check for LIBRIS took 0.21743488311767578s
Understandability | Number of label check for LIBRIS took 0.2556478977203369s
Understandability | URI regex check for LIBRIS took 0.295154333114624s
Understandability | Vocabs check for LIBRIS took 0.13650155067443848s
Verifiability | Authors check for LIBRIS took 0.14173221588134766s
Verifiability | Publishers check for LIBRIS took 0.15038728713989258s
Performance | Throughput check for LIBRIS took 10.739063024520874s
Amount of data | Check the number of entities for LIBRIS took 4.935264587402344e-05s
Verifiability | Contribs. check for LIBRIS took 0.14188528060913086s
Interlinking | sameAs chians check for LIBRIS took 0.1751258373260498s
Interlinking | skos check for LIBRIS took 0.1715073585510254s
Interlinking | skos check for LIBRIS took 0.1352686882019043s
Timeliness | dataset update frequency check for LIBRIS took 0.13082647323608398s
Currency | Creation date check for LIBRIS took 0.3372311592102051s
Currency | Modification date check for LIBRIS took 0.6535887718200684s
Rep.Conc. | URIs length for LIBRIS took 92.4533178806305s
Interoperability | New vocabularies check for LIBRIS took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.20958328247070312s
Accuracy | Check Functional Property for LIBRIS took 0.23801279067993164s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.17676186561584473s
Accuracy | Check Datatype consistency for LIBRIS took 0.27350735664367676s
Consistency | Disjoint class check for LIBRIS took 0.2184152603149414s
Consistency | Check Misplaced properties for LIBRIS took 70.39399814605713s
Consistency | Misplaced classes for LIBRIS took 1.1766722202301025s
Consistency | Check Ontology hijacking for LIBRIS took 3.300797462463379s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.2857544422149658s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 71.48368406295776s
Conciseness | Check Extensional conciseness for LIBRIS took 0.28887200355529785s
Conciseness | Check Intensional conciseness for LIBRIS took 0.432999849319458s
Security | Sign check for LIBRIS took 0.17189741134643555s
Availability | Check URIs Dereferenciability for LIBRIS took 9.249354124069214s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.4520082473754883s
Reputation | Calculation of the PageRank for LIBRIS took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.00010848045349121094s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.430511474609375e-06s
Believability | Calculation of trust value for LIBRIS took 1.3113021850585938e-05s
INFO | --- Analysis for libris took 1097.298320055008s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.18068289756774902s
Availability | VoID file availability check for Public Library of Veroia took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.31781625747680664s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.021126508712768555s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 8.058547973632812e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.2874603271484375e-05s
INFO | --- Analysis for libver took 4.3691089153289795s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.16517138481140137s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.28470492362976074s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0008134841918945312s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 9.441375732421875e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 9.775161743164062e-06s
INFO | --- Analysis for lichfield-spending took 2.909978151321411s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 0.00011372566223144531s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.28095364570617676s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.528594970703125e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 2.2411346435546875e-05s
INFO | --- Analysis for lime took 6.591837644577026s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 6.437301635742188e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.49765753746032715s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.3120429515838623s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.021784543991088867s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0001049041748046875s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.1682510375976562e-05s
INFO | --- Analysis for lingvoj took 15.440712451934814s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.3121953010559082s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020675182342529297s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.987022399902344e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.0967254638671875e-05s
INFO | --- Analysis for linked-crunchbase took 15.204338073730469s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1699087619781494s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2903890609741211s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.02107405662536621s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.414817810058594e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.3113021850585938e-05s
INFO | --- Analysis for linked-drugs took 8.295395374298096s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 7.796287536621094e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.2820565700531006s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020936250686645508s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.608268737792969e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 9.298324584960938e-06s
INFO | --- Analysis for linked-edgar took 4.841445684432983s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.673004150390625e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.2979319095611572s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.918212890625e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.867813110351562e-06s
INFO | --- Analysis for linked-eurostat took 3.797661304473877s
Availability | SPARQL endpoint availability check for linked hypernyms took 9.107589721679688e-05s
Availability | VoID file availability check for linked hypernyms took 0.00079345703125s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.278261661529541s
Reputation | Calculation of the PageRank for linked hypernyms took 0.021699190139770508s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 8.249282836914062e-05s
Believability | Calculation of trust value for linked hypernyms took 1.1682510375976562e-05s
INFO | --- Analysis for linked-hypernyms took 3.580848455429077s
Availability | SPARQL endpoint availability check for Linked Life Data took 208.61300134658813s
Availability | VoID file availability check for Linked Life Data took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.5347332954406738s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.935264587402344e-05s
Believability | Calculation of trust value for Linked Life Data took 1.3828277587890625e-05s
INFO | --- Analysis for linked-life-data took 622.5814256668091s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.30573558807373047s
Availability | VoID file availability check for Linked Logainm took 0.0005233287811279297s
Extra | Recovery of all triples for Linked Logainm took 1.6731970310211182s
Performance | Total latancy measurement for Linked Logainm took 0.5936713218688965s
Amount of data | Number of triples check for Linked Logainm took 0.16933202743530273s
Interoperability | New terms check for Linked Logainm took 1.4245498180389404s
Versatility | Languages check for Linked Logainm took 1.4955754280090332s
Interpretability | Number of blank nodes check for Linked Logainm took 0.14144396781921387s
Security | Check HTTPS for Linked Logainm took 0.259871244430542s
Interpretability | RDF structures check for Linked Logainm took 0.2568683624267578s
Versatility | Serialization formats check for Linked Logainm took 0.16304612159729004s
Availability | RDF dump link check for Linked Logainm took 0.12241244316101074s
License | MR license check for Linked Logainm took 0.12818574905395508s
License | HR license check for Linked Logainm took 0.11885690689086914s
Amount of data | Number of property check for Linked Logainm took 0.1494004726409912s
Understandability | Number of label check for Linked Logainm took 0.19992494583129883s
Understandability | URI regex check for Linked Logainm took 0.23322558403015137s
Understandability | Vocabs check for Linked Logainm took 0.10677051544189453s
Verifiability | Authors check for Linked Logainm took 0.11760973930358887s
Verifiability | Publishers check for Linked Logainm took 0.11397671699523926s
Performance | Throughput check for Linked Logainm took 10.947454929351807s
Amount of data | Check the number of entities for Linked Logainm took 7.2479248046875e-05s
Verifiability | Contribs. check for Linked Logainm took 0.11744093894958496s
Interlinking | sameAs chians check for Linked Logainm took 0.14919471740722656s
Interlinking | skos check for Linked Logainm took 0.14983701705932617s
Interlinking | skos check for Linked Logainm took 0.11264872550964355s
Timeliness | dataset update frequency check for Linked Logainm took 0.12043523788452148s
Currency | Creation date check for Linked Logainm took 0.26906847953796387s
Currency | Modification date check for Linked Logainm took 0.25994443893432617s
Rep.Conc. | URIs length for Linked Logainm took 0.8829696178436279s
Interoperability | New vocabularies check for Linked Logainm took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.14305853843688965s
Accuracy | Check Functional Property for Linked Logainm took 0.22156620025634766s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.18844938278198242s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.5616462230682373s
Accuracy | Check White space in annotation for Linked Logainm took 0.02451181411743164s
Accuracy | Check Datatype consistency for Linked Logainm took 0.03221774101257324s
Consistency | Disjoint class check for Linked Logainm took 0.18898415565490723s
Consistency | Check Misplaced properties for Linked Logainm took 0.3441760540008545s
Consistency | Misplaced classes for Linked Logainm took 0.2940225601196289s
Consistency | Check Ontology hijacking for Linked Logainm took 1.7708823680877686s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.2481794357299805s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.4902184009552002s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.03338003158569336s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.2036752700805664s
Security | Sign check for Linked Logainm took 0.12639856338500977s
Availability | Check URIs Dereferenciability for Linked Logainm took 1005.0050237178802s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.4495725631713867s
Reputation | Calculation of the PageRank for Linked Logainm took 0.022004365921020508s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Logainm took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 7.462501525878906e-05s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 3.337860107421875e-06s
Believability | Calculation of trust value for Linked Logainm took 1.0967254638671875e-05s
INFO | --- Analysis for linked-logainm took 1061.5298640727997s
Availability | SPARQL endpoint availability check for Linked NUTS took 8.559226989746094e-05s
Availability | VoID file availability check for Linked NUTS took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.2984311580657959s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020747661590576172s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.459785461425781e-05s
Believability | Calculation of trust value for Linked NUTS took 9.298324584960938e-06s
INFO | --- Analysis for linked-nuts took 2.8388071060180664s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.4278748035430908s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.3204386234283447s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.62396240234375e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 8.106231689453125e-06s
INFO | --- Analysis for linked-open-camera took 4.312095403671265s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.542056322097778s
Availability | VoID file availability check for Linked Open Commerce took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.30321168899536133s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.0013580322265625e-05s
INFO | --- Analysis for linked-open-commerce took 15.327652215957642s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 0.630305290222168s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.3044099807739258s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.02156209945678711s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010061264038085938s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.1205673217773438e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 3.3528928756713867s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2900395393371582s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 0.00011038780212402344s
Believability | Calculation of trust value for Linked Open Numbers took 1.0728836059570312e-05s
INFO | --- Analysis for linked-open-numbers took 2.870830535888672s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 8.797645568847656e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.27408504486083984s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.021347761154174805s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked Open Piracy took 8.344650268554688e-06s
INFO | --- Analysis for linked-open-piracy took 7.3551390171051025s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 3.6009957790374756s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0005900859832763672s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 91.14443731307983s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 8.078399181365967s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 1.869985580444336s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 3.1407055854797363s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 18.655791997909546s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 3.4288299083709717s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 1.069913387298584s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 1.6322729587554932s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 1.6526780128479004s
License | MR license check for Linked Open Vocabularies (LOV) took 1.3199799060821533s
License | HR license check for Linked Open Vocabularies (LOV) took 52.083372354507446s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 1.045919418334961s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 2.7483630180358887s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 3.6370980739593506s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 1.4173822402954102s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 1.308525800704956s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 1.923384189605713s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 19.535602569580078s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 1.0379323959350586s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 1.0369856357574463s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 1.8183262348175049s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 1.6754369735717773s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 1.4237473011016846s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 1.4210317134857178s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 5.2594895362854s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 1.4455018043518066s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 33.885278940200806s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 67.4375114440918s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 1.5741376876831055s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 1.7893385887145996s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.9415621757507324s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 9.187241554260254s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6873438358306885s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.726119041442871s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 0.8020644187927246s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 9.592784643173218s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 1.5744922161102295s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 8.331876993179321s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.3304920196533203s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.946324586868286s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 4.50797700881958s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.9272680282592773s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 5419.776599407196s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.7651534080505371s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.02181243896484375s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 6.890296936035156e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 6.818771362304688e-05s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 66.79419231414795s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.1682510375976562e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 6693.5630671978s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.3399362564086914s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020888566970825195s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.647804260253906e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 8.344650268554688e-06s
INFO | --- Analysis for linked-periodicals took 2.977820634841919s
Availability | SPARQL endpoint availability check for Linked Index took 8.487701416015625e-05s
Availability | VoID file availability check for Linked Index took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Linked Index took 0.28885602951049805s
Reputation | Calculation of the PageRank for Linked Index took 0.02134108543395996s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.487701416015625e-05s
Believability | Calculation of trust value for Linked Index took 1.0728836059570312e-05s
INFO | --- Analysis for linked-stockindex took 3.4570958614349365s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.964104175567627s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2905232906341553s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.02088642120361328s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.981590270996094e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.2874603271484375e-05s
INFO | --- Analysis for linked-structured-product-labels took 18.721091747283936s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.055002689361572266s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.303668737411499s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.2636184692382812e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 3.120292901992798s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.376765251159668s
Availability | VoID file availability check for Linked TCGA took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.2974109649658203s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02083420753479004s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.845329284667969e-05s
Believability | Calculation of trust value for Linked TCGA took 1.0728836059570312e-05s
INFO | --- Analysis for linked-tcga took 63.0774884223938s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.09759688377380371s
Availability | VoID file availability check for Linked User Feedback took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.2748851776123047s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.022666215896606445s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 4.00543212890625e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.0728836059570312e-05s
INFO | --- Analysis for linked-user-feedback took 2.860562324523926s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.100799560546875e-05s
Availability | VoID file availability check for USPTO Patent data took 0.00115966796875s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.29300737380981445s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.02082085609436035s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.867813110351562e-05s
Believability | Calculation of trust value for USPTO Patent data took 1.1205673217773438e-05s
INFO | --- Analysis for linked-uspto-patent-data took 53.556697845458984s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.1865689754486084s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.37489986419677734s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02084970474243164s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 4.00543212890625e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.0728836059570312e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 3.2865610122680664s
Availability | SPARQL endpoint availability check for LinkedCT took 1.386099100112915s
Availability | VoID file availability check for LinkedCT took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.3451082706451416s
Reputation | Calculation of the PageRank for LinkedCT took 0.020876407623291016s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.799003601074219e-05s
Believability | Calculation of trust value for LinkedCT took 1.0251998901367188e-05s
INFO | --- Analysis for linkedct took 5.189468860626221s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.1671292781829834s
Availability | VoID file availability check for LinkedGeoData took 0.0004913806915283203s
Extra | Recovery of all triples for LinkedGeoData took 7.047373533248901s
Performance | Total latancy measurement for LinkedGeoData took 0.7007040977478027s
Amount of data | Number of triples check for LinkedGeoData took 52.78327226638794s
Interoperability | New terms check for LinkedGeoData took 90.81780481338501s
Versatility | Languages check for LinkedGeoData took 180.37115001678467s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.20949578285217285s
Security | Check HTTPS for LinkedGeoData took 0.32643604278564453s
Interpretability | RDF structures check for LinkedGeoData took 0.6413960456848145s
Versatility | Serialization formats check for LinkedGeoData took 0.3689393997192383s
Availability | RDF dump link check for LinkedGeoData took 0.16768598556518555s
License | MR license check for LinkedGeoData took 0.6316120624542236s
License | HR license check for LinkedGeoData took 116.49064779281616s
Amount of data | Number of property check for LinkedGeoData took 0.1683955192565918s
Understandability | Number of label check for LinkedGeoData took 2.1144461631774902s
Understandability | URI regex check for LinkedGeoData took 0.39702510833740234s
Understandability | Vocabs check for LinkedGeoData took 0.1686704158782959s
Verifiability | Authors check for LinkedGeoData took 0.19820356369018555s
Verifiability | Publishers check for LinkedGeoData took 0.13460183143615723s
Performance | Throughput check for LinkedGeoData took 10.61394739151001s
Amount of data | Check the number of entities for LinkedGeoData took 0.06771135330200195s
Verifiability | Contribs. check for LinkedGeoData took 0.16568779945373535s
Interlinking | sameAs chians check for LinkedGeoData took 0.2524547576904297s
Interlinking | skos check for LinkedGeoData took 0.39148783683776855s
Interlinking | skos check for LinkedGeoData took 0.12674999237060547s
Timeliness | dataset update frequency check for LinkedGeoData took 0.3814516067504883s
Currency | Creation date check for LinkedGeoData took 0.35600733757019043s
Currency | Modification date check for LinkedGeoData took 0.28204965591430664s
Rep.Conc. | URIs length for LinkedGeoData took 270.9702351093292s
Interoperability | New vocabularies check for LinkedGeoData took 43.793240785598755s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.15555024147033691s
Accuracy | Check Functional Property for LinkedGeoData took 0.17499542236328125s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.18312335014343262s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.8494782447814941s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15793824195861816s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13486099243164062s
Consistency | Disjoint class check for LinkedGeoData took 0.19439196586608887s
Consistency | Check Misplaced properties for LinkedGeoData took 182.3753159046173s
Consistency | Misplaced classes for LinkedGeoData took 0.7877519130706787s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.652336835861206s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.2841343879699707s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.08840680122375s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.15474629402160645s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.28325796127319336s
Security | Sign check for LinkedGeoData took 0.636786937713623s
Availability | Check URIs Dereferenciability for LinkedGeoData took 17.24148678779602s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.5142059326171875s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021510839462280273s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00012946128845214844s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 53.944169759750366s
Believability | Calculation of trust value for LinkedGeoData took 1.3589859008789062e-05s
INFO | --- Analysis for linkedgeodata took 2248.4514269828796s
Availability | SPARQL endpoint availability check for LinkedLCCN took 0.956162691116333s
Availability | VoID file availability check for LinkedLCCN took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.30869531631469727s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.022013425827026367s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010609626770019531s
Believability | Calculation of trust value for LinkedLCCN took 1.2159347534179688e-05s
INFO | --- Analysis for linkedlccn took 26.064990043640137s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 8.7738037109375e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.290132999420166s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020873546600341797s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.743171691894531e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.33514404296875e-05s
INFO | --- Analysis for linkedmarkmail took 2.939326763153076s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.60297250747681s
Availability | VoID file availability check for Linked Movie DataBase took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.31603026390075684s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.0210416316986084s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013971328735351562s
Believability | Calculation of trust value for Linked Movie DataBase took 1.3589859008789062e-05s
INFO | --- Analysis for linkedmdb took 133.73174238204956s
Availability | SPARQL endpoint availability check for LinkedSpending took 0.4930083751678467s
Availability | VoID file availability check for LinkedSpending took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for LinkedSpending took 0.34163618087768555s
Reputation | Calculation of the PageRank for LinkedSpending took 0.022154808044433594s
Interlinking | Calculation of Degree of Connection for LinkedSpending took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for LinkedSpending took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for LinkedSpending took 8.392333984375e-05s
Believability | Calculation of trust value for LinkedSpending took 1.2636184692382812e-05s
INFO | --- Analysis for linkedspending took 4.35457181930542s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.06823205947875977s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.30028724670410156s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02123284339904785s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00011134147644042969s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.3828277587890625e-05s
INFO | --- Analysis for linklion took 2.7518045902252197s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 600.4694526195526s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.29758596420288086s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.745887756347656e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.3828277587890625e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 1215.0707201957703s
Availability | SPARQL endpoint availability check for lobid-organisations took 0.9697778224945068s
Availability | VoID file availability check for lobid-organisations took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.3058736324310303s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.72747802734375e-05s
Believability | Calculation of trust value for lobid-organisations took 1.1205673217773438e-05s
INFO | --- Analysis for lobid-organisations took 5.761242628097534s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.764498233795166s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.3052184581756592s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.02062535285949707s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010085105895996094s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.3589859008789062e-05s
INFO | --- Analysis for lobid-resources took 7.708569288253784s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.458427429199219e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.3217611312866211s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 8.0108642578125e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.0251998901367188e-05s
INFO | --- Analysis for loc took 7.4962685108184814s
Availability | SPARQL endpoint availability check for Location Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Location Ontology took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.273728609085083s
Reputation | Calculation of the PageRank for Location Ontology took 0.021913528442382812s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for Location Ontology took 5.793571472167969e-05s
INFO | --- Analysis for Location_Ontology took 5.231739521026611s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 8.726119995117188e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.303450345993042s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.021934032440185547s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.170967102050781e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.0728836059570312e-05s
INFO | --- Analysis for locv took 33.95384335517883s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7871823310852051s
Availability | VoID file availability check for LOD-a-lot took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.3293118476867676s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020650386810302734s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.3855438232421875e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.1682510375976562e-05s
INFO | --- Analysis for lod-a-lot took 14.292715072631836s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 8.940696716308594e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.32610559463500977s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.021409034729003906s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.916854858398438e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.1205673217773438e-05s
INFO | --- Analysis for lod2-project-wiki took 3.2922163009643555s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.676765203475952s
Availability | VoID file availability check for LODAC BDLS took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.3233344554901123s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.021565914154052734s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 8.225440979003906e-05s
Believability | Calculation of trust value for LODAC BDLS took 1.1920928955078125e-05s
INFO | --- Analysis for lodac-bdls took 14.056105375289917s
Availability | SPARQL endpoint availability check for lofd took 0.12709617614746094s
Availability | VoID file availability check for lofd took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for lofd took 0.27871179580688477s
Reputation | Calculation of the PageRank for lofd took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for lofd took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for lofd took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for lofd took 3.147125244140625e-05s
Believability | Calculation of trust value for lofd took 1.0251998901367188e-05s
INFO | --- Analysis for lofd took 2.8700923919677734s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.2513575553894s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.28147435188293457s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.7697296142578125e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 9.775161743164062e-06s
INFO | --- Analysis for loius took 585.535001039505s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.6254355907440186s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.3028244972229004s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.0209503173828125s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.364418029785156e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 9.059906005859375e-06s
INFO | --- Analysis for london-gazette took 4.2767252922058105s
Availability | SPARQL endpoint availability check for Weather Stations took 4.267692565917969e-05s
Availability | VoID file availability check for Weather Stations took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.3219122886657715s
Reputation | Calculation of the PageRank for Weather Stations took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.368492126464844e-05s
Believability | Calculation of trust value for Weather Stations took 1.3589859008789062e-05s
INFO | --- Analysis for los_metar took 10.989062309265137s
Availability | SPARQL endpoint availability check for Lotico took 0.5432314872741699s
Availability | VoID file availability check for Lotico took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for Lotico took 0.3197963237762451s
Reputation | Calculation of the PageRank for Lotico took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for Lotico took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.463859558105469e-05s
Believability | Calculation of trust value for Lotico took 1.2159347534179688e-05s
INFO | --- Analysis for lotico took 4.955860137939453s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.36069560050964355s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0007352828979492188s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.0850050449371338s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.9485228061676025s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.20023870468139648s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.5851476192474365s
Versatility | Languages check for Lower Layer Super Output Areas took 0.591144323348999s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.235656261444092s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.1946258544921875s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.14829206466674805s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.223341703414917s
Availability | RDF dump link check for Lower Layer Super Output Areas took 51.135167360305786s
License | MR license check for Lower Layer Super Output Areas took 0.14558029174804688s
License | HR license check for Lower Layer Super Output Areas took 30.250284910202026s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.14172148704528809s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.20737338066101074s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.34552907943725586s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.13647818565368652s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.14162087440490723s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.20798611640930176s
Performance | Throughput check for Lower Layer Super Output Areas took 11.305211782455444s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 7.009506225585938e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.19553589820861816s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.21644091606140137s
Interlinking | skos check for Lower Layer Super Output Areas took 0.14999628067016602s
Interlinking | skos check for Lower Layer Super Output Areas took 0.13260865211486816s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.5076367855072021s
Currency | Creation date check for Lower Layer Super Output Areas took 0.4218904972076416s
Currency | Modification date check for Lower Layer Super Output Areas took 0.1934816837310791s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.4868435859680176s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.1851809024810791s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.1477499008178711s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.14994263648986816s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.20618081092834473s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 1.178645372390747s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 1.5469598770141602s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.5095782279968262s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.00014495849609375s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.46219682693481445s
Security | Sign check for Lower Layer Super Output Areas took 0.14863991737365723s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.2956380844116211s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020905017852783203s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.647804260253906e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 1.6689300537109375e-06s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.0967254638671875e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 268.69071793556213s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6280248165130615s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0005514621734619141s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 117.40313720703125s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9703898429870605s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.221365451812744s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.061473369598389s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.1896073818207s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.382397413253784s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3604695796966553s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.892115354537964s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.36637425422668457s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9678497314453125s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2171552181244s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21271038055419922s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2057685852050781s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2634625434875488s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6293637752532959s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21326398849487305s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.24491500854492188s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.37430477142334s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.2901763916015625e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19670343399047852s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19370579719543457s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5254578590393066s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.44238805770874023s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.893463850021362s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.49784326553344727s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.24983501434326172s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 160.1563606262207s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1853783130645752s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5116841793060303s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5176947116851807s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 39.48508977890015s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.711085319519043s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.615694999694824s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.18450617790222168s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 85.45565438270569s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.403287649154663s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 30.634440183639526s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3162548542022705s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 86.73643708229065s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.8500936031341553s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5567111968994141s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2121899127960205s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 16.490116596221924s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5597336292266846s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.981590270996094e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for LPIS_(Poland) took 2273.051338195801s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21215367317199707s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0005085468292236328s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 112.4692440032959s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9509820938110352s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.925867557525635s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 13.961581468582153s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.22709035873413s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.0315699577331543s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19535565376281738s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.972213745117188s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4024217128753662s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8821420669555664s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.245267868042s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1847536563873291s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1831657886505127s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0373201370239258s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.6643218994140625s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19769668579101562s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22655797004699707s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.365501880645752s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.295608520507812e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18683576583862305s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1829211711883545s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.45043087005615234s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4029257297515869s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.188916444778442s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5249176025390625s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.24210524559020996s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 157.20595908164978s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19415974617004395s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19279170036315918s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20934128761291504s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 40.66929364204407s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.681083917617798s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7311644554138184s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1767270565032959s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.00512385368347s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.504088878631592s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 39.3091504573822s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3964264392852783s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.5271966457367s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.9345107078552246s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5423355102539062s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19660353660583496s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.409968376159668s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.695929288864136s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.020987987518310547s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.318092346191406e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2274.021135568619s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 9.059906005859375e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.27254652976989746s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.020664453506469727s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.3855438232421875e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.2874603271484375e-05s
INFO | --- Analysis for lremap-auth took 3.3441081047058105s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.38690185546875e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.30023860931396484s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.0279159545898438e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 9.775161743164062e-06s
INFO | --- Analysis for lremap-conf took 2.931666135787964s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 0.00014925003051757812s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.2825582027435303s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 2.86102294921875e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.3828277587890625e-05s
INFO | --- Analysis for lremap-ri took 2.952927589416504s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 8.845329284667969e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.27352309226989746s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.0203554630279541s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 2.9087066650390625e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.0251998901367188e-05s
INFO | --- Analysis for lremap-sub took 3.037357807159424s
Availability | SPARQL endpoint availability check for LSQ took 8.511543273925781e-05s
Availability | VoID file availability check for LSQ took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for LSQ took 0.28846287727355957s
Reputation | Calculation of the PageRank for LSQ took 0.022069692611694336s
Interlinking | Calculation of Degree of Connection for LSQ took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.075599670410156e-05s
Believability | Calculation of trust value for LSQ took 1.33514404296875e-05s
INFO | --- Analysis for lsq took 4.534363746643066s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6982741355895996s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006964206695556641s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.27889299392700195s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for LucaniPharsalia took 4.537170648574829s
Availability | SPARQL endpoint availability check for Linked rules took 8.845329284667969e-05s
Availability | VoID file availability check for Linked rules took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Linked rules took 0.3006770610809326s
Reputation | Calculation of the PageRank for Linked rules took 0.02074599266052246s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.266334533691406e-05s
Believability | Calculation of trust value for Linked rules took 1.1682510375976562e-05s
INFO | --- Analysis for Luminaires_senlis took 2.668182134628296s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.20759081840515s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.2663917541503906s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020769119262695312s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.0517578125e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.239776611328125e-05s
INFO | --- Analysis for makg took 63.704615116119385s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.792213439941406e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.2889900207519531s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.409385681152344e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 1.2636184692382812e-05s
INFO | --- Analysis for manchester-university-reading-lists took 4.018430471420288s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.482269287109375e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2835569381713867s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.021051406860351562s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.1682510375976562e-05s
INFO | --- Analysis for manish took 2.7838897705078125s
Availability | SPARQL endpoint availability check for MARC Codes List took 8.916854858398438e-05s
Availability | VoID file availability check for MARC Codes List took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.31558871269226074s
Reputation | Calculation of the PageRank for MARC Codes List took 0.02118062973022461s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0009799003601074219s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.0001461505889892578s
Believability | Calculation of trust value for MARC Codes List took 1.3589859008789062e-05s
INFO | --- Analysis for marc-codes took 13.936233043670654s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.012222290039062e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.27748727798461914s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020780563354492188s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0008885860443115234s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 5.1021575927734375e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.2159347534179688e-05s
INFO | --- Analysis for masc took 6.233139991760254s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 9.059906005859375e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.27976536750793457s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020860910415649414s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 4.0531158447265625e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.1920928955078125e-05s
INFO | --- Analysis for masc-bn-nif took 2.836338758468628s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.1601698398590088s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.28756284713745117s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.147125244140625e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 1.239776611328125e-05s
INFO | --- Analysis for massobservationarchivecatalogue took 3.9225316047668457s
Availability | SPARQL endpoint availability check for medline took 4.291534423828125e-05s
Availability | VoID file availability check for medline took 0.0007464885711669922s
Completeness | Calculation of interlinking completeness for medline took 0.34078288078308105s
Reputation | Calculation of the PageRank for medline took 0.02102065086364746s
Interlinking | Calculation of Degree of Connection for medline took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for medline took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for medline took 3.6716461181640625e-05s
Believability | Calculation of trust value for medline took 1.3828277587890625e-05s
INFO | --- Analysis for medline took 7.2002270221710205s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.8352136611938477s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0008399486541748047s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.3132009506225586s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02135944366455078s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007538795471191406s
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.239776611328125e-05s
INFO | --- Analysis for meducator took 12.41514253616333s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 9.179115295410156e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.28707170486450195s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.939338684082031e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.2874603271484375e-05s
INFO | --- Analysis for metashare took 2.693021059036255s
Availability | SPARQL endpoint availability check for MExiCo took 8.845329284667969e-05s
Availability | VoID file availability check for MExiCo took 0.0008194446563720703s
Completeness | Calculation of interlinking completeness for MExiCo took 0.32593750953674316s
Reputation | Calculation of the PageRank for MExiCo took 0.022369861602783203s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.887580871582031e-05s
Believability | Calculation of trust value for MExiCo took 1.4066696166992188e-05s
INFO | --- Analysis for mexico took 22.92096972465515s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.058793306350708s
Availability | VoID file availability check for Coronavirus dataset took 0.00029587745666503906s
Extra | Recovery of all triples for Coronavirus dataset took 5.802303075790405s
Performance | Total latancy measurement for Coronavirus dataset took 2.4935386180877686s
Amount of data | Number of triples check for Coronavirus dataset took 1.1912896633148193s
Interoperability | New terms check for Coronavirus dataset took 2.6167850494384766s
Versatility | Languages check for Coronavirus dataset took 60.525009870529175s
Interpretability | Number of blank nodes check for Coronavirus dataset took 2.994563579559326s
Interpretability | RDF structures check for Coronavirus dataset took 0.5542552471160889s
Versatility | Serialization formats check for Coronavirus dataset took 0.5505955219268799s
Availability | RDF dump link check for Coronavirus dataset took 0.48889589309692383s
License | MR license check for Coronavirus dataset took 0.5644609928131104s
License | HR license check for Coronavirus dataset took 42.588858127593994s
Amount of data | Number of property check for Coronavirus dataset took 0.5302951335906982s
Understandability | Number of label check for Coronavirus dataset took 1.509061574935913s
Understandability | URI regex check for Coronavirus dataset took 1.0056400299072266s
Understandability | Vocabs check for Coronavirus dataset took 0.5079653263092041s
Verifiability | Authors check for Coronavirus dataset took 0.5648901462554932s
Verifiability | Publishers check for Coronavirus dataset took 0.49837803840637207s
Performance | Throughput check for Coronavirus dataset took 13.836087226867676s
Amount of data | Check the number of entities for Coronavirus dataset took 7.295608520507812e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.49493908882141113s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5424926280975342s
Interlinking | skos check for Coronavirus dataset took 0.5394906997680664s
Interlinking | skos check for Coronavirus dataset took 0.4844503402709961s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.49921488761901855s
Currency | Creation date check for Coronavirus dataset took 1.0276570320129395s
Currency | Modification date check for Coronavirus dataset took 1.0315518379211426s
Rep.Conc. | URIs length for Coronavirus dataset took 8.289840459823608s
Interoperability | New vocabularies check for Coronavirus dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5995142459869385s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7700085639953613s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.7356719970703125s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.1099562644958496s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.02286982536315918s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.02763199806213379s
Consistency | Disjoint class check for Coronavirus dataset took 1.0334134101867676s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.713581562042236s
Consistency | Misplaced classes for Coronavirus dataset took 0.6144857406616211s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.362062692642212s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.2310094833374023s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.544698476791382s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03186368942260742s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5428969860076904s
Security | Sign check for Coronavirus dataset took 0.5299592018127441s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3141.5635418891907s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.7611637115478516s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 6.437301635742188e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Coronavirus dataset took 3.62396240234375e-05s
INFO | --- Analysis for micro-coronavirus took 3375.1110310554504s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0001010894775390625s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.31399083137512207s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00011587142944335938s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.775161743164062e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 5.9162070751190186s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011014938354492188s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.30426597595214844s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020878314971923828s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010919570922851562s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 5.7220458984375e-06s
INFO | --- Analysis for mismuseos-gnoss took 8.869771718978882s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.10331416130065918s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.27207112312316895s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.482269287109375e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.152557373046875e-06s
INFO | --- Analysis for mlsa took 3.3152658939361572s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 8.606910705566406e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.30100035667419434s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020909547805786133s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.814697265625e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 1.1444091796875e-05s
INFO | --- Analysis for model took 37.78579568862915s
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 8.487701416015625e-05s
Availability | VoID file availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.28058433532714844s
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.020473718643188477s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 2.9087066650390625e-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.3589859008789062e-05s
INFO | --- Analysis for model1 took 21.47147011756897s
Availability | SPARQL endpoint availability check for MORElab took 1.0158629417419434s
Availability | VoID file availability check for MORElab took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for MORElab took 0.3096897602081299s
Reputation | Calculation of the PageRank for MORElab took 0.02285480499267578s
Interlinking | Calculation of Degree of Connection for MORElab took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for MORElab took 9.131431579589844e-05s
Believability | Calculation of trust value for MORElab took 1.2874603271484375e-05s
INFO | --- Analysis for morelab took 5.778167247772217s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 2.004829168319702s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.28914976119995117s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.022443294525146484s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0012471675872802734s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 0.0001220703125s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.3589859008789062e-05s
INFO | --- Analysis for msc took 16.955925226211548s
Availability | SPARQL endpoint availability check for Multext-East took 5.125999450683594e-05s
Availability | VoID file availability check for Multext-East took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for Multext-East took 0.291259765625s
Reputation | Calculation of the PageRank for Multext-East took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for Multext-East took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Multext-East took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.457069396972656e-05s
Believability | Calculation of trust value for Multext-East took 1.0251998901367188e-05s
INFO | --- Analysis for multext-east took 2.642944574356079s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.3392181396484375e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.37081456184387207s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.02421259880065918s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0012049674987792969s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 4.410743713378906e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.2874603271484375e-05s
INFO | --- Analysis for multimedia-lab took 2.8362460136413574s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.6455371379852295s
Availability | VoID file availability check for Muninn World War I took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.30072474479675293s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.320808410644531e-05s
Believability | Calculation of trust value for Muninn World War I took 1.3589859008789062e-05s
INFO | --- Analysis for muninn-world-war-i took 11.182575225830078s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 9.107589721679688e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.28928351402282715s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.021430253982543945s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011420249938964844s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.2636184692382812e-05s
INFO | --- Analysis for museosespania-gnoss took 39.99376106262207s
Availability | SPARQL endpoint availability check for Italian Museums took 1.4441311359405518s
Availability | VoID file availability check for Italian Museums took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.291780948638916s
Reputation | Calculation of the PageRank for Italian Museums took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for Italian Museums took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.177757263183594e-05s
Believability | Calculation of trust value for Italian Museums took 1.239776611328125e-05s
INFO | --- Analysis for museums-in-italy took 4.177076578140259s
Availability | SPARQL endpoint availability check for Muziekweb took 0.8556592464447021s
Availability | VoID file availability check for Muziekweb took 0.0005950927734375s
Extra | Recovery of all triples for Muziekweb took 1.5039260387420654s
Performance | Total latancy measurement for Muziekweb took 1.5064647197723389s
Amount of data | Number of triples check for Muziekweb took 0.40464329719543457s
Interoperability | New terms check for Muziekweb took 1.6573851108551025s
Versatility | Languages check for Muziekweb took 56.74397134780884s
Interpretability | Number of blank nodes check for Muziekweb took 0.3188145160675049s
Interpretability | RDF structures check for Muziekweb took 0.3559596538543701s
Versatility | Serialization formats check for Muziekweb took 0.32515597343444824s
Availability | RDF dump link check for Muziekweb took 0.3265678882598877s
License | MR license check for Muziekweb took 0.32989931106567383s
License | HR license check for Muziekweb took 11.739486455917358s
Amount of data | Number of property check for Muziekweb took 0.311877965927124s
Understandability | Number of label check for Muziekweb took 0.33246493339538574s
Understandability | URI regex check for Muziekweb took 0.6443030834197998s
Understandability | Vocabs check for Muziekweb took 0.3355245590209961s
Verifiability | Authors check for Muziekweb took 0.34557056427001953s
Verifiability | Publishers check for Muziekweb took 0.30011844635009766s
Performance | Throughput check for Muziekweb took 12.46777606010437s
Amount of data | Check the number of entities for Muziekweb took 7.510185241699219e-05s
Verifiability | Contribs. check for Muziekweb took 0.2988283634185791s
Interlinking | sameAs chians check for Muziekweb took 0.3144376277923584s
Interlinking | skos check for Muziekweb took 0.39629173278808594s
Interlinking | skos check for Muziekweb took 0.3198826313018799s
Timeliness | dataset update frequency check for Muziekweb took 0.3088493347167969s
Currency | Creation date check for Muziekweb took 0.8469541072845459s
Currency | Modification date check for Muziekweb took 0.7875967025756836s
Rep.Conc. | URIs length for Muziekweb took 1.922940731048584s
Interoperability | New vocabularies check for Muziekweb took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.28577637672424316s
Accuracy | Check Functional Property for Muziekweb took 0.528334379196167s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.5377776622772217s
Accuracy | Check Empty annotation labels for Muziekweb took 0.8935542106628418s
Accuracy | Check White space in annotation for Muziekweb took 0.028385162353515625s
Accuracy | Check Datatype consistency for Muziekweb took 0.028759241104125977s
Consistency | Disjoint class check for Muziekweb took 0.5646870136260986s
Consistency | Check Misplaced properties for Muziekweb took 1.1651966571807861s
Consistency | Check Ontology hijacking for Muziekweb took 2.2028467655181885s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.226654052734375s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.503171682357788s
Conciseness | Check Extensional conciseness for Muziekweb took 0.033356666564941406s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3435027599334717s
Security | Sign check for Muziekweb took 0.3135542869567871s
Availability | Check URIs Dereferenciability for Muziekweb took 1956.896384716034s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.5348074436187744s
Reputation | Calculation of the PageRank for Muziekweb took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for Muziekweb took 6.461143493652344e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.794929504394531e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.9073486328125e-06s
Believability | Calculation of trust value for Muziekweb took 1.0967254638671875e-05s
INFO | --- Analysis for muziekweb took 2087.630386829376s
Availability | SPARQL endpoint availability check for myExperiment took 130.39722228050232s
Availability | VoID file availability check for myExperiment took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for myExperiment took 0.4331636428833008s
Reputation | Calculation of the PageRank for myExperiment took 0.020899534225463867s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010156631469726562s
Believability | Calculation of trust value for myExperiment took 1.430511474609375e-05s
INFO | --- Analysis for my-experiment took 1181.638912677765s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.07408905029296875s
Availability | VoID file availability check for My Family Lineage took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.34500956535339355s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.797645568847656e-05s
Believability | Calculation of trust value for My Family Lineage took 1.3828277587890625e-05s
INFO | --- Analysis for my-family-lineage took 3.955284833908081s
Availability | SPARQL endpoint availability check for My ontology test took 0.8974037170410156s
Availability | VoID file availability check for My ontology test took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for My ontology test took 0.3003866672515869s
Reputation | Calculation of the PageRank for My ontology test took 0.021140336990356445s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.2901763916015625e-05s
Believability | Calculation of trust value for My ontology test took 1.0013580322265625e-05s
INFO | --- Analysis for myontologytest took 3.836613893508911s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 9.369850158691406e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.3007357120513916s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020849943161010742s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00011277198791503906s
Believability | Calculation of trust value for myopenlink dataspaces took 1.0013580322265625e-05s
INFO | --- Analysis for myopenlink-dataspaces took 4.157065153121948s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 7.549212455749512s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.3410770893096924s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020904064178466797s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.961822509765625e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for n-lex-as-linked-data took 19.58957529067993s
Availability | SPARQL endpoint availability check for NAICS 2007 took 26.235087156295776s
Availability | VoID file availability check for NAICS 2007 took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.31090450286865234s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.02232074737548828s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.0531158447265625e-05s
Believability | Calculation of trust value for NAICS 2007 took 8.344650268554688e-06s
INFO | --- Analysis for naics-2007 took 125.54896378517151s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.926170110702515s
Availability | VoID file availability check for NAICS 2012 took 0.0008640289306640625s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.2859642505645752s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.020812034606933594s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.340576171875e-05s
Believability | Calculation of trust value for NAICS 2012 took 8.344650268554688e-06s
INFO | --- Analysis for naics-2012 took 123.563551902771s
Availability | SPARQL endpoint availability check for Usernames  took 4.220008850097656e-05s
Availability | VoID file availability check for Usernames  took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Usernames  took 0.29694485664367676s
Reputation | Calculation of the PageRank for Usernames  took 0.020955324172973633s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Usernames  took 2.9802322387695312e-05s
Believability | Calculation of trust value for Usernames  took 6.4373016357421875e-06s
INFO | --- Analysis for Names took 2.73066782951355s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.2476015090942383s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0007042884826660156s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 0.9577281475067139s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 3.2735724449157715s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 11.802016258239746s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 13.843024730682373s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.8401908874511719s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.433563232421875s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.32288098335266113s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.8411822319030762s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.36424803733825684s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.34964537620544434s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.3928563594818115s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.81256651878357s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.8635315895080566s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.52577543258667s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.6916189193725586s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.7870204448699951s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.8800864219665527s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.3477654457092285s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 12.011724472045898s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.58306884765625e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.38420915603637695s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.4912455081939697s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.580474615097046s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.0347938537597656s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.36428260803222656s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.6034398078918457s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7457377910614014s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 0.7546329498291016s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.38070130348205566s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.34058332443237305s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.35077381134033203s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.39357495307922363s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007331371307373047s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0011339187622070312s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.7757234573364258s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7521405220031738s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.8203232288360596s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.6868793964385986s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.2925832271575928s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.6696202754974365s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006802082061767578s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.37907886505126953s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 5.506550550460815s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.41879940032958984s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.020932435989379883s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.270408630371094e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 8.344650268554688e-06s
INFO | --- Analysis for national-diet-library-authorities took 236.2527470588684s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.3801610469818115s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0005750656127929688s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.42576003074646s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 2.9761106967926025s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.790003538131714s
Interoperability | New terms check for National Diet Library of Japan subject headings took 15.78929352760315s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.35871148109436035s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.340607404708862s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.7990086078643799s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.837655782699585s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.3475363254547119s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.39574480056762695s
License | MR license check for National Diet Library of Japan subject headings took 0.3767130374908447s
License | HR license check for National Diet Library of Japan subject headings took 91.35608768463135s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.4296450614929199s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.243927001953125s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7123494148254395s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.8158442974090576s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.35112833976745605s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.368274450302124s
Performance | Throughput check for National Diet Library of Japan subject headings took 12.680510520935059s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.678436279296875e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.3870980739593506s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.47594261169433594s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.2435204982757568s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.0449635982513428s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.3864612579345703s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.1291694641113281s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7983989715576172s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.7648608684539795s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.3987300395965576s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.37396669387817383s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.3600592613220215s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.3762240409851074s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0006029605865478516s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0004754066467285156s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.39905643463134766s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.6960623264312744s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3438284397125244s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.660489797592163s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.2957818508148193s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.6677935123443604s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006914138793945312s
Security | Sign check for National Diet Library of Japan subject headings took 0.3702399730682373s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 4.354323625564575s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.4047243595123291s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 1.0728836059570312e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 230.3388545513153s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.141714334487915s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.3367197513580322s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.02246999740600586s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.506111145019531e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 1.3589859008789062e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 5.717014789581299s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.410743713378906e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.3013184070587158s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02326369285583496s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.152557373046875e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2159347534179688e-05s
INFO | --- Analysis for Naturopathy took 3.763294219970703s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.401658773422241s
Availability | VoID file availability check for COVID-19 Data took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.31415390968322754s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.02178192138671875s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.361701965332031e-05s
Believability | Calculation of trust value for COVID-19 Data took 1.2159347534179688e-05s
INFO | --- Analysis for NCMI-COVID-19 took 7.490298748016357s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.415065050125122s
Availability | VoID file availability check for NCMI-COVID-19 took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.29946327209472656s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.022579431533813477s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.239776611328125e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 1.049041748046875e-05s
INFO | --- Analysis for NCMICOVID-19 took 6.518820524215698s
Availability | SPARQL endpoint availability check for Near took 9.012222290039062e-05s
Availability | VoID file availability check for Near took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Near took 0.4002060890197754s
Reputation | Calculation of the PageRank for Near took 0.022341251373291016s
Interlinking | Calculation of Degree of Connection for Near took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Near took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Near took 8.96453857421875e-05s
Believability | Calculation of trust value for Near took 1.2874603271484375e-05s
INFO | --- Analysis for near took 8.119226455688477s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 0.00011515617370605469s
Availability | VoID file availability check for NeuroLex Wiki took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.29604125022888184s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.0994415283203125e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.0967254638671875e-05s
INFO | --- Analysis for neurolex-wiki took 2.724484443664551s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 8.630752563476562e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.28956031799316406s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.021324634552001953s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.363059997558594e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.0728836059570312e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 4.314814329147339s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 0.00010323524475097656s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.29971790313720703s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.937980651855469e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 6.198883056640625e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.426131248474121s
Availability | SPARQL endpoint availability check for neXtProt took 1.7139256000518799s
Availability | VoID file availability check for neXtProt took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for neXtProt took 0.3251817226409912s
Reputation | Calculation of the PageRank for neXtProt took 0.022286176681518555s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.6716461181640625e-05s
Believability | Calculation of trust value for neXtProt took 1.1682510375976562e-05s
INFO | --- Analysis for nextprot took 5.18230676651001s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 8.7738037109375e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2760157585144043s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010466575622558594s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.0251998901367188e-05s
INFO | --- Analysis for nextweb-gnoss took 8.718533515930176s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.267692565917969e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.30584049224853516s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.0207827091217041s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.368492126464844e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 8.821487426757812e-06s
INFO | --- Analysis for nhs-jargon took 3.0475802421569824s
Availability | SPARQL endpoint availability check for NIT Patna took 8.797645568847656e-05s
Availability | VoID file availability check for NIT Patna took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.29854464530944824s
Reputation | Calculation of the PageRank for NIT Patna took 0.02078533172607422s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.747245788574219e-05s
Believability | Calculation of trust value for NIT Patna took 1.0251998901367188e-05s
INFO | --- Analysis for NITP took 3.661858558654785s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 8.487701416015625e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2998621463775635s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02198624610900879s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for nlr-dataset-mod took 4.2918806076049805s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.6582052707672119s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.30800342559814453s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0010073184967041016s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 4.76837158203125e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.4066696166992188e-05s
INFO | --- Analysis for NLW took 4.48378324508667s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.352607488632202s
Availability | VoID file availability check for Nobel Prizes took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.30843138694763184s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02156209945678711s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.369850158691406e-05s
Believability | Calculation of trust value for Nobel Prizes took 9.5367431640625e-06s
INFO | --- Analysis for nobelprizes took 9.15245532989502s
Availability | SPARQL endpoint availability check for NoiPA took 0.26936960220336914s
Availability | VoID file availability check for NoiPA took 0.000507354736328125s
Extra | Recovery of all triples for NoiPA took 0.9845371246337891s
Performance | Total latancy measurement for NoiPA took 0.7170748710632324s
Amount of data | Number of triples check for NoiPA took 1.3109328746795654s
Interoperability | New terms check for NoiPA took 2.720193862915039s
Versatility | Languages check for NoiPA took 60.168036222457886s
Interpretability | Number of blank nodes check for NoiPA took 0.3515017032623291s
Interpretability | RDF structures check for NoiPA took 0.23359084129333496s
Versatility | Serialization formats check for NoiPA took 0.2732536792755127s
Availability | RDF dump link check for NoiPA took 0.22965168952941895s
License | MR license check for NoiPA took 0.25989723205566406s
License | HR license check for NoiPA took 60.240727186203s
Amount of data | Number of property check for NoiPA took 0.2937326431274414s
Understandability | Number of label check for NoiPA took 0.612379789352417s
Understandability | URI regex check for NoiPA took 0.33159780502319336s
Understandability | Vocabs check for NoiPA took 0.22175860404968262s
Verifiability | Authors check for NoiPA took 0.14175796508789062s
Verifiability | Publishers check for NoiPA took 0.1293041706085205s
Performance | Throughput check for NoiPA took 10.57871699333191s
Amount of data | Check the number of entities for NoiPA took 6.890296936035156e-05s
Verifiability | Contribs. check for NoiPA took 0.1357567310333252s
Interlinking | sameAs chians check for NoiPA took 0.1831660270690918s
Interlinking | skos check for NoiPA took 0.13709640502929688s
Interlinking | skos check for NoiPA took 0.15583586692810059s
Timeliness | dataset update frequency check for NoiPA took 0.1367952823638916s
Currency | Creation date check for NoiPA took 0.3369898796081543s
Currency | Modification date check for NoiPA took 0.12920641899108887s
Rep.Conc. | URIs length for NoiPA took 17.751311540603638s
Interoperability | New vocabularies check for NoiPA took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.286452054977417s
Accuracy | Check Functional Property for NoiPA took 0.16223931312561035s
Accuracy | Check Inverse Functional Property for NoiPA took 0.1683049201965332s
Accuracy | Check Empty annotation labels for NoiPA took 0.4495518207550049s
Accuracy | Check White space in annotation for NoiPA took 0.026148319244384766s
Accuracy | Check Datatype consistency for NoiPA took 0.029122114181518555s
Consistency | Disjoint class check for NoiPA took 0.14226007461547852s
Consistency | Check Misplaced properties for NoiPA took 16.028393983840942s
Consistency | Misplaced classes for NoiPA took 0.2397935390472412s
Consistency | Check Ontology hijacking for NoiPA took 1.806793212890625s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.281902551651001s
Consistency | Check Invalid usage of undefined properties for NoiPA took 17.473766565322876s
Conciseness | Check Extensional conciseness for NoiPA took 0.036386966705322266s
Conciseness | Check Intensional conciseness for NoiPA took 0.15419483184814453s
Security | Sign check for NoiPA took 0.13848543167114258s
Availability | Check URIs Dereferenciability for NoiPA took 10.343177556991577s
Completeness | Calculation of interlinking completeness for NoiPA took 0.42651891708374023s
Reputation | Calculation of the PageRank for NoiPA took 0.021764278411865234s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.430511474609375e-06s
Believability | Calculation of trust value for NoiPA took 1.2874603271484375e-05s
INFO | --- Analysis for NoiPA took 512.0785248279572s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 1.0153300762176514s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.2761197090148926s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020343780517578125s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 8.821487426757812e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.049041748046875e-05s
INFO | --- Analysis for nom took 9.336421012878418s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 26.31685972213745s
Availability | VoID file availability check for Nomenclator Asturias took 0.0009279251098632812s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.3241250514984131s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.021184921264648438s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.678436279296875e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 2.47955322265625e-05s
INFO | --- Analysis for nomenclator-asturias took 140.13058590888977s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.5288822650909424s
Availability | VoID file availability check for Nomisma.org  took 0.0005335807800292969s
Extra | Recovery of all triples for Nomisma.org  took 300.083270072937s
Performance | Total latancy measurement for Nomisma.org  took 2.161836862564087s
Amount of data | Number of triples check for Nomisma.org  took 37.82556653022766s
Interoperability | New terms check for Nomisma.org  took 7.054667711257935s
Versatility | Languages check for Nomisma.org  took 90.23200798034668s
Interpretability | Number of blank nodes check for Nomisma.org  took 28.547427892684937s
Security | Check HTTPS for Nomisma.org  took 1.1690235137939453s
Interpretability | RDF structures check for Nomisma.org  took 0.436173677444458s
Versatility | Serialization formats check for Nomisma.org  took 0.6586792469024658s
Availability | RDF dump link check for Nomisma.org  took 916.4429996013641s
License | MR license check for Nomisma.org  took 0.46582961082458496s
License | HR license check for Nomisma.org  took 88.34940886497498s
Amount of data | Number of property check for Nomisma.org  took 0.43433070182800293s
Understandability | Number of label check for Nomisma.org  took 6.940316915512085s
Understandability | URI regex check for Nomisma.org  took 0.8796181678771973s
Understandability | Vocabs check for Nomisma.org  took 0.3750877380371094s
Verifiability | Authors check for Nomisma.org  took 0.3838014602661133s
Verifiability | Publishers check for Nomisma.org  took 0.4435558319091797s
Performance | Throughput check for Nomisma.org  took 11.983986854553223s
Amount of data | Check the number of entities for Nomisma.org  took 0.0005238056182861328s
Verifiability | Contribs. check for Nomisma.org  took 0.47762131690979004s
Interlinking | sameAs chians check for Nomisma.org  took 0.4091150760650635s
Interlinking | skos check for Nomisma.org  took 1.3745405673980713s
Interlinking | skos check for Nomisma.org  took 0.6260685920715332s
Timeliness | dataset update frequency check for Nomisma.org  took 0.40797853469848633s
Currency | Creation date check for Nomisma.org  took 0.8318271636962891s
Currency | Modification date check for Nomisma.org  took 0.8399982452392578s
Rep.Conc. | URIs length for Nomisma.org  took 633.5200073719025s
Interoperability | New vocabularies check for Nomisma.org  took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.42728590965270996s
Accuracy | Check Functional Property for Nomisma.org  took 0.4161841869354248s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3940596580505371s
Accuracy | Check Empty annotation labels for Nomisma.org  took 475.95321393013s
Accuracy | Check White space in annotation for Nomisma.org  took 2.751495122909546s
Consistency | Disjoint class check for Nomisma.org  took 0.46428799629211426s
Consistency | Check Misplaced properties for Nomisma.org  took 26.767797470092773s
Consistency | Check Ontology hijacking for Nomisma.org  took 511.4332890510559s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 28.68497610092163s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.00017023086547851562s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.4615657329559326s
Security | Sign check for Nomisma.org  took 0.40802454948425293s
Availability | Check URIs Dereferenciability for Nomisma.org  took 2042.5270006656647s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 2.451277256011963s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.021209239959716797s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.9073486328125e-06s
Believability | Calculation of trust value for Nomisma.org  took 1.0013580322265625e-05s
INFO | --- Analysis for nomisma_org took 8504.272768974304s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.39304447174072266s
Availability | VoID file availability check for Curriculum Vitae took 0.00027298927307128906s
Extra | Recovery of all triples for Curriculum Vitae took 0.7605102062225342s
Performance | Total latancy measurement for Curriculum Vitae took 0.9715244770050049s
Amount of data | Number of triples check for Curriculum Vitae took 0.22662758827209473s
Interoperability | New terms check for Curriculum Vitae took 1.5399398803710938s
Versatility | Languages check for Curriculum Vitae took 0.2407829761505127s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.14804339408874512s
Interpretability | RDF structures check for Curriculum Vitae took 0.18460369110107422s
Versatility | Serialization formats check for Curriculum Vitae took 0.23168635368347168s
Availability | RDF dump link check for Curriculum Vitae took 0.1575930118560791s
License | MR license check for Curriculum Vitae took 0.1962728500366211s
License | HR license check for Curriculum Vitae took 0.1285390853881836s
Amount of data | Number of property check for Curriculum Vitae took 0.2280263900756836s
Understandability | Number of label check for Curriculum Vitae took 0.22050046920776367s
Understandability | URI regex check for Curriculum Vitae took 0.29610300064086914s
Understandability | Vocabs check for Curriculum Vitae took 0.13142776489257812s
Verifiability | Authors check for Curriculum Vitae took 0.24553155899047852s
Verifiability | Publishers check for Curriculum Vitae took 0.1598219871520996s
Performance | Throughput check for Curriculum Vitae took 11.110716104507446s
Amount of data | Check the number of entities for Curriculum Vitae took 6.937980651855469e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.12684392929077148s
Interlinking | sameAs chians check for Curriculum Vitae took 0.1277022361755371s
Interlinking | skos check for Curriculum Vitae took 0.13454031944274902s
Interlinking | skos check for Curriculum Vitae took 0.17395496368408203s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.13298249244689941s
Currency | Creation date check for Curriculum Vitae took 0.3859996795654297s
Currency | Modification date check for Curriculum Vitae took 0.2809598445892334s
Rep.Conc. | URIs length for Curriculum Vitae took 0.36681437492370605s
Interoperability | New vocabularies check for Curriculum Vitae took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.1791834831237793s
Accuracy | Check Functional Property for Curriculum Vitae took 0.15073156356811523s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.1448075771331787s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.16277694702148438s
Accuracy | Check White space in annotation for Curriculum Vitae took 9.179115295410156e-05s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.004923343658447266s
Consistency | Disjoint class check for Curriculum Vitae took 0.12375235557556152s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.3140981197357178s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.3599307537078857s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.2384235858917236s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.3912158012390137s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0015411376953125s
Security | Sign check for Curriculum Vitae took 0.13245439529418945s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 19.90708565711975s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.28961730003356934s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 2.9802322387695312e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.1920928955078125e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.0013580322265625e-05s
INFO | --- Analysis for Nordine_Bittich took 59.21004939079285s
Availability | SPARQL endpoint availability check for NorPark took 0.2644178867340088s
Availability | VoID file availability check for NorPark took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for NorPark took 0.3037374019622803s
Reputation | Calculation of the PageRank for NorPark took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for NorPark took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.267692565917969e-05s
Believability | Calculation of trust value for NorPark took 1.1682510375976562e-05s
INFO | --- Analysis for norpark took 3.148571729660034s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.025773048400878906s
Availability | VoID file availability check for Parking Dataset took 0.00042724609375s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.29333066940307617s
Reputation | Calculation of the PageRank for Parking Dataset took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.363059997558594e-05s
Believability | Calculation of trust value for Parking Dataset took 1.049041748046875e-05s
INFO | --- Analysis for norpark2 took 2.81253719329834s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.6975307464599609s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0005121231079101562s
Extra | Recovery of all triples for Norway fishery stocks dataset took 113.59411191940308s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.9834964275360107s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.073263168334961s
Interoperability | New terms check for Norway fishery stocks dataset took 14.058494567871094s
Versatility | Languages check for Norway fishery stocks dataset took 300.2491455078125s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 2.1446402072906494s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.20948266983032227s
Versatility | Serialization formats check for Norway fishery stocks dataset took 8.680520057678223s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.3187258243560791s
License | MR license check for Norway fishery stocks dataset took 0.8058769702911377s
License | HR license check for Norway fishery stocks dataset took 300.15960931777954s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.19440412521362305s
Understandability | Number of label check for Norway fishery stocks dataset took 3.1058709621429443s
Understandability | URI regex check for Norway fishery stocks dataset took 1.2436606884002686s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.6600627899169922s
Verifiability | Authors check for Norway fishery stocks dataset took 0.18985819816589355s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.2546415328979492s
Performance | Throughput check for Norway fishery stocks dataset took 11.557471513748169s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 7.295608520507812e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.2018110752105713s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.1988520622253418s
Interlinking | skos check for Norway fishery stocks dataset took 0.4210178852081299s
Interlinking | skos check for Norway fishery stocks dataset took 0.3981633186340332s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 5.550752639770508s
Currency | Creation date check for Norway fishery stocks dataset took 0.46984291076660156s
Currency | Modification date check for Norway fishery stocks dataset took 0.2274036407470703s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 147.8218162059784s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.18545079231262207s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.5026650428771973s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.46370720863342285s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 40.117401123046875s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.678487539291382s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.619511365890503s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.21416544914245605s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 85.76870441436768s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.375630855560303s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 32.7280216217041s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.388171672821045s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 86.54910135269165s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.8087215423583984s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5597479343414307s
Security | Sign check for Norway fishery stocks dataset took 1.6091246604919434s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 10.342698335647583s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.41684961318969727s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.021152734756469727s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 4.00543212890625e-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.0728836059570312e-05s
INFO | --- Analysis for Norway_Fishery_ took 2300.4534056186676s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.686779260635376s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.2776501178741455s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.9114227294921875e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.3589859008789062e-05s
INFO | --- Analysis for norwegian-geo-divisions took 4.7780256271362305s
Availability | SPARQL endpoint availability check for NITP took 8.893013000488281e-05s
Availability | VoID file availability check for NITP took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for NITP took 0.30951714515686035s
Reputation | Calculation of the PageRank for NITP took 0.020823001861572266s
Interlinking | Calculation of Degree of Connection for NITP took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for NITP took 6.890296936035156e-05s
Believability | Calculation of trust value for NITP took 1.0013580322265625e-05s
INFO | --- Analysis for notIdentifier took 3.457322835922241s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 9.274482727050781e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.2831854820251465s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02232217788696289s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.7670135498046875e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 9.5367431640625e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.994495153427124s
Availability | SPARQL endpoint availability check for NPM took 8.893013000488281e-05s
Availability | VoID file availability check for NPM took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for NPM took 0.3096179962158203s
Reputation | Calculation of the PageRank for NPM took 0.02178478240966797s
Interlinking | Calculation of Degree of Connection for NPM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for NPM took 3.600120544433594e-05s
Believability | Calculation of trust value for NPM took 9.775161743164062e-06s
INFO | --- Analysis for npm took 3.66377854347229s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.057090044021606445s
Availability | VoID file availability check for NTNU special collections took 0.00040221214294433594s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.3004124164581299s
Reputation | Calculation of the PageRank for NTNU special collections took 0.02080368995666504s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.602836608886719e-05s
Believability | Calculation of trust value for NTNU special collections took 1.0251998901367188e-05s
INFO | --- Analysis for ntnusc took 5.415501356124878s
Availability | SPARQL endpoint availability check for links took 4.172325134277344e-05s
Availability | VoID file availability check for links took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for links took 0.2878153324127197s
Reputation | Calculation of the PageRank for links took 0.021026611328125s
Interlinking | Calculation of Degree of Connection for links took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for links took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for links took 1.2159347534179688e-05s
Believability | Calculation of trust value for links took 1.2636184692382812e-05s
INFO | --- Analysis for nugmyanmar took 2.759854555130005s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 9.036064147949219e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.25966882705688477s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00010323524475097656s
Believability | Calculation of trust value for NUTS (GeoVocab) took 9.298324584960938e-06s
INFO | --- Analysis for nuts-geovocab took 2.7725119590759277s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.423748254776001s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.34148120880126953s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.937980651855469e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.33514404296875e-05s
INFO | --- Analysis for nvd took 4.454048156738281s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.7886991500854492s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.30092573165893555s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.022675037384033203s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.225440979003906e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.33514404296875e-05s
INFO | --- Analysis for nvs took 8.819230318069458s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.3392181396484375e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.2992823123931885s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.021534204483032227s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018715858459472656s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for nytimes-linked-open-data took 2.7338063716888428s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 5.599691867828369s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006172657012939453s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.3872840404510498s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.7542328834533691s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 4.252125978469849s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.7111566066741943s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 58.23008918762207s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 3.767385482788086s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.29489755630493164s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.4475436210632324s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.508028507232666s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.4799232482910156s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.572124719619751s
License | HR license check for Italian Chamber of Deputies - official dataset took 58.23742437362671s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.32035017013549805s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.851529598236084s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.7031793594360352s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.47118568420410156s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.5213737487792969s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.3891618251800537s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 11.009571075439453s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 7.200241088867188e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.36746692657470703s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.382051944732666s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.349287748336792s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.35686397552490234s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.4512784481048584s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.8575012683868408s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.34974074363708496s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 16.622496128082275s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.33831071853637695s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.3827681541442871s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.3831057548522949s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.8072068691253662s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.030881881713867188s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.0281524658203125s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.35406994819641113s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.574846506118774s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.4703640937805176s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 1.932016372680664s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.2369859218597412s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.503499031066895s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.033045053482055664s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.3856074810028076s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.3296816349029541s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 9.800427913665771s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.409761905670166s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.02087545394897461s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0009744167327880859s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00011587142944335938s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.430511474609375e-05s
INFO | --- Analysis for ocd took 402.4377987384796s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 0.00010991096496582031s
Availability | VoID file availability check for oceandrilling-borehole took 0.0007834434509277344s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.30339527130126953s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020297765731811523s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 4.00543212890625e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.2874603271484375e-05s
INFO | --- Analysis for oceandrilling-borehole took 3.819319009780884s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 3.1916110515594482s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0008950233459472656s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.28799867630004883s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.021580934524536133s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.869171142578125e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.52587890625e-05s
INFO | --- Analysis for oceandrilling-codices took 9.902928113937378s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 3.278024196624756s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.28398799896240234s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.022568941116333008s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.7670135498046875e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.3113021850585938e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 7.9478607177734375s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 2.7856826782226562s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.2990453243255615s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.021279335021972656s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.552436828613281e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.0967254638671875e-05s
INFO | --- Analysis for oceandrilling-forams took 7.997138023376465s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 2.739945888519287s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0008218288421630859s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.29086995124816895s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.5762786865234375e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-janus took 7.699861526489258s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 12.89858102798462s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.2829148769378662s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.7670135498046875e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.0013580322265625e-05s
INFO | --- Analysis for oceandrilling-janusamp took 18.40528392791748s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.8014721870422363s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0008306503295898438s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.3126492500305176s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.361701965332031e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.3589859008789062e-05s
INFO | --- Analysis for oceandrilling-ldeo took 7.769183158874512s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 8.797645568847656e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.3332784175872803s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02120184898376465s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.602836608886719e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.0728836059570312e-05s
INFO | --- Analysis for oclc-fast took 9.245573043823242s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.2821648120880127s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020920276641845703s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.218650817871094e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.775161743164062e-06s
INFO | --- Analysis for odc-imd-environment-score took 4.997692346572876s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.2147674560546875s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0005338191986083984s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 1.139249563217163s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 0.8206627368927002s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.13395237922668457s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.512495756149292s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.46054601669311523s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 30.18993067741394s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.16307306289672852s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.2497398853302002s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.9700362682342529s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 62.71073246002197s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.19829392433166504s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.232519388198853s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.15811371803283691s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.20666122436523438s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.42101597785949707s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.14362311363220215s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.20572876930236816s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.15024995803833008s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 11.549325942993164s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 7.224082946777344e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.1308608055114746s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.18747949600219727s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.13489317893981934s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.1477489471435547s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.2170097827911377s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.36548542976379395s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.15439343452453613s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.3795433044433594s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.2077174186706543s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.2277235984802246s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.15145587921142578s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.21395421028137207s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.9238076210021973s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 1.060274600982666s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.5063610076904297s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.00015783309936523438s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.2860584259033203s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.21446847915649414s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.3674020767211914s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 4.2438507080078125e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.7220458984375e-06s
INFO | --- Analysis for odc-lsoa took 279.71231055259705s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.10932135581970215s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.3058602809906006s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.02094101905822754s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.322166442871094e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for oecd-linked-data took 2.822052240371704s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.331955194473267s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0008111000061035156s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.30619335174560547s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.021367311477661133s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.57763671875e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.2874603271484375e-05s
INFO | --- Analysis for ogolod took 103.23555755615234s
Availability | SPARQL endpoint availability check for OLAC Metadata took 9.036064147949219e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.31163549423217773s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.0208437442779541s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0008246898651123047s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.410743713378906e-05s
Believability | Calculation of trust value for OLAC Metadata took 8.58306884765625e-06s
INFO | --- Analysis for olac took 22.91959834098816s
Availability | SPARQL endpoint availability check for OLiA took 4.291534423828125e-05s
Availability | VoID file availability check for OLiA took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for OLiA took 0.2938666343688965s
Reputation | Calculation of the PageRank for OLiA took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for OLiA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00011968612670898438s
Believability | Calculation of trust value for OLiA took 8.106231689453125e-06s
INFO | --- Analysis for olia took 12.50848126411438s
Availability | SPARQL endpoint availability check for OLiA Discourse took 5.125999450683594e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.34299445152282715s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0008733272552490234s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.673004150390625e-05s
Believability | Calculation of trust value for OLiA Discourse took 8.58306884765625e-06s
INFO | --- Analysis for olia-discourse took 7.556410551071167s
Availability | SPARQL endpoint availability check for Open Land Use took 0.17904019355773926s
Availability | VoID file availability check for Open Land Use took 0.00027632713317871094s
Extra | Recovery of all triples for Open Land Use took 111.84383487701416s
Performance | Total latancy measurement for Open Land Use took 0.9680228233337402s
Amount of data | Number of triples check for Open Land Use took 8.910128116607666s
Interoperability | New terms check for Open Land Use took 14.205520391464233s
Versatility | Languages check for Open Land Use took 300.24854135513306s
Interpretability | Number of blank nodes check for Open Land Use took 1.8056442737579346s
Interpretability | RDF structures check for Open Land Use took 0.18349838256835938s
Versatility | Serialization formats check for Open Land Use took 14.690406560897827s
Availability | RDF dump link check for Open Land Use took 0.39374518394470215s
License | MR license check for Open Land Use took 0.7993810176849365s
License | HR license check for Open Land Use took 300.17227053642273s
Amount of data | Number of property check for Open Land Use took 0.1919412612915039s
Understandability | Number of label check for Open Land Use took 1.1861116886138916s
Understandability | URI regex check for Open Land Use took 1.33632493019104s
Understandability | Vocabs check for Open Land Use took 0.21030068397521973s
Verifiability | Authors check for Open Land Use took 0.18224167823791504s
Verifiability | Publishers check for Open Land Use took 0.24076557159423828s
Performance | Throughput check for Open Land Use took 11.220081090927124s
Amount of data | Check the number of entities for Open Land Use took 7.200241088867188e-05s
Verifiability | Contribs. check for Open Land Use took 0.19593143463134766s
Interlinking | sameAs chians check for Open Land Use took 0.19799041748046875s
Interlinking | skos check for Open Land Use took 0.42828893661499023s
Interlinking | skos check for Open Land Use took 0.44864416122436523s
Timeliness | dataset update frequency check for Open Land Use took 5.74608850479126s
Currency | Creation date check for Open Land Use took 0.4937858581542969s
Currency | Modification date check for Open Land Use took 0.25482940673828125s
Rep.Conc. | URIs length for Open Land Use took 145.79434537887573s
Interoperability | New vocabularies check for Open Land Use took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.21005463600158691s
Accuracy | Check Functional Property for Open Land Use took 0.5229012966156006s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.507117748260498s
Accuracy | Check Empty annotation labels for Open Land Use took 40.04271149635315s
Accuracy | Check White space in annotation for Open Land Use took 2.712520122528076s
Accuracy | Check Datatype consistency for Open Land Use took 2.6581215858459473s
Consistency | Disjoint class check for Open Land Use took 0.21432256698608398s
Consistency | Check Misplaced properties for Open Land Use took 86.10958433151245s
Consistency | Misplaced classes for Open Land Use took 8.309310913085938s
Consistency | Check Ontology hijacking for Open Land Use took 29.595515251159668s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.3304862976074219s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 86.50341558456421s
Conciseness | Check Extensional conciseness for Open Land Use took 2.8196609020233154s
Conciseness | Check Intensional conciseness for Open Land Use took 0.4923226833343506s
Security | Sign check for Open Land Use took 0.1946699619293213s
Availability | Check URIs Dereferenciability for Open Land Use took 9.28598690032959s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.8666682243347168s
Reputation | Calculation of the PageRank for Open Land Use took 0.021555662155151367s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.38690185546875e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Land Use took 8.58306884765625e-06s
INFO | --- Analysis for OLU took 2256.109968185425s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.9911563396453857s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.327531099319458s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020704984664916992s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-als took 4.208488464355469s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2777888774871826s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.269603967666626s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-arb took 3.3292343616485596s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.25653934478759766s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.3094303607940674s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020277976989746094s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-bul took 3.43274188041687s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2689487934112549s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2754049301147461s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-cow took 3.3448071479797363s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2541234493255615s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2852802276611328s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-cwn took 3.360477924346924s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.3003072738647461s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.3163595199584961s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.022498607635498047s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-dan took 3.4483609199523926s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.23597359657287598s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2846970558166504s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.022333621978759766s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-ell took 3.30470609664917s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.25252294540405273s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2851855754852295s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-eng took 3.420046806335449s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.2661013603210449s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.00021576881408691406s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.2869691848754883s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.021098852157592773s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 5.245208740234375e-06s
INFO | --- Analysis for omwn-fas took 3.353879451751709s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.28948187828063965s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.28425073623657227s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.02205657958984375s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-fin took 3.4416468143463135s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.26242828369140625s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.28363966941833496s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020895719528198242s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-fra took 3.358264923095703s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.25461363792419434s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.29840588569641113s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.021115779876708984s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-heb took 3.3401031494140625s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2547311782836914s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.31685709953308105s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.02176213264465332s
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.0007357597351074219s
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.3113021850585938e-05s
INFO | --- Analysis for omwn-hrv took 3.46954607963562s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2522566318511963s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.00042724609375s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.29272961616516113s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.02164292335510254s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 6.580352783203125e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-isl took 3.3284757137298584s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2598896026611328s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.31052398681640625s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.021858930587768555s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-ita took 3.370392322540283s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2703514099121094s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.30948829650878906s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.02085566520690918s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-iwn took 3.392162322998047s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.24287199974060059s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2991209030151367s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-jpn took 3.265394687652588s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.301969051361084s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.29595518112182617s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-mcr took 3.3669724464416504s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2698800563812256s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.30841732025146484s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.022485733032226562s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-msa took 3.31607723236084s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.281113862991333s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.30506348609924316s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.02197718620300293s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
INFO | --- Analysis for omwn-nld took 3.349724292755127s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.24660229682922363s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.27881860733032227s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.02230691909790039s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
INFO | --- Analysis for omwn-nor took 3.2373058795928955s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2375965118408203s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2771735191345215s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.021254539489746094s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-pol took 3.2749102115631104s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2581808567047119s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2791171073913574s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.020669937133789062s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
INFO | --- Analysis for omwn-por took 3.3775336742401123s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.24648332595825195s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.3209247589111328s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-ron took 3.4274349212646484s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.25167036056518555s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2931239604949951s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
INFO | --- Analysis for omwn-slk took 3.3201513290405273s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.270615816116333s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.308337926864624s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-slv took 3.3331358432769775s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.30504918098449707s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.31616902351379395s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.022989511489868164s
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.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 4.3392181396484375e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-swe took 3.3844802379608154s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.2845580577850342s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2794647216796875s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 4.1961669921875e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
INFO | --- Analysis for omwn-tha took 3.3286397457122803s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.266692161560059s
Availability | VoID file availability check for OntoBeef Domain took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.3353753089904785s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.5299530029296875e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.0251998901367188e-05s
INFO | --- Analysis for ontobeef-domain took 27.492609977722168s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.291534423828125e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.285675048828125s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.179115295410156e-05s
Believability | Calculation of trust value for Ontos News Portal took 9.059906005859375e-06s
INFO | --- Analysis for ontos-news-portal took 6.482428550720215s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 8.630752563476562e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.29830241203308105s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020926713943481445s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.123283386230469e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 1.1205673217773438e-05s
INFO | --- Analysis for ookaboo-rdf-dump took 2.8713903427124023s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 9.012222290039062e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.2843506336212158s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.0207669734954834s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.910064697265625e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 1.1444091796875e-05s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 9.145256042480469s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 0.00012159347534179688s
Availability | VoID file availability check for Open Data Euskadi took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.31903648376464844s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.839897155761719e-05s
Believability | Calculation of trust value for Open Data Euskadi took 4.0531158447265625e-06s
INFO | --- Analysis for open-data-euskadi took 8.164536952972412s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 8.58306884765625e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.28680944442749023s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.0215914249420166s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010418891906738281s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 9.5367431640625e-06s
INFO | --- Analysis for open-data-risp took 6.8699867725372314s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.19408679008483887s
Availability | VoID file availability check for Open Data Thesaurus took 0.0005655288696289062s
Extra | Recovery of all triples for Open Data Thesaurus took 1.1187527179718018s
Performance | Total latancy measurement for Open Data Thesaurus took 0.47213053703308105s
Amount of data | Number of triples check for Open Data Thesaurus took 0.12308430671691895s
Interoperability | New terms check for Open Data Thesaurus took 1.384446620941162s
Versatility | Languages check for Open Data Thesaurus took 0.11849355697631836s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.12420654296875s
Security | Check HTTPS for Open Data Thesaurus took 0.30621814727783203s
Interpretability | RDF structures check for Open Data Thesaurus took 0.11586904525756836s
Versatility | Serialization formats check for Open Data Thesaurus took 0.11507749557495117s
Availability | RDF dump link check for Open Data Thesaurus took 1.0640881061553955s
License | MR license check for Open Data Thesaurus took 0.11830377578735352s
License | HR license check for Open Data Thesaurus took 0.0823214054107666s
Amount of data | Number of property check for Open Data Thesaurus took 0.11776566505432129s
Understandability | Number of label check for Open Data Thesaurus took 0.1098935604095459s
Understandability | URI regex check for Open Data Thesaurus took 0.17425060272216797s
Understandability | Vocabs check for Open Data Thesaurus took 0.11485123634338379s
Verifiability | Authors check for Open Data Thesaurus took 0.1235802173614502s
Verifiability | Publishers check for Open Data Thesaurus took 0.11095547676086426s
Performance | Throughput check for Open Data Thesaurus took 10.400350332260132s
Amount of data | Check the number of entities for Open Data Thesaurus took 7.62939453125e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.11605334281921387s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.11531472206115723s
Interlinking | skos check for Open Data Thesaurus took 0.10732054710388184s
Interlinking | skos check for Open Data Thesaurus took 0.09416079521179199s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.0871894359588623s
Currency | Creation date check for Open Data Thesaurus took 0.17285776138305664s
Currency | Modification date check for Open Data Thesaurus took 0.19126486778259277s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.44777369499206543s
Interoperability | New vocabularies check for Open Data Thesaurus took 2.193594217300415s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.11553812026977539s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.09610342979431152s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.09582638740539551s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.17430758476257324s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011258125305175781s
Consistency | Disjoint class check for Open Data Thesaurus took 0.08699798583984375s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.18368244171142578s
Consistency | Misplaced classes for Open Data Thesaurus took 0.08244800567626953s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.4045600891113281s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.3740851879119873s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00017189979553222656s
Security | Sign check for Open Data Thesaurus took 0.09577202796936035s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.3082406520843506s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020008325576782227s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.106231689453125e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 1.940448522567749s
Believability | Calculation of trust value for Open Data Thesaurus took 1.430511474609375e-05s
INFO | --- Analysis for open-data-thesaurus took 75.15918397903442s
Availability | SPARQL endpoint availability check for Open Election Data Project took 8.988380432128906e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.3200409412384033s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020373106002807617s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.580352783203125e-05s
Believability | Calculation of trust value for Open Election Data Project took 9.298324584960938e-06s
INFO | --- Analysis for open-election-data-project took 42.78032827377319s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.9043030738830566s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0008256435394287109s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.30053162574768066s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.678436279296875e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 9.059906005859375e-06s
INFO | --- Analysis for open-energy-info-wiki took 17.092300415039062s
Availability | SPARQL endpoint availability check for Open Library took 0.00016832351684570312s
Availability | VoID file availability check for Open Library took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for Open Library took 0.3855316638946533s
Reputation | Calculation of the PageRank for Open Library took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for Open Library took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0010077953338623047s
Interlinking | Calculation of Clustering coefficient for Open Library took 8.440017700195312e-05s
Believability | Calculation of trust value for Open Library took 1.3113021850585938e-05s
INFO | --- Analysis for open-library took 10.171635389328003s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.1833329200744629s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0005331039428710938s
Extra | Recovery of all triples for Open Land Use @PSNC took 100.70589447021484s
Performance | Total latancy measurement for Open Land Use @PSNC took 1.0670716762542725s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.218294382095337s
Interoperability | New terms check for Open Land Use @PSNC took 14.218379974365234s
Versatility | Languages check for Open Land Use @PSNC took 300.24699902534485s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 1.9337546825408936s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.18473339080810547s
Versatility | Serialization formats check for Open Land Use @PSNC took 9.823697328567505s
Availability | RDF dump link check for Open Land Use @PSNC took 0.20470142364501953s
License | MR license check for Open Land Use @PSNC took 0.4636874198913574s
License | HR license check for Open Land Use @PSNC took 300.22260546684265s
Amount of data | Number of property check for Open Land Use @PSNC took 0.17900323867797852s
Understandability | Number of label check for Open Land Use @PSNC took 1.1629657745361328s
Understandability | URI regex check for Open Land Use @PSNC took 0.8879280090332031s
Understandability | Vocabs check for Open Land Use @PSNC took 0.695612907409668s
Verifiability | Authors check for Open Land Use @PSNC took 0.18164610862731934s
Verifiability | Publishers check for Open Land Use @PSNC took 0.26348209381103516s
Performance | Throughput check for Open Land Use @PSNC took 11.367573261260986s
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.1995236873626709s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.19585323333740234s
Interlinking | skos check for Open Land Use @PSNC took 0.4712393283843994s
Interlinking | skos check for Open Land Use @PSNC took 0.4259343147277832s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 5.162549734115601s
Currency | Creation date check for Open Land Use @PSNC took 0.49066925048828125s
Currency | Modification date check for Open Land Use @PSNC took 0.22568583488464355s
Rep.Conc. | URIs length for Open Land Use @PSNC took 154.9057915210724s
Interoperability | New vocabularies check for Open Land Use @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.18305230140686035s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.2097787857055664s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.1805424690246582s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 34.80805587768555s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.6864373683929443s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.6147992610931396s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.18561291694641113s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 86.16237998008728s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.546473264694214s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 29.317086696624756s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.3816990852355957s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 87.00730013847351s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.837599277496338s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.6363873481750488s
Security | Sign check for Open Land Use @PSNC took 0.2502405643463135s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 10.336857795715332s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.5649902820587158s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.021195411682128906s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.3828277587890625e-05s
INFO | --- Analysis for Open_Land_Use took 2238.4762036800385s
Availability | SPARQL endpoint availability check for flyatlas took 1.1907343864440918s
Availability | VoID file availability check for flyatlas took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for flyatlas took 0.4342529773712158s
Reputation | Calculation of the PageRank for flyatlas took 0.02099132537841797s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.910064697265625e-05s
Believability | Calculation of trust value for flyatlas took 9.775161743164062e-06s
INFO | --- Analysis for openbiomed-flyatlas took 8.581711769104004s
Availability | SPARQL endpoint availability check for OpenCalais took 4.5299530029296875e-05s
Availability | VoID file availability check for OpenCalais took 0.0011477470397949219s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.3535614013671875s
Reputation | Calculation of the PageRank for OpenCalais took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010943412780761719s
Believability | Calculation of trust value for OpenCalais took 1.0013580322265625e-05s
INFO | --- Analysis for opencalais took 7.828834772109985s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 0.00010514259338378906s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.35187602043151855s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020854473114013672s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.581710815429688e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 4.0531158447265625e-06s
INFO | --- Analysis for opencorporates took 4.008503675460815s
Availability | SPARQL endpoint availability check for OpenCyc took 4.506111145019531e-05s
Availability | VoID file availability check for OpenCyc took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for OpenCyc took 1.4067306518554688s
Reputation | Calculation of the PageRank for OpenCyc took 0.02267289161682129s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010776519775390625s
Believability | Calculation of trust value for OpenCyc took 9.298324584960938e-06s
INFO | --- Analysis for opencyc took 4.832963466644287s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 8.368492126464844e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0006797313690185547s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 1.376474142074585s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.02221083641052246s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 7.902406215667725s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.000579833984375s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.3684957027435303s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020857572555541992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 4.219841957092285s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 9.036064147949219e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.36138010025024414s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.021529436111450195s
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.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.137634038925171s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 8.678436279296875e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.3129737377166748s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.7777042388916016s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 9.059906005859375e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.33888888359069824s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.022098302841186523s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.4914493560791016s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.3245980739593506s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 6.815490245819092s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 8.535385131835938e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0007822513580322266s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.28820133209228516s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.021383047103881836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 5.482658624649048s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.28711724281311035s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.021038532257080078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.6698334217071533s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 9.965896606445312e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.30014681816101074s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 8.795507669448853s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 8.416175842285156e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.3275411128997803s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 0.0001010894775390625s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 3.7820942401885986s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 8.487701416015625e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.3157920837402344s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.02261066436767578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 2.3603439331054688e-05s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 7.503765821456909s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.28687047958374023s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.021749496459960938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.3236231803894043s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.34088611602783203s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.022574901580810547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 3.4417636394500732s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 9.369850158691406e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.29912614822387695s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020884037017822266s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.7326321601867676s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 8.845329284667969e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0007719993591308594s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.29054760932922363s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02121114730834961s
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.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 3.7450830936431885s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.00010204315185546875s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.29456067085266113s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 3.4942262172698975s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.2851231098175049s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020821809768676758s
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.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.3402676582336426s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 8.463859558105469e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.31926965713500977s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.022529125213623047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.7226812839508057s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 8.58306884765625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.30582284927368164s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020636320114135742s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.000873565673828125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.718867063522339s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.083747863769531e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2793736457824707s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020924806594848633s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.410743713378906e-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 3.5495944023132324s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.2963736057281494s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.593748092651367s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0007312297821044922s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.3003220558166504s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.021090030670166016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 4.6469175815582275s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 6.103515625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007562637329101562s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.31336021423339844s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.022251605987548828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.219436407089233s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007510185241699219s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.30114221572875977s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.0731306076049805s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0001289844512939453s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007789134979248047s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2789914608001709s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020810365676879883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.602836608886719e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.2359840869903564s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 8.606910705566406e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.31719040870666504s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.357514381408691s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007228851318359375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.29473066329956055s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.023698568344116s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 9.107589721679688e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007827281951904297s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.3029792308807373s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.021201610565185547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.000869989395142s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.343120813369751s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.022307872772216797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 9.775161743164062e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.242746591567993s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 9.417533874511719e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.27209019660949707s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.02088475227355957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.088107347488403s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0008502006530761719s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.27953290939331055s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.021633386611938477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.9201250076293945s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.012222290039062e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0008425712585449219s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.30503368377685547s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020795106887817383s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.863755464553833s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 9.512901306152344e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.3343541622161865s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.021252155303955078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 3.6990549564361572s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.817413330078125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.31102705001831055s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.054473876953125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.7181262969970703s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00010275840759277344s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.27725863456726074s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.022874116897583008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.887580871582031e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.5449063777923584s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 9.34600830078125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007529258728027344s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.30171799659729004s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.02136969566345215s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 5.0067901611328125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.7713165283203125s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.001283407211303711s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.3091392517089844s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.022434234619140625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.9690515995025635s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.26728200912475586s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.021030902862548828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 4.271976947784424s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007472038269042969s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2983705997467041s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.02228379249572754s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0009906291961669922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 5.793571472167969e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.627501964569092s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.982948303222656e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007717609405517578s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.288013219833374s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.021043777465820312s
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.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 3.7609498500823975s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 5.91278076171875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.3217427730560303s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02084517478942871s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.468796253204346s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007977485656738281s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.32733893394470215s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020997047424316406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.413289785385132s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 8.845329284667969e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2982909679412842s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 3.7952685356140137s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 4.090393781661987s
Availability | VoID file availability check for Open Data of Ecuador took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.28624725341796875s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.022235631942749023s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 9.202957153320312e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 8.106231689453125e-06s
INFO | --- Analysis for opendataec took 10.857775211334229s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 7.462501525878906e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.3083207607269287s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.430511474609375e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 6.28074312210083s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.267692565917969e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0003814697265625s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.26973700523376465s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 8.344650268554688e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 4.076565504074097s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 0.00013017654418945312s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.3009183406829834s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020786046981811523s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.674269676208496s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 8.702278137207031e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.2885150909423828s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020796537399291992s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.717176914215088s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0008966922760009766s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.31376075744628906s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.021006107330322266s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.7694144248962402s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.2886326313018799s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020990610122680664s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.239776611328125e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.756481409072876s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 9.560585021972656e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.32544541358947754s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.4781951904296875e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.9106204509735107s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 8.654594421386719e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.3189506530761719s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020735502243041992s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0008203983306884766s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.769082546234131s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 9.179115295410156e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.28821754455566406s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.33514404296875e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.7716169357299805s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.570000410079956s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.288360595703125s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020899534225463867s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.3589859008789062e-05s
INFO | --- Analysis for openlink-lod-cache took 63.677430629730225s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 8.845329284667969e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.2895352840423584s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02178049087524414s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.298324584960938e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.2636184692382812e-05s
INFO | --- Analysis for openlinksw-dataspaces took 3.3116073608398438s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.220008850097656e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.303999662399292s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.179115295410156e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 8.821487426757812e-06s
INFO | --- Analysis for openlylocal took 9.01209306716919s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.3727693557739258s
Availability | VoID file availability check for OpenMobileNetwork took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.2914457321166992s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.022696971893310547s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.677078247070312e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.3828277587890625e-05s
INFO | --- Analysis for openmobilenetwork took 5.007174730300903s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.7634880542755127s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.31098127365112305s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02067279815673828s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.560585021972656e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 4.9387288093566895s
Availability | SPARQL endpoint availability check for oreilly took 8.726119995117188e-05s
Availability | VoID file availability check for oreilly took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for oreilly took 0.2896754741668701s
Reputation | Calculation of the PageRank for oreilly took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for oreilly took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.269050598144531e-05s
Believability | Calculation of trust value for oreilly took 1.2874603271484375e-05s
INFO | --- Analysis for oreilly took 4.437725305557251s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.415692090988159s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.2697892189025879s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.020667314529418945s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.4809112548828125e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.239776611328125e-05s
INFO | --- Analysis for Organchem-Data took 7.542818546295166s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.06684207916259766s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2896909713745117s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.021814823150634766s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0012423992156982422s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 9.393692016601562e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.5974044799804688e-05s
INFO | --- Analysis for organic-edunet took 9.173569202423096s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.44697070121765137s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0005500316619873047s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 6.359250068664551s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7140030860900879s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.17245221138000488s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.6380088329315186s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 5.4846351146698s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.15535640716552734s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.34961700439453125s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.1371152400970459s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.1295468807220459s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.13280725479125977s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.2147281169891357s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.161515474319458s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.19353842735290527s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.32703208923339844s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.1583254337310791s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.12295866012573242s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.12159156799316406s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.751225471496582s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 6.794929504394531e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.1543440818786621s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.13301301002502441s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.12868356704711914s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.30559563636779785s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.12192630767822266s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.3437948226928711s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.35422348976135254s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 3.7969186305999756s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.1303095817565918s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.18346095085144043s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.16738677024841309s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.692697525024414s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.2228689193725586s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2816126346588135s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.2561507225036621s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.3909916877746582s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.8643908500671387s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.158236503601074s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.3083627223968506s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.1357626914978027s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.30072498321533203s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.16470718383789062s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.1561894416809082s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 3451.7884936332703s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.5544602870941162s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.02094435691833496s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.3589859008789062e-05s
INFO | --- Analysis for orkg took 3682.811854839325s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.7414333820343018s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.2947578430175781s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.0214996337890625s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 9.1552734375e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.2636184692382812e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 28.895874738693237s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.6136043071746826s
Availability | VoID file availability check for OSM Semantic Network took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.33908677101135254s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.02063441276550293s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.933906555175781e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.049041748046875e-05s
INFO | --- Analysis for osm-semantic-network took 8.503237962722778s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.5593068599700928s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.0005240440368652344s
Extra | Recovery of all triples for Open Transport Map @PSNC took 113.30596709251404s
Performance | Total latancy measurement for Open Transport Map @PSNC took 1.004237174987793s
Amount of data | Number of triples check for Open Transport Map @PSNC took 9.133462190628052s
Interoperability | New terms check for Open Transport Map @PSNC took 14.043535232543945s
Versatility | Languages check for Open Transport Map @PSNC took 300.1905632019043s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 1.9601480960845947s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.3593168258666992s
Versatility | Serialization formats check for Open Transport Map @PSNC took 8.340694189071655s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.2120513916015625s
License | MR license check for Open Transport Map @PSNC took 0.18237996101379395s
License | HR license check for Open Transport Map @PSNC took 300.1766080856323s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.20177292823791504s
Understandability | Number of label check for Open Transport Map @PSNC took 1.1824455261230469s
Understandability | URI regex check for Open Transport Map @PSNC took 1.4296481609344482s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.6884605884552002s
Verifiability | Authors check for Open Transport Map @PSNC took 0.22085165977478027s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.255795955657959s
Performance | Throughput check for Open Transport Map @PSNC took 10.993809223175049s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 7.176399230957031e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.1929335594177246s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.19939374923706055s
Interlinking | skos check for Open Transport Map @PSNC took 0.435016393661499s
Interlinking | skos check for Open Transport Map @PSNC took 0.40130043029785156s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 6.359143972396851s
Currency | Creation date check for Open Transport Map @PSNC took 0.48608946800231934s
Currency | Modification date check for Open Transport Map @PSNC took 0.21855998039245605s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 153.96803402900696s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.215850830078125s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.49805307388305664s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.4495255947113037s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 33.207202672958374s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.6905643939971924s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.6106009483337402s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.1869971752166748s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 85.6121244430542s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.46041464805603s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 33.93792200088501s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.3820409774780273s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 86.9361822605133s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.8137052059173584s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.5585048198699951s
Security | Sign check for Open Transport Map @PSNC took 0.2082810401916504s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 15.576770067214966s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.4200472831726074s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.022004365921020508s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.0517578125e-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.3589859008789062e-05s
INFO | --- Analysis for OTM took 2258.566193819046s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.6365349292755127s
Availability | VoID file availability check for Pali English Lexicon took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.3086056709289551s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020938634872436523s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.314018249511719e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.3589859008789062e-05s
INFO | --- Analysis for pali-english-lexicon took 7.709301710128784s
Availability | SPARQL endpoint availability check for PanLex took 1.8396577835083008s
Availability | VoID file availability check for PanLex took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for PanLex took 0.3290541172027588s
Reputation | Calculation of the PageRank for PanLex took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.128715515136719e-05s
Believability | Calculation of trust value for PanLex took 9.298324584960938e-06s
INFO | --- Analysis for panlex took 4.68612265586853s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 8.96453857421875e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.29236626625061035s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.504753112792969e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.2874603271484375e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.547846794128418s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.05269765853881836s
Availability | VoID file availability check for patents.data.gov.uk took 0.00020885467529296875s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.3063986301422119s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.02088332176208496s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.9591064453125e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 8.106231689453125e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.789363384246826s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 8.7738037109375e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.33661484718322754s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.743171691894531e-05s
Believability | Calculation of trust value for PDEV-Lemon took 9.5367431640625e-06s
INFO | --- Analysis for pdev-lemon took 4.04861855506897s
Availability | SPARQL endpoint availability check for pdevlemon took 8.392333984375e-05s
Availability | VoID file availability check for pdevlemon took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.31911659240722656s
Reputation | Calculation of the PageRank for pdevlemon took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 2.86102294921875e-05s
Believability | Calculation of trust value for pdevlemon took 9.5367431640625e-06s
INFO | --- Analysis for pdevlemon took 3.367302894592285s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 8.702278137207031e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008058547973632812s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.345257043838501s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.559226989746094e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.52587890625e-05s
INFO | --- Analysis for periodo took 19.38111925125122s
Availability | SPARQL endpoint availability check for Personal_Homepages took 8.749961853027344e-05s
Availability | VoID file availability check for Personal_Homepages took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.30248069763183594s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.021404266357421875s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00038361549377441406s
Believability | Calculation of trust value for Personal_Homepages took 9.298324584960938e-06s
INFO | --- Analysis for personal-homepages took 2.845036268234253s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.5299530029296875e-05s
Availability | VoID file availability check for Ontology of University People took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.3933990001678467s
Reputation | Calculation of the PageRank for Ontology of University People took 0.021544456481933594s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.24249267578125e-05s
Believability | Calculation of trust value for Ontology of University People took 9.5367431640625e-06s
INFO | --- Analysis for PersonOnto took 2.843398094177246s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 5.899911403656006s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.32108378410339355s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0009553432464599609s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.33514404296875e-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 11.006001949310303s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.9828681945800781s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.30586886405944824s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1444091796875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.049041748046875e-05s
INFO | --- Analysis for PFRPPH took 6.304943323135376s
Availability | SPARQL endpoint availability check for PGxLOD took 30.173742055892944s
Availability | VoID file availability check for PGxLOD took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.29901933670043945s
Reputation | Calculation of the PageRank for PGxLOD took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 5.698204040527344e-05s
Believability | Calculation of trust value for PGxLOD took 8.344650268554688e-06s
INFO | --- Analysis for PGxLOD took 73.09807872772217s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.9256398677825928s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.307661771774292s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0219268798828125s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.361701965332031e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.3113021850585938e-05s
INFO | --- Analysis for phoible took 4.743396282196045s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 0.00010943412780761719s
Availability | VoID file availability check for Parallel ice sheet model took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.3665497303009033s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.020708322525024414s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.933906555175781e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.1920928955078125e-05s
INFO | --- Analysis for PISM took 193.3932445049286s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.2438507080078125e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0003170967102050781s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.3226907253265381s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.797645568847656e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 7.62939453125e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.7965164184570312s
Availability | SPARQL endpoint availability check for digitized plant specimen took 0.9848818778991699s
Availability | VoID file availability check for digitized plant specimen took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.28667688369750977s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 6.961822509765625e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.4066696166992188e-05s
INFO | --- Analysis for plant-specimen took 3.685635805130005s
Availability | SPARQL endpoint availability check for Pleiades took 8.726119995117188e-05s
Availability | VoID file availability check for Pleiades took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Pleiades took 0.3023972511291504s
Reputation | Calculation of the PageRank for Pleiades took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.320808410644531e-05s
Believability | Calculation of trust value for Pleiades took 1.3828277587890625e-05s
INFO | --- Analysis for pleiades took 15.206311225891113s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.220008850097656e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0004074573516845703s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.3049647808074951s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.1948089599609375e-05s
Believability | Calculation of trust value for podorozhnyk.com took 9.059906005859375e-06s
INFO | --- Analysis for podorozhnyk took 3.37066912651062s
Availability | SPARQL endpoint availability check for Poképédia took 5.5789947509765625e-05s
Availability | VoID file availability check for Poképédia took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Poképédia took 0.34969639778137207s
Reputation | Calculation of the PageRank for Poképédia took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.796287536621094e-05s
Believability | Calculation of trust value for Poképédia took 8.58306884765625e-06s
INFO | --- Analysis for pokepedia-fr took 2.814478635787964s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.5299530029296875e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.3347127437591553s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.02065443992614746s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.867813110351562e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.58306884765625e-06s
INFO | --- Analysis for polymath-virtual-library took 6.046145915985107s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.27388525009155273s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0006439685821533203s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.285269260406494s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.6052014827728271s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.4563894271850586s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6126821041107178s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3670191764831543s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.40187764167785645s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11690855026245117s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13027501106262207s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1138913631439209s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12228965759277344s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6083617210388184s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12636375427246094s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.15579962730407715s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2571065425872803s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11347460746765137s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1295938491821289s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12119054794311523s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.86609435081482s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.1948089599609375e-05s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12099838256835938s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12805986404418945s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11334848403930664s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12105560302734375s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1210169792175293s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.23550701141357422s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.23528409004211426s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.411473512649536s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13030219078063965s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1120920181274414s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11288857460021973s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.0850427150726318s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.19658493995666504s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.781116247177124s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12132978439331055s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.831073522567749s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.184419631958008s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.240882396697998s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.032963514328003s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.5480449199676514s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11965465545654297s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4862.299613714218s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.7520368099212646s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.02124500274658203s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.794929504394531e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0009856224060058594s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.2172927856445312e-05s
Interoperability | Check the re-using of existing vocabs for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.86102294921875e-06s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 8.58306884765625e-06s
INFO | --- Analysis for portuguese_prisons_releases took 4932.820569515228s
Availability | SPARQL endpoint availability check for prefix.cc took 8.797645568847656e-05s
Availability | VoID file availability check for prefix.cc took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.304962158203125s
Reputation | Calculation of the PageRank for prefix.cc took 0.020782470703125s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.839897155761719e-05s
Believability | Calculation of trust value for prefix.cc took 1.1682510375976562e-05s
INFO | --- Analysis for prefix-cc took 3.4272682666778564s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.8455779552459717s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.000640869140625s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.3112986087799072s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02337813377380371s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.887580871582031e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.3113021850585938e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 8.093602418899536s
Availability | SPARQL endpoint availability check for PreLex took 6.889081954956055s
Availability | VoID file availability check for PreLex took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for PreLex took 0.32118868827819824s
Reputation | Calculation of the PageRank for PreLex took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for PreLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.081031799316406e-05s
Believability | Calculation of trust value for PreLex took 1.049041748046875e-05s
INFO | --- Analysis for prelex took 19.25131893157959s
Availability | SPARQL endpoint availability check for Prelinger Archives took 11.630473613739014s
Availability | VoID file availability check for Prelinger Archives took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.2774350643157959s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.021486520767211914s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.075599670410156e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.049041748046875e-05s
INFO | --- Analysis for prelinger_archives took 32.426347732543945s
Availability | SPARQL endpoint availability check for PreMOn took 0.5185744762420654s
Availability | VoID file availability check for PreMOn took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for PreMOn took 0.285400390625s
Reputation | Calculation of the PageRank for PreMOn took 0.021250486373901367s
Interlinking | Calculation of Degree of Connection for PreMOn took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PreMOn took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for PreMOn took 5.125999450683594e-05s
Believability | Calculation of trust value for PreMOn took 1.0728836059570312e-05s
INFO | --- Analysis for premon took 6.09881329536438s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 9.417533874511719e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.30440545082092285s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.02262091636657715s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.435943603515625e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.049041748046875e-05s
INFO | --- Analysis for princeton-library-findingaids took 4.1196606159210205s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.6861426830291748s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.3132176399230957s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020920515060424805s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for PrinParLat took 4.866565465927124s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.3651881217956543s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.3006553649902344s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.249282836914062e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.3589859008789062e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 3.4450674057006836s
Availability | SPARQL endpoint availability check for Prior Panel took 8.96453857421875e-05s
Availability | VoID file availability check for Prior Panel took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.30182862281799316s
Reputation | Calculation of the PageRank for Prior Panel took 0.021613121032714844s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.647804260253906e-05s
Believability | Calculation of trust value for Prior Panel took 1.2874603271484375e-05s
INFO | --- Analysis for Prior_Panel took 2.850040912628174s
Availability | SPARQL endpoint availability check for ProductDB took 0.7183914184570312s
Availability | VoID file availability check for ProductDB took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for ProductDB took 0.27516603469848633s
Reputation | Calculation of the PageRank for ProductDB took 0.021795034408569336s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.176399230957031e-05s
Believability | Calculation of trust value for ProductDB took 9.775161743164062e-06s
INFO | --- Analysis for productdb took 3.996690273284912s
Availability | SPARQL endpoint availability check for Product Types Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.29102563858032227s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.022414445877075195s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.510185241699219e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for productontology took 8.665343761444092s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 8.678436279296875e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.27829957008361816s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020963668823242188s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010347366333007812s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 6.4373016357421875e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 7.053930044174194s
Availability | SPARQL endpoint availability check for provenanceweb took 0.158097505569458s
Availability | VoID file availability check for provenanceweb took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.30467867851257324s
Reputation | Calculation of the PageRank for provenanceweb took 0.023207426071166992s
Interlinking | Calculation of Degree of Connection for provenanceweb took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 9.417533874511719e-05s
Believability | Calculation of trust value for provenanceweb took 1.0967254638671875e-05s
INFO | --- Analysis for provenanceweb took 49.692370891571045s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.1961669921875e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.30905675888061523s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 9.989738464355469e-05s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.3589859008789062e-05s
INFO | --- Analysis for proyectoapadrina took 7.055237054824829s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.253708839416504s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.30799388885498047s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.838539123535156e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 4.5299530029296875e-06s
INFO | --- Analysis for pscs-catalogue took 124.89059805870056s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 8.797645568847656e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.27063846588134766s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.020911455154418945s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.343292236328125e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.2636184692382812e-05s
INFO | --- Analysis for psh-subject-headings took 3.293267250061035s
Availability | SPARQL endpoint availability check for Depression took 0.7223742008209229s
Availability | VoID file availability check for Depression took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Depression took 0.2873661518096924s
Reputation | Calculation of the PageRank for Depression took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for Depression took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Depression took 3.075599670410156e-05s
Believability | Calculation of trust value for Depression took 2.6941299438476562e-05s
INFO | --- Analysis for Psychology took 3.470150947570801s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.482269287109375e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.29268741607666016s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for PubChem RDF took 1.3589859008789062e-05s
INFO | --- Analysis for PubChem_RDF took 5.734295129776001s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 60.06408190727234s
Availability | VoID file availability check for Public Spending in Greece took 0.000732421875s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.29705333709716797s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020820140838623047s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 8.0108642578125e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.0967254638671875e-05s
INFO | --- Analysis for public-spending-in-greece took 147.66520047187805s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.23055815696716309s
Availability | VoID file availability check for Publications Office Authority tables took 0.000713348388671875s
Extra | Recovery of all triples for Publications Office Authority tables took 170.96404814720154s
Performance | Total latancy measurement for Publications Office Authority tables took 0.6521248817443848s
Amount of data | Number of triples check for Publications Office Authority tables took 48.75240707397461s
Interoperability | New terms check for Publications Office Authority tables took 57.54880475997925s
Versatility | Languages check for Publications Office Authority tables took 300.1273503303528s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 15.38278865814209s
Security | Check HTTPS for Publications Office Authority tables took 0.3731498718261719s
Interpretability | RDF structures check for Publications Office Authority tables took 0.5411992073059082s
Versatility | Serialization formats check for Publications Office Authority tables took 4.49221396446228s
Availability | RDF dump link check for Publications Office Authority tables took 0.20282340049743652s
License | MR license check for Publications Office Authority tables took 0.44875144958496094s
License | HR license check for Publications Office Authority tables took 300.0671720504761s
Amount of data | Number of property check for Publications Office Authority tables took 0.2003011703491211s
Understandability | Number of label check for Publications Office Authority tables took 1.5872106552124023s
Understandability | URI regex check for Publications Office Authority tables took 0.3784189224243164s
Understandability | Vocabs check for Publications Office Authority tables took 0.12648987770080566s
Verifiability | Authors check for Publications Office Authority tables took 0.192047119140625s
Verifiability | Publishers check for Publications Office Authority tables took 0.5373501777648926s
Performance | Throughput check for Publications Office Authority tables took 10.549814224243164s
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.14469456672668457s
Interlinking | sameAs chians check for Publications Office Authority tables took 6.431165933609009s
Interlinking | skos check for Publications Office Authority tables took 0.3130180835723877s
Interlinking | skos check for Publications Office Authority tables took 0.1518566608428955s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.27839088439941406s
Currency | Creation date check for Publications Office Authority tables took 0.4674339294433594s
Currency | Modification date check for Publications Office Authority tables took 0.14774370193481445s
Rep.Conc. | URIs length for Publications Office Authority tables took 417.77622294425964s
Interoperability | New vocabularies check for Publications Office Authority tables took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.17196941375732422s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.21982431411743164s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.1698744297027588s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 38.7327139377594s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.218173027038574s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.6209003925323486s
Consistency | Disjoint class check for Publications Office Authority tables took 0.1258072853088379s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.41234731674194s
Consistency | Misplaced classes for Publications Office Authority tables took 8.441181898117065s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 36.770310401916504s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.6842613220214844s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.49906158447266s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.1499602794647217s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.4229917526245117s
Security | Sign check for Publications Office Authority tables took 0.13576126098632812s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 11.293813705444336s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 5.745492935180664s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.02137470245361328s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.6689300537109375e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 1.0251998901367188e-05s
INFO | --- Analysis for publications_office_authority_tables took 14763.958245277405s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.458427429199219e-05s
Availability | VoID file availability check for QBOAirbase took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.33537936210632324s
Reputation | Calculation of the PageRank for QBOAirbase took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 8.082389831542969e-05s
Believability | Calculation of trust value for QBOAirbase took 1.1682510375976562e-05s
INFO | --- Analysis for qboairbase took 136.52476978302002s
Availability | SPARQL endpoint availability check for Qualité de l'air took 5.054473876953125e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.3141820430755615s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.020534515380859375s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.409385681152344e-05s
Believability | Calculation of trust value for Qualité de l'air took 1.33514404296875e-05s
INFO | --- Analysis for Qualité_de_l'air took 3.1635758876800537s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 9.131431579589844e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0007319450378417969s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.30274319648742676s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.021985530853271484s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.457069396972656e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.2159347534179688e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 55.93756818771362s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.639580249786377s
Availability | VoID file availability check for Querolus in LiLa took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.31621265411376953s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.021477699279785156s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for Querolus took 4.472574949264526s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.41838741302490234s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007028579711914062s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 28.884902000427246s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7258272171020508s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.452049970626831s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.9048614501953125s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.676002979278564s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.760643243789673s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2297523021697998s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.16165518760681152s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1427161693572998s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15476369857788086s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19192910194396973s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19150710105895996s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13248014450073242s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.29477548599243164s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14211440086364746s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14265799522399902s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.21634554862976074s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.843186378479004s
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.14319324493408203s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1526503562927246s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1432018280029297s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14169621467590332s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14215826988220215s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.35056328773498535s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3167757987976074s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 26.973572492599487s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14290904998779297s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1422431468963623s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14193511009216309s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1440446376800537s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.910064697265625e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.294738531112671s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13341426849365234s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.651041269302368s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.921692371368408s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.339277982711792s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.653004884719849s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.9041051864624023s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1411600112915039s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.784391164779663s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3865392208099365s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.1457672119140625e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.0728836059570312e-05s
INFO | --- Analysis for racai-legalnero took 162.5671830177307s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 0.00010013580322265625s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.29788732528686523s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.02075791358947754s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.123283386230469e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.33514404296875e-05s
INFO | --- Analysis for racai-llod-corola-we took 2.9092650413513184s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.13307523727416992s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0004982948303222656s
Extra | Recovery of all triples for PARSEME-Ro corpus took 30.282981157302856s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.7231020927429199s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.898864269256592s
Interoperability | New terms check for PARSEME-Ro corpus took 2.184096336364746s
Versatility | Languages check for PARSEME-Ro corpus took 18.170976638793945s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.775739669799805s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.1439812183380127s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.13270998001098633s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.141371488571167s
License | MR license check for PARSEME-Ro corpus took 0.13116097450256348s
License | HR license check for PARSEME-Ro corpus took 10.192280292510986s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.13107919692993164s
Understandability | Number of label check for PARSEME-Ro corpus took 0.21927833557128906s
Understandability | URI regex check for PARSEME-Ro corpus took 0.2852165699005127s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.14265871047973633s
Verifiability | Authors check for PARSEME-Ro corpus took 0.14260315895080566s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.1545259952545166s
Performance | Throughput check for PARSEME-Ro corpus took 11.024158477783203s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 7.557868957519531e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.13015198707580566s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.1528940200805664s
Interlinking | skos check for PARSEME-Ro corpus took 0.15401196479797363s
Interlinking | skos check for PARSEME-Ro corpus took 0.1562495231628418s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.1313948631286621s
Currency | Creation date check for PARSEME-Ro corpus took 0.296497106552124s
Currency | Modification date check for PARSEME-Ro corpus took 0.28420591354370117s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 80.13337731361389s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.14363503456115723s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.15254855155944824s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.14240550994873047s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 1.930797815322876s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.23137974739074707s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 4.018463850021362s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.13492298126220703s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 11.456329822540283s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 31.06693124771118s
Consistency | Check Invalid usage of undefined classes for PARSEME-Ro corpus took 1.6028506755828857s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 13.318694114685059s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 2.920107126235962s
Security | Sign check for PARSEME-Ro corpus took 0.12987947463989258s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.297292947769165s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.40932440757751465s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.409385681152344e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 2.1457672119140625e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.0251998901367188e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 282.1847915649414s
Availability | SPARQL endpoint availability check for RoLEX took 0.1419370174407959s
Availability | VoID file availability check for RoLEX took 0.0006673336029052734s
Extra | Recovery of all triples for RoLEX took 34.180246353149414s
Performance | Total latancy measurement for RoLEX took 0.7065489292144775s
Amount of data | Number of triples check for RoLEX took 1.5882525444030762s
Interoperability | New terms check for RoLEX took 1.679720401763916s
Versatility | Languages check for RoLEX took 4.053378105163574s
Interpretability | Number of blank nodes check for RoLEX took 1.101057767868042s
Interpretability | RDF structures check for RoLEX took 0.14310359954833984s
Versatility | Serialization formats check for RoLEX took 0.14275121688842773s
Availability | RDF dump link check for RoLEX took 0.14237308502197266s
License | MR license check for RoLEX took 0.15355873107910156s
License | HR license check for RoLEX took 0.1321117877960205s
Amount of data | Number of property check for RoLEX took 0.14112591743469238s
Understandability | Number of label check for RoLEX took 0.13217830657958984s
Understandability | URI regex check for RoLEX took 0.2942328453063965s
Understandability | Vocabs check for RoLEX took 0.14239716529846191s
Verifiability | Authors check for RoLEX took 0.1426072120666504s
Verifiability | Publishers check for RoLEX took 0.14190340042114258s
Performance | Throughput check for RoLEX took 11.06462025642395s
Amount of data | Check the number of entities for RoLEX took 7.534027099609375e-05s
Verifiability | Contribs. check for RoLEX took 0.14181041717529297s
Interlinking | sameAs chians check for RoLEX took 0.15250802040100098s
Interlinking | skos check for RoLEX took 0.14117860794067383s
Interlinking | skos check for RoLEX took 0.13114500045776367s
Timeliness | dataset update frequency check for RoLEX took 0.14210915565490723s
Currency | Creation date check for RoLEX took 0.3057219982147217s
Currency | Modification date check for RoLEX took 0.29482269287109375s
Rep.Conc. | URIs length for RoLEX took 56.82555317878723s
Interoperability | New vocabularies check for RoLEX took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.1401219367980957s
Accuracy | Check Functional Property for RoLEX took 0.128281831741333s
Accuracy | Check Inverse Functional Property for RoLEX took 0.12827730178833008s
Accuracy | Check Datatype consistency for RoLEX took 4.0854620933532715s
Consistency | Disjoint class check for RoLEX took 0.1423938274383545s
Consistency | Check Misplaced properties for RoLEX took 2.637193202972412s
Consistency | Check Ontology hijacking for RoLEX took 8.535935163497925s
Consistency | Check Invalid usage of undefined classes for RoLEX took 1.9413821697235107s
Consistency | Check Invalid usage of undefined properties for RoLEX took 4.131275177001953s
Conciseness | Check Extensional conciseness for RoLEX took 3.143385648727417s
Security | Sign check for RoLEX took 0.15128660202026367s
Availability | Check URIs Dereferenciability for RoLEX took 7.369534254074097s
Completeness | Calculation of interlinking completeness for RoLEX took 0.3460111618041992s
Reputation | Calculation of the PageRank for RoLEX took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.266334533691406e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 1.9073486328125e-06s
Believability | Calculation of trust value for RoLEX took 1.0728836059570312e-05s
INFO | --- Analysis for racai-llod-rolex took 175.26212239265442s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.29920005798339844s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.0994415283203125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.0728836059570312e-05s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.9740960597991943s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 8.726119995117188e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.3074526786804199s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.020813941955566406s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.0994415283203125e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 9.775161743164062e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.898055076599121s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 8.606910705566406e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.2869236469268799s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.022188663482666016s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.123283386230469e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.0251998901367188e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.793590784072876s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 9.298324584960938e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.28354406356811523s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.021152257919311523s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.170967102050781e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.33514404296875e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 3.0055439472198486s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.15586113929748535s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0006213188171386719s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 9.36152982711792s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.695155143737793s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.41514062881469727s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.4678778648376465s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.6231427192687988s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.2552812099456787s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.14328646659851074s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.1450972557067871s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.12960124015808105s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.1419696807861328s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.14928674697875977s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.14209389686584473s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.14701080322265625s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.2823066711425781s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.1414957046508789s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.14199471473693848s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.1304328441619873s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 10.83300495147705s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 8.559226989746094e-05s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.15276694297790527s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.1422748565673828s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.14182806015014648s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.15306854248046875s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.1447432041168213s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.2849297523498535s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.2735443115234375s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.550103187561035s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.15067815780639648s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.1402883529663086s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.1521923542022705s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.3678159713745117s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009787797927856445s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.265826940536499s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.15068435668945312s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.5139322280883789s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.0249063968658447s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.3048670291900635s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.6616506576538086s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.883561372756958s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.1387958526611328s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 3606.6081404685974s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 5.744083881378174s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 3.0994415283203125e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 2.384185791015625e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.3113021850585938e-05s
INFO | --- Analysis for racai-llod-rtasc took 3667.490608692169s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.1532588005065918s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0006160736083984375s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 33.884419441223145s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.7245666980743408s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0720674991607666s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.4800407886505127s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.3901681900024414s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.8516039848327637s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.14374017715454102s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.154616117477417s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.14296460151672363s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.1312408447265625s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.606315851211548s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.14265727996826172s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.15935754776000977s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.3046441078186035s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.1420576572418213s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.1313619613647461s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.14151620864868164s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.684448003768921s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 8.0108642578125e-05s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.14220929145812988s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.1414041519165039s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.1313459873199463s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.1544661521911621s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.14279651641845703s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.2856438159942627s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.29705095291137695s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.444828271865845s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.13921880722045898s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.1392972469329834s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.1405797004699707s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.7153899669647217s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.01958489418029785s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 4.1441330909729s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.1324293613433838s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.736644983291626s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.393871784210205s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.2865817546844482s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.8628902435302734s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 3.0216691493988037s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.14214468002319336s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 1539.2499890327454s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.3840067386627197s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.021450042724609375s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 4.172325134277344e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 1.6689300537109375e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.1205673217773438e-05s
INFO | --- Analysis for racai-llod-simonero took 1643.0735077857971s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.12027978897094727s
Availability | VoID file availability check for Rådata nå! took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.31302332878112793s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.20159912109375e-05s
Believability | Calculation of trust value for Rådata nå! took 1.33514404296875e-05s
INFO | --- Analysis for radatana took 4.503838539123535s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 8.797645568847656e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.28130173683166504s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.02179718017578125s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 4.076957702636719e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.3113021850585938e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 17.870198011398315s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 13.741196155548096s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.31019115447998047s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.021007776260375977s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.337860107421875e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.3589859008789062e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 29.557350873947144s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 392.6489453315735s
Availability | VoID file availability check for Polish LGU financial statements took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.35777902603149414s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021285295486450195s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 4.172325134277344e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 8.821487426757812e-06s
INFO | --- Analysis for Rb_PL_LGU took 667.6927666664124s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 8.988380432128906e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.3058154582977295s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.344650268554688e-05s
Believability | Calculation of trust value for RDF Book Mashup took 1.0967254638671875e-05s
INFO | --- Analysis for rdf-book-mashup took 3.5939111709594727s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 8.511543273925781e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.2998981475830078s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.02066946029663086s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 9.918212890625e-05s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 1.1682510375976562e-05s
INFO | --- Analysis for rdfize-lastfm took 2.7133541107177734s
Availability | SPARQL endpoint availability check for RDFLicense took 261.0025553703308s
Availability | VoID file availability check for RDFLicense took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.3857536315917969s
Reputation | Calculation of the PageRank for RDFLicense took 0.022224903106689453s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.790855407714844e-05s
Believability | Calculation of trust value for RDFLicense took 1.4066696166992188e-05s
INFO | --- Analysis for rdflicense took 536.0239901542664s
Availability | SPARQL endpoint availability check for RDFohloh took 0.00012803077697753906s
Availability | VoID file availability check for RDFohloh took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.3094608783721924s
Reputation | Calculation of the PageRank for RDFohloh took 0.02215862274169922s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.489059448242188e-05s
Believability | Calculation of trust value for RDFohloh took 1.2874603271484375e-05s
INFO | --- Analysis for rdfohloh took 7.213905096054077s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.7768304347991943s
Availability | VoID file availability check for Reactome RDF took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.3020308017730713s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.695487976074219e-05s
Believability | Calculation of trust value for Reactome RDF took 1.2159347534179688e-05s
INFO | --- Analysis for reactome-rdf took 4.1650166511535645s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.10954546928405762s
Availability | VoID file availability check for Rechtspraak.nl took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.28344106674194336s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.022187232971191406s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.107589721679688e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 8.821487426757812e-06s
INFO | --- Analysis for rechtspraak took 2.900592803955078s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 6.198883056640625e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.3180217742919922s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.022058725357055664s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 9.179115295410156e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.239776611328125e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 6.23972487449646s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.23714423179626465s
Availability | VoID file availability check for reference.data.gov.uk took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.29877567291259766s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.021435022354125977s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00014710426330566406s
Believability | Calculation of trust value for reference.data.gov.uk took 8.821487426757812e-06s
INFO | --- Analysis for reference-data-gov-uk took 3.0465028285980225s
Availability | SPARQL endpoint availability check for RELD took 0.6051425933837891s
Availability | VoID file availability check for RELD took 0.0004036426544189453s
Completeness | Calculation of interlinking completeness for RELD took 0.314070463180542s
Reputation | Calculation of the PageRank for RELD took 0.022203683853149414s
Interlinking | Calculation of Degree of Connection for RELD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for RELD took 3.361701965332031e-05s
Believability | Calculation of trust value for RELD took 1.5497207641601562e-05s
INFO | --- Analysis for RELD took 4.126631259918213s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.21847224235534668s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0006356239318847656s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.3657822608947754s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.43537139892578125s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.4932224750518799s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.6454546451568604s
Versatility | Languages check for Repository for Linked Open Archival Data took 20.312259912490845s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 17.50045394897461s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.2378687858581543s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.2200939655303955s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.2584104537963867s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.15550589561462402s
License | MR license check for Repository for Linked Open Archival Data took 0.3145742416381836s
License | HR license check for Repository for Linked Open Archival Data took 7.9318671226501465s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.13247060775756836s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.80548095703125s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.3437681198120117s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.11543130874633789s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.13817143440246582s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.17531704902648926s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.348885774612427s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 7.510185241699219e-05s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.07173657417297363s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.13300085067749023s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.2817397117614746s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.06654191017150879s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.19912505149841309s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.20073747634887695s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.1517350673675537s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.7560715675354004s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.12674784660339355s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.12342500686645508s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.09045124053955078s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.337313175201416s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.028467416763305664s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028441429138183594s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.17971539497375488s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 1.96242356300354s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.1975102424621582s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.5908429622650146s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.2747642993927002s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.0819156169891357s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.03476715087890625s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.13059616088867188s
Security | Sign check for Repository for Linked Open Archival Data took 0.3696107864379883s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1141.7008731365204s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.7513420581817627s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.021426677703857422s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.430511474609375e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.3589859008789062e-05s
INFO | --- Analysis for reload took 1285.4913980960846s
Availability | SPARQL endpoint availability check for Land use merced dataset took 0.00011897087097167969s
Availability | VoID file availability check for Land use merced dataset took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.3168199062347412s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.02265787124633789s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.049041748046875e-05s
INFO | --- Analysis for remote_Sensing took 3.3940846920013428s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.701061487197876s
Availability | VoID file availability check for Renewable Energy Generators took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.2781834602355957s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.022151470184326172s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.267692565917969e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 9.298324584960938e-06s
INFO | --- Analysis for renewable_energy_generators took 11.412917137145996s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.07722806930541992s
Availability | VoID file availability check for research.data.gov.uk took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.38095927238464355s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020867347717285156s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.131431579589844e-05s
Believability | Calculation of trust value for research.data.gov.uk took 1.0251998901367188e-05s
INFO | --- Analysis for research-data-gov-uk took 2.9200048446655273s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.4345855712890625e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.32183265686035156s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020811080932617188s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.890296936035156e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 1.2874603271484375e-05s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 4.324804782867432s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.06297135353088379s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.2767195701599121s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 2.9087066650390625e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.0013580322265625e-05s
INFO | --- Analysis for revistas_turismo took 2.735569477081299s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.2682337760925293s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.30029869079589844s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.021262168884277344s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.0001125335693359375s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.0251998901367188e-05s
INFO | --- Analysis for revyu took 2.9693353176116943s
Availability | SPARQL endpoint availability check for sdafsadf took 0.22638916969299316s
Availability | VoID file availability check for sdafsadf took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.28690171241760254s
Reputation | Calculation of the PageRank for sdafsadf took 0.02113819122314453s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.170967102050781e-05s
Believability | Calculation of trust value for sdafsadf took 1.049041748046875e-05s
INFO | --- Analysis for rgsdfg took 3.009335517883301s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.4345855712890625e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.3041379451751709s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.601478576660156e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.1444091796875e-05s
INFO | --- Analysis for riese took 22.978058338165283s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.25739479064941406s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0005702972412109375s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 22.051753520965576s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.49674487113952637s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 55.33840560913086s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 2.2037036418914795s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 163.90222191810608s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 47.41182494163513s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.24843811988830566s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.1919102668762207s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.1420135498046875s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.09587717056274414s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.12757396697998047s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.07958459854126s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 0.14548611640930176s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 14.563705205917358s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.25173425674438477s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.11181926727294922s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.11544489860534668s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.09903144836425781s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.610155582427979s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 7.200241088867188e-05s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.10394763946533203s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.432662010192871s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.16578197479248047s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.1213371753692627s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.0959470272064209s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.23984885215759277s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.2439408302307129s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 76.81559658050537s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.14908623695373535s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 0.1363081932067871s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.11977076530456543s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 10.951273679733276s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.42173171043396s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.8268492221832275s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.09974980354309082s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 44.64784216880798s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 4.625808954238892s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.2815346717834473s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 48.241785764694214s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.855368137359619s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.12477469444274902s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 1.526973009109497s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.5295987129211426s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.02093029022216797s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 6.031990051269531e-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.049041748046875e-05s
INFO | --- Analysis for rism took 1243.5578696727753s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.09937286376953125s
Availability | VoID file availability check for RISM Authority data took 0.0005743503570556641s
Extra | Recovery of all triples for RISM Authority data took 20.871596097946167s
Performance | Total latancy measurement for RISM Authority data took 0.5198416709899902s
Amount of data | Number of triples check for RISM Authority data took 50.518033266067505s
Interoperability | New terms check for RISM Authority data took 1.9297306537628174s
Versatility | Languages check for RISM Authority data took 156.89650750160217s
Interpretability | Number of blank nodes check for RISM Authority data took 47.319146394729614s
Security | Check HTTPS for RISM Authority data took 0.1419384479522705s
Interpretability | RDF structures check for RISM Authority data took 0.13186955451965332s
Versatility | Serialization formats check for RISM Authority data took 0.14168500900268555s
Availability | RDF dump link check for RISM Authority data took 0.09185123443603516s
License | MR license check for RISM Authority data took 0.09985685348510742s
License | HR license check for RISM Authority data took 300.0182182788849s
Amount of data | Number of property check for RISM Authority data took 0.1239473819732666s
Understandability | Number of label check for RISM Authority data took 7.5316002368927s
Understandability | URI regex check for RISM Authority data took 0.24016046524047852s
Understandability | Vocabs check for RISM Authority data took 0.0844871997833252s
Verifiability | Authors check for RISM Authority data took 0.10291385650634766s
Verifiability | Publishers check for RISM Authority data took 0.09931373596191406s
Performance | Throughput check for RISM Authority data took 10.619905710220337s
Amount of data | Check the number of entities for RISM Authority data took 0.00012946128845214844s
Verifiability | Contribs. check for RISM Authority data took 0.09369826316833496s
Interlinking | sameAs chians check for RISM Authority data took 1.4831595420837402s
Interlinking | skos check for RISM Authority data took 0.13199734687805176s
Interlinking | skos check for RISM Authority data took 0.10415315628051758s
Timeliness | dataset update frequency check for RISM Authority data took 0.0918569564819336s
Currency | Creation date check for RISM Authority data took 0.2507491111755371s
Currency | Modification date check for RISM Authority data took 0.2415163516998291s
Rep.Conc. | URIs length for RISM Authority data took 73.17183136940002s
Interoperability | New vocabularies check for RISM Authority data took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.18251299858093262s
Accuracy | Check Functional Property for RISM Authority data took 0.1590719223022461s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.10178446769714355s
Accuracy | Check Empty annotation labels for RISM Authority data took 20.343403577804565s
Accuracy | Check White space in annotation for RISM Authority data took 2.420128345489502s
Accuracy | Check Datatype consistency for RISM Authority data took 3.860759973526001s
Consistency | Disjoint class check for RISM Authority data took 0.09575271606445312s
Consistency | Check Misplaced properties for RISM Authority data took 46.07322907447815s
Consistency | Check Ontology hijacking for RISM Authority data took 4.721007585525513s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.291902780532837s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 45.0209743976593s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.933171510696411s
Security | Sign check for RISM Authority data took 0.13412690162658691s
Availability | Check URIs Dereferenciability for RISM Authority data took 1.4134774208068848s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.5931344032287598s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020940542221069336s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for RISM Authority data took 1.7404556274414062e-05s
Believability | Calculation of trust value for RISM Authority data took 1.33514404296875e-05s
INFO | --- Analysis for rism-authorities took 1225.8038697242737s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 8.654594421386719e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.27413463592529297s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.170967102050781e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.049041748046875e-05s
INFO | --- Analysis for rk took 2.6275594234466553s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.08718109130859375s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.3044466972351074s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00021958351135253906s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-acm took 2.9127979278564453s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.04282212257385254s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.00042629241943359375s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.30726099014282227s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.0001354217529296875s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.834127426147461s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.04527592658996582s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.28809070587158203s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.0001983642578125s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 2.770728588104248s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.043033599853515625s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.29232239723205566s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.021025657653808594s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0001583099365234375s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.793426036834717s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.04648303985595703s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0003070831298828125s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.2694823741912842s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00015473365783691406s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.855461835861206s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.04243063926696777s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.2854499816894531s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.02211284637451172s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 0.00010156631469726562s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.7940196990966797s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.04196977615356445s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.28585195541381836s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.02097487449645996s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0008525848388671875s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00012969970703125s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.8820502758026123s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.04679679870605469s
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.317990779876709s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.020672321319580078s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.435943603515625e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.937760353088379s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.04003596305847168s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.2989349365234375s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00022912025451660156s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-dblp took 2.784437894821167s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.0493931770324707s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.30108118057250977s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.2479248046875e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-deepblue took 2.834475040435791s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.3630390167236328s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.30501437187194824s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.021442651748657227s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.822845458984375e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-deploy took 4.189795017242432s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.050080299377441406s
Availability | VoID file availability check for digitaleconomy took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.28879737854003906s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020670175552368164s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.0994415283203125e-05s
Believability | Calculation of trust value for digitaleconomy took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.8230721950531006s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.04203438758850098s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.28827524185180664s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014925003051757812s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.8358230590820312e-05s
INFO | --- Analysis for rkb-explorer-dotac took 2.809910297393799s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.03467535972595215s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.31684112548828125s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.021847963333129883s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007143020629882812s
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.6689300537109375e-05s
INFO | --- Analysis for rkb-explorer-ecs took 3.4233343601226807s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.04553723335266113s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.2767024040222168s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0001761913299560547s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.9025814533233643s
Availability | SPARQL endpoint availability check for epsrc took 0.044320106506347656s
Availability | VoID file availability check for epsrc took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for epsrc took 0.3265717029571533s
Reputation | Calculation of the PageRank for epsrc took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for epsrc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for epsrc took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.91278076171875e-05s
Believability | Calculation of trust value for epsrc took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 2.8325488567352295s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.03606390953063965s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.3316333293914795s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0228424072265625s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.606910705566406e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-era took 2.8673713207244873s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.048354387283325195s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.33437609672546387s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 9.918212890625e-05s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 2.8182339668273926s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.39005064964294434s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.3287694454193115s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.179115295410156e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-ft took 4.313311576843262s
Availability | SPARQL endpoint availability check for fun took 0.051360368728637695s
Availability | VoID file availability check for fun took 0.00030922889709472656s
Completeness | Calculation of interlinking completeness for fun took 0.3204076290130615s
Reputation | Calculation of the PageRank for fun took 0.022125720977783203s
Interlinking | Calculation of Degree of Connection for fun took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for fun took 0.001079559326171875s
Interlinking | Calculation of Clustering coefficient for fun took 9.250640869140625e-05s
Believability | Calculation of trust value for fun took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.739065170288086s
Availability | SPARQL endpoint availability check for gdlc took 0.0424041748046875s
Availability | VoID file availability check for gdlc took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for gdlc took 0.29773807525634766s
Reputation | Calculation of the PageRank for gdlc took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for gdlc took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for gdlc took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.67572021484375e-05s
Believability | Calculation of trust value for gdlc took 2.7418136596679688e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 2.7330334186553955s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.047620296478271484s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.2901318073272705s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00010943412780761719s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.8116893768310547s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.04131317138671875s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.3114044666290283s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001285076141357422s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-ieee took 2.823913812637329s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.041489362716674805s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.28873753547668457s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00013375282287597656s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.736173391342163s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.048375606536865234s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.3328726291656494s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.02108621597290039s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 7.367134094238281e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-italy took 2.87747859954834s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.048126220703125s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.2830774784088135s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.700920104980469e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-jisc took 2.7423338890075684s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.049396514892578125s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2916090488433838s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.022214651107788086s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0008134841918945312s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 5.054473876953125e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 2.77030086517334s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.04885673522949219s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.32193756103515625s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0001595020294189453s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.8337783813476562s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.048990726470947266s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.26766037940979004s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020900249481201172s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00014829635620117188s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-laas took 2.7542061805725098s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04385852813720703s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.28719115257263184s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.021457433700561523s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.318092346191406e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.7326366901397705s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0370783805847168s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0007808208465576172s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.28772425651550293s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.02086162567138672s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00016069412231445312s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.787590742111206s
Availability | SPARQL endpoint availability check for notube took 0.036356449127197266s
Availability | VoID file availability check for notube took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for notube took 0.29271554946899414s
Reputation | Calculation of the PageRank for notube took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for notube took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for notube took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for notube took 4.458427429199219e-05s
Believability | Calculation of trust value for notube took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.6751716136932373s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.033286333084106445s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.3314321041107178s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00012874603271484375s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.742584466934204s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.048146724700927734s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.3127329349517822s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.000152587890625s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.750685691833496s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.04894542694091797s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.31901001930236816s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.021092891693115234s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.700920104980469e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-os took 2.925914764404297s
Availability | SPARQL endpoint availability check for photos took 0.047976016998291016s
Availability | VoID file availability check for photos took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for photos took 0.2803966999053955s
Reputation | Calculation of the PageRank for photos took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for photos took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for photos took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for photos took 7.295608520507812e-05s
Believability | Calculation of trust value for photos took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-photos took 2.7789852619171143s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.0355525016784668s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.32716870307922363s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.021540164947509766s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011420249938964844s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-pisa took 2.759700298309326s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.04442167282104492s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.29726672172546387s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.0217132568359375s
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.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019502639770507812s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.8346142768859863s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.050008296966552734s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.299790620803833s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.022620677947998047s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00013685226440429688s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-resex took 2.827756881713867s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.0489501953125s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.34577202796936035s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.021403074264526367s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.369850158691406e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.887430191040039s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.042234182357788086s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.2908010482788086s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012373924255371094s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-roma took 2.7856013774871826s
Availability | SPARQL endpoint availability check for roni took 0.0481414794921875s
Availability | VoID file availability check for roni took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for roni took 0.27176976203918457s
Reputation | Calculation of the PageRank for roni took 0.0210726261138916s
Interlinking | Calculation of Degree of Connection for roni took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for roni took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for roni took 3.170967102050781e-05s
Believability | Calculation of trust value for roni took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-roni took 2.647012233734131s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.04923105239868164s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.2914607524871826s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.021569490432739258s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00021910667419433594s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.7806918621063232s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04112052917480469s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.31261563301086426s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.02226424217224121s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010776519775390625s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-ulm took 2.838014841079712s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.04582333564758301s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.2747769355773926s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.022520065307617188s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00010037422180175781s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-unlocode took 2.724381685256958s
Availability | SPARQL endpoint availability check for webconf took 0.046915531158447266s
Availability | VoID file availability check for webconf took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for webconf took 0.2925722599029541s
Reputation | Calculation of the PageRank for webconf took 0.021686315536499023s
Interlinking | Calculation of Degree of Connection for webconf took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010991096496582031s
Believability | Calculation of trust value for webconf took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-webconf took 13.260447978973389s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.0431668758392334s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.2872140407562256s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.022700786590576172s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 6.961822509765625e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-webscience took 2.7408041954040527s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.04456686973571777s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.26629114151000977s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.022580385208129883s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00020265579223632812s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-wiki took 2.704543113708496s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.04569530487060547s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.29018306732177734s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.020821809768676758s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.322166442871094e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-wordnet took 2.897852897644043s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.2994496822357178s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0006477832794189453s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 41.012969732284546s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.41415858268737793s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.3936247825622559s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.6488635540008545s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 4.313141584396362s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.1590354442596436s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.09537672996520996s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.08949971199035645s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.0791463851928711s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.08045363426208496s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.0799863338470459s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.0866248607635498s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.08967185020446777s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.17052340507507324s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.09488868713378906s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.0877373218536377s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.09473681449890137s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.432677507400513s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 8.082389831542969e-05s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.08134317398071289s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.08138418197631836s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08150267601013184s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08935117721557617s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.08234000205993652s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.17533302307128906s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.1781015396118164s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 20.642167806625366s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.08790349960327148s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.08487105369567871s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.08476996421813965s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.8813745975494385s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.0936729907989502s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 2.726733922958374s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 10.87516474723816s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.3812768459320068s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.066837549209595s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.135854721069336s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.08459258079528809s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 1.0420057773590088s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.33399057388305664s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.487701416015625e-05s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.33514404296875e-05s
INFO | --- Analysis for roceeh-road took 131.93253755569458s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.363059997558594e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0006797313690185547s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.3122122287750244s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.021953821182250977s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 2.9802322387695312e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.2159347534179688e-05s
INFO | --- Analysis for ROSHANI took 5.749886512756348s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 8.893013000488281e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.2926328182220459s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.409385681152344e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 1.239776611328125e-05s
INFO | --- Analysis for ROSHANI_SAHU took 2.6953272819519043s
Availability | SPARQL endpoint availability check for x took 0.00010824203491210938s
Availability | VoID file availability check for x took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for x took 0.26901793479919434s
Reputation | Calculation of the PageRank for x took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for x took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for x took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for x took 3.0517578125e-05s
Believability | Calculation of trust value for x took 8.106231689453125e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.7217094898223877s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.38690185546875e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.267991304397583s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.02259373664855957s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.651878356933594e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 1.3113021850585938e-05s
INFO | --- Analysis for rss-500-nif-ner-corpus took 4.4588539600372314s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.2438507080078125e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.2857217788696289s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0009744167327880859s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 8.821487426757812e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 1.3589859008789062e-05s
INFO | --- Analysis for rubentaelman took 3.214592218399048s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.363059997558594e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.34017229080200195s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.58306884765625e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.2874603271484375e-05s
INFO | --- Analysis for rubenverborgh took 3.373471260070801s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.1399714946747s
Availability | VoID file availability check for Russian Universities Specialities took 0.0012879371643066406s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.3600349426269531s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.021054744720458984s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.410743713378906e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.049041748046875e-05s
INFO | --- Analysis for russian-universities-specialities took 681.5322380065918s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 3.744661331176758s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.3166201114654541s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.022546052932739258s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.0994415283203125e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 1.049041748046875e-05s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 8.701570510864258s
Availability | SPARQL endpoint availability check for SALDO-RDF took 0.9864351749420166s
Availability | VoID file availability check for SALDO-RDF took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.34111881256103516s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.6716461181640625e-05s
Believability | Calculation of trust value for SALDO-RDF took 5.9604644775390625e-06s
INFO | --- Analysis for saldo-rdf took 5.767132759094238s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6538796424865723s
Availability | VoID file availability check for SALDOM-RDF took 0.0004074573516845703s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2999410629272461s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020812511444091797s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 4.0531158447265625e-05s
Believability | Calculation of trust value for SALDOM-RDF took 7.3909759521484375e-06s
INFO | --- Analysis for saldom-rdf took 5.18419075012207s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.315376281738281e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.4623398780822754s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010585784912109375s
Believability | Calculation of trust value for Salzburgerland DE took 1.0251998901367188e-05s
INFO | --- Analysis for salzburgerland-com-de took 8.468778371810913s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 9.298324584960938e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.3032975196838379s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00010633468627929688s
Believability | Calculation of trust value for Salzburgerland EN took 1.1444091796875e-05s
INFO | --- Analysis for salzburgerland-com-en took 3.094010591506958s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.172325134277344e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.31684374809265137s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010156631469726562s
Believability | Calculation of trust value for Salzburgerland IT took 9.775161743164062e-06s
INFO | --- Analysis for salzburgerland-com-it took 3.199345588684082s
Availability | SPARQL endpoint availability check for sandrart.net took 4.291534423828125e-05s
Availability | VoID file availability check for sandrart.net took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.2961862087249756s
Reputation | Calculation of the PageRank for sandrart.net took 0.02081465721130371s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.890296936035156e-05s
Believability | Calculation of trust value for sandrart.net took 1.3113021850585938e-05s
INFO | --- Analysis for sandrart-net took 3.938020706176758s
Availability | SPARQL endpoint availability check for Taxons  took 0.2527320384979248s
Availability | VoID file availability check for Taxons  took 0.0004858970642089844s
Extra | Recovery of all triples for Taxons  took 18.30368208885193s
Performance | Total latancy measurement for Taxons  took 0.4518463611602783s
Amount of data | Number of triples check for Taxons  took 2.062946081161499s
Interoperability | New terms check for Taxons  took 1.8044798374176025s
Versatility | Languages check for Taxons  took 38.96615266799927s
Interpretability | Number of blank nodes check for Taxons  took 1.0294291973114014s
Security | Check HTTPS for Taxons  took 0.20441150665283203s
Interpretability | RDF structures check for Taxons  took 1.071192979812622s
Versatility | Serialization formats check for Taxons  took 0.5432183742523193s
Availability | RDF dump link check for Taxons  took 0.2954435348510742s
License | MR license check for Taxons  took 1.9282238483428955s
License | HR license check for Taxons  took 2.1067676544189453s
Amount of data | Number of property check for Taxons  took 0.11701226234436035s
Understandability | Number of label check for Taxons  took 2.7826740741729736s
Understandability | URI regex check for Taxons  took 0.7584335803985596s
Understandability | Vocabs check for Taxons  took 0.24659323692321777s
Verifiability | Authors check for Taxons  took 0.09231305122375488s
Verifiability | Publishers check for Taxons  took 0.09509754180908203s
Performance | Throughput check for Taxons  took 10.463349342346191s
Amount of data | Check the number of entities for Taxons  took 7.343292236328125e-05s
Verifiability | Contribs. check for Taxons  took 0.08791685104370117s
Interlinking | sameAs chians check for Taxons  took 0.16803359985351562s
Interlinking | skos check for Taxons  took 0.1613311767578125s
Interlinking | skos check for Taxons  took 0.09020590782165527s
Timeliness | dataset update frequency check for Taxons  took 0.4419858455657959s
Currency | Creation date check for Taxons  took 0.20337247848510742s
Currency | Modification date check for Taxons  took 0.22089457511901855s
Rep.Conc. | URIs length for Taxons  took 7.491950750350952s
Interoperability | New vocabularies check for Taxons  took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.12240076065063477s
Accuracy | Check Functional Property for Taxons  took 0.3928093910217285s
Accuracy | Check Inverse Functional Property for Taxons  took 0.369431734085083s
Accuracy | Check Empty annotation labels for Taxons  took 4.035195350646973s
Accuracy | Check White space in annotation for Taxons  took 0.3090388774871826s
Accuracy | Check Datatype consistency for Taxons  took 0.26523351669311523s
Consistency | Disjoint class check for Taxons  took 0.10529446601867676s
Consistency | Check Misplaced properties for Taxons  took 4.343785524368286s
Consistency | Misplaced classes for Taxons  took 0.9616775512695312s
Consistency | Check Ontology hijacking for Taxons  took 3.5919392108917236s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.2735142707824707s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.087196588516235s
Conciseness | Check Extensional conciseness for Taxons  took 0.2926352024078369s
Conciseness | Check Intensional conciseness for Taxons  took 0.2014636993408203s
Security | Sign check for Taxons  took 1.0104396343231201s
Availability | Check URIs Dereferenciability for Taxons  took 1731.274611234665s
Completeness | Calculation of interlinking completeness for Taxons  took 0.5835926532745361s
Reputation | Calculation of the PageRank for Taxons  took 0.021442413330078125s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Taxons  took 0.00013685226440429688s
Interoperability | Check the re-using of existing vocabs for Taxons  took 1.6689300537109375e-06s
Believability | Calculation of trust value for Taxons  took 1.0251998901367188e-05s
INFO | --- Analysis for sandre took 1914.2501196861267s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.710127592086792s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.356203556060791s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.1948089599609375e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.1444091796875e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 7.535057544708252s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 265.1317083835602s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.37086033821105957s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 3.62396240234375e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.049041748046875e-05s
INFO | --- Analysis for santillana_guide_dataset took 669.9603970050812s
Availability | SPARQL endpoint availability check for SATAR test  took 9.393692016601562e-05s
Availability | VoID file availability check for SATAR test  took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.32050228118896484s
Reputation | Calculation of the PageRank for SATAR test  took 0.022291183471679688s
Interlinking | Calculation of Degree of Connection for SATAR test  took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 3.147125244140625e-05s
Believability | Calculation of trust value for SATAR test  took 9.775161743164062e-06s
INFO | --- Analysis for SATAR_test took 5.123981237411499s
Availability | SPARQL endpoint availability check for SCBG Data took 21.91404366493225s
Availability | VoID file availability check for SCBG Data took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.31771397590637207s
Reputation | Calculation of the PageRank for SCBG Data took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for SCBG Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.273124694824219e-05s
Believability | Calculation of trust value for SCBG Data took 1.0251998901367188e-05s
INFO | --- Analysis for SCBG-Data took 54.82533860206604s
Availability | SPARQL endpoint availability check for Schemantra took 8.559226989746094e-05s
Availability | VoID file availability check for Schemantra took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Schemantra took 0.2884714603424072s
Reputation | Calculation of the PageRank for Schemantra took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.123283386230469e-05s
Believability | Calculation of trust value for Schemantra took 1.0013580322265625e-05s
INFO | --- Analysis for Schemantra took 2.6768200397491455s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.4775874614715576s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.29638147354125977s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.4332275390625e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.0013580322265625e-05s
INFO | --- Analysis for schemapedia took 4.487269878387451s
Availability | SPARQL endpoint availability check for Scholarometer took 4.1484832763671875e-05s
Availability | VoID file availability check for Scholarometer took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.2781364917755127s
Reputation | Calculation of the PageRank for Scholarometer took 0.021140098571777344s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.821487426757812e-05s
Believability | Calculation of trust value for Scholarometer took 1.1444091796875e-05s
INFO | --- Analysis for scholarometer took 7.444970369338989s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 8.630752563476562e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.3034787178039551s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.021908044815063477s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.170967102050781e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 1.0013580322265625e-05s
INFO | --- Analysis for scoreboard took 4.807282209396362s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 8.749961853027344e-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.00075531005859375s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.31772875785827637s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020743370056152344s
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.049041748046875e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.123283386230469e-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.2636184692382812e-05s
INFO | --- Analysis for SDDEC took 28.973840713500977s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 8.845329284667969e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.283275842666626s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.314018249511719e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0013580322265625e-05s
INFO | --- Analysis for SDG took 3.5593812465667725s
Availability | SPARQL endpoint availability check for sears.com took 9.298324584960938e-05s
Availability | VoID file availability check for sears.com took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for sears.com took 0.28601694107055664s
Reputation | Calculation of the PageRank for sears.com took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for sears.com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for sears.com took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.771087646484375e-05s
Believability | Calculation of trust value for sears.com took 1.0251998901367188e-05s
INFO | --- Analysis for sears took 5.694253921508789s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.09190678596496582s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.29843616485595703s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020919084548950195s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.344650268554688e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 7.867813110351562e-06s
INFO | --- Analysis for sec-rdfabout took 6.597486734390259s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.755114793777466s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.31758928298950195s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.749961853027344e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for secold took 167.80792999267578s
Availability | SPARQL endpoint availability check for semanlink took 4.76837158203125e-05s
Availability | VoID file availability check for semanlink took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for semanlink took 0.3177313804626465s
Reputation | Calculation of the PageRank for semanlink took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for semanlink took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.0001430511474609375s
Believability | Calculation of trust value for semanlink took 1.1920928955078125e-05s
INFO | --- Analysis for semanlink took 3.863914728164673s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.08362340927124023s
Availability | VoID file availability check for Semantic Universe Data took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.3110170364379883s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 2.86102294921875e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.0013580322265625e-05s
INFO | --- Analysis for semantic-universe took 2.732936382293701s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.721663236618042s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.30657124519348145s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011873245239257812s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.0251998901367188e-05s
INFO | --- Analysis for semantic-web-dog-food took 83.6676516532898s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 6.985664367675781e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.2946491241455078s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.02073383331298828s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.7206878662109375e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.430511474609375e-05s
INFO | --- Analysis for semantic-web-grundlagen took 3.2270679473876953s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 8.916854858398438e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.000720977783203125s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.2896144390106201s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.021880626678466797s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 9.298324584960938e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 4.5299530029296875e-06s
INFO | --- Analysis for semantic-xbrl took 3.6125988960266113s
Availability | SPARQL endpoint availability check for Semantic Quran took 7.043902397155762s
Availability | VoID file availability check for Semantic Quran took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Semantic Quran took 0.29967498779296875s
Reputation | Calculation of the PageRank for Semantic Quran took 0.02200460433959961s
Interlinking | Calculation of Degree of Connection for Semantic Quran took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Semantic Quran took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Semantic Quran took 7.557868957519531e-05s
Believability | Calculation of trust value for Semantic Quran took 1.2874603271484375e-05s
INFO | --- Analysis for semanticquran took 16.422528743743896s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.38690185546875e-05s
Availability | VoID file availability check for SemanticTweet took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.2932474613189697s
Reputation | Calculation of the PageRank for SemanticTweet took 0.021146297454833984s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.6743621826171875e-05s
Believability | Calculation of trust value for SemanticTweet took 1.0728836059570312e-05s
INFO | --- Analysis for semantictweet took 2.851785898208618s
Availability | SPARQL endpoint availability check for semanticweb.org took 9.703636169433594e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.3184223175048828s
Reputation | Calculation of the PageRank for semanticweb.org took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.724761962890625e-05s
Believability | Calculation of trust value for semanticweb.org took 1.4066696166992188e-05s
INFO | --- Analysis for semanticweb-org took 23.120573043823242s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.10446667671203613s
Availability | VoID file availability check for Semantic CrunchBase took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.30328917503356934s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.02151179313659668s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.842613220214844e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.2159347534179688e-05s
INFO | --- Analysis for semsol-crunchbase took 2.9694769382476807s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.2558326721191406s
Availability | VoID file availability check for SentimentWortschatz took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.3303718566894531s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.0210568904876709s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 2.9087066650390625e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.220008850097656e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.0013580322265625e-05s
INFO | --- Analysis for sentiws took 4.397719860076904s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.14697504043579s
Availability | VoID file availability check for seoul-bike-data took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.27844786643981934s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.02131509780883789s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.933906555175781e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.0728836059570312e-05s
INFO | --- Analysis for seoul-bike-data took 73.16746520996094s
Availability | SPARQL endpoint availability check for Serendipity took 3.9428789615631104s
Availability | VoID file availability check for Serendipity took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Serendipity took 0.3274540901184082s
Reputation | Calculation of the PageRank for Serendipity took 0.021515846252441406s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.414817810058594e-05s
Believability | Calculation of trust value for Serendipity took 1.4543533325195312e-05s
INFO | --- Analysis for serendipity took 10.534871816635132s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.1961669921875e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.31803464889526367s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020654916763305664s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.170967102050781e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 9.775161743164062e-06s
INFO | --- Analysis for Sherry_Wine took 3.0035886764526367s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.696846008300781e-05s
Availability | VoID file availability check for Sherry Wine took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.27579617500305176s
Reputation | Calculation of the PageRank for Sherry Wine took 0.02075934410095215s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.0517578125e-05s
Believability | Calculation of trust value for Sherry Wine took 1.0728836059570312e-05s
INFO | --- Analysis for Sherry_Wine_ took 2.668153762817383s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.20064377784729004s
Availability | VoID file availability check for Shoah victims? names took 0.2959563732147217s
Extra | Recovery of all triples for Shoah victims? names took 0.9963476657867432s
Performance | Total latancy measurement for Shoah victims? names took 0.36892127990722656s
Amount of data | Number of triples check for Shoah victims? names took 1.2128856182098389s
Interoperability | New terms check for Shoah victims? names took 1.6299054622650146s
Versatility | Languages check for Shoah victims? names took 18.072115898132324s
Interpretability | Number of blank nodes check for Shoah victims? names took 6.022733449935913s
Security | Check HTTPS for Shoah victims? names took 0.19901657104492188s
Interpretability | RDF structures check for Shoah victims? names took 0.21774673461914062s
Versatility | Serialization formats check for Shoah victims? names took 0.23614025115966797s
Availability | RDF dump link check for Shoah victims? names took 0.1313638687133789s
License | MR license check for Shoah victims? names took 0.30588197708129883s
License | HR license check for Shoah victims? names took 8.115759134292603s
Amount of data | Number of property check for Shoah victims? names took 0.12247490882873535s
Understandability | Number of label check for Shoah victims? names took 0.7816989421844482s
Understandability | URI regex check for Shoah victims? names took 0.369584321975708s
Understandability | Vocabs check for Shoah victims? names took 0.08510518074035645s
Verifiability | Authors check for Shoah victims? names took 0.16079950332641602s
Verifiability | Publishers check for Shoah victims? names took 0.13466191291809082s
Performance | Throughput check for Shoah victims? names took 10.688679933547974s
Amount of data | Check the number of entities for Shoah victims? names took 7.05718994140625e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.09279513359069824s
Interlinking | sameAs chians check for Shoah victims? names took 0.12890148162841797s
Interlinking | skos check for Shoah victims? names took 0.19115090370178223s
Interlinking | skos check for Shoah victims? names took 0.06250667572021484s
Timeliness | dataset update frequency check for Shoah victims? names took 0.22811627388000488s
Currency | Creation date check for Shoah victims? names took 0.17510318756103516s
Currency | Modification date check for Shoah victims? names took 0.177764892578125s
Rep.Conc. | URIs length for Shoah victims? names took 2.5905709266662598s
Interoperability | New vocabularies check for Shoah victims? names took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.10042452812194824s
Accuracy | Check Functional Property for Shoah victims? names took 0.12272429466247559s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.09003710746765137s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.4122457504272461s
Accuracy | Check White space in annotation for Shoah victims? names took 0.028433561325073242s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.02830791473388672s
Consistency | Disjoint class check for Shoah victims? names took 0.18377208709716797s
Consistency | Check Misplaced properties for Shoah victims? names took 1.9689922332763672s
Consistency | Misplaced classes for Shoah victims? names took 0.22671198844909668s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.5787975788116455s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.249657392501831s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.004967212677002s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.03365731239318848s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.12659764289855957s
Security | Sign check for Shoah victims? names took 0.33835792541503906s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1000.9255633354187s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.6931731700897217s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.02257227897644043s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 5.4836273193359375e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 2.1457672119140625e-06s
Believability | Calculation of trust value for Shoah victims? names took 1.2636184692382812e-05s
INFO | --- Analysis for shoah-victims-names took 1118.0582995414734s
Availability | SPARQL endpoint availability check for Person took 4.4345855712890625e-05s
Availability | VoID file availability check for Person took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Person took 0.2730538845062256s
Reputation | Calculation of the PageRank for Person took 0.02298879623413086s
Interlinking | Calculation of Degree of Connection for Person took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Person took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Person took 3.361701965332031e-05s
Believability | Calculation of trust value for Person took 1.430511474609375e-05s
INFO | --- Analysis for Shripriya_Dubey took 2.6848909854888916s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 8.797645568847656e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.2720479965209961s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.0218353271484375s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.337860107421875e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 1.4781951904296875e-05s
INFO | --- Analysis for Shutterstock took 2.7030012607574463s
Availability | SPARQL endpoint availability check for SIMPLE took 0.00011610984802246094s
Availability | VoID file availability check for SIMPLE took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.29836320877075195s
Reputation | Calculation of the PageRank for SIMPLE took 0.021773338317871094s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 5.4836273193359375e-05s
Believability | Calculation of trust value for SIMPLE took 1.3589859008789062e-05s
INFO | --- Analysis for simple took 8.347357749938965s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.952085494995117s
Availability | VoID file availability check for SITC-V4 took 0.0007796287536621094s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.2969660758972168s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02223825454711914s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.100799560546875e-05s
Believability | Calculation of trust value for SITC-V4 took 8.344650268554688e-06s
INFO | --- Analysis for sitc-v4 took 125.05330228805542s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 8.940696716308594e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0008132457733154297s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.31846189498901367s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.021098613739013672s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.482269287109375e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0967254638671875e-05s
INFO | --- Analysis for sli_galnet_rdf took 12.89818000793457s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.3392181396484375e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.28335022926330566s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.0213623046875s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.147125244140625e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.049041748046875e-05s
INFO | --- Analysis for slideshare2rdf took 2.839413642883301s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.46814632415771484s
Availability | VoID file availability check for Linked Stage Graph took 0.0005497932434082031s
Extra | Recovery of all triples for Linked Stage Graph took 1.850013256072998s
Performance | Total latancy measurement for Linked Stage Graph took 1.2825570106506348s
Amount of data | Number of triples check for Linked Stage Graph took 0.25118398666381836s
Interoperability | New terms check for Linked Stage Graph took 1.597130298614502s
Versatility | Languages check for Linked Stage Graph took 0.695357084274292s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.28334641456604004s
Security | Check HTTPS for Linked Stage Graph took 0.18038320541381836s
Interpretability | RDF structures check for Linked Stage Graph took 0.49840378761291504s
Versatility | Serialization formats check for Linked Stage Graph took 0.32569241523742676s
Availability | RDF dump link check for Linked Stage Graph took 0.25864386558532715s
License | MR license check for Linked Stage Graph took 0.4959697723388672s
License | HR license check for Linked Stage Graph took 1.7885620594024658s
Amount of data | Number of property check for Linked Stage Graph took 0.2800765037536621s
Understandability | Number of label check for Linked Stage Graph took 0.7875161170959473s
Understandability | URI regex check for Linked Stage Graph took 0.6884255409240723s
Understandability | Vocabs check for Linked Stage Graph took 0.34555816650390625s
Verifiability | Authors check for Linked Stage Graph took 0.29233431816101074s
Verifiability | Publishers check for Linked Stage Graph took 0.25415658950805664s
Performance | Throughput check for Linked Stage Graph took 11.029463529586792s
Amount of data | Check the number of entities for Linked Stage Graph took 8.440017700195312e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.2529940605163574s
Interlinking | sameAs chians check for Linked Stage Graph took 0.33277106285095215s
Interlinking | skos check for Linked Stage Graph took 0.3173243999481201s
Interlinking | skos check for Linked Stage Graph took 0.25773119926452637s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.43294405937194824s
Currency | Creation date check for Linked Stage Graph took 0.5266356468200684s
Currency | Modification date check for Linked Stage Graph took 0.5207066535949707s
Rep.Conc. | URIs length for Linked Stage Graph took 1.5956459045410156s
Interoperability | New vocabularies check for Linked Stage Graph took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.256633996963501s
Accuracy | Check Functional Property for Linked Stage Graph took 0.46595239639282227s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.49604058265686035s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.807732343673706s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.024056673049926758s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.03194928169250488s
Consistency | Disjoint class check for Linked Stage Graph took 0.2501342296600342s
Consistency | Check Misplaced properties for Linked Stage Graph took 1.0364437103271484s
Consistency | Misplaced classes for Linked Stage Graph took 0.6116845607757568s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.069218635559082s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.2914855480194092s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.8517320156097412s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.03191375732421875s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.6276001930236816s
Security | Sign check for Linked Stage Graph took 0.641150712966919s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 4516.825735330582s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.8859844207763672s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.2233891487121582s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 6.365776062011719e-05s
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.430511474609375e-05s
INFO | --- Analysis for slod took 4586.26412820816s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.5883622169494629s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0005002021789550781s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 105.68872380256653s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.961033821105957s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 9.040124893188477s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.049457311630249s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.2009949684143s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.056999683380127s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.3648874759674072s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 8.001986026763916s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.3796050548553467s
License | MR license check for Smart Points Of Interest @PSNC took 0.9456624984741211s
License | HR license check for Smart Points Of Interest @PSNC took 300.15863513946533s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.21103525161743164s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.9829447269439697s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 1.2140731811523438s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.6463942527770996s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.21252942085266113s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.2610743045806885s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.587429761886597s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 7.200241088867188e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.18662095069885254s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.19107913970947266s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.5236389636993408s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.41373705863952637s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 5.471588373184204s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.4764676094055176s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.2321021556854248s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 156.6640956401825s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.1822648048400879s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.4308900833129883s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.4661269187927246s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 35.69921517372131s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.688727378845215s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.6581332683563232s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.2166914939880371s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 85.9269471168518s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.5202157497406s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 44.08291244506836s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.3469505310058594s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 86.76243042945862s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7956559658050537s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.59346604347229s
Security | Sign check for Smart Points Of Interest @PSNC took 1.6216094493865967s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 9.913795232772827s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.41562461853027344s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.020961999893188477s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00010514259338378906s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.0728836059570312e-05s
INFO | --- Analysis for Smart_POI_dataset took 2266.3254120349884s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.9109930992126465s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0008375644683837891s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.29439282417297363s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020883560180664062s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.8623809814453125e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.1682510375976562e-05s
INFO | --- Analysis for smartlink took 15.41309404373169s
Availability | SPARQL endpoint availability check for SNIK took 0.3931849002838135s
Availability | VoID file availability check for SNIK took 0.0007798671722412109s
Extra | Recovery of all triples for SNIK took 3.228182077407837s
Performance | Total latancy measurement for SNIK took 0.9348776340484619s
Amount of data | Number of triples check for SNIK took 0.19324660301208496s
Interoperability | New terms check for SNIK took 1.4083857536315918s
Versatility | Languages check for SNIK took 0.2123243808746338s
Interpretability | Number of blank nodes check for SNIK took 0.20816469192504883s
Interpretability | RDF structures check for SNIK took 0.2167067527770996s
Versatility | Serialization formats check for SNIK took 0.21492290496826172s
Availability | RDF dump link check for SNIK took 0.21303915977478027s
License | MR license check for SNIK took 0.21960139274597168s
License | HR license check for SNIK took 0.23075485229492188s
Amount of data | Number of property check for SNIK took 0.17546963691711426s
Understandability | Number of label check for SNIK took 0.22461390495300293s
Understandability | URI regex check for SNIK took 0.3988969326019287s
Understandability | Vocabs check for SNIK took 0.18581676483154297s
Verifiability | Authors check for SNIK took 0.1962571144104004s
Verifiability | Publishers check for SNIK took 0.20274758338928223s
Performance | Throughput check for SNIK took 11.24190354347229s
Amount of data | Check the number of entities for SNIK took 6.985664367675781e-05s
Verifiability | Contribs. check for SNIK took 0.20177412033081055s
Interlinking | sameAs chians check for SNIK took 0.19174647331237793s
Interlinking | skos check for SNIK took 0.1857461929321289s
Interlinking | skos check for SNIK took 0.19818854331970215s
Timeliness | dataset update frequency check for SNIK took 0.2061307430267334s
Currency | Creation date check for SNIK took 0.41664648056030273s
Currency | Modification date check for SNIK took 0.3796555995941162s
Rep.Conc. | URIs length for SNIK took 1.4367055892944336s
Interoperability | New vocabularies check for SNIK took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.18242406845092773s
Accuracy | Check Functional Property for SNIK took 0.21486568450927734s
Accuracy | Check Inverse Functional Property for SNIK took 0.19739389419555664s
Accuracy | Check Empty annotation labels for SNIK took 0.6136116981506348s
Accuracy | Check White space in annotation for SNIK took 0.02734375s
Accuracy | Check Datatype consistency for SNIK took 0.21796584129333496s
Consistency | Disjoint class check for SNIK took 0.19682693481445312s
Consistency | Check Misplaced properties for SNIK took 0.6421010494232178s
Consistency | Misplaced classes for SNIK took 0.6894183158874512s
Consistency | Check Ontology hijacking for SNIK took 1.7673087120056152s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.2270748615264893s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.4823811054229736s
Conciseness | Check Extensional conciseness for SNIK took 0.156327486038208s
Conciseness | Check Intensional conciseness for SNIK took 0.31343722343444824s
Security | Sign check for SNIK took 0.19582891464233398s
Availability | Check URIs Dereferenciability for SNIK took 1652.8262450695038s
Completeness | Calculation of interlinking completeness for SNIK took 0.7006628513336182s
Reputation | Calculation of the PageRank for SNIK took 0.02153921127319336s
Interlinking | Calculation of Degree of Connection for SNIK took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for SNIK took 7.271766662597656e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.6689300537109375e-06s
Believability | Calculation of trust value for SNIK took 1.0251998901367188e-05s
INFO | --- Analysis for snik took 1707.561451435089s
Availability | SPARQL endpoint availability check for SocialLink took 1.2741167545318604s
Availability | VoID file availability check for SocialLink took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for SocialLink took 0.2927684783935547s
Reputation | Calculation of the PageRank for SocialLink took 0.0215609073638916s
Interlinking | Calculation of Degree of Connection for SocialLink took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SocialLink took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.605552673339844e-05s
Believability | Calculation of trust value for SocialLink took 1.1205673217773438e-05s
INFO | --- Analysis for SocialLink took 5.120086431503296s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 8.893013000488281e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.31418561935424805s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.0279159545898438e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.0251998901367188e-05s
INFO | --- Analysis for SocialRoles took 10.24759292602539s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 1.0650913715362549s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0007002353668212891s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 17.104448080062866s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.48615193367004395s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.18456697463989258s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.5156245231628418s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.3915278911590576s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.17614150047302246s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.3375062942504883s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.14441585540771484s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.2509903907775879s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.7590017318725586s
License | MR license check for Social Semantic Web Thesaurus took 0.13824868202209473s
License | HR license check for Social Semantic Web Thesaurus took 0.1157371997833252s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.1139976978302002s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.12312126159667969s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.17766785621643066s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.11824774742126465s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.1303727626800537s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.12909793853759766s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.485120296478271s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 7.390975952148438e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.12100791931152344s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.11243343353271484s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.1251077651977539s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.08954668045043945s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.08948612213134766s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.18927669525146484s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.20133280754089355s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.4577789306640625s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 0.7418982982635498s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.12363958358764648s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.08748078346252441s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.08730697631835938s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.4542810916900635s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012332439422607422s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.09489703178405762s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.25861263275146484s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.08164691925048828s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.046888828277588s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.4358270168304443s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00016236305236816406s
Security | Sign check for Social Semantic Web Thesaurus took 0.09511709213256836s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 110.875821352005s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.39589786529541016s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 0.6481959819793701s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.430511474609375e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 307.7446942329407s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.34000325202941895s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0005164146423339844s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 125.79448676109314s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9461798667907715s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.150763750076294s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.253404378890991s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2153549194336s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.913621425628662s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20137691497802734s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 6.9738757610321045s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.38753747940063477s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2081279754638672s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2479820251465s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2129805088043213s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.162604570388794s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.6088192462921143s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1786792278289795s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.22694730758666992s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.23995757102966309s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.592313289642334s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.653236389160156e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20234107971191406s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21448826789855957s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.42455029487609863s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.42707014083862305s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 5.2629899978637695s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5067963600158691s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2506589889526367s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 152.11609268188477s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19051003456115723s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1934521198272705s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1929309368133545s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 41.217310667037964s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.706451654434204s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.665940999984741s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20736932754516602s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 86.30560088157654s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.537884712219238s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 37.96337628364563s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.3351621627807617s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 86.54685997962952s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.820882797241211s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5682482719421387s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20914220809936523s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.342630863189697s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.38951849937438965s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.02205657958984375s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.124641418457031e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.5299530029296875e-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 2270.164642095566s
Availability | SPARQL endpoint availability check for terrorrist ontology took 0.00010848045349121094s
Availability | VoID file availability check for terrorrist ontology took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.2828848361968994s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0014684200286865234s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.3113021850585938e-05s
INFO | --- Analysis for somya_omer took 2.7500710487365723s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.2438507080078125e-05s
Availability | VoID file availability check for Sonclubcx took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.29638004302978516s
Reputation | Calculation of the PageRank for Sonclubcx took 0.02193284034729004s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.0728836059570312e-05s
Believability | Calculation of trust value for Sonclubcx took 1.811981201171875e-05s
INFO | --- Analysis for sonclubcx took 4.080464839935303s
Availability | SPARQL endpoint availability check for SORS took 4.2438507080078125e-05s
Availability | VoID file availability check for SORS took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for SORS took 0.2864091396331787s
Reputation | Calculation of the PageRank for SORS took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for SORS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SORS took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for SORS took 4.76837158203125e-05s
Believability | Calculation of trust value for SORS took 7.62939453125e-06s
INFO | --- Analysis for sors took 12.849431276321411s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 0.00010132789611816406s
Availability | VoID file availability check for southampton-ac-uk took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.3059203624725342s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.021578550338745117s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.059906005859375e-05s
Believability | Calculation of trust value for southampton-ac-uk took 1.1682510375976562e-05s
INFO | --- Analysis for southampton-ac-uk took 4.252816438674927s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.1604089736938477s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0003886222839355469s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.3001375198364258s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 1.239776611328125e-05s
INFO | --- Analysis for southampton-ac-uk-apps took 11.033107995986938s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 0.00010704994201660156s
Availability | VoID file availability check for ECS Southampton EPrints took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.2945270538330078s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 8.916854858398438e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.239776611328125e-05s
INFO | --- Analysis for southampton-ecs-eprints took 2.770768880844116s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5140018463134766s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0004673004150390625s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 160.07296347618103s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.2047185897827148s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.1200625896453857s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.2096216678619385s
Versatility | Languages check for Spanish Linguistic Datasets took 44.96323347091675s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.2033822536468506s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.144866943359375s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.2966303825378418s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.30156779289245605s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.2842726707458496s
License | MR license check for Spanish Linguistic Datasets took 0.29108214378356934s
License | HR license check for Spanish Linguistic Datasets took 0.7672455310821533s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.279468297958374s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.33704566955566406s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5826799869537354s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.2964973449707031s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.28264856338500977s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.2790679931640625s
Performance | Throughput check for Spanish Linguistic Datasets took 11.277389526367188s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 8.58306884765625e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.304166316986084s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.3114967346191406s
Interlinking | skos check for Spanish Linguistic Datasets took 0.30274224281311035s
Interlinking | skos check for Spanish Linguistic Datasets took 0.24239253997802734s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.295520544052124s
Currency | Creation date check for Spanish Linguistic Datasets took 0.6197628974914551s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5827028751373291s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 57.71424198150635s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.3089027404785156s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.270005464553833s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.28153300285339355s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.927422046661377s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010315179824829102s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.6505954265594482s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.28374719619750977s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.698261022567749s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.455427885055542s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 43.880908727645874s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.5225958824157715s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.676527976989746s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 3.00641131401062s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.2899281978607178s
Security | Sign check for Spanish Linguistic Datasets took 0.28530097007751465s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 10.799017906188965s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.4566965103149414s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021263599395751953s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.3855438232421875e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 1.9073486328125e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.1444091796875e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 411.649605512619s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.05670356750488281s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.3067286014556885s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.7206878662109375e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 1.2636184692382812e-05s
INFO | --- Analysis for sparql-endpoint-status took 2.7703592777252197s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 0.00010824203491210938s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.3282146453857422s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.344650268554688e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.239776611328125e-05s
INFO | --- Analysis for springernaturescigraph took 3.428657054901123s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.2438507080078125e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.3191945552825928s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020123004913330078s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.457069396972656e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 7.867813110351562e-06s
INFO | --- Analysis for srcmf took 8.357168912887573s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.3295783996582031s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0005640983581542969s
Extra | Recovery of all triples for Lexicon of Syntactic and Semantic Framework took 1.1914401054382324s
Performance | Total latancy measurement for Lexicon of Syntactic and Semantic Framework took 0.7467014789581299s
Amount of data | Number of triples check for Lexicon of Syntactic and Semantic Framework took 0.13849210739135742s
Interoperability | New terms check for Lexicon of Syntactic and Semantic Framework took 1.3640515804290771s
Versatility | Languages check for Lexicon of Syntactic and Semantic Framework took 0.1615922451019287s
Interpretability | Number of blank nodes check for Lexicon of Syntactic and Semantic Framework took 0.1569533348083496s
Security | Check HTTPS for Lexicon of Syntactic and Semantic Framework took 0.10257267951965332s
Interpretability | RDF structures check for Lexicon of Syntactic and Semantic Framework took 0.14641666412353516s
Versatility | Serialization formats check for Lexicon of Syntactic and Semantic Framework took 0.15541553497314453s
Availability | RDF dump link check for Lexicon of Syntactic and Semantic Framework took 0.14192581176757812s
License | MR license check for Lexicon of Syntactic and Semantic Framework took 0.1613178253173828s
License | HR license check for Lexicon of Syntactic and Semantic Framework took 0.17032861709594727s
Amount of data | Number of property check for Lexicon of Syntactic and Semantic Framework took 0.1479642391204834s
Understandability | Number of label check for Lexicon of Syntactic and Semantic Framework took 0.15782403945922852s
Understandability | URI regex check for Lexicon of Syntactic and Semantic Framework took 0.3148794174194336s
Understandability | Vocabs check for Lexicon of Syntactic and Semantic Framework took 0.15053701400756836s
Verifiability | Authors check for Lexicon of Syntactic and Semantic Framework took 0.15239977836608887s
Verifiability | Publishers check for Lexicon of Syntactic and Semantic Framework took 0.14292311668395996s
Performance | Throughput check for Lexicon of Syntactic and Semantic Framework took 10.552783966064453s
Amount of data | Check the number of entities for Lexicon of Syntactic and Semantic Framework took 7.033348083496094e-05s
Verifiability | Contribs. check for Lexicon of Syntactic and Semantic Framework took 0.13263869285583496s
Interlinking | sameAs chians check for Lexicon of Syntactic and Semantic Framework took 0.14716029167175293s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.14466142654418945s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.16060495376586914s
Timeliness | dataset update frequency check for Lexicon of Syntactic and Semantic Framework took 0.16997194290161133s
Currency | Creation date check for Lexicon of Syntactic and Semantic Framework took 0.2882239818572998s
Currency | Modification date check for Lexicon of Syntactic and Semantic Framework took 0.30116748809814453s
Rep.Conc. | URIs length for Lexicon of Syntactic and Semantic Framework took 0.46589207649230957s
Interoperability | New vocabularies check for Lexicon of Syntactic and Semantic Framework took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Lexicon of Syntactic and Semantic Framework took 0.15710783004760742s
Accuracy | Check Functional Property for Lexicon of Syntactic and Semantic Framework took 0.15740585327148438s
Accuracy | Check Inverse Functional Property for Lexicon of Syntactic and Semantic Framework took 0.1498103141784668s
Accuracy | Check Empty annotation labels for Lexicon of Syntactic and Semantic Framework took 0.153350830078125s
Accuracy | Check White space in annotation for Lexicon of Syntactic and Semantic Framework took 0.0003147125244140625s
Accuracy | Check Datatype consistency for Lexicon of Syntactic and Semantic Framework took 0.0332033634185791s
Consistency | Disjoint class check for Lexicon of Syntactic and Semantic Framework took 0.166412353515625s
Consistency | Check Misplaced properties for Lexicon of Syntactic and Semantic Framework took 0.2826817035675049s
Consistency | Misplaced classes for Lexicon of Syntactic and Semantic Framework took 0.20439362525939941s
Consistency | Check Ontology hijacking for Lexicon of Syntactic and Semantic Framework took 1.4919898509979248s
Consistency | Check Invalid usage of undefined classes for Lexicon of Syntactic and Semantic Framework took 1.2961018085479736s
Consistency | Check Invalid usage of undefined properties for Lexicon of Syntactic and Semantic Framework took 1.4401540756225586s
Conciseness | Check Extensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.022087812423706055s
Conciseness | Check Intensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.15236830711364746s
Security | Sign check for Lexicon of Syntactic and Semantic Framework took 0.16736102104187012s
Availability | Check URIs Dereferenciability for Lexicon of Syntactic and Semantic Framework took 270.78959679603577s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.34650468826293945s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020761966705322266s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for Lexicon of Syntactic and Semantic Framework took 1.9073486328125e-06s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.0251998901367188e-05s
INFO | --- Analysis for ssf took 311.039443731308s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 8.988380432128906e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.29416322708129883s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.02151346206665039s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.790855407714844e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 1.3828277587890625e-05s
INFO | --- Analysis for st-andrews-resource-lists took 3.3084263801574707s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 6.0558319091796875e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.30248379707336426s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020920515060424805s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.790855407714844e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.775161743164062e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 3.3703582286834717s
Availability | SPARQL endpoint availability check for Stammbuch took 8.630752563476562e-05s
Availability | VoID file availability check for Stammbuch took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2803645133972168s
Reputation | Calculation of the PageRank for Stammbuch took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 2.9802322387695312e-05s
Believability | Calculation of trust value for Stammbuch took 1.239776611328125e-05s
INFO | --- Analysis for Stammbuch took 2.6763014793395996s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.1974859237670898s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.3164386749267578s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.021367788314819336s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.0001068115234375s
Believability | Calculation of trust value for statistics.data.gov.uk took 8.344650268554688e-06s
INFO | --- Analysis for statistics-data-gov-uk took 4.3961405754089355s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.3321223258972168s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.02096724510192871s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00011134147644042969s
Believability | Calculation of trust value for statusnet-1w6-org took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-1w6-org took 3.6300113201141357s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.3153228759765625s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.413459777832031e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-20100-org took 2.8703575134277344s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.26662182807922363s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02049708366394043s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.937980651855469e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 6.0558319091796875e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 3.136615514755249s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.29698681831359863s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.02203202247619629s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0009613037109375s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 9.918212890625e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.825676441192627s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.3117499351501465s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.02024054527282715s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 0.0001513957977294922s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-belfalas-org took 2.8647119998931885s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 8.869171142578125e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0008015632629394531s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.3164551258087158s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.023025989532470703s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.000949859619140625s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.0001475811004638672s
Believability | Calculation of trust value for statusnet-bka-li took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-bka-li took 12.838998794555664s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 8.821487426757812e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.2885019779205322s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.981590270996094e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.618163585662842s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 9.34600830078125e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.31064844131469727s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020371198654174805s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.078315734863281e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-ced117-net took 4.315520763397217s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 0.00013017654418945312s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.32376933097839355s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 6.937980651855469e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.950874090194702s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 8.487701416015625e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.2943582534790039s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.022090435028076172s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011277198791503906s
Believability | Calculation of trust value for statusnet-chromic-org took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-chromic-org took 2.8335354328155518s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 0.00010061264038085938s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.3044302463531494s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.022050857543945312s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 8.106231689453125e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 6.136369466781616s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2949638366699219s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 6.318092346191406e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 2.6917788982391357s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0012123584747314453s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2979462146759033s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.224082946777344e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.394280195236206s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.3062136173248291s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02052593231201172s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.860058546066284s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 0.00012254714965820312s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.2679896354675293s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.7825231552124023s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.28235697746276855s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.02032327651977539s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-doomicile-de took 4.085996389389038s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.29868245124816895s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.022275447845458984s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.151199340820312e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-dtdns-net took 2.992435932159424s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.00041961669921875s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.2917921543121338s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.7670135498046875e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.6567623615264893s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.27665019035339355s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.021816730499267578s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.462501525878906e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-exdc-net took 2.7701048851013184s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 8.749961853027344e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.2939779758453369s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020306110382080078s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.179115295410156e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-fcac-com took 3.0754570960998535s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.3151414394378662s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 3.4947152137756348s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 8.869171142578125e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.29888391494750977s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020417451858520508s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.0001811981201171875s
Believability | Calculation of trust value for statusnet-fragdev-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-fragdev-com took 3.6088435649871826s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 7.343292236328125e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.2807042598724365s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020847558975219727s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.915496826171875e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.8902409076690674s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.3314485549926758s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.021539926528930664s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010848045349121094s
Believability | Calculation of trust value for statusnet-gegeweb-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-gegeweb-org took 2.843374252319336s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.3500478267669678s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0008420944213867188s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 7.081031799316406e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-glou-org took 2.895446538925171s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 9.369850158691406e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.3157343864440918s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.0001201629638671875s
Believability | Calculation of trust value for statusnet-gomertronic-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-gomertronic-com took 2.7349514961242676s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.00040793418884277344s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.3137047290802002s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.0001049041748046875s
Believability | Calculation of trust value for statusnet-hackerposse-com took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-hackerposse-com took 3.1665449142456055s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 8.749961853027344e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.00034236907958984375s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.28803181648254395s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020972251892089844s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 5.0067901611328125e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-hii-co-il took 3.954483985900879s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.33230018615722656s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.202957153320312e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.0515153408050537s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 0.00010395050048828125s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.27432942390441895s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.02266669273376465s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 5.817413330078125e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 2.796008825302124s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.29575586318969727s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020714998245239258s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 3.838539123535156e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-integralblue-com took 3.003967523574829s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0008025169372558594s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.27753257751464844s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.020926237106323242s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0009241104125976562s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 6.842613220214844e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.698688507080078s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.29643917083740234s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.021212339401245117s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.0001266002655029297s
Believability | Calculation of trust value for statusnet-jonkman-ca took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-jonkman-ca took 4.516446590423584s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2941274642944336s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.022368431091308594s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.608268737792969e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.852356433868408s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 8.988380432128906e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0003211498260498047s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.32373046875s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.022635221481323242s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.935264587402344e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 2.8231685161590576s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2784421443939209s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.029273986816406e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 3.549173355102539s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.3053574562072754s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.021502971649169922s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 8.7738037109375e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-keuser-fr took 2.6671652793884277s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.3271811008453369s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02088308334350586s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 3.2010133266448975s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 0.00012993812561035156s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.3019073009490967s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020356178283691406s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.127357482910156e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 2.921517848968506s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 5.888938903808594e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.3210947513580322s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.465217590332031e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 3.421992778778076s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.290391206741333s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011777877807617188s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.7609128952026367s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.001585245132446289s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.2765014171600342s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-ludost-net took 4.033602952957153s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 8.535385131835938e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2874915599822998s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.751319885253906e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 2.7212390899658203s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.31976819038391113s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.021961212158203125s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.6027064323425293s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.326824426651001s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020308494567871094s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00014638900756835938s
Believability | Calculation of trust value for statusnet-macno-org took 2.5510787963867188e-05s
INFO | --- Analysis for statusnet-macno-org took 2.830270290374756s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 8.7738037109375e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.309781551361084s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02138686180114746s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.961822509765625e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 3.248948335647583s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 0.00010561943054199219s
Availability | VoID file availability check for statusnet-maymay-net took 0.0007832050323486328s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.5383501052856445s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.225440979003906e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-maymay-net took 42.527902126312256s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.3270609378814697s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.02210402488708496s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00015425682067871094s
Believability | Calculation of trust value for statusnet-morphtown-de took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-morphtown-de took 2.8776450157165527s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.2895681858062744s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020294904708862305s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.775161743164062e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 2.7934341430664062s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.28844451904296875s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.02086329460144043s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-mulestable-net took 3.427422523498535s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.2805290222167969s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-my-status-tk took 2.7720274925231934s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 9.703636169433594e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.28052568435668945s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020459413528442383s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00011038780212402344s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 3.504753112792969e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.6894140243530273s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2689480781555176s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.020335674285888672s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.843522787094116s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.2790951728820801s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.022127389907836914s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-otbm-fr took 3.0851855278015137s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 0.00011014938354492188s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.30231261253356934s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.225440979003906e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.847780466079712s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 5.555152893066406e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2666778564453125s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.02048349380493164s
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.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.8160552978515625e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-panda-id-au took 3.295248508453369s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 9.489059448242188e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2980823516845703s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.703636169433594e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-piana-eu took 2.780507802963257s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 8.535385131835938e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.30365872383117676s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.02103900909423828s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.843971252441406e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 2.8946988582611084s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.3060638904571533s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002276897430419922s
Believability | Calculation of trust value for statusnet-postblue-info took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.8623900413513184s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.32181882858276367s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020891904830932617s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.82012939453125e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-progval-net took 2.822270393371582s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.76837158203125e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.3077394962310791s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.022733211517333984s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011730194091796875s
Believability | Calculation of trust value for statusnet-qdnx-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-qdnx-org took 3.3317766189575195s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 9.322166442871094e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.2939774990081787s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.021204710006713867s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.29425048828125e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-qth-fr took 3.575413227081299s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.4515831470489502s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.022161483764648438s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.0002181529998779297s
Believability | Calculation of trust value for statusnet-quitter-se took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-quitter-se took 6.798938751220703s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 8.749961853027344e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.29256439208984375s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.02233433723449707s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00012111663818359375s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.9950127601623535s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0008020401000976562s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.29003047943115234s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020277738571166992s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-recit-org took 13.133538722991943s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.29758405685424805s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.0221254825592041s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00014710426330566406s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-russwurm-org took 3.5743634700775146s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.28236937522888184s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.368492126464844e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-samnoble-org took 5.137373685836792s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 9.036064147949219e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2937796115875244s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.20159912109375e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-schiessle-org took 2.9602768421173096s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 8.749961853027344e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.3028595447540283s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.751319885253906e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-scoffoni-net took 2.760723114013672s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 0.0001506805419921875s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.3236401081085205s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 2.84491229057312s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 8.845329284667969e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.3163588047027588s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020839452743530273s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.000942230224609375s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 9.083747863769531e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 3.656651496887207s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 0.00010895729064941406s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0008919239044189453s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.31029343605041504s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.02275848388671875s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00020933151245117188s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 3.3445630073547363s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.28809022903442383s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02256035804748535s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010442733764648438s
Believability | Calculation of trust value for statusnet-somsants-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.722388744354248s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.27904176712036133s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020529747009277344s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.0001342296600341797s
Believability | Calculation of trust value for statusnet-soucy-cc took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-soucy-cc took 4.633020877838135s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 9.059906005859375e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.29857444763183594s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-spip-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-spip-org took 3.6418616771698s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2885899543762207s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-spraci-org took 5.988155364990234s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.2901022434234619s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.022250890731811523s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00010728836059570312s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.6689300537109375e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 5.545506954193115s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.33151984214782715s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.021279573440551758s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022268295288085938s
Believability | Calculation of trust value for statusnet-status-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-status-net took 3.8427350521087646s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2861363887786865s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.340576171875e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.6815829277038574s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 9.441375732421875e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.2874271869659424s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020333290100097656s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 8.797645568847656e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 1.6689300537109375e-05s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.8536715507507324s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.28046703338623047s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.022305965423583984s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.000118255615234375s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 2.9932944774627686s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.29410362243652344s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.021228790283203125s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-thornton2-com took 7.120135068893433s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.00040793418884277344s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.28592371940612793s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00011420249938964844s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.9400253295898438s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.29355335235595703s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.838539123535156e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-tl1n-com took 3.7485275268554688s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 9.083747863769531e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2866828441619873s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.021652698516845703s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.842613220214844e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.9926159381866455s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 0.00011658668518066406s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.3026304244995117s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 4.506111145019531e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 3.6492929458618164s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 9.012222290039062e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.29433417320251465s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for steak took 3.051719903945923s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 8.440017700195312e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.319338321685791s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.0208737850189209s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.221366882324219e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.0967254638671875e-05s
INFO | --- Analysis for stitch-rameau took 4.27801251411438s
Availability | SPARQL endpoint availability check for Stone Tech Square took 1.624913215637207s
Availability | VoID file availability check for Stone Tech Square took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.31945180892944336s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.621246337890625e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.3589859008789062e-05s
INFO | --- Analysis for stone-tech-square-data took 5.314672946929932s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.4545159339904785s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0006916522979736328s
Extra | Recovery of all triples for STW Thesaurus for Economics took 21.71213722229004s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.1872127056121826s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6131198406219482s
Interoperability | New terms check for STW Thesaurus for Economics took 1.5111520290374756s
Versatility | Languages check for STW Thesaurus for Economics took 1.6233346462249756s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5490171909332275s
Security | Check HTTPS for STW Thesaurus for Economics took 0.14938807487487793s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.28522443771362305s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.27984619140625s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.27413272857666016s
License | MR license check for STW Thesaurus for Economics took 0.2479236125946045s
License | HR license check for STW Thesaurus for Economics took 2.39632511138916s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.2405705451965332s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6456015110015869s
Understandability | URI regex check for STW Thesaurus for Economics took 0.5042610168457031s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.2511916160583496s
Verifiability | Authors check for STW Thesaurus for Economics took 0.22779369354248047s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.26439523696899414s
Performance | Throughput check for STW Thesaurus for Economics took 10.859194040298462s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7258040904998779s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.23285341262817383s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.27869391441345215s
Interlinking | skos check for STW Thesaurus for Economics took 0.35570621490478516s
Interlinking | skos check for STW Thesaurus for Economics took 0.3024935722351074s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.23766613006591797s
Currency | Creation date check for STW Thesaurus for Economics took 0.5241754055023193s
Currency | Modification date check for STW Thesaurus for Economics took 0.5403106212615967s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.078158855438232s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 3.137117862701416s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2740638256072998s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.24587464332580566s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.2575995922088623s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 4.4639739990234375s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0547842979431152s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.3542680740356445s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.2709681987762451s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2572071552276611s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.7177157402038574s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.2715981006622314s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.275454044342041s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6877446174621582s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2643437385559082s
Security | Sign check for STW Thesaurus for Economics took 0.2505195140838623s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2985.4066956043243s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.5087323188781738s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.5942037105560303s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00012183189392089844s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 3.0768866539001465s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.2636184692382812e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 3086.987277984619s
Availability | SPARQL endpoint availability check for SudershanTech took 8.96453857421875e-05s
Availability | VoID file availability check for SudershanTech took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.3166525363922119s
Reputation | Calculation of the PageRank for SudershanTech took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for SudershanTech took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SudershanTech took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 2.765655517578125e-05s
Believability | Calculation of trust value for SudershanTech took 1.2159347534179688e-05s
INFO | --- Analysis for SudershanTech took 2.84598445892334s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.8866920471191406s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0007588863372802734s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.2877533435821533s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.57763671875e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.2636184692382812e-05s
INFO | --- Analysis for sudocfr took 7.57148289680481s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0101020336151123s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006794929504394531s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 22.278788805007935s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.689011573791504s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.5651497840881348s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.8501250743865967s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.122098207473755s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.5031368732452393s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5168256759643555s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5540461540222168s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5449273586273193s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5723366737365723s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 8.634283065795898s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.6316885948181152s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.6644611358642578s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.0796310901641846s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5061230659484863s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5333349704742432s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5212931632995605s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.54395866394043s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 7.343292236328125e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5273101329803467s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5385191440582275s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6319379806518555s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5738611221313477s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5070486068725586s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.1018543243408203s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.0778605937957764s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 41.87760877609253s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5176575183868408s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5212447643280029s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5186135768890381s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 3.065459728240967s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.3836848735809326s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5390522480010986s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 32.86310172080994s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.392482995986938s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.4558789730072s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 25.36200714111328s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 3.1327033042907715s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.5723183155059814s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5607395172119141s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4560.203673362732s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.7924096584320068s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.021508216857910156s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 3.3855438232421875e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 8.7738037109375e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 1.9073486328125e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.1682510375976562e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 8132.049054384232s
Availability | SPARQL endpoint availability check for Surge Radio took 4.6253204345703125e-05s
Availability | VoID file availability check for Surge Radio took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.2751946449279785s
Reputation | Calculation of the PageRank for Surge Radio took 0.020873308181762695s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.678436279296875e-05s
Believability | Calculation of trust value for Surge Radio took 7.867813110351562e-06s
INFO | --- Analysis for surge-radio took 3.653923511505127s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 8.749961853027344e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0003514289855957031s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.28430938720703125s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 2.8848648071289062e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 8.344650268554688e-06s
INFO | --- Analysis for SWAT took 28.43003749847412s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.3392181396484375e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.4484126567840576s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.28304052352905273s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.747245788574219e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 7.62939453125e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.104836463928223s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.0295872688293457s
Availability | VoID file availability check for SweFN-RDF took 0.000339508056640625s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.2812533378601074s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.743171691894531e-05s
Believability | Calculation of trust value for SweFN-RDF took 9.775161743164062e-06s
INFO | --- Analysis for swefn-rdf took 5.810033082962036s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.220008850097656e-05s
Availability | VoID file availability check for SwetoDblp took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.2843332290649414s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.790855407714844e-05s
Believability | Calculation of trust value for SwetoDblp took 1.239776611328125e-05s
INFO | --- Analysis for sweto-dblp took 23.132819652557373s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.46381330490112305s
Availability | VoID file availability check for Swift Vocabulary took 0.0006089210510253906s
Extra | Recovery of all triples for Swift Vocabulary took 2.256570816040039s
Performance | Total latancy measurement for Swift Vocabulary took 1.069457769393921s
Amount of data | Number of triples check for Swift Vocabulary took 0.16767430305480957s
Interoperability | New terms check for Swift Vocabulary took 1.424731969833374s
Versatility | Languages check for Swift Vocabulary took 0.16656255722045898s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.15346646308898926s
Interpretability | RDF structures check for Swift Vocabulary took 0.17523694038391113s
Versatility | Serialization formats check for Swift Vocabulary took 0.174605131149292s
Availability | RDF dump link check for Swift Vocabulary took 0.18741226196289062s
License | MR license check for Swift Vocabulary took 0.1743147373199463s
License | HR license check for Swift Vocabulary took 0.15872812271118164s
Amount of data | Number of property check for Swift Vocabulary took 0.1573638916015625s
Understandability | Number of label check for Swift Vocabulary took 0.19815540313720703s
Understandability | URI regex check for Swift Vocabulary took 0.364870548248291s
Understandability | Vocabs check for Swift Vocabulary took 0.21328139305114746s
Verifiability | Authors check for Swift Vocabulary took 0.22982144355773926s
Verifiability | Publishers check for Swift Vocabulary took 0.20791983604431152s
Performance | Throughput check for Swift Vocabulary took 10.567400455474854s
Amount of data | Check the number of entities for Swift Vocabulary took 8.463859558105469e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.20920348167419434s
Interlinking | sameAs chians check for Swift Vocabulary took 0.2074449062347412s
Interlinking | skos check for Swift Vocabulary took 0.18944334983825684s
Interlinking | skos check for Swift Vocabulary took 0.20729851722717285s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.19367265701293945s
Currency | Creation date check for Swift Vocabulary took 0.4389157295227051s
Currency | Modification date check for Swift Vocabulary took 0.41883254051208496s
Rep.Conc. | URIs length for Swift Vocabulary took 0.8187105655670166s
Interoperability | New vocabularies check for Swift Vocabulary took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.2245008945465088s
Accuracy | Check Functional Property for Swift Vocabulary took 0.20904278755187988s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.20656871795654297s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.332444429397583s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.001958608627319336s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03639650344848633s
Consistency | Disjoint class check for Swift Vocabulary took 0.22736096382141113s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.4415242671966553s
Consistency | Misplaced classes for Swift Vocabulary took 0.28426456451416016s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.5761504173278809s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.3073606491088867s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.482562780380249s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.027124643325805664s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.17983531951904297s
Security | Sign check for Swift Vocabulary took 0.18375778198242188s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 955.0486414432526s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.6438467502593994s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.02167224884033203s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 8.559226989746094e-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 9.775161743164062e-06s
INFO | --- Analysis for Swift took 1001.0424346923828s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 8.749961853027344e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.2873048782348633s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020560741424560547s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 2.9325485229492188e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.2159347534179688e-05s
INFO | --- Analysis for symptoms-in-chinese took 53.14001727104187s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.3900904655456543s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0006775856018066406s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.45641422271728516s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.9025635719299316s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 7.797420024871826s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 18.011117458343506s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.19835877418518066s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.2854647636413574s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.10994839668273926s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.4108586311340332s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.20592379570007324s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.17260503768920898s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.3059263229370117s
License | HR license check for National Digital Data Archive of Hungary (partial) took 52.9187798500061s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.47987937927246094s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 32.561809062957764s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3417682647705078s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.2538318634033203s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.16719937324523926s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.17696094512939453s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.764113664627075s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.152557373046875e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.9467926025390625s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 2.158571481704712s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 2.0284810066223145s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.9786334037780762s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.8871409893035889s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.6138129234313965s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 3.3498854637145996s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 61.489253997802734s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.16761398315429688s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.20236492156982422s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.18383455276489258s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.261521577835083s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.002775430679321289s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.003136157989501953s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.17267727851867676s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 44.140188455581665s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.24108600616455078s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.5883653163909912s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3191204071044922s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.10879826545715s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002399444580078125s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.453014612197876s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.1789414882659912s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 9.664469003677368s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.3780059814453125s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.021126508712768555s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.940696716308594e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.430511474609375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 1.0728836059570312e-05s
INFO | --- Analysis for sztaki-lod took 468.0520086288452s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00010848045349121094s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.2933924198150635s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020789146423339844s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.078315734863281e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.0967254638671875e-05s
INFO | --- Analysis for t4gm-info took 2.9478397369384766s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.2438507080078125e-05s
Availability | VoID file availability check for tags2con delicious took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.30223917961120605s
Reputation | Calculation of the PageRank for tags2con delicious took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.553794860839844e-05s
Believability | Calculation of trust value for tags2con delicious took 1.2874603271484375e-05s
INFO | --- Analysis for tags2con-delicious took 49.99754738807678s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.0237708091736s
Availability | VoID file availability check for Taiwan geographic names took 0.0008854866027832031s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.356372594833374s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.0217435359954834s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.435943603515625e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.1444091796875e-05s
INFO | --- Analysis for taiwan-geographic-names took 667.1145820617676s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 9.441375732421875e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.3024282455444336s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.020905494689941406s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 8.845329284667969e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.2159347534179688e-05s
INFO | --- Analysis for talis-openlibrary took 4.133297920227051s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.8832578659057617s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.30034899711608887s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.025702953338623047s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00011897087097167969s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 7.867813110351562e-06s
INFO | --- Analysis for taxonconcept took 13.394874572753906s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 8.96453857421875e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0003237724304199219s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.2916524410247803s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.021997690200805664s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.001074075698852539s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 9.870529174804688e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.2636184692382812e-05s
INFO | --- Analysis for taxonconcept-assets took 3.0780982971191406s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 8.916854858398438e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.3041975498199463s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.022893190383911133s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 4.8160552978515625e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.3113021850585938e-05s
INFO | --- Analysis for taxonconcept-occurences took 3.1355481147766113s
Availability | SPARQL endpoint availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 21.2324960231781s
Availability | VoID file availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.3040752410888672s
Reputation | Calculation of the PageRank for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.021208524703979492s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 4.57763671875e-05s
Believability | Calculation of trust value for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.2159347534179688e-05s
INFO | --- Analysis for taxref-ld took 75.3294370174408s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 263.0202865600586s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.29844117164611816s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.020825862884521484s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.743171691894531e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.3113021850585938e-05s
INFO | --- Analysis for tcga took 543.183197259903s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3680388927459717s
Availability | VoID file availability check for TCGA Roadmap took 0.00037407875061035156s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.3128085136413574s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02106451988220215s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.2479248046875e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.049041748046875e-05s
INFO | --- Analysis for tcga-roadmap took 6.534924745559692s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.3275611400604248s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.3536503314971924s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.02118206024169922s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010895729064941406s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for tcmgenedit_dataset took 137.4564847946167s
Availability | SPARQL endpoint availability check for TDS took 4.5299530029296875e-05s
Availability | VoID file availability check for TDS took 0.0008587837219238281s
Completeness | Calculation of interlinking completeness for TDS took 0.3315436840057373s
Reputation | Calculation of the PageRank for TDS took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for TDS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for TDS took 4.3392181396484375e-05s
Believability | Calculation of trust value for TDS took 1.430511474609375e-05s
INFO | --- Analysis for tds took 5.0191075801849365s
Availability | SPARQL endpoint availability check for TEKORD took 4.57763671875e-05s
Availability | VoID file availability check for TEKORD took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for TEKORD took 0.31894731521606445s
Reputation | Calculation of the PageRank for TEKORD took 0.021653413772583008s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0010685920715332031s
Interlinking | Calculation of Clustering coefficient for TEKORD took 5.745887756347656e-05s
Believability | Calculation of trust value for TEKORD took 1.3113021850585938e-05s
INFO | --- Analysis for tekord took 5.638366937637329s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 2.624242067337036s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.2817697525024414s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020707130432128906s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00012087821960449219s
Believability | Calculation of trust value for Telegraphis Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for telegraphis took 9.020136833190918s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 0.00010418891906738281s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.27756333351135254s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.022318601608276367s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.128715515136719e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.2159347534179688e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 14.13259482383728s
Availability | SPARQL endpoint availability check for Ontology took 9.560585021972656e-05s
Availability | VoID file availability check for Ontology took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Ontology took 0.341902494430542s
Reputation | Calculation of the PageRank for Ontology took 0.02093815803527832s
Interlinking | Calculation of Degree of Connection for Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for Terrorist_attack took 3.316159963607788s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.458427429199219e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.30014848709106445s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020922422409057617s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.147125244140625e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.1682510375976562e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 2.71975040435791s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.291534423828125e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.3658792972564697s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.02099299430847168s
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.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.218650817871094e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.0967254638671875e-05s
INFO | --- Analysis for Tesla_Deaths took 4.339070081710815s
Availability | SPARQL endpoint availability check for test took 4.291534423828125e-05s
Availability | VoID file availability check for test took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for test took 0.31216883659362793s
Reputation | Calculation of the PageRank for test took 0.021172761917114258s
Interlinking | Calculation of Degree of Connection for test took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for test took 0.0008275508880615234s
Interlinking | Calculation of Clustering coefficient for test took 3.314018249511719e-05s
Believability | Calculation of trust value for test took 1.3589859008789062e-05s
INFO | --- Analysis for test took 2.72463059425354s
Availability | SPARQL endpoint availability check for Test took 8.606910705566406e-05s
Availability | VoID file availability check for Test took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Test took 0.29834532737731934s
Reputation | Calculation of the PageRank for Test took 0.020769834518432617s
Interlinking | Calculation of Degree of Connection for Test took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Test took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Test took 3.0994415283203125e-05s
Believability | Calculation of trust value for Test took 1.2159347534179688e-05s
INFO | --- Analysis for Test took 2.757619857788086s
Availability | SPARQL endpoint availability check for test-svu took 20.195005655288696s
Availability | VoID file availability check for test-svu took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for test-svu took 0.2899973392486572s
Reputation | Calculation of the PageRank for test-svu took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for test-svu took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.1948089599609375e-05s
Believability | Calculation of trust value for test-svu took 1.3589859008789062e-05s
INFO | --- Analysis for test-svu took 52.91938543319702s
Availability | SPARQL endpoint availability check for Test took 9.72747802734375e-05s
Availability | VoID file availability check for Test took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Test took 0.29205322265625s
Reputation | Calculation of the PageRank for Test took 0.02254033088684082s
Interlinking | Calculation of Degree of Connection for Test took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Test took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Test took 3.3855438232421875e-05s
Believability | Calculation of trust value for Test took 1.3113021850585938e-05s
INFO | --- Analysis for Test_ took 2.6295859813690186s
Availability | SPARQL endpoint availability check for xxxxx took 261.98478603363037s
Availability | VoID file availability check for xxxxx took 0.0008461475372314453s
Completeness | Calculation of interlinking completeness for xxxxx took 0.422393798828125s
Reputation | Calculation of the PageRank for xxxxx took 0.02113485336303711s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for xxxxx took 5.14984130859375e-05s
Believability | Calculation of trust value for xxxxx took 1.049041748046875e-05s
INFO | --- Analysis for testee took 797.1447746753693s
Availability | SPARQL endpoint availability check for tharawat magazine took 0.00010228157043457031s
Availability | VoID file availability check for tharawat magazine took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.32088184356689453s
Reputation | Calculation of the PageRank for tharawat magazine took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010800361633300781s
Believability | Calculation of trust value for tharawat magazine took 1.3113021850585938e-05s
INFO | --- Analysis for tharawat-magazine-com took 3.483497142791748s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.4752943515777588s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.26563239097595215s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 2.956390380859375e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 7.906026363372803s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 3.3194382190704346s
Availability | VoID file availability check for The European Library Open Dataset took 0.0008273124694824219s
Extra | Recovery of all triples for The European Library Open Dataset took 7.0522894859313965s
Performance | Total latancy measurement for The European Library Open Dataset took 16.00358533859253s
Amount of data | Number of triples check for The European Library Open Dataset took 63.861146211624146s
Interoperability | New terms check for The European Library Open Dataset took 60.389525413513184s
Versatility | Languages check for The European Library Open Dataset took 3.199770927429199s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.2013328075408936s
Interpretability | RDF structures check for The European Library Open Dataset took 3.2044265270233154s
Versatility | Serialization formats check for The European Library Open Dataset took 3.200962543487549s
Availability | RDF dump link check for The European Library Open Dataset took 3.1960971355438232s
License | MR license check for The European Library Open Dataset took 3.2118005752563477s
License | HR license check for The European Library Open Dataset took 3.1927802562713623s
Amount of data | Number of property check for The European Library Open Dataset took 3.1981394290924072s
Understandability | Number of label check for The European Library Open Dataset took 3.7411038875579834s
Understandability | URI regex check for The European Library Open Dataset took 6.401170253753662s
Understandability | Vocabs check for The European Library Open Dataset took 3.201348304748535s
Verifiability | Authors check for The European Library Open Dataset took 3.197822093963623s
Verifiability | Publishers check for The European Library Open Dataset took 3.205484390258789s
Performance | Throughput check for The European Library Open Dataset took 31.994090795516968s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.939338684082031e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.206888198852539s
Interlinking | sameAs chians check for The European Library Open Dataset took 3.365648031234741s
Interlinking | skos check for The European Library Open Dataset took 3.271493434906006s
Interlinking | skos check for The European Library Open Dataset took 3.2556347846984863s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.1923091411590576s
Currency | Creation date check for The European Library Open Dataset took 6.403313636779785s
Currency | Modification date check for The European Library Open Dataset took 6.394987106323242s
Rep.Conc. | URIs length for The European Library Open Dataset took 124.20356011390686s
Interoperability | New vocabularies check for The European Library Open Dataset took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 3.220381736755371s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.471372604370117s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.026587724685668945s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.028443098068237305s
Consistency | Disjoint class check for The European Library Open Dataset took 3.194079637527466s
Consistency | Check Misplaced properties for The European Library Open Dataset took 67.2697331905365s
Consistency | Misplaced classes for The European Library Open Dataset took 3.280449151992798s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.804959297180176s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.298072099685669s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 63.42435312271118s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03553938865661621s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 3.1779537200927734s
Security | Sign check for The European Library Open Dataset took 3.203038454055786s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 11.471123218536377s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.6239926815032959s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.021061182022094727s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 7.152557373046875e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 1.3828277587890625e-05s
INFO | --- Analysis for the-european-library-open-dataset took 918.8753399848938s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.040871381759644s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.36732983589172363s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010347366333007812s
Believability | Calculation of trust value for The Eurostat Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for the-eurostat-linked-data took 242.99493765830994s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 8.678436279296875e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0004019737243652344s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.30095624923706055s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.0211946964263916s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.748603820800781e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.239776611328125e-05s
INFO | --- Analysis for the-living-lod-cloud took 48.721688985824585s
Availability | SPARQL endpoint availability check for The View From took 20.04996156692505s
Availability | VoID file availability check for The View From took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for The View From took 0.3149068355560303s
Reputation | Calculation of the PageRank for The View From took 0.02290058135986328s
Interlinking | Calculation of Degree of Connection for The View From took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for The View From took 8.249282836914062e-05s
Believability | Calculation of trust value for The View From took 8.106231689453125e-06s
INFO | --- Analysis for the-view-from took 62.811177253723145s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.464021921157837s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2738020420074463s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 2.956390380859375e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.33514404296875e-05s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.24796509742737s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.080978393554688s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2865636348724365s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.022672176361083984s
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.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.552436828613281e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.2874603271484375e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 103.06567859649658s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.38690185546875e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.29683780670166016s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.020958662033081055s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010943412780761719s
Believability | Calculation of trust value for The Content Wrangler took 1.0013580322265625e-05s
INFO | --- Analysis for thecontentwrangler-com took 3.3259382247924805s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 8.726119995117188e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.3131544589996338s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020941972732543945s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.075599670410156e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 1.1205673217773438e-05s
INFO | --- Analysis for thesaurus-datenwissen took 2.766796350479126s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.6403110027313232s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.28055882453918457s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.021558284759521484s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.82012939453125e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.239776611328125e-05s
INFO | --- Analysis for thesaurus-w took 4.324635982513428s
Availability | SPARQL endpoint availability check for theses.fr took 4.3392181396484375e-05s
Availability | VoID file availability check for theses.fr took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for theses.fr took 0.2890589237213135s
Reputation | Calculation of the PageRank for theses.fr took 0.022388696670532227s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.792213439941406e-05s
Believability | Calculation of trust value for theses.fr took 1.3113021850585938e-05s
INFO | --- Analysis for thesesfr took 4.414340019226074s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 8.440017700195312e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.31240272521972656s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.021187782287597656s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007052421569824219s
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.0967254638671875e-05s
INFO | --- Analysis for Thinkphile took 2.7954623699188232s
Availability | SPARQL endpoint availability check for ThIST took 265.14072370529175s
Availability | VoID file availability check for ThIST took 0.0006103515625s
Completeness | Calculation of interlinking completeness for ThIST took 0.33980727195739746s
Reputation | Calculation of the PageRank for ThIST took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for ThIST took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.72747802734375e-05s
Believability | Calculation of trust value for ThIST took 5.4836273193359375e-06s
INFO | --- Analysis for thist took 563.0746273994446s
Availability | SPARQL endpoint availability check for TIP took 40.04365420341492s
Availability | VoID file availability check for TIP took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for TIP took 0.29477739334106445s
Reputation | Calculation of the PageRank for TIP took 0.022908449172973633s
Interlinking | Calculation of Degree of Connection for TIP took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010967254638671875s
Believability | Calculation of trust value for TIP took 1.1205673217773438e-05s
INFO | --- Analysis for tip took 102.74270963668823s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 9.083747863769531e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.297760009765625s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.02273106575012207s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.266334533691406e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 6.079673767089844e-05s
INFO | --- Analysis for TOPMODEL took 23.092345476150513s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.7132256031036377s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.30766725540161133s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.021351337432861328s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.504753112792969e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 9.5367431640625e-06s
INFO | --- Analysis for TP-data took 7.826744556427002s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.8846697807312012s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.3303253650665283s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.021175861358642578s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.839897155761719e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for traditional-korean-medicine took 4.20428204536438s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.2275252342224121s
Availability | VoID file availability check for Traffic Scotland took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.300661563873291s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.02094244956970215s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.790855407714844e-05s
Believability | Calculation of trust value for Traffic Scotland took 9.775161743164062e-06s
INFO | --- Analysis for traffic-scotland took 3.083707332611084s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.12035131454467773s
Availability | VoID file availability check for Transparency International Linked Data took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.28883790969848633s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010657310485839844s
Believability | Calculation of trust value for Transparency International Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for transparency-linked-data took 2.927720785140991s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.9298989772796631s
Availability | VoID file availability check for transport.data.gov.uk took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.2957596778869629s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.417533874511719e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 1.0728836059570312e-05s
INFO | --- Analysis for transport-data-gov-uk took 4.5450263023376465s
Availability | SPARQL endpoint availability check for Trelios took 4.649162292480469e-05s
Availability | VoID file availability check for Trelios took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Trelios took 0.33742499351501465s
Reputation | Calculation of the PageRank for Trelios took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for Trelios took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.1682510375976562e-05s
Believability | Calculation of trust value for Trelios took 1.2636184692382812e-05s
INFO | --- Analysis for Trelios took 2.76251220703125s
Availability | SPARQL endpoint availability check for Twarql took 10.577647924423218s
Availability | VoID file availability check for Twarql took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Twarql took 0.291947603225708s
Reputation | Calculation of the PageRank for Twarql took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for Twarql took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.604194641113281e-05s
Believability | Calculation of trust value for Twarql took 1.0251998901367188e-05s
INFO | --- Analysis for twarql took 13.298530578613281s
Availability | SPARQL endpoint availability check for TWC Data-gov took 8.845329284667969e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0007679462432861328s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.3034079074859619s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.021099328994750977s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.123283386230469e-05s
Believability | Calculation of trust value for TWC Data-gov took 9.059906005859375e-06s
INFO | --- Analysis for twc-data-gov took 13.571479082107544s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.15959811210632324s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.2880363464355469s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 4.172325134277344e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 9.5367431640625e-06s
INFO | --- Analysis for twc-healthdata took 14.979268074035645s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.3450117111206055s
Availability | VoID file availability check for Instance Hub (all) took 0.0008473396301269531s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.3028898239135742s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.02113628387451172s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 7.891654968261719e-05s
Believability | Calculation of trust value for Instance Hub (all) took 1.4066696166992188e-05s
INFO | --- Analysis for twc-hub took 77.30033802986145s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.13916993141174316s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.42988133430480957s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.023410797119140625s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.000110626220703125s
Believability | Calculation of trust value for IEEE VIS Source Data took 1.33514404296875e-05s
INFO | --- Analysis for twc-ieeevis took 105.51738595962524s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.410743713378906e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.28420567512512207s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.226799011230469e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 9.059906005859375e-06s
INFO | --- Analysis for twc-logd took 2.886826753616333s
Availability | SPARQL endpoint availability check for twc-opendap took 0.1294262409210205s
Availability | VoID file availability check for twc-opendap took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.31493401527404785s
Reputation | Calculation of the PageRank for twc-opendap took 0.02163982391357422s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 6.914138793945312e-05s
Believability | Calculation of trust value for twc-opendap took 9.775161743164062e-06s
INFO | --- Analysis for twc-opendap took 52.130616426467896s
Availability | SPARQL endpoint availability check for typepad took 4.887580871582031e-05s
Availability | VoID file availability check for typepad took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for typepad took 0.2784261703491211s
Reputation | Calculation of the PageRank for typepad took 0.022396564483642578s
Interlinking | Calculation of Degree of Connection for typepad took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for typepad took 4.9114227294921875e-05s
Believability | Calculation of trust value for typepad took 9.775161743164062e-06s
INFO | --- Analysis for typepad took 3.414318323135376s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.9601573944091797s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.2838258743286133s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.02114105224609375s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.172325134277344e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.33514404296875e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 5.093411445617676s
Availability | SPARQL endpoint availability check for Uberblic.org took 5.3507397174835205s
Availability | VoID file availability check for Uberblic.org took 0.001184701919555664s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.29569363594055176s
Reputation | Calculation of the PageRank for Uberblic.org took 0.021955251693725586s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010347366333007812s
Believability | Calculation of trust value for Uberblic.org took 1.2159347534179688e-05s
INFO | --- Analysis for uberblic took 13.061888933181763s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.6823742389678955s
Availability | VoID file availability check for UDante in LiLa took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.29221081733703613s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.02265024185180664s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 4.363059997558594e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for UDante took 4.470036029815674s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 0.9665467739105225s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.3217184543609619s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.020961999893188477s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for ufo took 5.009304046630859s
Availability | SPARQL endpoint availability check for Uganda Disasters took 4.458427429199219e-05s
Availability | VoID file availability check for Uganda Disasters took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.32990121841430664s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.02114701271057129s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 4.601478576660156e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.3113021850585938e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.7059268951416016s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.06741952896118164s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.29640793800354004s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 9.632110595703125e-05s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for uis-linked-data took 2.8066909313201904s
Availability | SPARQL endpoint availability check for UK Legislation took 8.988380432128906e-05s
Availability | VoID file availability check for UK Legislation took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.30167365074157715s
Reputation | Calculation of the PageRank for UK Legislation took 0.022229433059692383s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.559226989746094e-05s
Believability | Calculation of trust value for UK Legislation took 8.106231689453125e-06s
INFO | --- Analysis for uk-legislation-api took 3.6911163330078125s
Availability | SPARQL endpoint availability check for UK Postcodes took 9.083747863769531e-05s
Availability | VoID file availability check for UK Postcodes took 0.0007801055908203125s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.31748485565185547s
Reputation | Calculation of the PageRank for UK Postcodes took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.459785461425781e-05s
Believability | Calculation of trust value for UK Postcodes took 9.298324584960938e-06s
INFO | --- Analysis for uk-postcodes took 22.7339825630188s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 9.751319885253906e-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.3085594177246094s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.02274632453918457s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0008313655853271484s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0001220703125s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1920928955078125e-05s
INFO | --- Analysis for umbel took 6.751786470413208s
Availability | SPARQL endpoint availability check for German environmental thesaurus UMTHES took 8.940696716308594e-05s
Availability | VoID file availability check for German environmental thesaurus UMTHES took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for German environmental thesaurus UMTHES took 0.30834412574768066s
Reputation | Calculation of the PageRank for German environmental thesaurus UMTHES took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for German environmental thesaurus UMTHES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for German environmental thesaurus UMTHES took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for German environmental thesaurus UMTHES took 4.1961669921875e-05s
Believability | Calculation of trust value for German environmental thesaurus UMTHES took 9.5367431640625e-06s
INFO | --- Analysis for umthes took 3.803570032119751s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 2.765380859375s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0008258819580078125s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.3022778034210205s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 2.765655517578125e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 8.106231689453125e-06s
INFO | --- Analysis for un-hazardous-numbers took 12.64138150215149s
Availability | SPARQL endpoint availability check for UniProt took 3.7347664833068848s
Availability | VoID file availability check for UniProt took 0.0006074905395507812s
Extra | Recovery of all triples for UniProt took 19.58959412574768s
Performance | Total latancy measurement for UniProt took 10.774278163909912s
Amount of data | Number of triples check for UniProt took 1.0437805652618408s
Interoperability | New terms check for UniProt took 1.9501903057098389s
Versatility | Languages check for UniProt took 2.6843421459198s
Interpretability | Number of blank nodes check for UniProt took 5.729175090789795s
Interpretability | RDF structures check for UniProt took 3.095407009124756s
Versatility | Serialization formats check for UniProt took 4.225218772888184s
Availability | RDF dump link check for UniProt took 0.5106122493743896s
License | MR license check for UniProt took 2.112715482711792s
License | HR license check for UniProt took 300.1541414260864s
Amount of data | Number of property check for UniProt took 0.09860920906066895s
Understandability | Number of label check for UniProt took 53.392406702041626s
Understandability | URI regex check for UniProt took 1.387669563293457s
Understandability | Vocabs check for UniProt took 1.6123709678649902s
Verifiability | Authors check for UniProt took 2.850984811782837s
Verifiability | Publishers check for UniProt took 2.57734751701355s
Performance | Throughput check for UniProt took 50.368802547454834s
Amount of data | Check the number of entities for UniProt took 7.43865966796875e-05s
Verifiability | Contribs. check for UniProt took 1.062281847000122s
Interlinking | sameAs chians check for UniProt took 0.9933412075042725s
Interlinking | skos check for UniProt took 2.2381958961486816s
Interlinking | skos check for UniProt took 0.08872628211975098s
Timeliness | dataset update frequency check for UniProt took 2.602320909500122s
Currency | Creation date check for UniProt took 2.7601981163024902s
Currency | Modification date check for UniProt took 3.0129306316375732s
Rep.Conc. | URIs length for UniProt took 174.15070486068726s
Interoperability | New vocabularies check for UniProt took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.6522266864776611s
Accuracy | Check Functional Property for UniProt took 0.5367562770843506s
Accuracy | Check Inverse Functional Property for UniProt took 0.5995721817016602s
Accuracy | Check Empty annotation labels for UniProt took 12.407694101333618s
Accuracy | Check White space in annotation for UniProt took 2.5495152473449707s
Accuracy | Check Datatype consistency for UniProt took 7.24835205078125s
Consistency | Disjoint class check for UniProt took 0.6162493228912354s
Consistency | Check Misplaced properties for UniProt took 2.3137924671173096s
Consistency | Check Ontology hijacking for UniProt took 8.540255546569824s
Consistency | Check Invalid usage of undefined classes for UniProt took 19425.76776790619s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.854093313217163s
Conciseness | Check Extensional conciseness for UniProt took 2.7671749591827393s
Conciseness | Check Intensional conciseness for UniProt took 0.7939188480377197s
Security | Sign check for UniProt took 1.118872880935669s
Availability | Check URIs Dereferenciability for UniProt took 4.578675746917725s
Completeness | Calculation of interlinking completeness for UniProt took 0.9759809970855713s
Reputation | Calculation of the PageRank for UniProt took 0.02129673957824707s
Interlinking | Calculation of Degree of Connection for UniProt took 0.00011396408081054688s
Interlinking | Calculation of Centrality for UniProt took 0.0011806488037109375s
Interlinking | Calculation of Clustering coefficient for UniProt took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 2.384185791015625e-06s
Believability | Calculation of trust value for UniProt took 8.58306884765625e-06s
INFO | --- Analysis for UniProt took 20540.532014131546s
Availability | SPARQL endpoint availability check for UniProt took 2.466850757598877s
Availability | VoID file availability check for UniProt took 0.0003771781921386719s
Extra | Recovery of all triples for UniProt took 16.68983221054077s
Performance | Total latancy measurement for UniProt took 6.620514869689941s
Amount of data | Number of triples check for UniProt took 0.6178290843963623s
Versatility | Languages check for UniProt took 1.6015706062316895s
Interpretability | Number of blank nodes check for UniProt took 3.326582670211792s
Security | Check HTTPS for UniProt took 3.547795295715332s
Interpretability | RDF structures check for UniProt took 0.19230246543884277s
Versatility | Serialization formats check for UniProt took 0.1811990737915039s
Availability | RDF dump link check for UniProt took 0.18532443046569824s
License | MR license check for UniProt took 0.18404150009155273s
License | HR license check for UniProt took 0.1959514617919922s
Amount of data | Number of property check for UniProt took 0.17783188819885254s
Understandability | Number of label check for UniProt took 0.17586517333984375s
Understandability | URI regex check for UniProt took 0.32033824920654297s
Understandability | Vocabs check for UniProt took 0.1828763484954834s
Verifiability | Authors check for UniProt took 0.18669366836547852s
Verifiability | Publishers check for UniProt took 0.16613078117370605s
Performance | Throughput check for UniProt took 31.46622133255005s
Amount of data | Check the number of entities for UniProt took 0.0001614093780517578s
Verifiability | Contribs. check for UniProt took 0.230302095413208s
Interlinking | sameAs chians check for UniProt took 0.16199326515197754s
Interlinking | skos check for UniProt took 0.17038655281066895s
Interlinking | skos check for UniProt took 0.15065813064575195s
Timeliness | dataset update frequency check for UniProt took 0.17258429527282715s
Currency | Creation date check for UniProt took 0.3589365482330322s
Currency | Modification date check for UniProt took 0.3586091995239258s
Rep.Conc. | URIs length for UniProt took 114.75349617004395s
Interoperability | New vocabularies check for UniProt took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.17302417755126953s
Accuracy | Check Datatype consistency for UniProt took 7.226568698883057s
Consistency | Disjoint class check for UniProt took 0.16942715644836426s
Consistency | Check Ontology hijacking for UniProt took 0.17550230026245117s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.841416835784912s
Conciseness | Check Extensional conciseness for UniProt took 2.764587640762329s
Security | Sign check for UniProt took 0.16449928283691406s
Availability | Check URIs Dereferenciability for UniProt took 4.058973073959351s
Completeness | Calculation of interlinking completeness for UniProt took 0.42970943450927734s
Reputation | Calculation of the PageRank for UniProt took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for UniProt took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.67572021484375e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 9.5367431640625e-07s
Believability | Calculation of trust value for UniProt took 1.1682510375976562e-05s
INFO | --- Analysis for uniprot took 738.0282909870148s
Availability | SPARQL endpoint availability check for uniprot-metadata took 4.458427429199219e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.3055710792541504s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.175041198730469e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.1682510375976562e-05s
INFO | --- Analysis for uniprot-metadata took 4.0886390209198s
Availability | SPARQL endpoint availability check for UniProtKB took 2.3705039024353027s
Availability | VoID file availability check for UniProtKB took 0.0006897449493408203s
Extra | Recovery of all triples for UniProtKB took 14.885126829147339s
Performance | Total latancy measurement for UniProtKB took 5.352004289627075s
Amount of data | Number of triples check for UniProtKB took 0.4672276973724365s
Interoperability | New terms check for UniProtKB took 1.706176996231079s
Versatility | Languages check for UniProtKB took 1.4436664581298828s
Interpretability | Number of blank nodes check for UniProtKB took 2.9120564460754395s
Interpretability | RDF structures check for UniProtKB took 1.7347068786621094s
Versatility | Serialization formats check for UniProtKB took 2.369016408920288s
Availability | RDF dump link check for UniProtKB took 0.29387640953063965s
License | MR license check for UniProtKB took 1.295778512954712s
License | HR license check for UniProtKB took 300.1360399723053s
Amount of data | Number of property check for UniProtKB took 0.14641475677490234s
Understandability | Number of label check for UniProtKB took 55.158945083618164s
Understandability | URI regex check for UniProtKB took 0.7988905906677246s
Understandability | Vocabs check for UniProtKB took 1.0143029689788818s
Verifiability | Authors check for UniProtKB took 1.4049019813537598s
Verifiability | Publishers check for UniProtKB took 1.1952483654022217s
Performance | Throughput check for UniProtKB took 30.989197731018066s
Amount of data | Check the number of entities for UniProtKB took 7.128715515136719e-05s
Verifiability | Contribs. check for UniProtKB took 0.81546950340271s
Interlinking | sameAs chians check for UniProtKB took 0.387514591217041s
Interlinking | skos check for UniProtKB took 1.1368720531463623s
Interlinking | skos check for UniProtKB took 1.1401772499084473s
Timeliness | dataset update frequency check for UniProtKB took 1.3296926021575928s
Currency | Creation date check for UniProtKB took 1.6294548511505127s
Currency | Modification date check for UniProtKB took 1.5069820880889893s
Rep.Conc. | URIs length for UniProtKB took 114.45175838470459s
Interoperability | New vocabularies check for UniProtKB took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.4746363162994385s
Accuracy | Check Functional Property for UniProtKB took 0.3644232749938965s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.4620625972747803s
Accuracy | Check Empty annotation labels for UniProtKB took 25.229923486709595s
Accuracy | Check White space in annotation for UniProtKB took 2.5213286876678467s
Accuracy | Check Datatype consistency for UniProtKB took 7.209228515625s
Consistency | Disjoint class check for UniProtKB took 0.36381053924560547s
Consistency | Check Misplaced properties for UniProtKB took 2.5992980003356934s
Consistency | Check Ontology hijacking for UniProtKB took 8.653355836868286s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 19177.936882972717s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 1.8939223289489746s
Conciseness | Check Extensional conciseness for UniProtKB took 2.7735202312469482s
Conciseness | Check Intensional conciseness for UniProtKB took 0.7578277587890625s
Security | Sign check for UniProtKB took 1.1074905395507812s
Availability | Check URIs Dereferenciability for UniProtKB took 4.547132253646851s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.8821990489959717s
Reputation | Calculation of the PageRank for UniProtKB took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 3.5762786865234375e-06s
Believability | Calculation of trust value for UniProtKB took 1.1920928955078125e-05s
INFO | --- Analysis for uniprotkb took 20299.27526140213s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 8.96453857421875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0007123947143554688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.32166504859924316s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.021067142486572266s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.827781200408936s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.29680466651916504s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.021397113800048828s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 4.273688793182373s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 9.036064147949219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0008347034454345703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.33708763122558594s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.020998716354370117s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.696846008300781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.603332996368408s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.744529724121094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0004112720489501953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.2984156608581543s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.381514310836792s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 9.226799011230469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0007638931274414062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.2883179187774658s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.020849943161010742s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.406113147735596s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.31697678565979004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.538394212722778s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 8.225440979003906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0003597736358642578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.27583765983581543s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.71661376953125e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 4.370735168457031s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.3287675380706787s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.614869832992554s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 9.036064147949219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.3529627323150635s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020728111267089844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.546725273132324s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.3334615230560303s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.020531415939331055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.47305679321289s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.29605960845947266s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.021010398864746094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0011005401611328125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.863739013671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.398914337158203s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 8.988380432128906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0007052421569824219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.2977907657623291s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.021099567413330078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.387935161590576s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 8.630752563476562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.28967952728271484s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.266282796859741s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.320789098739624s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.47896409034729s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 8.58306884765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0007672309875488281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.3192167282104492s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.372978210449219s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.029273986816406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0007936954498291016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.27924656867980957s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.02096700668334961s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.839897155761719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.394448518753052s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 8.702278137207031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0007393360137939453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.28028392791748047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.020745038986206055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.220228910446167s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.3008091449737549s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.251618146896362s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 8.821487426757812e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0007786750793457031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.31884050369262695s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.544248104095459s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 9.083747863769531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.30911731719970703s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.022023439407348633s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 6.859907388687134s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0008726119995117188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.2938816547393799s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.022814035415649414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 13.366576433181763s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0008087158203125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.31925058364868164s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.02178955078125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.384392976760864s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 8.845329284667969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.2922632694244385s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.48722505569458s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 8.821487426757812e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.2989509105682373s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.02077507972717285s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 4.048241376876831s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.29015088081359863s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.02093029022216797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-german took 4.260150194168091s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 9.012222290039062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.27834367752075195s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 4.223331451416016s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 9.322166442871094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0007066726684570312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.3402576446533203s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 6.869791746139526s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.3303189277648926s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.439520359039307s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.29569053649902344s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.551225423812866s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.2938864231109619s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.021465539932250977s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 4.288814306259155s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.30005764961242676s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.556046485900879s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.3047192096710205s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.0211179256439209s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 4.135981321334839s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0007228851318359375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.319749116897583s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.481885433197021s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 8.726119995117188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0007169246673583984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.28990840911865234s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.605213165283203s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.27583885192871094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 4.026877164840698s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0007579326629638672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.2954671382904053s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.02072596549987793s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.7206878662109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.436986684799194s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.3370692729949951s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.021891117095947266s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 4.120415449142456s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 8.702278137207031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.37909841537475586s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02094268798828125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.399148941040039s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0007989406585693359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.30808520317077637s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.02174067497253418s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.242629766464233s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0007636547088623047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.31244349479675293s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.022378921508789062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.346815586090088s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0009319782257080078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.2831711769104004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.022530078887939453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.201658487319946s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 8.988380432128906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.29376816749572754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.465595960617065s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.29851460456848145s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.021461009979248047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 4.203217029571533s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.31196069717407227s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.424837112426758s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 9.870529174804688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.32970690727233887s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.021039962768554688s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 13.059124231338501s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.696846008300781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0008220672607421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.29843759536743164s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020889997482299805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.251880407333374s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.28086185455322266s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020836353302001953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.463785409927368s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.702278137207031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2875664234161377s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.021245241165161133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0009853839874267578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.839897155761719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.59579348564148s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0007779598236083984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.2786731719970703s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.02213907241821289s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.538833618164062s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 9.298324584960938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.31818675994873047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.02186107635498047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 3.9702422618865967s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0008366107940673828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.31778860092163086s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.02094101905822754s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.49870777130127s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 8.940696716308594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.3351774215698242s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.021829843521118164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.673004150390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.466747760772705s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.26841020584106445s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.02270197868347168s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.379548072814941s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 5.245208740234375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.30863094329833984s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.283122777938843s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 8.940696716308594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.28257012367248535s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020780086517333984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.479955196380615s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 9.059906005859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.34128904342651367s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.02086949348449707s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.33471131324768s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0012056827545166016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.29247522354125977s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.02104949951171875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 4.149340629577637s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.2782268524169922s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 3.791910409927368s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.00010895729064941406s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.3128993511199951s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.021358013153076172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.49037790298462s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.3246440887451172s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.625831127166748s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 8.511543273925781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.32249999046325684s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.468032121658325s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0007863044738769531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.3004298210144043s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.021643877029418945s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.458337545394897s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.33176136016845703s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.515655040740967s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 8.96453857421875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.28801512718200684s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.022481441497802734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.459118604660034s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 8.511543273925781e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.27966785430908203s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.02231454849243164s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.67572021484375e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.239776611328125e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.702329158782959s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.458427429199219e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.26437950134277344s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 4.649162292480469e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.0251998901367188e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 3.22782564163208s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 8.893013000488281e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.2913947105407715s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.022316455841064453s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.743171691894531e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.1205673217773438e-05s
INFO | --- Analysis for university-sussex-reading-lists took 3.0108659267425537s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 6.555671215057373s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.29081273078918457s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 6.914138793945312e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 9.775161743164062e-06s
INFO | --- Analysis for unodc took 18.73060655593872s
Availability | SPARQL endpoint availability check for Super Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for Super Ontology took 0.0007886886596679688s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.29355692863464355s
Reputation | Calculation of the PageRank for Super Ontology took 0.021196842193603516s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 9.083747863769531e-05s
Believability | Calculation of trust value for Super Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for upper-ontology took 3.8453009128570557s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 1.0797746181488037s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.32041049003601074s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.021029949188232422s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.62396240234375e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for Upper_Ontology took 5.340548515319824s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 4.482269287109375e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.2869124412536621s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.020791053771972656s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 2.8848648071289062e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.0013580322265625e-05s
INFO | --- Analysis for Urban_Atlas_ took 2.6383211612701416s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.6980772018432617s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0006504058837890625s
Extra | Recovery of all triples for Urban Atlas dataset @PSNC took 100.33477401733398s
Performance | Total latancy measurement for Urban Atlas dataset @PSNC took 1.0026111602783203s
Amount of data | Number of triples check for Urban Atlas dataset @PSNC took 9.113365411758423s
Interoperability | New terms check for Urban Atlas dataset @PSNC took 14.06333613395691s
Versatility | Languages check for Urban Atlas dataset @PSNC took 300.2484600543976s
Interpretability | Number of blank nodes check for Urban Atlas dataset @PSNC took 2.215411424636841s
Interpretability | RDF structures check for Urban Atlas dataset @PSNC took 0.3096802234649658s
Versatility | Serialization formats check for Urban Atlas dataset @PSNC took 11.072511434555054s
Availability | RDF dump link check for Urban Atlas dataset @PSNC took 0.3166069984436035s
License | MR license check for Urban Atlas dataset @PSNC took 0.6436686515808105s
License | HR license check for Urban Atlas dataset @PSNC took 300.21790981292725s
Amount of data | Number of property check for Urban Atlas dataset @PSNC took 0.2179577350616455s
Understandability | Number of label check for Urban Atlas dataset @PSNC took 2.6990678310394287s
Understandability | URI regex check for Urban Atlas dataset @PSNC took 1.008920669555664s
Understandability | Vocabs check for Urban Atlas dataset @PSNC took 0.5251905918121338s
Verifiability | Authors check for Urban Atlas dataset @PSNC took 0.20528817176818848s
Verifiability | Publishers check for Urban Atlas dataset @PSNC took 0.30558228492736816s
Performance | Throughput check for Urban Atlas dataset @PSNC took 11.431369304656982s
Amount of data | Check the number of entities for Urban Atlas dataset @PSNC took 6.890296936035156e-05s
Verifiability | Contribs. check for Urban Atlas dataset @PSNC took 0.19926834106445312s
Interlinking | sameAs chians check for Urban Atlas dataset @PSNC took 0.2176065444946289s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.42072224617004395s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.38558053970336914s
Timeliness | dataset update frequency check for Urban Atlas dataset @PSNC took 6.000288963317871s
Currency | Creation date check for Urban Atlas dataset @PSNC took 0.47719717025756836s
Currency | Modification date check for Urban Atlas dataset @PSNC took 0.2590212821960449s
Rep.Conc. | URIs length for Urban Atlas dataset @PSNC took 156.25912833213806s
Interoperability | New vocabularies check for Urban Atlas dataset @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Urban Atlas dataset @PSNC took 0.20208144187927246s
Accuracy | Check Functional Property for Urban Atlas dataset @PSNC took 0.396651029586792s
Accuracy | Check Inverse Functional Property for Urban Atlas dataset @PSNC took 0.37851452827453613s
Accuracy | Check Empty annotation labels for Urban Atlas dataset @PSNC took 42.28899431228638s
Accuracy | Check White space in annotation for Urban Atlas dataset @PSNC took 2.717741012573242s
Accuracy | Check Datatype consistency for Urban Atlas dataset @PSNC took 2.64363956451416s
Consistency | Disjoint class check for Urban Atlas dataset @PSNC took 0.196868896484375s
Consistency | Check Misplaced properties for Urban Atlas dataset @PSNC took 85.95510625839233s
Consistency | Misplaced classes for Urban Atlas dataset @PSNC took 8.431239604949951s
Consistency | Check Ontology hijacking for Urban Atlas dataset @PSNC took 36.786425828933716s
Consistency | Check Invalid usage of undefined classes for Urban Atlas dataset @PSNC took 1.3892571926116943s
Consistency | Check Invalid usage of undefined properties for Urban Atlas dataset @PSNC took 87.14279651641846s
Conciseness | Check Extensional conciseness for Urban Atlas dataset @PSNC took 2.8181934356689453s
Conciseness | Check Intensional conciseness for Urban Atlas dataset @PSNC took 0.531296968460083s
Security | Sign check for Urban Atlas dataset @PSNC took 1.166780948638916s
Availability | Check URIs Dereferenciability for Urban Atlas dataset @PSNC took 10.332759380340576s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.5002658367156982s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.021216869354248047s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007052421569824219s
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 1.9073486328125e-06s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 1.0967254638671875e-05s
INFO | --- Analysis for Urban_Atlas_Dataset took 2264.536289215088s
Availability | SPARQL endpoint availability check for URIBurner took 0.9410247802734375s
Availability | VoID file availability check for URIBurner took 0.0006308555603027344s
Extra | Recovery of all triples for URIBurner took 121.32817196846008s
Performance | Total latancy measurement for URIBurner took 2.764357805252075s
Amount of data | Number of triples check for URIBurner took 3.5012128353118896s
Interoperability | New terms check for URIBurner took 37.77884340286255s
Versatility | Languages check for URIBurner took 122.64007377624512s
Interpretability | Number of blank nodes check for URIBurner took 1.8376893997192383s
Security | Check HTTPS for URIBurner took 0.9224898815155029s
Interpretability | RDF structures check for URIBurner took 0.819610595703125s
Versatility | Serialization formats check for URIBurner took 6.0853657722473145s
Availability | RDF dump link check for URIBurner took 44.8540894985199s
License | MR license check for URIBurner took 0.797846794128418s
License | HR license check for URIBurner took 122.8072156906128s
Amount of data | Number of property check for URIBurner took 0.7559645175933838s
Understandability | Number of label check for URIBurner took 3.081190824508667s
Understandability | URI regex check for URIBurner took 1.2245597839355469s
Understandability | Vocabs check for URIBurner took 0.5888381004333496s
Verifiability | Authors check for URIBurner took 0.7625961303710938s
Verifiability | Publishers check for URIBurner took 0.5882375240325928s
Performance | Throughput check for URIBurner took 10.998527765274048s
Amount of data | Check the number of entities for URIBurner took 4.1961669921875e-05s
Verifiability | Contribs. check for URIBurner took 0.5951740741729736s
Interlinking | sameAs chians check for URIBurner took 0.9515986442565918s
Interlinking | skos check for URIBurner took 0.5842418670654297s
Interlinking | skos check for URIBurner took 0.5361368656158447s
Timeliness | dataset update frequency check for URIBurner took 1.0020017623901367s
Currency | Creation date check for URIBurner took 3.1283040046691895s
Currency | Modification date check for URIBurner took 0.6346435546875s
Rep.Conc. | URIs length for URIBurner took 116.15760064125061s
Interoperability | New vocabularies check for URIBurner took 26.14066219329834s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.6204814910888672s
Accuracy | Check Functional Property for URIBurner took 0.6075713634490967s
Accuracy | Check Inverse Functional Property for URIBurner took 0.579535722732544s
Accuracy | Check Empty annotation labels for URIBurner took 56.43930649757385s
Accuracy | Check White space in annotation for URIBurner took 0.18808293342590332s
Consistency | Disjoint class check for URIBurner took 0.5805249214172363s
Consistency | Check Misplaced properties for URIBurner took 384.3264801502228s
Consistency | Misplaced classes for URIBurner took 56.822782039642334s
Consistency | Check Ontology hijacking for URIBurner took 58.711217641830444s
Consistency | Check Invalid usage of undefined properties for URIBurner took 59.579248905181885s
Conciseness | Check Extensional conciseness for URIBurner took 0.00015592575073242188s
Conciseness | Check Intensional conciseness for URIBurner took 111.37195253372192s
Security | Sign check for URIBurner took 0.773141622543335s
Completeness | Calculation of interlinking completeness for URIBurner took 0.7757389545440674s
Reputation | Calculation of the PageRank for URIBurner took 0.02075791358947754s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00011229515075683594s
Interoperability | Check the re-using of existing vocabs for URIBurner took 22.27558970451355s
Believability | Calculation of trust value for URIBurner took 1.6450881958007812e-05s
INFO | --- Analysis for uriburner took 11569.21133852005s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00010156631469726562s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.3191540241241455s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.021203041076660156s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.337860107421875e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.33514404296875e-05s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.7793524265289307s
Availability | SPARQL endpoint availability check for Legija Stranaca took 8.988380432128906e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.26696109771728516s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.023869752883911133s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.24249267578125e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.430511474609375e-05s
INFO | --- Analysis for Uros_Legija_Susa took 2.6777217388153076s
Availability | SPARQL endpoint availability check for Legija took 0.00011086463928222656s
Availability | VoID file availability check for Legija took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Legija took 0.29894447326660156s
Reputation | Calculation of the PageRank for Legija took 0.02092742919921875s
Interlinking | Calculation of Degree of Connection for Legija took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Legija took 3.3855438232421875e-05s
Believability | Calculation of trust value for Legija took 1.1920928955078125e-05s
INFO | --- Analysis for Uros_Susa took 2.7655563354492188s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.5066962242126465s
Availability | VoID file availability check for USAGE review corpus took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.298663854598999s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020773649215698242s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.457069396972656e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.1205673217773438e-05s
INFO | --- Analysis for usage-review-corpus took 3.9223289489746094s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 3.844179153442383s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.3175058364868164s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.02246546745300293s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.796287536621094e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.1205673217773438e-05s
INFO | --- Analysis for utpl-lod took 10.442935705184937s
Availability | SPARQL endpoint availability check for terrorist attack took 9.107589721679688e-05s
Availability | VoID file availability check for terrorist attack took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.3060767650604248s
Reputation | Calculation of the PageRank for terrorist attack took 0.020874738693237305s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.457069396972656e-05s
Believability | Calculation of trust value for terrorist attack took 1.0251998901367188e-05s
INFO | --- Analysis for varsha took 4.504960775375366s
Availability | SPARQL endpoint availability check for VA took 0.00010085105895996094s
Availability | VoID file availability check for VA took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for VA took 0.28528690338134766s
Reputation | Calculation of the PageRank for VA took 0.022537946701049805s
Interlinking | Calculation of Degree of Connection for VA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for VA took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for VA took 3.337860107421875e-05s
Believability | Calculation of trust value for VA took 1.1682510375976562e-05s
INFO | --- Analysis for Vehicule_Autonome took 3.2149598598480225s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.6846189498901367s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.3241415023803711s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.02103281021118164s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 4.172325134277344e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 1.430511474609375e-05s
INFO | --- Analysis for VelezIndexTotiusArtis took 4.421571493148804s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.570846796035767s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.3260784149169922s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.022884607315063477s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 0.00010085105895996094s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.3113021850585938e-05s
INFO | --- Analysis for verrijktkoninkrijk took 15.88497018814087s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 4.4345855712890625e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.3092379570007324s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.02265000343322754s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.001245737075805664s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00022149085998535156s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.239776611328125e-05s
INFO | --- Analysis for viaf took 20.205224990844727s
Availability | SPARQL endpoint availability check for Vihar Exports took 8.7738037109375e-05s
Availability | VoID file availability check for Vihar Exports took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.3000919818878174s
Reputation | Calculation of the PageRank for Vihar Exports took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.170967102050781e-05s
Believability | Calculation of trust value for Vihar Exports took 6.9141387939453125e-06s
INFO | --- Analysis for Vihar_Exports took 2.70192813873291s
Availability | SPARQL endpoint availability check for VIVO took 4.315376281738281e-05s
Availability | VoID file availability check for VIVO took 0.0007894039154052734s
Completeness | Calculation of interlinking completeness for VIVO took 0.27741265296936035s
Reputation | Calculation of the PageRank for VIVO took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for VIVO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.914138793945312e-05s
Believability | Calculation of trust value for VIVO took 1.239776611328125e-05s
INFO | --- Analysis for vivo took 5.291356801986694s
Availability | SPARQL endpoint availability check for VIVO Cornell took 8.845329284667969e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.29490208625793457s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.020862102508544922s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.153915405273438e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.2636184692382812e-05s
INFO | --- Analysis for vivo-cornell-university took 6.382771968841553s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.267692565917969e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.3087749481201172s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.022543907165527344s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.559226989746094e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.0728836059570312e-05s
INFO | --- Analysis for vivo-indiana-university took 3.4307315349578857s
Availability | SPARQL endpoint availability check for VIVO Ponce took 8.916854858398438e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.32329845428466797s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0009465217590332031s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 4.5299530029296875e-05s
Believability | Calculation of trust value for VIVO Ponce took 1.3113021850585938e-05s
INFO | --- Analysis for vivo-ponce took 3.1336543560028076s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 8.869171142578125e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.001168966293334961s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.3048529624938965s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 4.0531158447265625e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 1.2874603271484375e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 3.792006254196167s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 8.96453857421875e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.27617979049682617s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.02106165885925293s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.870529174804688e-05s
Believability | Calculation of trust value for VIVO University of Florida took 1.1444091796875e-05s
INFO | --- Analysis for vivo-university-of-florida took 2.7187693119049072s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 9.965896606445312e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.3038651943206787s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.02237701416015625s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0010840892791748047s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 4.982948303222656e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 1.33514404296875e-05s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 3.179720163345337s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 0.00011086463928222656s
Availability | VoID file availability check for VIVO WUSTL took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.30776524543762207s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.02175450325012207s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.719329833984375e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.2874603271484375e-05s
INFO | --- Analysis for vivo-wustl took 3.113330602645874s
Availability | SPARQL endpoint availability check for vivo2doi took 8.678436279296875e-05s
Availability | VoID file availability check for vivo2doi took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.29433393478393555s
Reputation | Calculation of the PageRank for vivo2doi took 0.02077627182006836s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.4345855712890625e-05s
Believability | Calculation of trust value for vivo2doi took 1.1205673217773438e-05s
INFO | --- Analysis for vivo2doi took 26.621965646743774s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 4.363059997558594e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.000682830810546875s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.2985727787017822s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.961822509765625e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.3113021850585938e-05s
INFO | --- Analysis for vu-wordnet took 14.921596050262451s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.07630348205566406s
Availability | VoID file availability check for vulnerapedia took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.31250452995300293s
Reputation | Calculation of the PageRank for vulnerapedia took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.842613220214844e-05s
Believability | Calculation of trust value for vulnerapedia took 1.239776611328125e-05s
INFO | --- Analysis for vulnerapedia took 3.3967175483703613s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 9.012222290039062e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.3161187171936035s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.02286219596862793s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.2636184692382812e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.2874603271484375e-05s
INFO | --- Analysis for VVASIAK took 2.572094202041626s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 9.059906005859375e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.3060455322265625s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.528594970703125e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.049041748046875e-05s
INFO | --- Analysis for Vyvasta took 2.7743687629699707s
Availability | SPARQL endpoint availability check for W3C took 4.673004150390625e-05s
Availability | VoID file availability check for W3C took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for W3C took 0.31009435653686523s
Reputation | Calculation of the PageRank for W3C took 0.021541357040405273s
Interlinking | Calculation of Degree of Connection for W3C took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001380443572998047s
Believability | Calculation of trust value for W3C took 1.2636184692382812e-05s
INFO | --- Analysis for w3c took 2.90801739692688s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 4.315376281738281e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.27280306816101074s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00011277198791503906s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.1205673217773438e-05s
INFO | --- Analysis for w3c-wordnet took 4.004676103591919s
Availability | SPARQL endpoint availability check for WarSampo took 0.35677361488342285s
Availability | VoID file availability check for WarSampo took 0.0007128715515136719s
Extra | Recovery of all triples for WarSampo took 23.157562971115112s
Performance | Total latancy measurement for WarSampo took 0.8185348510742188s
Amount of data | Number of triples check for WarSampo took 18.524518728256226s
Interoperability | New terms check for WarSampo took 3.851861000061035s
Versatility | Languages check for WarSampo took 60.19165253639221s
Interpretability | Number of blank nodes check for WarSampo took 19.18511152267456s
Security | Check HTTPS for WarSampo took 0.40007829666137695s
Interpretability | RDF structures check for WarSampo took 0.19069600105285645s
Versatility | Serialization formats check for WarSampo took 0.20898866653442383s
Availability | RDF dump link check for WarSampo took 1.0441007614135742s
License | MR license check for WarSampo took 0.20025253295898438s
License | HR license check for WarSampo took 45.29446053504944s
Amount of data | Number of property check for WarSampo took 0.1931138038635254s
Understandability | Number of label check for WarSampo took 9.045318603515625s
Understandability | URI regex check for WarSampo took 0.35944461822509766s
Understandability | Vocabs check for WarSampo took 0.16146063804626465s
Verifiability | Authors check for WarSampo took 0.1872708797454834s
Verifiability | Publishers check for WarSampo took 0.18860578536987305s
Performance | Throughput check for WarSampo took 11.171932935714722s
Amount of data | Check the number of entities for WarSampo took 15.363735437393188s
Verifiability | Contribs. check for WarSampo took 0.18320631980895996s
Interlinking | sameAs chians check for WarSampo took 0.2067244052886963s
Interlinking | skos check for WarSampo took 0.19927740097045898s
Interlinking | skos check for WarSampo took 0.1600799560546875s
Timeliness | dataset update frequency check for WarSampo took 0.16599583625793457s
Currency | Creation date check for WarSampo took 0.37262868881225586s
Currency | Modification date check for WarSampo took 0.3609323501586914s
Rep.Conc. | URIs length for WarSampo took 48.232691049575806s
Interoperability | New vocabularies check for WarSampo took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.18902230262756348s
Accuracy | Check Functional Property for WarSampo took 0.19471311569213867s
Accuracy | Check Inverse Functional Property for WarSampo took 0.1615276336669922s
Accuracy | Check Empty annotation labels for WarSampo took 10.818318843841553s
Accuracy | Check White space in annotation for WarSampo took 2.222571611404419s
Accuracy | Check Datatype consistency for WarSampo took 5.292274713516235s
Consistency | Disjoint class check for WarSampo took 0.18688035011291504s
Consistency | Check Misplaced properties for WarSampo took 19.818682432174683s
Consistency | Check Ontology hijacking for WarSampo took 19.199700832366943s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.3957502841949463s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.624542474746704s
Conciseness | Check Extensional conciseness for WarSampo took 2.933648109436035s
Conciseness | Check Intensional conciseness for WarSampo took 0.27520227432250977s
Security | Sign check for WarSampo took 0.1688685417175293s
Availability | Check URIs Dereferenciability for WarSampo took 2.68182110786438s
Completeness | Calculation of interlinking completeness for WarSampo took 0.5091097354888916s
Reputation | Calculation of the PageRank for WarSampo took 0.021122455596923828s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for WarSampo took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 3.337860107421875e-06s
Believability | Calculation of trust value for WarSampo took 8.106231689453125e-06s
INFO | --- Analysis for warsampo took 949.7382919788361s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.400988340377808s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.3414885997772217s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.02062368392944336s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 8.20159912109375e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.1444091796875e-05s
INFO | --- Analysis for wasabi took 55.41539645195007s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.5998508930206299s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.000522613525390625s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 115.91402244567871s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 0.9568047523498535s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 9.187061786651611s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 14.064294576644897s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 300.2522327899933s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 2.1348540782928467s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.19636273384094238s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 9.005664587020874s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.19252324104309082s
License | MR license check for FAO water areas classification as linked data @PSNC took 1.0744256973266602s
License | HR license check for FAO water areas classification as linked data @PSNC took 300.20001196861267s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.19654345512390137s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 1.1673545837402344s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 0.378140926361084s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.1955246925354004s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.2147974967956543s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.23633623123168945s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 11.524230003356934s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 5.841255187988281e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.20134663581848145s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.20885252952575684s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.5160503387451172s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.4087789058685303s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 5.262702941894531s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.5165319442749023s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.26201391220092773s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 148.03892970085144s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.20241403579711914s
Accuracy | Check Functional Property for FAO water areas classification as linked data @PSNC took 0.1927323341369629s
Accuracy | Check Inverse Functional Property for FAO water areas classification as linked data @PSNC took 0.18843293190002441s
Accuracy | Check Empty annotation labels for FAO water areas classification as linked data @PSNC took 39.14026951789856s
Accuracy | Check White space in annotation for FAO water areas classification as linked data @PSNC took 2.71561598777771s
Accuracy | Check Datatype consistency for FAO water areas classification as linked data @PSNC took 2.625927686691284s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.22356653213500977s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 86.19167041778564s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 8.498088836669922s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 33.1168475151062s
Consistency | Check Invalid usage of undefined classes for FAO water areas classification as linked data @PSNC took 1.3318891525268555s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 86.540363073349s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 2.8284783363342285s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.5246679782867432s
Security | Sign check for FAO water areas classification as linked data @PSNC took 1.570561408996582s
Availability | Check URIs Dereferenciability for FAO water areas classification as linked data @PSNC took 10.391775608062744s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.4532201290130615s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.021226882934570312s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 4.172325134277344e-05s
Interoperability | Check the re-using of existing vocabs for FAO water areas classification as linked data @PSNC took 5.0067901611328125e-06s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 1.3589859008789062e-05s
INFO | --- Analysis for Water_Areas_Classification took 2259.331102848053s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.19891929626464844s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.00025343894958496094s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 115.05789375305176s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 0.986851692199707s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 9.02133059501648s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 14.085298538208008s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 300.21251797676086s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 1.9955785274505615s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.21150970458984375s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 6.9508140087127686s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.17717957496643066s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.19190454483032227s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 300.16175603866577s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.21149277687072754s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 1.1938705444335938s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 1.008030891418457s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.2081737518310547s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.17675375938415527s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.2626035213470459s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 11.156369924545288s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 6.842613220214844e-05s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.19424748420715332s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.1820223331451416s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.46994853019714355s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.4206109046936035s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 4.270889043807983s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.4772367477416992s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.2355198860168457s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 159.3522448539734s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.19991636276245117s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.19566965103149414s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.19801712036132812s
Accuracy | Check Empty annotation labels for Water buffer dataset from Czech Republic @PSNC took 33.7201783657074s
Accuracy | Check White space in annotation for Water buffer dataset from Czech Republic @PSNC took 2.7226810455322266s
Accuracy | Check Datatype consistency for Water buffer dataset from Czech Republic @PSNC took 2.658140182495117s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.19299006462097168s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 85.69050073623657s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 8.49578595161438s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 36.16293215751648s
Consistency | Check Invalid usage of undefined classes for Water buffer dataset from Czech Republic @PSNC took 1.474940538406372s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 86.60140919685364s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 2.8024556636810303s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.5192511081695557s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 0.17644858360290527s
Availability | Check URIs Dereferenciability for Water buffer dataset from Czech Republic @PSNC took 9.345128536224365s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 1.4827444553375244s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.021509885787963867s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 6.413459777832031e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for Water buffer dataset from Czech Republic @PSNC took 4.5299530029296875e-06s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.5020370483398438e-05s
INFO | --- Analysis for Water_Buffer took 2298.7030017375946s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.29576611518859863s
Availability | VoID file availability check for WebIsALOD took 0.000537872314453125s
Extra | Recovery of all triples for WebIsALOD took 1.1432137489318848s
Performance | Total latancy measurement for WebIsALOD took 0.43526577949523926s
Amount of data | Number of triples check for WebIsALOD took 23.96505832672119s
Interoperability | New terms check for WebIsALOD took 20.051100969314575s
Versatility | Languages check for WebIsALOD took 62.74490189552307s
Interpretability | Number of blank nodes check for WebIsALOD took 0.11766552925109863s
Interpretability | RDF structures check for WebIsALOD took 0.12895750999450684s
Versatility | Serialization formats check for WebIsALOD took 0.13546133041381836s
Availability | RDF dump link check for WebIsALOD took 1.3545763492584229s
License | MR license check for WebIsALOD took 0.10776162147521973s
License | HR license check for WebIsALOD took 21.053134202957153s
Amount of data | Number of property check for WebIsALOD took 0.11588287353515625s
Understandability | Number of label check for WebIsALOD took 0.2916438579559326s
Understandability | URI regex check for WebIsALOD took 0.1704397201538086s
Understandability | Vocabs check for WebIsALOD took 0.11103677749633789s
Verifiability | Authors check for WebIsALOD took 0.11825084686279297s
Verifiability | Publishers check for WebIsALOD took 0.12580537796020508s
Performance | Throughput check for WebIsALOD took 10.511770009994507s
Amount of data | Check the number of entities for WebIsALOD took 0.00011014938354492188s
Verifiability | Contribs. check for WebIsALOD took 0.11185526847839355s
Interlinking | sameAs chians check for WebIsALOD took 0.17810487747192383s
Interlinking | skos check for WebIsALOD took 0.12505269050598145s
Interlinking | skos check for WebIsALOD took 0.08234047889709473s
Timeliness | dataset update frequency check for WebIsALOD took 0.09255719184875488s
Currency | Creation date check for WebIsALOD took 0.24068737030029297s
Currency | Modification date check for WebIsALOD took 0.19657349586486816s
Rep.Conc. | URIs length for WebIsALOD took 80.1430253982544s
Interoperability | New vocabularies check for WebIsALOD took 3.745206117630005s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 0.2826199531555176s
Accuracy | Check Functional Property for WebIsALOD took 0.14310169219970703s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.10308480262756348s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.5250325202941895s
Accuracy | Check White space in annotation for WebIsALOD took 0.030286550521850586s
Accuracy | Check Datatype consistency for WebIsALOD took 0.02908182144165039s
Consistency | Disjoint class check for WebIsALOD took 0.11085104942321777s
Consistency | Check Misplaced properties for WebIsALOD took 62.16061091423035s
Consistency | Misplaced classes for WebIsALOD took 0.22767162322998047s
Consistency | Check Ontology hijacking for WebIsALOD took 1.9633026123046875s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.597245216369629s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 62.92679691314697s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.03369736671447754s
Conciseness | Check Intensional conciseness for WebIsALOD took 0.1545877456665039s
Security | Sign check for WebIsALOD took 0.10236287117004395s
Availability | Check URIs Dereferenciability for WebIsALOD took 9.909307718276978s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.4325554370880127s
Reputation | Calculation of the PageRank for WebIsALOD took 0.021562576293945312s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 6.771087646484375e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 0.00013780593872070312s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 2.516963481903076s
Believability | Calculation of trust value for WebIsALOD took 1.4066696166992188e-05s
INFO | --- Analysis for webisalod took 532.7639329433441s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 4.291534423828125e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.3125s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.6716461181640625e-05s
Believability | Calculation of trust value for webnmasunotraveler took 8.344650268554688e-06s
INFO | --- Analysis for webnmasunotraveler took 8.883602380752563s
Availability | SPARQL endpoint availability check for Whisky Circle took 4.3392181396484375e-05s
Availability | VoID file availability check for Whisky Circle took 0.0003228187561035156s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.28946590423583984s
Reputation | Calculation of the PageRank for Whisky Circle took 0.021009206771850586s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.0001068115234375s
Believability | Calculation of trust value for Whisky Circle took 1.0013580322265625e-05s
INFO | --- Analysis for whisky-circle-info took 6.309392690658569s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 17.528759956359863s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0008022785186767578s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.299121618270874s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.022164106369018555s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.6716461181640625e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.239776611328125e-05s
INFO | --- Analysis for WHOnto took 36.975013256073s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 9.322166442871094e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.28459787368774414s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.021876811981201172s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.33514404296875e-05s
INFO | --- Analysis for whonto took 8.595520973205566s
Availability | SPARQL endpoint availability check for Wikidata took 0.5404911041259766s
Availability | VoID file availability check for Wikidata took 0.0006546974182128906s
Extra | Recovery of all triples for Wikidata took 1.442307710647583s
Amount of data | Number of triples check for Wikidata took 65.18104124069214s
Versatility | Languages check for Wikidata took 0.1683797836303711s
Interpretability | Number of blank nodes check for Wikidata took 0.30006861686706543s
Interpretability | RDF structures check for Wikidata took 0.1690692901611328s
Versatility | Serialization formats check for Wikidata took 0.16816949844360352s
Availability | RDF dump link check for Wikidata took 0.16938233375549316s
License | MR license check for Wikidata took 0.17834830284118652s
License | HR license check for Wikidata took 0.168287992477417s
Amount of data | Number of property check for Wikidata took 0.47773289680480957s
Understandability | Number of label check for Wikidata took 60.186172008514404s
Understandability | URI regex check for Wikidata took 0.33962488174438477s
Understandability | Vocabs check for Wikidata took 0.18053555488586426s
Verifiability | Authors check for Wikidata took 0.1685192584991455s
Verifiability | Publishers check for Wikidata took 0.18348288536071777s
Amount of data | Check the number of entities for Wikidata took 0.00013303756713867188s
Verifiability | Contribs. check for Wikidata took 0.16953730583190918s
Interlinking | sameAs chians check for Wikidata took 0.16949772834777832s
Interlinking | skos check for Wikidata took 0.19657158851623535s
Interlinking | skos check for Wikidata took 0.1842632293701172s
Timeliness | dataset update frequency check for Wikidata took 0.16872143745422363s
Currency | Creation date check for Wikidata took 0.5112583637237549s
Currency | Modification date check for Wikidata took 0.3488309383392334s
Rep.Conc. | URIs length for Wikidata took 8.628678798675537s
Interoperability | New vocabularies check for Wikidata took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for Wikidata took 0.16588759422302246s
Consistency | Disjoint class check for Wikidata took 0.1695694923400879s
Consistency | Check Ontology hijacking for Wikidata took 0.16962862014770508s
Consistency | Check Invalid usage of undefined properties for Wikidata took 1.4416418075561523s
Conciseness | Check Extensional conciseness for Wikidata took 0.0001285076141357422s
Security | Sign check for Wikidata took 0.2546091079711914s
Completeness | Calculation of interlinking completeness for Wikidata took 0.38079833984375s
Reputation | Calculation of the PageRank for Wikidata took 0.02228569984436035s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0002944469451904297s
Interoperability | Check the re-using of existing vocabs for Wikidata took 4.76837158203125e-07s
Believability | Calculation of trust value for Wikidata took 9.298324584960938e-06s
INFO | --- Analysis for wikidata took 232.60944509506226s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 4.410743713378906e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.27692222595214844s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.020145416259765625s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 6.723403930664062e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 7.62939453125e-06s
INFO | --- Analysis for wikilinks-rdf-nif took 2.9414985179901123s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2855188846588135s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.2934751510620117s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.058547973632812e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 8.344650268554688e-06s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.5097057819366455s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2837257385253906s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.29298973083496094s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.022587299346923828s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.910064697265625e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.239776611328125e-05s
INFO | --- Analysis for wl-kg took 4.213736534118652s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 8.7738037109375e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.27788567543029785s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.022258758544921875s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 9.012222290039062e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.0251998901367188e-05s
INFO | --- Analysis for wn-wiki-instances took 3.4276340007781982s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.2165696620941162s
Availability | VoID file availability check for World Loanword Database took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.2822139263153076s
Reputation | Calculation of the PageRank for World Loanword Database took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.271766662597656e-05s
Believability | Calculation of trust value for World Loanword Database took 1.0967254638671875e-05s
INFO | --- Analysis for wold took 3.0540037155151367s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 0.00010156631469726562s
Availability | VoID file availability check for Wood Trick LLC took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.2944779396057129s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.020826339721679688s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 3.528594970703125e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.1205673217773438e-05s
INFO | --- Analysis for woodtrick took 3.300877332687378s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.5623855590820312s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0013060569763183594s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.2894444465637207s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.02028369903564453s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for WordFormationLatin took 4.355787515640259s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 8.392333984375e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.29798030853271484s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.02231454849243164s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010776519775390625s
Believability | Calculation of trust value for WordLift Blog EN took 1.3828277587890625e-05s
INFO | --- Analysis for wordlift-io-blog-en took 3.21445894241333s
Availability | SPARQL endpoint availability check for WordLift IT took 4.410743713378906e-05s
Availability | VoID file availability check for WordLift IT took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.3006157875061035s
Reputation | Calculation of the PageRank for WordLift IT took 0.02073955535888672s
Interlinking | Calculation of Degree of Connection for WordLift IT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00010514259338378906s
Believability | Calculation of trust value for WordLift IT took 1.049041748046875e-05s
INFO | --- Analysis for wordlift-io-blog-it took 4.489312171936035s
Availability | SPARQL endpoint availability check for WordNet-RDF took 0.00010228157043457031s
Availability | VoID file availability check for WordNet-RDF took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.27562713623046875s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.02262425422668457s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.131431579589844e-05s
Believability | Calculation of trust value for WordNet-RDF took 1.4066696166992188e-05s
INFO | --- Analysis for wordnet-rdf took 2.7650535106658936s
Availability | SPARQL endpoint availability check for wordpress took 8.940696716308594e-05s
Availability | VoID file availability check for wordpress took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for wordpress took 0.3007636070251465s
Reputation | Calculation of the PageRank for wordpress took 0.02202129364013672s
Interlinking | Calculation of Degree of Connection for wordpress took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.726119995117188e-05s
Believability | Calculation of trust value for wordpress took 1.1205673217773438e-05s
INFO | --- Analysis for wordpress took 3.186457872390747s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.11848688125610352s
Availability | VoID file availability check for World Bank Linked Data took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.29537105560302734s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.021967411041259766s
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.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.0001227855682373047s
Believability | Calculation of trust value for World Bank Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for world-bank-linked-data took 2.924492835998535s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 1.124903678894043s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.2843897342681885s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.344650268554688e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 9.775161743164062e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 5.644739151000977s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.363059997558594e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.31227779388427734s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.020884275436401367s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.58306884765625e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 9.059906005859375e-06s
INFO | --- Analysis for world-wide-web-foundation took 5.9995739459991455s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.3853027820587158s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0007109642028808594s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 2.5412161350250244s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8047146797180176s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.23783612251281738s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.494466781616211s
Versatility | Languages check for World War 1 as Linked Open Data took 0.36743927001953125s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.24062275886535645s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.4025309085845947s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.31622791290283203s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.2834951877593994s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.7554168701171875s
License | MR license check for World War 1 as Linked Open Data took 0.1974468231201172s
License | HR license check for World War 1 as Linked Open Data took 1.4867103099822998s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.19608187675476074s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.2651844024658203s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.36452364921569824s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.22365522384643555s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.19715023040771484s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.18776512145996094s
Performance | Throughput check for World War 1 as Linked Open Data took 11.10603141784668s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07270002365112305s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.18865966796875s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.2186119556427002s
Interlinking | skos check for World War 1 as Linked Open Data took 0.18812918663024902s
Interlinking | skos check for World War 1 as Linked Open Data took 0.16420722007751465s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.15625405311584473s
Currency | Creation date check for World War 1 as Linked Open Data took 0.37981295585632324s
Currency | Modification date check for World War 1 as Linked Open Data took 0.19211363792419434s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 2.001452922821045s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 5.415650844573975s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.19993209838867188s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.18758654594421387s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.16665077209472656s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.1218712329864502s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.050161123275756836s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.3067007064819336s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.18729782104492188s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6046907901763916s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.0023016929626465s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.2582085132598877s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.501377820968628s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.1916217803955078s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.6481883525848389s
Security | Sign check for World War 1 as Linked Open Data took 0.17233681678771973s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1537.1538894176483s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.5014815330505371s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.02135777473449707s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 5.7220458984375e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 9.417533874511719e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 5.522583723068237s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for ww1lod took 1615.673284292221s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.36586833000183105s
Availability | VoID file availability check for xLiD-Lexica took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.28857994079589844s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 6.67572021484375e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.4781951904296875e-05s
INFO | --- Analysis for xlid-lexica took 4.35031270980835s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 0.00010132789611816406s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.29751038551330566s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.022312641143798828s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.647804260253906e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 5.316734313964844e-05s
INFO | --- Analysis for xwn took 3.2751128673553467s
Availability | SPARQL endpoint availability check for xxx took 8.535385131835938e-05s
Availability | VoID file availability check for xxx took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for xxx took 0.28652048110961914s
Reputation | Calculation of the PageRank for xxx took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for xxx took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for xxx took 2.9802322387695312e-05s
Believability | Calculation of trust value for xxx took 1.0251998901367188e-05s
INFO | --- Analysis for xx took 2.6119470596313477s
Availability | SPARQL endpoint availability check for YAGO took 4.2438507080078125e-05s
Availability | VoID file availability check for YAGO took 0.0012927055358886719s
Completeness | Calculation of interlinking completeness for YAGO took 0.290602445602417s
Reputation | Calculation of the PageRank for YAGO took 0.022210359573364258s
Interlinking | Calculation of Degree of Connection for YAGO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00013113021850585938s
Believability | Calculation of trust value for YAGO took 1.2874603271484375e-05s
INFO | --- Analysis for yago took 4.534292459487915s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 1.6625337600708008s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.33089137077331543s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.02018451690673828s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.748603820800781e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.1920928955078125e-05s
INFO | --- Analysis for yahoo_geoplanet took 33.72221899032593s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.1690812110900879s
Availability | VoID file availability check for Yale Senselab took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.2980661392211914s
Reputation | Calculation of the PageRank for Yale Senselab took 0.02208733558654785s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0010492801666259766s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 3.5762786865234375e-05s
Believability | Calculation of trust value for Yale Senselab took 1.1920928955078125e-05s
INFO | --- Analysis for yale_senselab took 11.69829249382019s
Availability | SPARQL endpoint availability check for test-dapp-2 took 8.702278137207031e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.3138289451599121s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.021709203720092773s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 2.9802322387695312e-05s
Believability | Calculation of trust value for test-dapp-2 took 1.1444091796875e-05s
INFO | --- Analysis for yordhis took 2.731982946395874s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.83229660987854s
Availability | VoID file availability check for Yovisto - academic video search took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.28081655502319336s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.556510925292969e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 4.0531158447265625e-06s
INFO | --- Analysis for yovisto took 24.6401150226593s
Availability | SPARQL endpoint availability check for YSA - General Finnish Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for YSA - General Finnish Thesaurus took 0.00031304359436035156s
Completeness | Calculation of interlinking completeness for YSA - General Finnish Thesaurus took 0.28682780265808105s
Reputation | Calculation of the PageRank for YSA - General Finnish Thesaurus took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for YSA - General Finnish Thesaurus took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for YSA - General Finnish Thesaurus took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for YSA - General Finnish Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for YSA - General Finnish Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for ysa took 4.144983530044556s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.2701907157897949s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.054473876953125e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for yso took 4.353578805923462s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.2438507080078125e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0003592967987060547s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.27982378005981445s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.02046489715576172s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.147125244140625e-05s
Believability | Calculation of trust value for yso-fi-allars took 4.76837158203125e-06s
INFO | --- Analysis for yso-fi-allars took 3.2656919956207275s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.076957702636719e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0015652179718017578s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.3161764144897461s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.2901763916015625e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.3828277587890625e-05s
INFO | --- Analysis for yso-fi-ysa took 3.3533058166503906s
Availability | SPARQL endpoint availability check for YSO places took 0.7016637325286865s
Availability | VoID file availability check for YSO places took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for YSO places took 0.2944941520690918s
Reputation | Calculation of the PageRank for YSO places took 0.0206601619720459s
Interlinking | Calculation of Degree of Connection for YSO places took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.1948089599609375e-05s
Believability | Calculation of trust value for YSO places took 1.3589859008789062e-05s
INFO | --- Analysis for yso-paikat took 4.378290414810181s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.601478576660156e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.3230247497558594s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.022413253784179688s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.409385681152344e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 8.106231689453125e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 73.2853479385376s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 8.726119995117188e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.3234899044036865s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.021003246307373047s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.266334533691406e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.2636184692382812e-05s
INFO | --- Analysis for zaragoza_turruta took 12.747893810272217s
Availability | SPARQL endpoint availability check for ZBW Labs took 7.009506225585938e-05s
Availability | VoID file availability check for ZBW Labs took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.30651307106018066s
Reputation | Calculation of the PageRank for ZBW Labs took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 6.866455078125e-05s
Believability | Calculation of trust value for ZBW Labs took 1.239776611328125e-05s
INFO | --- Analysis for zbw-labs took 3.7502706050872803s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.15662217140197754s
Availability | VoID file availability check for 20th Century Press Archives took 0.00033283233642578125s
Extra | Recovery of all triples for 20th Century Press Archives took 25.542206525802612s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7705566883087158s
Amount of data | Number of triples check for 20th Century Press Archives took 2.2103025913238525s
Interoperability | New terms check for 20th Century Press Archives took 1.8775460720062256s
Versatility | Languages check for 20th Century Press Archives took 6.8872129917144775s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 1.1514179706573486s
Interpretability | RDF structures check for 20th Century Press Archives took 0.16075611114501953s
Versatility | Serialization formats check for 20th Century Press Archives took 0.14048290252685547s
Availability | RDF dump link check for 20th Century Press Archives took 0.1476123332977295s
License | MR license check for 20th Century Press Archives took 0.16312837600708008s
License | HR license check for 20th Century Press Archives took 5.670569181442261s
Amount of data | Number of property check for 20th Century Press Archives took 0.16930890083312988s
Understandability | Number of label check for 20th Century Press Archives took 0.6684525012969971s
Understandability | URI regex check for 20th Century Press Archives took 0.2936563491821289s
Understandability | Vocabs check for 20th Century Press Archives took 0.15266060829162598s
Verifiability | Authors check for 20th Century Press Archives took 0.1643505096435547s
Verifiability | Publishers check for 20th Century Press Archives took 0.1521289348602295s
Performance | Throughput check for 20th Century Press Archives took 10.659263372421265s
Amount of data | Check the number of entities for 20th Century Press Archives took 0.00010752677917480469s
Verifiability | Contribs. check for 20th Century Press Archives took 0.1505751609802246s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.13799309730529785s
Interlinking | skos check for 20th Century Press Archives took 0.19741296768188477s
Interlinking | skos check for 20th Century Press Archives took 0.1821610927581787s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.12993979454040527s
Currency | Creation date check for 20th Century Press Archives took 0.2892436981201172s
Currency | Modification date check for 20th Century Press Archives took 0.30927419662475586s
Rep.Conc. | URIs length for 20th Century Press Archives took 15.706083297729492s
Interoperability | New vocabularies check for 20th Century Press Archives took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.14252614974975586s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.16384339332580566s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.12808918952941895s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 4.768808841705322s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8999247550964355s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.0860748291015625s
Consistency | Disjoint class check for 20th Century Press Archives took 0.16200852394104004s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.1885874271392822s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.553985834121704s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 6.825479507446289s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.3638436794281006s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.867100238800049s
Security | Sign check for 20th Century Press Archives took 0.13826298713684082s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1045.2055099010468s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.6606738567352295s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021504878997802734s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 6.532669067382812e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00010776519775390625s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 1.9073486328125e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 9.775161743164062e-06s
INFO | --- Analysis for zbw-pressemappe20 took 1169.2295401096344s
Availability | SPARQL endpoint availability check for zhishi.lemon took 9.059906005859375e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0009658336639404297s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.2711448669433594s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.020976543426513672s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.506111145019531e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.0967254638671875e-05s
INFO | --- Analysis for zhishi-lemon took 25.196552276611328s
Availability | SPARQL endpoint availability check for Zhishi.me took 5.539751052856445s
Availability | VoID file availability check for Zhishi.me took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.30033016204833984s
Reputation | Calculation of the PageRank for Zhishi.me took 0.020263195037841797s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.009506225585938e-05s
Believability | Calculation of trust value for Zhishi.me took 1.3828277587890625e-05s
INFO | --- Analysis for zhishi-me took 11.765894651412964s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.315376281738281e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0014562606811523438s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.30892395973205566s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 5.936622619628906e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 1.2636184692382812e-05s
INFO | --- Analysis for zitgist-musicbrainz took 3.4683997631073s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 4.291534423828125e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.3142385482788086s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.021360158920288086s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 3.266334533691406e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.1682510375976562e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.894742012023926s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.34899210929870605s
Availability | VoID file availability check for performing-arts.ch took 0.0005178451538085938s
Extra | Recovery of all triples for performing-arts.ch took 17.27234387397766s
Performance | Total latancy measurement for performing-arts.ch took 0.7221002578735352s
Amount of data | Number of triples check for performing-arts.ch took 36.555094480514526s
Interoperability | New terms check for performing-arts.ch took 1.4867157936096191s
Versatility | Languages check for performing-arts.ch took 60.12691640853882s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.139533042907715s
Interpretability | RDF structures check for performing-arts.ch took 0.14856672286987305s
Versatility | Serialization formats check for performing-arts.ch took 0.17742085456848145s
Availability | RDF dump link check for performing-arts.ch took 0.14687037467956543s
License | MR license check for performing-arts.ch took 0.15282607078552246s
License | HR license check for performing-arts.ch took 42.11705470085144s
Amount of data | Number of property check for performing-arts.ch took 0.17487287521362305s
Understandability | Number of label check for performing-arts.ch took 2.9394328594207764s
Understandability | URI regex check for performing-arts.ch took 0.34865403175354004s
Understandability | Vocabs check for performing-arts.ch took 0.16071367263793945s
Verifiability | Authors check for performing-arts.ch took 0.16400551795959473s
Verifiability | Publishers check for performing-arts.ch took 0.14411306381225586s
Performance | Throughput check for performing-arts.ch took 10.695186853408813s
Amount of data | Check the number of entities for performing-arts.ch took 7.128715515136719e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.16154170036315918s
Interlinking | sameAs chians check for performing-arts.ch took 0.6817812919616699s
Interlinking | skos check for performing-arts.ch took 0.1923809051513672s
Interlinking | skos check for performing-arts.ch took 0.18318438529968262s
Timeliness | dataset update frequency check for performing-arts.ch took 0.16261744499206543s
Currency | Creation date check for performing-arts.ch took 0.3161203861236572s
Currency | Modification date check for performing-arts.ch took 0.3342301845550537s
Rep.Conc. | URIs length for performing-arts.ch took 26.364386558532715s
Interoperability | New vocabularies check for performing-arts.ch took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.15627455711364746s
Accuracy | Check Functional Property for performing-arts.ch took 0.1700592041015625s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.1576077938079834s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.259328126907349s
Accuracy | Check White space in annotation for performing-arts.ch took 2.5560173988342285s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.801792860031128s
Consistency | Disjoint class check for performing-arts.ch took 0.16195321083068848s
Consistency | Check Misplaced properties for performing-arts.ch took 0.37615466117858887s
Consistency | Misplaced classes for performing-arts.ch took 8.589033126831055s
Consistency | Check Ontology hijacking for performing-arts.ch took 44.40575098991394s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 15230.31408071518s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.7819526195526123s
Conciseness | Check Extensional conciseness for performing-arts.ch took 3.003009557723999s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.30502963066101074s
Security | Sign check for performing-arts.ch took 0.16960740089416504s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.4583911895751953s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.7813835144042969s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.049904584884643555s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.7642974853515625e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 1.9073486328125e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.2159347534179688e-05s
INFO | --- Analysis for performing-arts.ch took 16039.706988573074s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.419362783432007s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.3268270492553711s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.02181839942932129s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.1920928955078125e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for The-AA-Thesaurus took 8.217942476272583s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.5987601280212402s
Availability | VoID file availability check for MiMoTextBase took 0.0004000663757324219s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.30019378662109375s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.1444091796875e-05s
Believability | Calculation of trust value for MiMoTextBase took 7.62939453125e-06s
INFO | --- Analysis for MiMoTextBase took 6.788207292556763s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.5232656002044678s
Availability | VoID file availability check for National Library of Sweden took 0.0003886222839355469s
Extra | Recovery of all triples for National Library of Sweden took 5.953346490859985s
Performance | Total latancy measurement for National Library of Sweden took 1.0313005447387695s
Amount of data | Number of triples check for National Library of Sweden took 32.052061557769775s
Interoperability | New terms check for National Library of Sweden took 17.98313307762146s
Versatility | Languages check for National Library of Sweden took 0.19627737998962402s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.18971395492554s
Interpretability | RDF structures check for National Library of Sweden took 0.23206663131713867s
Versatility | Serialization formats check for National Library of Sweden took 0.21828556060791016s
Availability | RDF dump link check for National Library of Sweden took 0.20503020286560059s
License | MR license check for National Library of Sweden took 0.2365100383758545s
License | HR license check for National Library of Sweden took 0.24740386009216309s
Amount of data | Number of property check for National Library of Sweden took 0.19849252700805664s
Understandability | Number of label check for National Library of Sweden took 0.2575523853302002s
Understandability | URI regex check for National Library of Sweden took 0.4092519283294678s
Understandability | Vocabs check for National Library of Sweden took 0.19426584243774414s
Verifiability | Authors check for National Library of Sweden took 0.19974684715270996s
Verifiability | Publishers check for National Library of Sweden took 0.20662856101989746s
Performance | Throughput check for National Library of Sweden took 10.264071464538574s
Amount of data | Check the number of entities for National Library of Sweden took 3.361701965332031e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.20627164840698242s
Interlinking | sameAs chians check for National Library of Sweden took 0.19388723373413086s
Interlinking | skos check for National Library of Sweden took 0.22574353218078613s
Interlinking | skos check for National Library of Sweden took 0.21610474586486816s
Timeliness | dataset update frequency check for National Library of Sweden took 0.20203495025634766s
Currency | Creation date check for National Library of Sweden took 0.4451427459716797s
Currency | Modification date check for National Library of Sweden took 0.44637560844421387s
Rep.Conc. | URIs length for National Library of Sweden took 94.41674733161926s
Interoperability | New vocabularies check for National Library of Sweden took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.203721284866333s
Accuracy | Check Functional Property for National Library of Sweden took 0.22021698951721191s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.1954965591430664s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.27106404304504395s
Consistency | Disjoint class check for National Library of Sweden took 0.21433234214782715s
Consistency | Check Misplaced properties for National Library of Sweden took 69.57699465751648s
Consistency | Misplaced classes for National Library of Sweden took 1.1345775127410889s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.3429534435272217s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.3033511638641357s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 71.21661233901978s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.2942485809326172s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.3567490577697754s
Security | Sign check for National Library of Sweden took 0.25870537757873535s
Availability | Check URIs Dereferenciability for National Library of Sweden took 10.253543615341187s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.32865357398986816s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.9073486328125e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.9073486328125e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.4066696166992188e-05s
INFO | --- Analysis for NLS took 1416.8836543560028s
Availability | SPARQL endpoint availability check for Japan Search took 1.7429256439208984s
Availability | VoID file availability check for Japan Search took 0.0004954338073730469s
Extra | Recovery of all triples for Japan Search took 3.8537163734436035s
Performance | Total latancy measurement for Japan Search took 2.3653347492218018s
Amount of data | Number of triples check for Japan Search took 7.009068250656128s
Interoperability | New terms check for Japan Search took 4.08804988861084s
Versatility | Languages check for Japan Search took 0.7432100772857666s
Interpretability | Number of blank nodes check for Japan Search took 10.31872820854187s
Interpretability | RDF structures check for Japan Search took 0.9552655220031738s
Versatility | Serialization formats check for Japan Search took 0.42519426345825195s
Availability | RDF dump link check for Japan Search took 0.30794620513916016s
License | MR license check for Japan Search took 1.0455973148345947s
License | HR license check for Japan Search took 12.277486562728882s
Amount of data | Number of property check for Japan Search took 0.7440237998962402s
Understandability | Number of label check for Japan Search took 2.890869617462158s
Understandability | URI regex check for Japan Search took 1.0083661079406738s
Understandability | Vocabs check for Japan Search took 0.28795742988586426s
Verifiability | Authors check for Japan Search took 0.3697826862335205s
Verifiability | Publishers check for Japan Search took 0.31212711334228516s
Performance | Throughput check for Japan Search took 11.535474061965942s
Amount of data | Check the number of entities for Japan Search took 0.00011110305786132812s
Verifiability | Contribs. check for Japan Search took 0.3532407283782959s
Interlinking | sameAs chians check for Japan Search took 0.2812771797180176s
Interlinking | skos check for Japan Search took 0.5318210124969482s
Interlinking | skos check for Japan Search took 0.2875077724456787s
Timeliness | dataset update frequency check for Japan Search took 0.33792972564697266s
Currency | Creation date check for Japan Search took 0.7273585796356201s
Currency | Modification date check for Japan Search took 0.6958332061767578s
Rep.Conc. | URIs length for Japan Search took 13.953171730041504s
Interoperability | New vocabularies check for Japan Search took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.31070756912231445s
Accuracy | Check Functional Property for Japan Search took 0.4004700183868408s
Accuracy | Check Inverse Functional Property for Japan Search took 0.8606202602386475s
Accuracy | Check Empty annotation labels for Japan Search took 2.2107038497924805s
Accuracy | Check White space in annotation for Japan Search took 0.029657840728759766s
Accuracy | Check Datatype consistency for Japan Search took 0.029143095016479492s
Consistency | Disjoint class check for Japan Search took 0.3742482662200928s
Consistency | Check Misplaced properties for Japan Search took 10.610509395599365s
Consistency | Misplaced classes for Japan Search took 0.38770270347595215s
Consistency | Check Ontology hijacking for Japan Search took 3.5223333835601807s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.3180489540100098s
Consistency | Check Invalid usage of undefined properties for Japan Search took 11.59946084022522s
Conciseness | Check Extensional conciseness for Japan Search took 0.03642845153808594s
Conciseness | Check Intensional conciseness for Japan Search took 1.0149600505828857s
Security | Sign check for Japan Search took 0.7423014640808105s
Availability | Check URIs Dereferenciability for Japan Search took 8.885267496109009s
Completeness | Calculation of interlinking completeness for Japan Search took 0.30449366569519043s
Reputation | Calculation of the PageRank for Japan Search took 0.020908117294311523s
Interlinking | Calculation of Degree of Connection for Japan Search took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.8835067749023438e-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.0013580322265625e-05s
INFO | --- Analysis for Japan-Search took 406.0011353492737s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.2159249782562256s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.29601287841796875s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.1205673217773438e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.0013580322265625e-05s
INFO | --- Analysis for Rijksmuseum took 5.116512775421143s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 2.748310089111328s
Availability | VoID file availability check for Finnish Public Libraries took 0.0006875991821289062s
Extra | Recovery of all triples for Finnish Public Libraries took 21.91046929359436s
Performance | Total latancy measurement for Finnish Public Libraries took 1.463679313659668s
Amount of data | Number of triples check for Finnish Public Libraries took 60.34264612197876s
Interoperability | New terms check for Finnish Public Libraries took 17.289937496185303s
Versatility | Languages check for Finnish Public Libraries took 60.17584729194641s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 60.41488480567932s
Interpretability | RDF structures check for Finnish Public Libraries took 0.49332380294799805s
Versatility | Serialization formats check for Finnish Public Libraries took 0.1586451530456543s
Availability | RDF dump link check for Finnish Public Libraries took 0.2547013759613037s
License | MR license check for Finnish Public Libraries took 0.31265854835510254s
License | HR license check for Finnish Public Libraries took 59.59092426300049s
Amount of data | Number of property check for Finnish Public Libraries took 0.5043718814849854s
Understandability | Number of label check for Finnish Public Libraries took 17.942461252212524s
Understandability | URI regex check for Finnish Public Libraries took 0.5070979595184326s
Understandability | Vocabs check for Finnish Public Libraries took 0.22124576568603516s
Verifiability | Authors check for Finnish Public Libraries took 0.2539377212524414s
Verifiability | Publishers check for Finnish Public Libraries took 0.3515028953552246s
Performance | Throughput check for Finnish Public Libraries took 10.874898195266724s
Amount of data | Check the number of entities for Finnish Public Libraries took 8.726119995117188e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.1324465274810791s
Interlinking | sameAs chians check for Finnish Public Libraries took 4.290422439575195s
Interlinking | skos check for Finnish Public Libraries took 0.17490553855895996s
Interlinking | skos check for Finnish Public Libraries took 0.14050531387329102s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.11992502212524414s
Currency | Creation date check for Finnish Public Libraries took 0.3221559524536133s
Currency | Modification date check for Finnish Public Libraries took 0.269228458404541s
Rep.Conc. | URIs length for Finnish Public Libraries took 95.72977137565613s
Interoperability | New vocabularies check for Finnish Public Libraries took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.3642904758453369s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 8.22932481765747s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.2079639434814453s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.413024663925171s
Consistency | Disjoint class check for Finnish Public Libraries took 0.250042200088501s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.50093197822571s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 15.843838214874268s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.4856791496276855s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 61.60026717185974s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.8379013538360596s
Security | Sign check for Finnish Public Libraries took 0.18311357498168945s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 0.878619909286499s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.4315836429595947s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.02152538299560547s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.2636184692382812e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 1.430511474609375e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 1.2159347534179688e-05s
INFO | --- Analysis for FI-Library took 714.3020932674408s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 2.3893282413482666s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0005083084106445312s
Extra | Recovery of all triples for Shanghai Library Open Data Platform took 10.849493741989136s
Performance | Total latancy measurement for Shanghai Library Open Data Platform took 3.4742374420166016s
Amount of data | Number of triples check for Shanghai Library Open Data Platform took 1.1969950199127197s
Interoperability | New terms check for Shanghai Library Open Data Platform took 4.886465072631836s
Versatility | Languages check for Shanghai Library Open Data Platform took 60.69970393180847s
Interpretability | Number of blank nodes check for Shanghai Library Open Data Platform took 17.273134469985962s
Interpretability | RDF structures check for Shanghai Library Open Data Platform took 1.2021353244781494s
Versatility | Serialization formats check for Shanghai Library Open Data Platform took 0.8695986270904541s
Availability | RDF dump link check for Shanghai Library Open Data Platform took 0.7233598232269287s
License | MR license check for Shanghai Library Open Data Platform took 1.0958762168884277s
License | HR license check for Shanghai Library Open Data Platform took 37.802762508392334s
Amount of data | Number of property check for Shanghai Library Open Data Platform took 0.6805884838104248s
Understandability | Number of label check for Shanghai Library Open Data Platform took 1.501734972000122s
Understandability | URI regex check for Shanghai Library Open Data Platform took 1.6021268367767334s
Understandability | Vocabs check for Shanghai Library Open Data Platform took 0.7545328140258789s
Verifiability | Authors check for Shanghai Library Open Data Platform took 0.8221416473388672s
Verifiability | Publishers check for Shanghai Library Open Data Platform took 0.7525544166564941s
Performance | Throughput check for Shanghai Library Open Data Platform took 13.831003904342651s
Amount of data | Check the number of entities for Shanghai Library Open Data Platform took 8.463859558105469e-05s
Verifiability | Contribs. check for Shanghai Library Open Data Platform took 0.7189385890960693s
Interlinking | sameAs chians check for Shanghai Library Open Data Platform took 0.6990506649017334s
Interlinking | skos check for Shanghai Library Open Data Platform took 0.9966487884521484s
Interlinking | skos check for Shanghai Library Open Data Platform took 0.6758134365081787s
Timeliness | dataset update frequency check for Shanghai Library Open Data Platform took 0.8594443798065186s
Currency | Creation date check for Shanghai Library Open Data Platform took 1.5995259284973145s
Currency | Modification date check for Shanghai Library Open Data Platform took 1.4554274082183838s
Rep.Conc. | URIs length for Shanghai Library Open Data Platform took 9.943598747253418s
Interoperability | New vocabularies check for Shanghai Library Open Data Platform took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for Shanghai Library Open Data Platform took 0.7592499256134033s
Accuracy | Check Functional Property for Shanghai Library Open Data Platform took 0.7194585800170898s
Accuracy | Check Inverse Functional Property for Shanghai Library Open Data Platform took 0.7369871139526367s
Accuracy | Check Empty annotation labels for Shanghai Library Open Data Platform took 3.500462055206299s
Accuracy | Check White space in annotation for Shanghai Library Open Data Platform took 0.15549707412719727s
Accuracy | Check Datatype consistency for Shanghai Library Open Data Platform took 0.1391749382019043s
Consistency | Disjoint class check for Shanghai Library Open Data Platform took 0.8647406101226807s
Consistency | Check Misplaced properties for Shanghai Library Open Data Platform took 6.421831846237183s
Consistency | Misplaced classes for Shanghai Library Open Data Platform took 1.3118538856506348s
Consistency | Check Ontology hijacking for Shanghai Library Open Data Platform took 5.7500786781311035s
Consistency | Check Invalid usage of undefined classes for Shanghai Library Open Data Platform took 1.4132156372070312s
Consistency | Check Invalid usage of undefined properties for Shanghai Library Open Data Platform took 7.004464864730835s
Conciseness | Check Extensional conciseness for Shanghai Library Open Data Platform took 0.1549830436706543s
Conciseness | Check Intensional conciseness for Shanghai Library Open Data Platform took 1.1938889026641846s
Security | Sign check for Shanghai Library Open Data Platform took 1.0118224620819092s
Availability | Check URIs Dereferenciability for Shanghai Library Open Data Platform took 20.13081192970276s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.39434266090393066s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 2.09808349609375e-05s
Interoperability | Check the re-using of existing vocabs for Shanghai Library Open Data Platform took 1.9073486328125e-06s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.5974044799804688e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 354.825603723526s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.2749719619750977s
Availability | VoID file availability check for National Library Netherlands took 0.0005867481231689453s
Extra | Recovery of all triples for National Library Netherlands took 0.6799478530883789s
Performance | Total latancy measurement for National Library Netherlands took 0.7443356513977051s
Amount of data | Number of triples check for National Library Netherlands took 0.14761137962341309s
Interoperability | New terms check for National Library Netherlands took 1.4432621002197266s
Versatility | Languages check for National Library Netherlands took 58.137837648391724s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.16138768196105957s
Interpretability | RDF structures check for National Library Netherlands took 0.19148683547973633s
Versatility | Serialization formats check for National Library Netherlands took 0.1446552276611328s
Availability | RDF dump link check for National Library Netherlands took 0.13812899589538574s
License | MR license check for National Library Netherlands took 0.17050933837890625s
License | HR license check for National Library Netherlands took 0.18405461311340332s
Amount of data | Number of property check for National Library Netherlands took 0.16234779357910156s
Understandability | Number of label check for National Library Netherlands took 0.14842534065246582s
Understandability | URI regex check for National Library Netherlands took 0.2991178035736084s
Understandability | Vocabs check for National Library Netherlands took 0.1597898006439209s
Verifiability | Authors check for National Library Netherlands took 0.15000176429748535s
Verifiability | Publishers check for National Library Netherlands took 0.15555500984191895s
Performance | Throughput check for National Library Netherlands took 10.577906370162964s
Amount of data | Check the number of entities for National Library Netherlands took 7.414817810058594e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.17959976196289062s
Interlinking | sameAs chians check for National Library Netherlands took 0.15518951416015625s
Interlinking | skos check for National Library Netherlands took 0.1392650604248047s
Interlinking | skos check for National Library Netherlands took 0.14938616752624512s
Timeliness | dataset update frequency check for National Library Netherlands took 0.17818403244018555s
Currency | Creation date check for National Library Netherlands took 0.31392860412597656s
Currency | Modification date check for National Library Netherlands took 0.32636094093322754s
Rep.Conc. | URIs length for National Library Netherlands took 0.6601266860961914s
Interoperability | New vocabularies check for National Library Netherlands took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.1591482162475586s
Accuracy | Check Functional Property for National Library Netherlands took 0.14702773094177246s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.16119003295898438s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.5143108367919922s
Accuracy | Check White space in annotation for National Library Netherlands took 0.02789616584777832s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.02731013298034668s
Consistency | Disjoint class check for National Library Netherlands took 0.16557955741882324s
Consistency | Check Misplaced properties for National Library Netherlands took 0.35480761528015137s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.881514549255371s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.3479046821594238s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.546687364578247s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.030318498611450195s
Security | Sign check for National Library Netherlands took 0.1707453727722168s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1706.7024009227753s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.7928802967071533s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.021458148956298828s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 2.3365020751953125e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 2.1457672119140625e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.1682510375976562e-05s
INFO | --- Analysis for National-Library-Netherlands took 1812.7526800632477s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.6413276195526123s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.2694716453552246s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.021903038024902344s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.3113021850585938e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.3113021850585938e-05s
INFO | --- Analysis for Antique-Renaissance took 6.065133810043335s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 4.129187822341919s
Availability | VoID file availability check for ARTSDATA.CA took 0.0007240772247314453s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.30623841285705566s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.02044057846069336s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.1444091796875e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 3.62396240234375e-05s
INFO | --- Analysis for ARTSDATA-CA took 9.717951774597168s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.24835562705993652s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.31198883056640625s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.0728836059570312e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 1.2159347534179688e-05s
INFO | --- Analysis for ArCo took 3.841876268386841s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.37499165534973145s
Availability | VoID file availability check for ConfermentSampo took 0.0004894733428955078s
Extra | Recovery of all triples for ConfermentSampo took 17.639426231384277s
Performance | Total latancy measurement for ConfermentSampo took 0.837242841720581s
Amount of data | Number of triples check for ConfermentSampo took 8.006252765655518s
Interoperability | New terms check for ConfermentSampo took 2.6957437992095947s
Versatility | Languages check for ConfermentSampo took 25.780089378356934s
Interpretability | Number of blank nodes check for ConfermentSampo took 7.903507709503174s
Security | Check HTTPS for ConfermentSampo took 0.40535426139831543s
Interpretability | RDF structures check for ConfermentSampo took 0.2027881145477295s
Versatility | Serialization formats check for ConfermentSampo took 0.20975041389465332s
Availability | RDF dump link check for ConfermentSampo took 3.043964385986328s
License | MR license check for ConfermentSampo took 0.18597769737243652s
License | HR license check for ConfermentSampo took 0.250105619430542s
Amount of data | Number of property check for ConfermentSampo took 0.18639159202575684s
Understandability | Number of label check for ConfermentSampo took 5.351453065872192s
Understandability | URI regex check for ConfermentSampo took 0.36659860610961914s
Understandability | Vocabs check for ConfermentSampo took 0.17194557189941406s
Verifiability | Authors check for ConfermentSampo took 0.19622588157653809s
Verifiability | Publishers check for ConfermentSampo took 0.19968509674072266s
Performance | Throughput check for ConfermentSampo took 10.861929893493652s
Amount of data | Check the number of entities for ConfermentSampo took 4.04889440536499s
Verifiability | Contribs. check for ConfermentSampo took 0.17252111434936523s
Interlinking | sameAs chians check for ConfermentSampo took 0.5180323123931885s
Interlinking | skos check for ConfermentSampo took 0.1716763973236084s
Interlinking | skos check for ConfermentSampo took 0.15574860572814941s
Timeliness | dataset update frequency check for ConfermentSampo took 0.16365790367126465s
Currency | Creation date check for ConfermentSampo took 0.35318970680236816s
Currency | Modification date check for ConfermentSampo took 0.35783863067626953s
Rep.Conc. | URIs length for ConfermentSampo took 34.03547143936157s
Interoperability | New vocabularies check for ConfermentSampo took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.19977641105651855s
Accuracy | Check Functional Property for ConfermentSampo took 0.18059444427490234s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.17147254943847656s
Accuracy | Check Empty annotation labels for ConfermentSampo took 14.7152841091156s
Accuracy | Check White space in annotation for ConfermentSampo took 3.0642127990722656s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.206426382064819s
Consistency | Disjoint class check for ConfermentSampo took 0.1755685806274414s
Consistency | Check Misplaced properties for ConfermentSampo took 7.193790674209595s
Consistency | Check Ontology hijacking for ConfermentSampo took 15.133008003234863s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.435675859451294s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.554124355316162s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.9151270389556885s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.1961057186126709s
Security | Sign check for ConfermentSampo took 0.16164803504943848s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1394.8029656410217s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.39952754974365234s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.022246360778808594s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 6.532669067382812e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 6.937980651855469e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 4.291534423828125e-06s
Believability | Calculation of trust value for ConfermentSampo took 1.5735626220703125e-05s
INFO | --- Analysis for ConfermentSampo took 1686.092279434204s
Availability | SPARQL endpoint availability check for Museum Finland took 0.4429903030395508s
Availability | VoID file availability check for Museum Finland took 0.0005276203155517578s
Extra | Recovery of all triples for Museum Finland took 4.42406964302063s
Performance | Total latancy measurement for Museum Finland took 0.8059425354003906s
Amount of data | Number of triples check for Museum Finland took 0.34238505363464355s
Interoperability | New terms check for Museum Finland took 1.7612817287445068s
Versatility | Languages check for Museum Finland took 0.6508021354675293s
Interpretability | Number of blank nodes check for Museum Finland took 0.30476808547973633s
Security | Check HTTPS for Museum Finland took 0.23118329048156738s
Interpretability | RDF structures check for Museum Finland took 0.40102219581604004s
Versatility | Serialization formats check for Museum Finland took 0.20778346061706543s
Availability | RDF dump link check for Museum Finland took 0.16115021705627441s
License | MR license check for Museum Finland took 0.19648122787475586s
License | HR license check for Museum Finland took 0.40883421897888184s
Amount of data | Number of property check for Museum Finland took 0.1903831958770752s
Understandability | Number of label check for Museum Finland took 0.2897493839263916s
Understandability | URI regex check for Museum Finland took 0.313274621963501s
Understandability | Vocabs check for Museum Finland took 0.17096185684204102s
Verifiability | Authors check for Museum Finland took 0.16493487358093262s
Verifiability | Publishers check for Museum Finland took 0.15967059135437012s
Performance | Throughput check for Museum Finland took 10.913033246994019s
Amount of data | Check the number of entities for Museum Finland took 7.700920104980469e-05s
Verifiability | Contribs. check for Museum Finland took 0.1599884033203125s
Interlinking | sameAs chians check for Museum Finland took 0.16187334060668945s
Interlinking | skos check for Museum Finland took 0.1535015106201172s
Interlinking | skos check for Museum Finland took 0.15648865699768066s
Timeliness | dataset update frequency check for Museum Finland took 0.1790323257446289s
Currency | Creation date check for Museum Finland took 0.33611106872558594s
Currency | Modification date check for Museum Finland took 0.37409210205078125s
Rep.Conc. | URIs length for Museum Finland took 3.5261168479919434s
Interoperability | New vocabularies check for Museum Finland took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.17648625373840332s
Accuracy | Check Functional Property for Museum Finland took 0.15883660316467285s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.16328072547912598s
Accuracy | Check Empty annotation labels for Museum Finland took 1.0251350402832031s
Accuracy | Check White space in annotation for Museum Finland took 0.0617518424987793s
Accuracy | Check Datatype consistency for Museum Finland took 0.9679265022277832s
Consistency | Disjoint class check for Museum Finland took 0.15921401977539062s
Consistency | Check Misplaced properties for Museum Finland took 0.6104319095611572s
Consistency | Check Ontology hijacking for Museum Finland took 2.396155834197998s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.5863003730773926s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.78261137008667s
Conciseness | Check Extensional conciseness for Museum Finland took 0.695732593536377s
Conciseness | Check Intensional conciseness for Museum Finland took 0.31595468521118164s
Security | Sign check for Museum Finland took 0.15302300453186035s
Availability | Check URIs Dereferenciability for Museum Finland took 7.929473638534546s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.3188741207122803s
Reputation | Calculation of the PageRank for Museum Finland took 0.021008014678955078s
Interlinking | Calculation of Degree of Connection for Museum Finland took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 2.1457672119140625e-06s
Believability | Calculation of trust value for Museum Finland took 1.2636184692382812e-05s
INFO | --- Analysis for FI-Museum took 62.912485122680664s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.19733428955078125s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0005929470062255859s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 20.35445499420166s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.805027961730957s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 38.34937000274658s
Interoperability | New terms check for Mapping Manuscript Migrations took 4.724197626113892s
Versatility | Languages check for Mapping Manuscript Migrations took 76.50707149505615s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.201929807662964s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.3997225761413574s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.1600937843322754s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.16118669509887695s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.15272283554077148s
License | MR license check for Mapping Manuscript Migrations took 0.18449044227600098s
License | HR license check for Mapping Manuscript Migrations took 1.8265259265899658s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.1609494686126709s
Understandability | Number of label check for Mapping Manuscript Migrations took 8.789246797561646s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3444371223449707s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.1626121997833252s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.18465971946716309s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.19162511825561523s
Performance | Throughput check for Mapping Manuscript Migrations took 11.076541900634766s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0359416007995605s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.18700766563415527s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5548803806304932s
Interlinking | skos check for Mapping Manuscript Migrations took 0.16857147216796875s
Interlinking | skos check for Mapping Manuscript Migrations took 0.16419100761413574s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.1672496795654297s
Currency | Creation date check for Mapping Manuscript Migrations took 0.32535505294799805s
Currency | Modification date check for Mapping Manuscript Migrations took 0.18522953987121582s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 49.88872456550598s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.19513821601867676s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.17841553688049316s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.15177369117736816s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.41141390800476s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.460507869720459s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.711524724960327s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.20146632194519043s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 22.443129777908325s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.3088538646698s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.5920121669769287s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.5996224880218506s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.9419798851013184s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.18866634368896484s
Security | Sign check for Mapping Manuscript Migrations took 0.1660935878753662s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1581.279498577118s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.7436769008636475s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.021430253982543945s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 7.414817810058594e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.5735626220703125e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 2.1457672119140625e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.3113021850585938e-05s
INFO | --- Analysis for MMM took 1999.4939577579498s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.19435954093933105s
Availability | VoID file availability check for Semantic Kalevala took 0.0005085468292236328s
Extra | Recovery of all triples for Semantic Kalevala took 9.102310180664062s
Performance | Total latancy measurement for Semantic Kalevala took 0.8425619602203369s
Amount of data | Number of triples check for Semantic Kalevala took 0.41718149185180664s
Interoperability | New terms check for Semantic Kalevala took 1.5197877883911133s
Versatility | Languages check for Semantic Kalevala took 0.9583466053009033s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.3831295967102051s
Security | Check HTTPS for Semantic Kalevala took 0.4173135757446289s
Interpretability | RDF structures check for Semantic Kalevala took 0.2870762348175049s
Versatility | Serialization formats check for Semantic Kalevala took 0.18816232681274414s
Availability | RDF dump link check for Semantic Kalevala took 0.16764044761657715s
License | MR license check for Semantic Kalevala took 0.17859244346618652s
License | HR license check for Semantic Kalevala took 1.3192565441131592s
Amount of data | Number of property check for Semantic Kalevala took 0.1863236427307129s
Understandability | Number of label check for Semantic Kalevala took 0.523613452911377s
Understandability | URI regex check for Semantic Kalevala took 0.3134121894836426s
Understandability | Vocabs check for Semantic Kalevala took 0.16954946517944336s
Verifiability | Authors check for Semantic Kalevala took 0.16896986961364746s
Verifiability | Publishers check for Semantic Kalevala took 0.1616833209991455s
Performance | Throughput check for Semantic Kalevala took 11.109608173370361s
Amount of data | Check the number of entities for Semantic Kalevala took 7.319450378417969e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.175462007522583s
Interlinking | sameAs chians check for Semantic Kalevala took 0.19688081741333008s
Interlinking | skos check for Semantic Kalevala took 0.2499070167541504s
Interlinking | skos check for Semantic Kalevala took 0.1573171615600586s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.1853013038635254s
Currency | Creation date check for Semantic Kalevala took 0.35352015495300293s
Currency | Modification date check for Semantic Kalevala took 0.3473775386810303s
Rep.Conc. | URIs length for Semantic Kalevala took 4.86752986907959s
Interoperability | New vocabularies check for Semantic Kalevala took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.18162035942077637s
Accuracy | Check Functional Property for Semantic Kalevala took 0.18740630149841309s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.15895652770996094s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.7916755676269531s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.29792189598083496s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.40982985496521s
Consistency | Disjoint class check for Semantic Kalevala took 0.1626758575439453s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7812716960906982s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.255986213684082s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.3830127716064453s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.561671495437622s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.9112417697906494s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.2830641269683838s
Security | Sign check for Semantic Kalevala took 0.15261578559875488s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2293.5493519306183s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.526216983795166s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.5857503414154053s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.3589859008789062e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.6689300537109375e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.049041748046875e-05s
INFO | --- Analysis for Semantic-Kalevala took 2358.2409892082214s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.9160277843475342s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0005860328674316406s
Extra | Recovery of all triples for Smithsonian American Art Museum took 276.52948236465454s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.0648298263549805s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5785815715789795s
Interoperability | New terms check for Smithsonian American Art Museum took 3.2779483795166016s
Versatility | Languages check for Smithsonian American Art Museum took 27.066944122314453s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5773031711578369s
Security | Check HTTPS for Smithsonian American Art Museum took 0.37068629264831543s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.679121732711792s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.5767619609832764s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.5927519798278809s
License | MR license check for Smithsonian American Art Museum took 0.5946612358093262s
License | HR license check for Smithsonian American Art Museum took 16.33250641822815s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5850470066070557s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5843422412872314s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1850569248199463s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.5850894451141357s
Verifiability | Authors check for Smithsonian American Art Museum took 0.5992059707641602s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.5917332172393799s
Performance | Throughput check for Smithsonian American Art Museum took 11.673383951187134s
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.580331563949585s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5775232315063477s
Interlinking | skos check for Smithsonian American Art Museum took 0.5771698951721191s
Interlinking | skos check for Smithsonian American Art Museum took 0.5775890350341797s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5931940078735352s
Currency | Creation date check for Smithsonian American Art Museum took 1.2332136631011963s
Currency | Modification date check for Smithsonian American Art Museum took 1.2022559642791748s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 104.42248511314392s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.603961706161499s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 22.216906547546387s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.5029590129852295s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.22043776512146s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5813891887664795s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 5.048136472702026s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 94.47592329978943s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.5943734645843506s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 4.628057241439819s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.9918863773345947s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.5781114101409912s
Security | Sign check for Smithsonian American Art Museum took 0.6026215553283691s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.293693542480469s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.4649643898010254s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.021322250366210938s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 1.6689300537109375e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 1.4066696166992188e-05s
INFO | --- Analysis for Smithsonian took 693.0741903781891s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.21468853950500488s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.2849705219268799s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.021387577056884766s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.239776611328125e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.0967254638671875e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 6.268440008163452s
Availability | SPARQL endpoint availability check for Archives Hub took 21.449811220169067s
Availability | VoID file availability check for Archives Hub took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.3080260753631592s
Reputation | Calculation of the PageRank for Archives Hub took 0.020679473876953125s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.7642974853515625e-05s
Believability | Calculation of trust value for Archives Hub took 1.1682510375976562e-05s
INFO | --- Analysis for Archives-Hub took 54.843108892440796s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.6114578247070312s
Availability | VoID file availability check for Yale centre of British Art took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.3312034606933594s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.0967254638671875e-05s
Believability | Calculation of trust value for Yale centre of British Art took 1.3113021850585938e-05s
INFO | --- Analysis for Yale took 5.0148351192474365s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 262.1992893218994s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.3301517963409424s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 2.0265579223632812e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.1205673217773438e-05s
INFO | --- Analysis for ADL took 537.2036607265472s
Availability | SPARQL endpoint availability check for MusicKG took 0.7888264656066895s
Availability | VoID file availability check for MusicKG took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for MusicKG took 0.3193323612213135s
Reputation | Calculation of the PageRank for MusicKG took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.239776611328125e-05s
Believability | Calculation of trust value for MusicKG took 1.2874603271484375e-05s
INFO | --- Analysis for MusicKG took 4.799844741821289s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.8441846370697021s
Availability | VoID file availability check for CIDOC-CRM took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.28940367698669434s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.020557641983032227s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.3113021850585938e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.3828277587890625e-05s
INFO | --- Analysis for CIDOC-CRM took 4.378716468811035s
Availability | SPARQL endpoint availability check for Mondis took 262.1773843765259s
Availability | VoID file availability check for Mondis took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Mondis took 0.300506591796875s
Reputation | Calculation of the PageRank for Mondis took 0.022391080856323242s
Interlinking | Calculation of Degree of Connection for Mondis took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.5497207641601562e-05s
Believability | Calculation of trust value for Mondis took 1.2636184692382812e-05s
INFO | --- Analysis for Mondis took 265.667361497879s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.7729289531707764s
Availability | VoID file availability check for DigitalNZ took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.29616785049438477s
Reputation | Calculation of the PageRank for DigitalNZ took 0.020696640014648438s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.1444091796875e-05s
Believability | Calculation of trust value for DigitalNZ took 1.2159347534179688e-05s
INFO | --- Analysis for DigitalNZ took 8.14412522315979s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.17299842834472656s
Availability | VoID file availability check for Fondazione Zeri took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.2953193187713623s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.239776611328125e-05s
Believability | Calculation of trust value for Fondazione Zeri took 1.3589859008789062e-05s
INFO | --- Analysis for Fondazione-Zeri took 3.548039674758911s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.19256162643432617s
Availability | VoID file availability check for Digital Public Library of America took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.39367198944091797s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.1682510375976562e-05s
Believability | Calculation of trust value for Digital Public Library of America took 1.1205673217773438e-05s
INFO | --- Analysis for Library-of-America took 4.202244520187378s
Availability | SPARQL endpoint availability check for Auckland Museum took 2.023608446121216s
Availability | VoID file availability check for Auckland Museum took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.29523420333862305s
Reputation | Calculation of the PageRank for Auckland Museum took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.3113021850585938e-05s
Believability | Calculation of trust value for Auckland Museum took 1.0728836059570312e-05s
INFO | --- Analysis for Auckland-Museum took 6.922256231307983s
Availability | SPARQL endpoint availability check for National Library of Spain took 3.944380521774292s
Availability | VoID file availability check for National Library of Spain took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.30171680450439453s
Reputation | Calculation of the PageRank for National Library of Spain took 0.02025771141052246s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.0728836059570312e-05s
Believability | Calculation of trust value for National Library of Spain took 1.4781951904296875e-05s
INFO | --- Analysis for BNE took 7.299529314041138s
Availability | SPARQL endpoint availability check for National Library of Korea took 1.5630731582641602s
Availability | VoID file availability check for National Library of Korea took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.27280235290527344s
Reputation | Calculation of the PageRank for National Library of Korea took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.239776611328125e-05s
Believability | Calculation of trust value for National Library of Korea took 1.3113021850585938e-05s
INFO | --- Analysis for Korea-Library took 4.7643938064575195s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.4732389450073242s
Availability | VoID file availability check for The State Russian Museum took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.32691001892089844s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.020835399627685547s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.1444091796875e-05s
Believability | Calculation of trust value for The State Russian Museum took 1.2874603271484375e-05s
INFO | --- Analysis for Russian-Museum took 4.834486484527588s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.599907398223877s
Availability | VoID file availability check for National Library of Scotland took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.35405564308166504s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.52587890625e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.239776611328125e-05s
Believability | Calculation of trust value for National Library of Scotland took 1.0251998901367188e-05s
INFO | --- Analysis for National-Library-of-Scotland took 7.2352235317230225s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.3654036521911621s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.3080272674560547s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.2874603271484375e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.2874603271484375e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.7979350090026855s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.19255304336547852s
Availability | VoID file availability check for OntoComedySources took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.3225243091583252s
Reputation | Calculation of the PageRank for OntoComedySources took 0.02098369598388672s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.430511474609375e-05s
Believability | Calculation of trust value for OntoComedySources took 1.5974044799804688e-05s
INFO | --- Analysis for OntoComedySources took 4.233312606811523s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.20008635520935059s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.2973151206970215s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.1920928955078125e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.2159347534179688e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 4.418225526809692s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.1513819694519043s
Availability | VoID file availability check for SaintGall Ontology took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.29841017723083496s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.2636184692382812e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for SaintGall-Ontology took 3.447875738143921s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.7607731819152832s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.2991759777069092s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.021838903427124023s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 4.5299530029296875e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.2636184692382812e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 4.277680158615112s
Availability | SPARQL endpoint availability check for ICON took 0.32114648818969727s
Availability | VoID file availability check for ICON took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for ICON took 0.3291442394256592s
Reputation | Calculation of the PageRank for ICON took 0.021319150924682617s
Interlinking | Calculation of Degree of Connection for ICON took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for ICON took 0.0008180141448974609s
Interlinking | Calculation of Clustering coefficient for ICON took 1.239776611328125e-05s
Believability | Calculation of trust value for ICON took 1.1920928955078125e-05s
INFO | --- Analysis for ICON took 4.508681297302246s
Availability | SPARQL endpoint availability check for Polifonia took 0.28848862648010254s
Availability | VoID file availability check for Polifonia took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for Polifonia took 0.2987406253814697s
Reputation | Calculation of the PageRank for Polifonia took 0.022019386291503906s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.0728836059570312e-05s
Believability | Calculation of trust value for Polifonia took 9.5367431640625e-06s
INFO | --- Analysis for Polifonia took 4.708282232284546s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 1.0578291416168213s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.27666759490966797s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.020944833755493164s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.1682510375976562e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 7.62939453125e-06s
INFO | --- Analysis for Atlas-of-Paths took 5.0174853801727295s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.2882845401763916s
Availability | VoID file availability check for Music Note Ontology took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.29476284980773926s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.1444091796875e-05s
Believability | Calculation of trust value for Music Note Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Music-Note-Ontology took 8.726571559906006s
Availability | SPARQL endpoint availability check for HaMSE took 0.21473312377929688s
Availability | VoID file availability check for HaMSE took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for HaMSE took 0.3149566650390625s
Reputation | Calculation of the PageRank for HaMSE took 0.02106189727783203s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.1205673217773438e-05s
Believability | Calculation of trust value for HaMSE took 1.2159347534179688e-05s
INFO | --- Analysis for HaMSE took 5.6285905838012695s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.10582327842712402s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.2992289066314697s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.020383358001708984s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.1920928955078125e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 1.0251998901367188e-05s
INFO | --- Analysis for FOod took 5.16326642036438s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.7853233814239502s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0003533363342285156s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.2904658317565918s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.021063804626464844s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.33514404296875e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 1.430511474609375e-05s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.374150991439819s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.4047372341156006s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0007784366607666016s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.2897145748138428s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.02060389518737793s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 3.0040740966796875e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 1.1205673217773438e-05s
INFO | --- Analysis for ARIADNE took 5.812548875808716s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 0.41312122344970703s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0005314350128173828s
Extra | Recovery of all triples for Rijksmuseum Collection took 5.294236660003662s
Performance | Total latancy measurement for Rijksmuseum Collection took 0.8520288467407227s
Amount of data | Number of triples check for Rijksmuseum Collection took 0.5307936668395996s
Interoperability | New terms check for Rijksmuseum Collection took 1.5860581398010254s
Versatility | Languages check for Rijksmuseum Collection took 0.705552339553833s
Interpretability | Number of blank nodes check for Rijksmuseum Collection took 0.4670686721801758s
Interpretability | RDF structures check for Rijksmuseum Collection took 0.20886802673339844s
Versatility | Serialization formats check for Rijksmuseum Collection took 0.18095707893371582s
Availability | RDF dump link check for Rijksmuseum Collection took 0.169907808303833s
License | MR license check for Rijksmuseum Collection took 0.2028946876525879s
License | HR license check for Rijksmuseum Collection took 0.2199265956878662s
Amount of data | Number of property check for Rijksmuseum Collection took 0.15059876441955566s
Understandability | Number of label check for Rijksmuseum Collection took 0.16826367378234863s
Understandability | URI regex check for Rijksmuseum Collection took 0.34797215461730957s
Understandability | Vocabs check for Rijksmuseum Collection took 0.17084145545959473s
Verifiability | Authors check for Rijksmuseum Collection took 0.20030999183654785s
Verifiability | Publishers check for Rijksmuseum Collection took 0.18613505363464355s
Performance | Throughput check for Rijksmuseum Collection took 11.10273551940918s
Amount of data | Check the number of entities for Rijksmuseum Collection took 0.00012922286987304688s
Verifiability | Contribs. check for Rijksmuseum Collection took 0.18445396423339844s
Interlinking | sameAs chians check for Rijksmuseum Collection took 0.18248987197875977s
Interlinking | skos check for Rijksmuseum Collection took 0.19405031204223633s
Interlinking | skos check for Rijksmuseum Collection took 0.14722919464111328s
Timeliness | dataset update frequency check for Rijksmuseum Collection took 0.1784687042236328s
Currency | Creation date check for Rijksmuseum Collection took 0.3715548515319824s
Currency | Modification date check for Rijksmuseum Collection took 0.4055356979370117s
Rep.Conc. | URIs length for Rijksmuseum Collection took 3.1373677253723145s
Interoperability | New vocabularies check for Rijksmuseum Collection took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Rijksmuseum Collection took 0.17367053031921387s
Accuracy | Check Empty annotation labels for Rijksmuseum Collection took 0.31752586364746094s
Accuracy | Check White space in annotation for Rijksmuseum Collection took 0.0018913745880126953s
Accuracy | Check Datatype consistency for Rijksmuseum Collection took 0.476032018661499s
Consistency | Disjoint class check for Rijksmuseum Collection took 0.1580641269683838s
Consistency | Check Misplaced properties for Rijksmuseum Collection took 0.6439127922058105s
Consistency | Check Ontology hijacking for Rijksmuseum Collection took 1.968839168548584s
Consistency | Check Invalid usage of undefined classes for Rijksmuseum Collection took 1.293095350265503s
Consistency | Check Invalid usage of undefined properties for Rijksmuseum Collection took 1.4491219520568848s
Conciseness | Check Extensional conciseness for Rijksmuseum Collection took 0.29308342933654785s
Security | Sign check for Rijksmuseum Collection took 0.1790294647216797s
Availability | Check URIs Dereferenciability for Rijksmuseum Collection took 798.6384136676788s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.5420644283294678s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Rijksmuseum Collection took 1.6689300537109375e-06s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.0251998901367188e-05s
INFO | --- Analysis for rijksmuseum took 850.7532885074615s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.3201148509979248s
Availability | VoID file availability check for Odeuropa Ontology took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.2970447540283203s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.0208740234375s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.2159347534179688e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.33514404296875e-05s
INFO | --- Analysis for Odeuropa took 3.6950790882110596s

--- Total time for analysis:483852.77500653267s ---
--- Total time for analysis:134.40354861292573 hours ---