Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.649162292480469e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0003886222839355469s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.2902367115020752s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.8915572166442871s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00043129920959472656s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 8.344650268554688e-06s
INFO | --- Analysis for 0080-3626 took 7.6157472133636475s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.363059997558594e-05s
Availability | VoID file availability check for 土地利用图 took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.6903371810913086s
Reputation | Calculation of the PageRank for 土地利用图 took 0.019956350326538086s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.1948089599609375e-05s
Believability | Calculation of trust value for 土地利用图 took 1.4543533325195312e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 4.190066337585449s
Availability | SPARQL endpoint availability check for 113322 took 4.3392181396484375e-05s
Availability | VoID file availability check for 113322 took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for 113322 took 0.2729454040527344s
Reputation | Calculation of the PageRank for 113322 took 0.020140886306762695s
Interlinking | Calculation of Degree of Connection for 113322 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.075599670410156e-05s
Believability | Calculation of trust value for 113322 took 8.106231689453125e-06s
INFO | --- Analysis for 11 took 5.049071550369263s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.3392181396484375e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2586479187011719s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.600120544433594e-05s
Believability | Calculation of trust value for Korepetycje Buki took 8.106231689453125e-06s
INFO | --- Analysis for 12323 took 3.640866994857788s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 2.0281052589416504s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.26671671867370605s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.845329284667969e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 7.867813110351562e-06s
INFO | --- Analysis for 2000-us-census-rdf took 12.836737155914307s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.7234482765197754s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.3139009475708008s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.021073341369628906s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.410743713378906e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 5.9604644775390625e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.040852069854736s
Availability | SPARQL endpoint availability check for Open Data Web took 0.1293630599975586s
Availability | VoID file availability check for Open Data Web took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.24666881561279297s
Reputation | Calculation of the PageRank for Open Data Web took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.600120544433594e-05s
Believability | Calculation of trust value for Open Data Web took 8.821487426757812e-06s
INFO | --- Analysis for _data.odw.tw took 2.5670864582061768s
Availability | SPARQL endpoint availability check for 土地利用 took 7.581710815429688e-05s
Availability | VoID file availability check for 土地利用 took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.262225866317749s
Reputation | Calculation of the PageRank for 土地利用 took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.0279159545898438e-05s
Believability | Calculation of trust value for 土地利用 took 8.106231689453125e-06s
INFO | --- Analysis for _data1.odw.tw took 2.367185115814209s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.363059997558594e-05s
Availability | VoID file availability check for 土地利用模型 took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.277726411819458s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 3.600120544433594e-05s
Believability | Calculation of trust value for 土地利用模型 took 8.58306884765625e-06s
INFO | --- Analysis for _data2.odw.tw took 6.001014471054077s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.482269287109375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0007350444793701172s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2622840404510498s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.147125244140625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 8.821487426757812e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.3893604278564453s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.267692565917969e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2679634094238281s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.1948089599609375e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 9.059906005859375e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.8564810752868652s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.291534423828125e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0007779598236083984s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.28540873527526855s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.0279159545898438e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 5.7220458984375e-06s
INFO | --- Analysis for A1 took 2.852682590484619s
Availability | SPARQL endpoint availability check for SummerOlympics took 1.1229474544525146s
Availability | VoID file availability check for SummerOlympics took 0.0007350444793701172s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.2617194652557373s
Reputation | Calculation of the PageRank for SummerOlympics took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.651878356933594e-05s
Believability | Calculation of trust value for SummerOlympics took 7.867813110351562e-06s
INFO | --- Analysis for abc took 5.607977867126465s
Availability | SPARQL endpoint availability check for Test_m took 4.4345855712890625e-05s
Availability | VoID file availability check for Test_m took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Test_m took 0.2783944606781006s
Reputation | Calculation of the PageRank for Test_m took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for Test_m took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.147125244140625e-05s
Believability | Calculation of trust value for Test_m took 8.58306884765625e-06s
INFO | --- Analysis for ABC took 2.423543691635132s
Availability | SPARQL endpoint availability check for my intro took 4.363059997558594e-05s
Availability | VoID file availability check for my intro took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for my intro took 0.26665759086608887s
Reputation | Calculation of the PageRank for my intro took 0.02093815803527832s
Interlinking | Calculation of Degree of Connection for my intro took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for my intro took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for my intro took 3.361701965332031e-05s
Believability | Calculation of trust value for my intro took 8.821487426757812e-06s
INFO | --- Analysis for abhay_intro took 2.3394718170166016s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.7196996212005615s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0003657341003417969s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.29972362518310547s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010251998901367188s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for abs-linked-data took 3.125490427017212s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 4.076957702636719e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.2847726345062256s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020677804946899414s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.0279159545898438e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 6.9141387939453125e-06s
INFO | --- Analysis for academic-offer-of-unl took 3.0194427967071533s
Availability | SPARQL endpoint availability check for AcadOnto took 4.291534423828125e-05s
Availability | VoID file availability check for AcadOnto took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.27300357818603516s
Reputation | Calculation of the PageRank for AcadOnto took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.170967102050781e-05s
Believability | Calculation of trust value for AcadOnto took 8.344650268554688e-06s
INFO | --- Analysis for acadonto took 2.818639039993286s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 10.226336479187012s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2653810977935791s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.790855407714844e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for acorn-sat took 37.03731727600098s
Availability | SPARQL endpoint availability check for Addgene took 5.745887756347656e-05s
Availability | VoID file availability check for Addgene took 0.0007846355438232422s
Completeness | Calculation of interlinking completeness for Addgene took 0.2671027183532715s
Reputation | Calculation of the PageRank for Addgene took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for Addgene took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.5762786865234375e-05s
Believability | Calculation of trust value for Addgene took 7.867813110351562e-06s
INFO | --- Analysis for addgene took 19.77355170249939s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.57763671875e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.27247142791748047s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.417533874511719e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 7.62939453125e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 2.9478347301483154s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 31.82541537284851s
Availability | VoID file availability check for AEMET metereological dataset took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.2516896724700928s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.649162292480469e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 7.152557373046875e-06s
INFO | --- Analysis for aemet took 146.1346082687378s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.0531158447265625e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.7083404064178467s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 5.1021575927734375e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 7.867813110351562e-06s
INFO | --- Analysis for agenda-de-zaragoza took 3.3910279273986816s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.04037642478942871s
Availability | VoID file availability check for AgriNepalData took 0.0003502368927001953s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2648341655731201s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.224082946777344e-05s
Believability | Calculation of trust value for AgriNepalData took 8.106231689453125e-06s
INFO | --- Analysis for agrinepaldata took 2.481335401535034s
Availability | SPARQL endpoint availability check for AGRIS took 261.3261024951935s
Availability | VoID file availability check for AGRIS took 0.0003972053527832031s
Completeness | Calculation of interlinking completeness for AGRIS took 0.28764843940734863s
Reputation | Calculation of the PageRank for AGRIS took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for AGRIS took 8.177757263183594e-05s
Believability | Calculation of trust value for AGRIS took 7.62939453125e-06s
INFO | --- Analysis for agris took 556.4974367618561s
Availability | SPARQL endpoint availability check for AGROVOC took 0.1896045207977295s
Availability | VoID file availability check for AGROVOC took 0.0006451606750488281s
Extra | Recovery of all triples for AGROVOC took 30.83917808532715s
Performance | Total latancy measurement for AGROVOC took 0.45449209213256836s
Amount of data | Number of triples check for AGROVOC took 13.600372791290283s
Interoperability | New terms check for AGROVOC took 3.253655195236206s
Versatility | Languages check for AGROVOC took 30.073035717010498s
Interpretability | Number of blank nodes check for AGROVOC took 23.780293703079224s
Interpretability | RDF structures check for AGROVOC took 0.10172700881958008s
Versatility | Serialization formats check for AGROVOC took 0.09903192520141602s
Availability | RDF dump link check for AGROVOC took 0.0861506462097168s
License | MR license check for AGROVOC took 0.08843064308166504s
License | HR license check for AGROVOC took 0.3741586208343506s
Amount of data | Number of property check for AGROVOC took 0.09084701538085938s
Understandability | Number of label check for AGROVOC took 26.131299018859863s
Understandability | URI regex check for AGROVOC took 0.1871490478515625s
Understandability | Vocabs check for AGROVOC took 0.07836294174194336s
Verifiability | Authors check for AGROVOC took 0.0894927978515625s
Verifiability | Publishers check for AGROVOC took 0.0872344970703125s
Performance | Throughput check for AGROVOC took 10.382827758789062s
Amount of data | Check the number of entities for AGROVOC took 6.794929504394531e-05s
Verifiability | Contribs. check for AGROVOC took 0.08647298812866211s
Interlinking | sameAs chians check for AGROVOC took 0.09899520874023438s
Interlinking | skos check for AGROVOC took 0.43350911140441895s
Interlinking | skos check for AGROVOC took 0.12508368492126465s
Timeliness | dataset update frequency check for AGROVOC took 0.0894770622253418s
Currency | Creation date check for AGROVOC took 0.17825818061828613s
Currency | Modification date check for AGROVOC took 0.1556565761566162s
Rep.Conc. | URIs length for AGROVOC took 31.645693063735962s
Interoperability | New vocabularies check for AGROVOC took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.0876164436340332s
Accuracy | Check Functional Property for AGROVOC took 0.0860598087310791s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.08681869506835938s
Accuracy | Check Empty annotation labels for AGROVOC took 17.394415616989136s
Accuracy | Check White space in annotation for AGROVOC took 2.648862600326538s
Consistency | Disjoint class check for AGROVOC took 0.08741474151611328s
Consistency | Check Misplaced properties for AGROVOC took 10.514118671417236s
Consistency | Check Ontology hijacking for AGROVOC took 18.326931715011597s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 11.934638023376465s
Conciseness | Check Extensional conciseness for AGROVOC took 0.00016164779663085938s
Conciseness | Check Intensional conciseness for AGROVOC took 0.08072209358215332s
Security | Sign check for AGROVOC took 0.0743093490600586s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.8248085975646973s
Reputation | Calculation of the PageRank for AGROVOC took 0.020856380462646484s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011229515075683594s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.6689300537109375e-06s
Believability | Calculation of trust value for AGROVOC took 7.62939453125e-06s
INFO | --- Analysis for agrovoc took 300.2124307155609s
Availability | SPARQL endpoint availability check for AGROVOC took 3.981590270996094e-05s
Availability | VoID file availability check for AGROVOC took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.2821683883666992s
Reputation | Calculation of the PageRank for AGROVOC took 0.020054101943969727s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.745887756347656e-05s
Believability | Calculation of trust value for AGROVOC took 6.9141387939453125e-06s
INFO | --- Analysis for agrovoc-skos took 4.397243499755859s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 5.507469177246094e-05s
Availability | VoID file availability check for Analytics India Magazine took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.2829294204711914s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020056724548339844s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 2.8371810913085938e-05s
Believability | Calculation of trust value for Analytics India Magazine took 6.198883056640625e-06s
INFO | --- Analysis for AIM took 2.8744187355041504s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.100799560546875e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.2979872226715088s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 2.956390380859375e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 7.152557373046875e-06s
INFO | --- Analysis for AISHE took 2.3817780017852783s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for  equipment ontology took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.25882792472839355s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 2.8133392333984375e-05s
Believability | Calculation of trust value for  equipment ontology took 6.9141387939453125e-06s
INFO | --- Analysis for akash took 2.3879876136779785s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.029273986816406e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.000244140625s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.2659308910369873s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020147085189819336s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 2.8848648071289062e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 6.9141387939453125e-06s
INFO | --- Analysis for aksworg took 3.3665783405303955s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.6253204345703125e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.2868006229400635s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 2.8371810913085938e-05s
Believability | Calculation of trust value for AlchemyAPI took 8.106231689453125e-06s
INFO | --- Analysis for alchemyapi took 3.028250217437744s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 3.9577484130859375e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.28665661811828613s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.7179718017578125e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 6.9141387939453125e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.9979970455169678s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.1691884994506836s
Availability | VoID file availability check for aliada-scanbit-net took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.25908565521240234s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00010943412780761719s
Believability | Calculation of trust value for aliada-scanbit-net took 7.152557373046875e-06s
INFO | --- Analysis for aliada-scanbit-net took 3.71510648727417s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.076957702636719e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.26840829849243164s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02087688446044922s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.266334533691406e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 7.62939453125e-06s
INFO | --- Analysis for allen-brain-atlas took 2.950756072998047s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.9080367088317871s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006775856018066406s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 552.2368731498718s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7025539875030518s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.531848669052124s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.6927361488342285s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0169291496277s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.4104013442993164s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8804028034210205s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.6716856956481934s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.7410907745361328s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5352752208709717s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.7029612064361572s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 34.53557586669922s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.591820240020752s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 1.3206522464752197s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.181807041168213s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.7474286556243896s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.7332274913787842s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.6720247268676758s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.775171995162964s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 0.000102996826171875s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5455293655395508s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5796070098876953s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.661428689956665s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.8275048732757568s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.7941617965698242s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.4410099983215332s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.136986494064331s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 206.4936239719391s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.6172037124633789s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6725220680236816s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.7020666599273682s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 149.76394510269165s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0162546634674072s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.5916969776153564s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.5947027206420898s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 11.253486394882202s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.931747436523438s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 129.97528386116028s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.395012378692627s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 12.288010597229004s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.772658586502075s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8566234111785889s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5783464908599854s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 11490.11769270897s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.6220645904541016s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02448105812072754s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.416175842285156e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 1.9073486328125e-06s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 7.867813110351562e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 13018.515810728073s
Availability | SPARQL endpoint availability check for Alojamientos took 4.100799560546875e-05s
Availability | VoID file availability check for Alojamientos took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.7067685127258301s
Reputation | Calculation of the PageRank for Alojamientos took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.1948089599609375e-05s
Believability | Calculation of trust value for Alojamientos took 7.867813110351562e-06s
INFO | --- Analysis for alojamientos-zaragoza took 4.727899074554443s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.316364049911499s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.694239616394043s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.02008342742919922s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0008056163787841797s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.124641418457031e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 8.58306884765625e-06s
INFO | --- Analysis for alpino-rdf took 4.968523740768433s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.482269287109375e-05s
Availability | VoID file availability check for AAT-atawil took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.2670421600341797s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.123283386230469e-05s
Believability | Calculation of trust value for AAT-atawil took 1.8835067749023438e-05s
INFO | --- Analysis for Altawil took 2.8251497745513916s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 3.933906555175781e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.28870463371276855s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020207881927490234s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 2.8371810913085938e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 7.3909759521484375e-06s
INFO | --- Analysis for am-collections-online took 3.463684320449829s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.124641418457031e-05s
Availability | VoID file availability check for Amer Nejma took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.26201295852661133s
Reputation | Calculation of the PageRank for Amer Nejma took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 2.8371810913085938e-05s
Believability | Calculation of trust value for Amer Nejma took 6.9141387939453125e-06s
INFO | --- Analysis for Amer_Nejma took 2.3982064723968506s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.910064697265625e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0002961158752441406s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.2556183338165283s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.02005290985107422s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for amon took 2.922785758972168s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.8078958988189697s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.2511875629425049s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020363569259643555s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.655952453613281e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0013580322265625e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 13.85183334350586s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.1484832763671875e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.25238537788391113s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020840883255004883s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 2.956390380859375e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 7.3909759521484375e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.9073994159698486s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.0531158447265625e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.28001880645751953s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020534753799438477s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 2.9802322387695312e-05s
Believability | Calculation of trust value for Animal Diversity Web took 7.867813110351562e-06s
INFO | --- Analysis for animal-diversity-web took 2.9569618701934814s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.267692565917969e-05s
Availability | VoID file availability check for Anime Dataset took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.25705623626708984s
Reputation | Calculation of the PageRank for Anime Dataset took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.0517578125e-05s
Believability | Calculation of trust value for Anime Dataset took 7.867813110351562e-06s
INFO | --- Analysis for Anime took 3.590681314468384s
Availability | SPARQL endpoint availability check for ANNO took 4.315376281738281e-05s
Availability | VoID file availability check for ANNO took 0.0003895759582519531s
Completeness | Calculation of interlinking completeness for ANNO took 0.25862741470336914s
Reputation | Calculation of the PageRank for ANNO took 0.019996166229248047s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.0994415283203125e-05s
Believability | Calculation of trust value for ANNO took 7.3909759521484375e-06s
INFO | --- Analysis for anno took 15.204161882400513s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.38690185546875e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.2588627338409424s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.62939453125e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 9.059906005859375e-06s
INFO | --- Analysis for AntiqueCarsCollection took 4.268778562545776s
Availability | SPARQL endpoint availability check for apache took 8.034706115722656e-05s
Availability | VoID file availability check for apache took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for apache took 0.272475004196167s
Reputation | Calculation of the PageRank for apache took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for apache took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for apache took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for apache took 5.269050598144531e-05s
Believability | Calculation of trust value for apache took 6.9141387939453125e-06s
INFO | --- Analysis for apache took 3.3884165287017822s
Availability | SPARQL endpoint availability check for Apertium RDF took 8.678436279296875e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.25248050689697266s
Reputation | Calculation of the PageRank for Apertium RDF took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf took 5.209270238876343s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 5.53131103515625e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.28739094734191895s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.02025604248046875s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.842011213302612s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.27902913093566895s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007700920104980469s
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 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.955163240432739s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.27931690216064453s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.588493347167969s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.2756483554840088s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 6.530614376068115s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.25670766830444336s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.589630842208862s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.3018808364868164s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0021784305572509766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 0.00011754035949707031s
Believability | Calculation of trust value for Apertium RDF EO-EN took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.795169830322266s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.26632213592529297s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.982948303222656e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.4549829959869385s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2777364253997803s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007522106170654297s
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 8.821487426757812e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.679062843322754s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.029273986816406e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.000354766845703125s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2528533935546875s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02098846435546875s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0009918212890625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 5.14984130859375e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.794520378112793s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.24664521217346191s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020232439041137695s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 5.125999450683594e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 6.350087642669678s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.26727819442749023s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020397663116455078s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 25.058676719665527s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.25698208808898926s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020580291748046875s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 5.5786542892456055s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 7.343292236328125e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.2777721881866455s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.775444984436035s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.00038051605224609375s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.25234031677246094s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02025914192199707s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.863653898239136s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 3.981590270996094e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.26561737060546875s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.020392417907714844s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.64015007019043s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.100799560546875e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.2563157081604004s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.68290376663208s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.2553853988647461s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.95617151260376s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.26451754570007324s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 5.684321641921997s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 5.340576171875e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.260756254196167s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.839897155761719e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.650846481323242s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.076957702636719e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.26524972915649414s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.558042287826538s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.2794985771179199s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02020430564880371s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.913177490234375s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.24867701530456543s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020213842391967773s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.917975902557373s
Availability | SPARQL endpoint availability check for AragoDBPedia took 2.056572437286377s
Availability | VoID file availability check for AragoDBPedia took 0.0006425380706787109s
Extra | Recovery of all triples for AragoDBPedia took 4.125046491622925s
Performance | Total latancy measurement for AragoDBPedia took 1.913320779800415s
Amount of data | Number of triples check for AragoDBPedia took 0.9193720817565918s
Interoperability | New terms check for AragoDBPedia took 2.2160263061523438s
Versatility | Languages check for AragoDBPedia took 60.53600597381592s
Interpretability | Number of blank nodes check for AragoDBPedia took 4.3400654792785645s
Security | Check HTTPS for AragoDBPedia took 0.25061893463134766s
Interpretability | RDF structures check for AragoDBPedia took 0.9487979412078857s
Versatility | Serialization formats check for AragoDBPedia took 0.9350745677947998s
Availability | RDF dump link check for AragoDBPedia took 0.5143511295318604s
License | MR license check for AragoDBPedia took 0.6733102798461914s
License | HR license check for AragoDBPedia took 6.943425893783569s
Amount of data | Number of property check for AragoDBPedia took 0.4058375358581543s
Understandability | Number of label check for AragoDBPedia took 0.6342008113861084s
Understandability | URI regex check for AragoDBPedia took 1.0466020107269287s
Understandability | Vocabs check for AragoDBPedia took 0.5307977199554443s
Verifiability | Authors check for AragoDBPedia took 0.4760427474975586s
Verifiability | Publishers check for AragoDBPedia took 0.46570396423339844s
Performance | Throughput check for AragoDBPedia took 12.113919734954834s
Amount of data | Check the number of entities for AragoDBPedia took 7.224082946777344e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.5330619812011719s
Interlinking | sameAs chians check for AragoDBPedia took 0.4810338020324707s
Interlinking | skos check for AragoDBPedia took 0.7061290740966797s
Interlinking | skos check for AragoDBPedia took 0.4212160110473633s
Timeliness | dataset update frequency check for AragoDBPedia took 0.4811513423919678s
Currency | Creation date check for AragoDBPedia took 1.7999687194824219s
Currency | Modification date check for AragoDBPedia took 0.4228630065917969s
Rep.Conc. | URIs length for AragoDBPedia took 6.175083875656128s
Interoperability | New vocabularies check for AragoDBPedia took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.4298379421234131s
Accuracy | Check Functional Property for AragoDBPedia took 0.5219042301177979s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.5240042209625244s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.3786802291870117s
Accuracy | Check White space in annotation for AragoDBPedia took 0.027508974075317383s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.0272367000579834s
Consistency | Disjoint class check for AragoDBPedia took 0.38190340995788574s
Consistency | Check Misplaced properties for AragoDBPedia took 4.786905288696289s
Consistency | Misplaced classes for AragoDBPedia took 0.6858980655670166s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.5625908374786377s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.2780048847198486s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.548880577087402s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03139543533325195s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.6602797508239746s
Security | Sign check for AragoDBPedia took 0.7892937660217285s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3378.474221229553s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 2.152109146118164s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.023692607879638672s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.1920928955078125e-06s
Believability | Calculation of trust value for AragoDBPedia took 4.76837158203125e-06s
INFO | --- Analysis for aragodbpedia took 23041.281774282455s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.266743898391724s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2667570114135742s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.02024388313293457s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.2928924560546875e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.62939453125e-06s
INFO | --- Analysis for archiveshub-linkeddata took 85.60852241516113s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.553794860839844e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.7109255790710449s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 2.956390380859375e-05s
Believability | Calculation of trust value for Archivi ISMA took 6.9141387939453125e-06s
INFO | --- Analysis for archivio-isma took 4.795214891433716s
Availability | SPARQL endpoint availability check for ARIADNE took 4.172325134277344e-05s
Availability | VoID file availability check for ARIADNE took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.24288582801818848s
Reputation | Calculation of the PageRank for ARIADNE took 0.02051067352294922s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 2.8133392333984375e-05s
Believability | Calculation of trust value for ARIADNE took 7.3909759521484375e-06s
INFO | --- Analysis for ariadne took 3.834768533706665s
Availability | SPARQL endpoint availability check for Aristotle University took 4.1484832763671875e-05s
Availability | VoID file availability check for Aristotle University took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.27664804458618164s
Reputation | Calculation of the PageRank for Aristotle University took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.266334533691406e-05s
Believability | Calculation of trust value for Aristotle University took 7.867813110351562e-06s
INFO | --- Analysis for aristotle-university took 3.889970064163208s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 6.559299468994141s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.26758456230163574s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 4.267692565917969e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 7.867813110351562e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 20.5599684715271s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.220008850097656e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.27728891372680664s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020914077758789062s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.218650817871094e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 8.344650268554688e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 3.0298447608947754s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 2.9222240447998047s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.2872927188873291s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.814697265625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 6.9141387939453125e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 15.406696319580078s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.220008850097656e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.27998876571655273s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010037422180175781s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 8.518708944320679s
Availability | SPARQL endpoint availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 4.076957702636719e-05s
Availability | VoID file availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.2498922348022461s
Reputation | Calculation of the PageRank for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.020561695098876953s
Interlinking | Calculation of Degree of Connection for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.1682510375976562e-05s
Believability | Calculation of trust value for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 7.3909759521484375e-06s
INFO | --- Analysis for Arthron took 2.4385905265808105s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.38690185546875e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0008094310760498047s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.28232622146606445s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 9.918212890625e-05s
Believability | Calculation of trust value for Arthroscopy community took 8.106231689453125e-06s
INFO | --- Analysis for arthroscopy took 3.2137539386749268s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.880058765411377s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0006983280181884766s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 0.08220505714416504s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 0.07281947135925293s
Versatility | Languages check for Wikidata entry for Art × Science International took 0.08418107032775879s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 0.08464574813842773s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.09408020973205566s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.08757877349853516s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.08116722106933594s
License | MR license check for Wikidata entry for Art × Science International took 0.08293437957763672s
License | HR license check for Wikidata entry for Art × Science International took 0.08348298072814941s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.08386516571044922s
Understandability | Number of label check for Wikidata entry for Art × Science International took 0.09453964233398438s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.16913700103759766s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.08552789688110352s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.09604263305664062s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.07193875312805176s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 0.0001461505889892578s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.08345508575439453s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 0.08449578285217285s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.08640456199645996s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.08240938186645508s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.08292746543884277s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.1893298625946045s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.1694636344909668s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 0.16800260543823242s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.08443188667297363s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.0820150375366211s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 0.09397649765014648s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 1.4000980854034424s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 0.00014281272888183594s
Security | Sign check for Wikidata entry for Art × Science International took 0.09262371063232422s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.26175856590270996s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020159244537353516s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.2636184692382812e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 4.76837158203125e-07s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 6.67572021484375e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 20.682297706604004s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.5686895847320557s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2849421501159668s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.02020740509033203s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.605552673339844e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.621246337890625e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 12.395366191864014s
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.2317912578582764s
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.0005688667297363281s
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.289074182510376s
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.020582914352416992s
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.1682510375976562e-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.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.987022399902344e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 10.588001728057861s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.2455458641052246s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.26253437995910645s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020348787307739258s
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 8.893013000488281e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 11.587584495544434s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.2356252670288086s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2712838649749756s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.1961669921875e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.5497207641601562e-05s
INFO | --- Analysis for ASCDC-CRB took 13.62296724319458s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.258099317550659s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2736649513244629s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.584426879882812e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.086431980133057s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.233581304550171s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.33462953567504883s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020483016967773438s
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.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-DQOT took 12.186696767807007s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.2707011699676514s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2623717784881592s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.843971252441406e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.216620922088623s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.24465012550354s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.3030354976654053s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.02018451690673828s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.106231689453125e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 13.073200941085815s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.2476911544799805s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.3027215003967285s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020302772521972656s
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.1205673217773438e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.245208740234375e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.101838827133179s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.2327234745025635s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2778327465057373s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 6.365776062011719e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 12.09023141860962s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.6999425888061523s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.27136921882629395s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.935264587402344e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 15.262503623962402s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.2328073978424072s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2759673595428467s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02032327651977539s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.367134094238281e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 10.651376724243164s
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.2362656593322754s
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.0007081031799316406s
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.26929211616516113s
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.02039027214050293s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.796287536621094e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.054226160049438s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.2447474002838135s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.28329920768737793s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020118236541748047s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.506111145019531e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC_-_DNB took 10.628777265548706s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.291534423828125e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2900702953338623s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.341934204101562e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 6.9141387939453125e-06s
INFO | --- Analysis for asit took 10.455229997634888s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.3392181396484375e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.2772557735443115s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.647804260253906e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 7.62939453125e-06s
INFO | --- Analysis for asjp took 5.241090774536133s
Availability | SPARQL endpoint availability check for ASN:US took 524.7035088539124s
Availability | VoID file availability check for ASN:US took 0.0010762214660644531s
Completeness | Calculation of interlinking completeness for ASN:US took 1.1656031608581543s
Reputation | Calculation of the PageRank for ASN:US took 0.021299123764038086s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.62939453125e-05s
Believability | Calculation of trust value for ASN:US took 5.7220458984375e-06s
INFO | --- Analysis for asn-us took 1341.9674518108368s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.3392181396484375e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.7270257472991943s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.147125244140625e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 5.245208740234375e-06s
INFO | --- Analysis for aspire-mmu took 8.461827278137207s
Availability | SPARQL endpoint availability check for associations took 5.817413330078125e-05s
Availability | VoID file availability check for associations took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for associations took 0.2668192386627197s
Reputation | Calculation of the PageRank for associations took 0.0203554630279541s
Interlinking | Calculation of Degree of Connection for associations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for associations took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for associations took 6.461143493652344e-05s
Believability | Calculation of trust value for associations took 6.9141387939453125e-06s
INFO | --- Analysis for associations took 8.944383144378662s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.124641418457031e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.23849177360534668s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.86102294921875e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 7.62939453125e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 3.8263819217681885s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.4345855712890625e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.2622702121734619s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.584426879882812e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 7.62939453125e-06s
INFO | --- Analysis for athelia-rfid took 4.253719806671143s
Availability | SPARQL endpoint availability check for AuditSocials Social Media Advertising Compliance Glossary took 5.888938903808594e-05s
Availability | VoID file availability check for AuditSocials Social Media Advertising Compliance Glossary took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for AuditSocials Social Media Advertising Compliance Glossary took 0.25075793266296387s
Reputation | Calculation of the PageRank for AuditSocials Social Media Advertising Compliance Glossary took 0.020479202270507812s
Interlinking | Calculation of Degree of Connection for AuditSocials Social Media Advertising Compliance Glossary took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for AuditSocials Social Media Advertising Compliance Glossary took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for AuditSocials Social Media Advertising Compliance Glossary took 1.33514404296875e-05s
Believability | Calculation of trust value for AuditSocials Social Media Advertising Compliance Glossary took 7.3909759521484375e-06s
INFO | --- Analysis for auditsocials-glossary took 4.357183933258057s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.839897155761719e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.26763391494750977s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.147125244140625e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.8436119556427s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5251116752624512s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.00035190582275390625s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.2582988739013672s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020442724227905273s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.1021575927734375e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for AugustiniConfessiones took 3.9387624263763428s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6219565868377686s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.37277746200561523s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02027726173400879s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.1552734375e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 7.3909759521484375e-06s
INFO | --- Analysis for austrian_ski_racers took 3.9255776405334473s
Availability | SPARQL endpoint availability check for AVsOnto took 4.482269287109375e-05s
Availability | VoID file availability check for AVsOnto took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.2612743377685547s
Reputation | Calculation of the PageRank for AVsOnto took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.1948089599609375e-05s
Believability | Calculation of trust value for AVsOnto took 6.67572021484375e-06s
INFO | --- Analysis for AVsOnto took 3.263667345046997s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3206005096435547s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007090568542480469s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 210.89664936065674s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.495969295501709s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.07919788360596s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 266.11507844924927s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.06408309936523s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.06810235977173s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23117995262145996s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1687605381011963s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1337900161743164s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12439513206481934s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 51.51746129989624s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0280487537384s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1535334587097168s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 212.70284962654114s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24711155891418457s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10600471496582031s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09914350509643555s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10971760749816895s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.99670958518982s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.559226989746094e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10891389846801758s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.00700330734253s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1498398780822754s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10329556465148926s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13396191596984863s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2444934844970703s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2619974613189697s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 393.1560034751892s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14100265502929688s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 31.61995553970337s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.2650465965270996s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.868850231170654s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12521076202392578s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1770884990692s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 62.78838038444519s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.2895395755767822s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.5230453014374s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.8388357162475586s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1971893310546875s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.179333209991455s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.746109962463379s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.02156829833984375s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1457672119140625e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.7220458984375e-06s
INFO | --- Analysis for b3kat took 3992.300168991089s
Availability | SPARQL endpoint availability check for BabelNet took 0.7171106338500977s
Availability | VoID file availability check for BabelNet took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for BabelNet took 0.7216410636901855s
Reputation | Calculation of the PageRank for BabelNet took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001709461212158203s
Believability | Calculation of trust value for BabelNet took 7.867813110351562e-06s
INFO | --- Analysis for babelnet took 6.835389137268066s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 9.036064147949219e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.27167797088623047s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020231246948242188s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bacevicius.lt took 7.152557373046875e-06s
INFO | --- Analysis for Bacevicius.lt took 3.2761034965515137s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5523486137390137s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.6912119388580322s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.363059997558594e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 7.62939453125e-06s
INFO | --- Analysis for bag took 6.117117881774902s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.9275262355804443s
Availability | VoID file availability check for 红色经典歌曲 took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2470841407775879s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.9802322387695312e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.867813110351562e-06s
INFO | --- Analysis for baixue took 3.3662326335906982s
Availability | SPARQL endpoint availability check for baixue composer took 4.220008850097656e-05s
Availability | VoID file availability check for baixue composer took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for baixue composer took 0.26965880393981934s
Reputation | Calculation of the PageRank for baixue composer took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.314018249511719e-05s
Believability | Calculation of trust value for baixue composer took 5.7220458984375e-06s
INFO | --- Analysis for baixue_composer took 3.2265284061431885s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.410743713378906e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.27358579635620117s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.170967102050781e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.3909759521484375e-06s
INFO | --- Analysis for baixue_imagery took 2.9419198036193848s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.511543273925781e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.25771212577819824s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020238399505615234s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.7894973754882812e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.62939453125e-06s
INFO | --- Analysis for baixue_imagery1 took 3.3464279174804688s
Availability | SPARQL endpoint availability check for BAMS took 4.0531158447265625e-05s
Availability | VoID file availability check for BAMS took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for BAMS took 0.2653839588165283s
Reputation | Calculation of the PageRank for BAMS took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for BAMS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for BAMS took 2.8371810913085938e-05s
Believability | Calculation of trust value for BAMS took 7.867813110351562e-06s
INFO | --- Analysis for bams took 2.8151512145996094s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.172325134277344e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.27350425720214844s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020488977432250977s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.910064697265625e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 8.106231689453125e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 2.9637789726257324s
Availability | SPARQL endpoint availability check for BBC Music took 0.6414890289306641s
Availability | VoID file availability check for BBC Music took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for BBC Music took 0.2517995834350586s
Reputation | Calculation of the PageRank for BBC Music took 0.02062225341796875s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001475811004638672s
Believability | Calculation of trust value for BBC Music took 8.106231689453125e-06s
INFO | --- Analysis for bbc-music took 3.554380178451538s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.2727377414703369s
Availability | VoID file availability check for BBC Programmes took 0.0007007122039794922s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.26963067054748535s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010061264038085938s
Believability | Calculation of trust value for BBC Programmes took 7.62939453125e-06s
INFO | --- Analysis for bbc-programmes took 9.51528263092041s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.2731049060821533s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.26215243339538574s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010323524475097656s
Believability | Calculation of trust value for BBC Wildlife Finder took 7.3909759521484375e-06s
INFO | --- Analysis for bbc-wildlife-finder took 8.02815294265747s
Availability | SPARQL endpoint availability check for BBOP took 4.00543212890625e-05s
Availability | VoID file availability check for BBOP took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for BBOP took 0.25940418243408203s
Reputation | Calculation of the PageRank for BBOP took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.9325485229492188e-05s
Believability | Calculation of trust value for BBOP took 7.62939453125e-06s
INFO | --- Analysis for bbop took 2.9250988960266113s
Availability | SPARQL endpoint availability check for BBOP took 4.2438507080078125e-05s
Availability | VoID file availability check for BBOP took 0.0009407997131347656s
Completeness | Calculation of interlinking completeness for BBOP took 0.2718667984008789s
Reputation | Calculation of the PageRank for BBOP took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for BBOP took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.8371810913085938e-05s
Believability | Calculation of trust value for BBOP took 7.62939453125e-06s
INFO | --- Analysis for bbop-selected took 18.44488215446472s
Availability | SPARQL endpoint availability check for Bdgp took 239.5109658241272s
Availability | VoID file availability check for Bdgp took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Bdgp took 0.7099146842956543s
Reputation | Calculation of the PageRank for Bdgp took 0.020804405212402344s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Bdgp took 4.553794860839844e-05s
Believability | Calculation of trust value for Bdgp took 9.298324584960938e-06s
INFO | --- Analysis for bdgp took 247.9743492603302s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.220008850097656e-05s
Availability | VoID file availability check for Bendev Junior took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.2840597629547119s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bendev Junior took 8.58306884765625e-06s
INFO | --- Analysis for bendevoficial took 5.800814628601074s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 304.4383554458618s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.2832496166229248s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.867813110351562e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 4.76837158203125e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 315.6109755039215s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.029273986816406e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.26068639755249023s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020224571228027344s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.075599670410156e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 7.152557373046875e-06s
INFO | --- Analysis for berlin-offener-haushalt took 4.235075235366821s
Availability | SPARQL endpoint availability check for berlios took 4.124641418457031e-05s
Availability | VoID file availability check for berlios took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for berlios took 0.2646777629852295s
Reputation | Calculation of the PageRank for berlios took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for berlios took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for berlios took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for berlios took 8.702278137207031e-05s
Believability | Calculation of trust value for berlios took 7.152557373046875e-06s
INFO | --- Analysis for berlios took 3.431366205215454s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.220008850097656e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.31294727325439453s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.723403930664062e-05s
Believability | Calculation of trust value for Between Our Worlds took 8.106231689453125e-06s
INFO | --- Analysis for betweenourworlds took 10.330816507339478s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.9931333065032959s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.7254350185394287s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.179115295410156e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for bfs-linked-data took 4.081526279449463s
Availability | SPARQL endpoint availability check for BibBase took 0.08574080467224121s
Availability | VoID file availability check for BibBase took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for BibBase took 0.25433874130249023s
Reputation | Calculation of the PageRank for BibBase took 0.02072906494140625s
Interlinking | Calculation of Degree of Connection for BibBase took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.751319885253906e-05s
Believability | Calculation of trust value for BibBase took 1.0251998901367188e-05s
INFO | --- Analysis for bibbase took 2.520477771759033s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.506111145019531e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.26687026023864746s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.02028632164001465s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.918212890625e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 6.198883056640625e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 4.575223922729492s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.1484832763671875e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.278214693069458s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.560585021972656e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 7.62939453125e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 3.091975450515747s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.124641418457031e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.2702963352203369s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 2.7418136596679688e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.9786758422851562s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.5299530029296875e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2540748119354248s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.337860107421875e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 7.152557373046875e-06s
INFO | --- Analysis for BibSonomy took 9.565311193466187s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 5.602836608886719e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2809164524078369s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.8133392333984375e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 6.9141387939453125e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.405529022216797s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.172325134277344e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.3038499355316162s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 2.8848648071289062e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 7.867813110351562e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.6931188106536865s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.2902395725250244s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.85699725151062s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 60.04387354850769s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.2666134834289551s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.02070450782775879s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010037422180175781s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 242.61979579925537s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 60.061522006988525s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0008225440979003906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.7477977275848389s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.02083444595336914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00012421607971191406s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-biomodels took 265.11319875717163s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.2909584045410156s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020943164825439453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 2.955461025238037s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 60.06091380119324s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 1.413177490234375s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020859241485595703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00041604042053222656s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-bioportal took 446.48026061058044s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 60.05733060836792s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0007579326629638672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 1.2495896816253662s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.745887756347656e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-chembl took 447.75756311416626s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 60.05128812789917s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.7162022590637207s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020781517028808594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.340576171875e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 265.74968123435974s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 60.05470037460327s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.7607817649841309s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020939350128173828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.67572021484375e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-ctd took 446.3800621032715s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.172325134277344e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.7152712345123291s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.744529724121094e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-dataset took 24.257888555526733s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 60.062373638153076s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.7271163463592529s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020795822143554688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.127357482910156e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 266.45165610313416s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 60.0616135597229s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.9028525352478027s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.02091240882873535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.000110626220703125s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-drugbank took 284.5603737831116s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 60.06282711029053s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0007548332214355469s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.27628397941589355s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.021124839782714844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.008148193359375e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-genage took 286.09341859817505s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.270094633102417s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0008406639099121094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.127357482910156e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-genbank took 5.098837375640869s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 60.0592520236969s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.26109862327575684s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020907878875732422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.4836273193359375e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-gendr took 287.53945755958557s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 60.063337326049805s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0007910728454589844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.7952630519866943s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.021553754806518555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.628036499023438e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-goa took 446.19422125816345s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 60.06469750404358s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0007488727569580078s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.2752842903137207s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020907878875732422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011038780212402344s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-hgnc took 264.85798025131226s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 60.06319570541382s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.2752344608306885s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.340576171875e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-homologene took 266.9849326610565s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.26015543937683105s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-inoh took 5.121399641036987s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 60.055886030197144s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 1.216261863708496s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 9.703636169433594e-05s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-interpro took 265.9018340110779s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 60.06349182128906s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0009284019470214844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 1.2723662853240967s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02120065689086914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 8.940696716308594e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-iproclass took 447.8634903430939s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 60.04884195327759s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.7681365013122559s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020990848541259766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 7.987022399902344e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-irefindex took 266.28432631492615s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 5.412101745605469e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.2707493305206299s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.127357482910156e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-kegg took 5.1817357540130615s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.2728121280670166s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 4.322495222091675s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 60.05178117752075s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.28823113441467285s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020999670028686523s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 4.3392181396484375e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 265.10418486595154s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 60.05244731903076s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.6944460868835449s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.412101745605469e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-lsr took 265.1231391429901s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 60.06253457069397s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.3008878231048584s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02074909210205078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.605552673339844e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-mesh took 304.98044419288635s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 60.05795931816101s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0008115768432617188s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 1.3717637062072754s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 0.00010156631469726562s
Believability | Calculation of trust value for Bio2RDF::Mgi took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-mgi took 327.61365938186646s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 60.05927753448486s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0008141994476318359s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.3471105098724365s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.021149873733520508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012564659118652344s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 406.8805134296417s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 60.060046911239624s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 1.1719129085540771s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.673004150390625e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-ndc took 266.94818449020386s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.7197067737579346s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-netpath took 6.073416471481323s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 40.04024863243103s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.27892208099365234s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02078080177307129s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-nextprot took 124.72246766090393s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 60.051294803619385s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0007336139678955078s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.7674596309661865s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020650386810302734s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.000125885009765625s
Believability | Calculation of trust value for Bio2RDF::Omim took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-omim took 266.6780824661255s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.6253204345703125e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006103515625s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2865920066833496s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020849227905273438s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.076957702636719e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 24.13488745689392s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 60.05620193481445s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.7579362392425537s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.392333984375e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-orphanet took 345.72526693344116s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 60.06145405769348s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.709186315536499s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.886222839355469e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 266.33549761772156s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 60.05694031715393s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.4121513366699219s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 8.392333984375e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 365.7833158969879s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.27163219451904297s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 5.5053746700286865s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.26800990104675293s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-pid took 4.354773998260498s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.2599012851715088s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 5.245208740234375e-05s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.8148248195648193s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 60.0628502368927s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0007855892181396484s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.2724478244781494s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.0001404285430908203s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pubmed took 244.71866273880005s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 5.817413330078125e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.2817554473876953s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.628036499023438e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-reactome took 6.1701436042785645s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 3.981590270996094e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.2791104316711426s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020151853561401367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 4.935264587402344e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.8575446605682373s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 60.05249810218811s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0007834434509277344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.2696380615234375s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020937442779541016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 8.416175842285156e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sabiork took 265.9030125141144s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 60.06485867500305s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.28443312644958496s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020920276641845703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011348724365234375s
Believability | Calculation of trust value for Bio2RDF::Sgd took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-sgd took 265.3667733669281s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.124641418457031e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.29746508598327637s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.314018249511719e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 24.677017211914062s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 60.05725407600403s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0014886856079101562s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.7463080883026123s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.021081209182739258s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.76837158203125e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-sider took 325.89285111427307s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.4345855712890625e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.2750279903411865s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-spike took 5.1708104610443115s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.1961669921875e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.6986489295959473s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.022566556930541992s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.744529724121094e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-taxon took 23.727023601531982s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 60.05997395515442s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0007648468017578125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.9689412117004395s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.02070307731628418s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010442733764648438s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 346.787814617157s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 60.059985876083374s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.8558080196380615s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.910064697265625e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 446.89120745658875s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 60.06217169761658s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 1.2634258270263672s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.02087545394897461s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.939338684082031e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-wormbase took 347.4901580810547s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.363059997558594e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.299548864364624s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.1444091796875e-05s
Believability | Calculation of trust value for Biografías y Vidas took 7.152557373046875e-06s
INFO | --- Analysis for biografiasyvidas took 4.19940447807312s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.28434133529663086s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.265855073928833s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020211219787597656s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 7.963180541992188e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 5.245208740234375e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.701444149017334s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.2783372402191162s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 2.7418136596679688e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for biolit took 3.765531301498413s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.100799560546875e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.26282382011413574s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.02012181282043457s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.695487976074219e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 7.3909759521484375e-06s
INFO | --- Analysis for biolod-pdb took 9.30327558517456s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.738682746887207s
Availability | VoID file availability check for BioModels RDF took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2690439224243164s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020209789276123047s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0008335113525390625s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.552436828613281e-05s
Believability | Calculation of trust value for BioModels RDF took 7.3909759521484375e-06s
INFO | --- Analysis for biomodels-rdf took 4.248207330703735s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.6585440635681152s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2906970977783203s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.314018249511719e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.62939453125e-06s
INFO | --- Analysis for Biop took 7.837820053100586s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.0531158447265625e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2711045742034912s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020951032638549805s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.504753112792969e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 6.9141387939453125e-06s
INFO | --- Analysis for Bioportal took 2.854543685913086s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.100799560546875e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2852792739868164s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006306171417236328s
Believability | Calculation of trust value for Amphibian gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-aao took 2.82075834274292s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.172325134277344e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.258880615234375s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020227909088134766s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0002930164337158203s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-aba took 2.6783037185668945s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2518777847290039s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.001483917236328125s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-acgt took 2.6989247798919678s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.172325134277344e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.27765703201293945s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003421306610107422s
Believability | Calculation of trust value for Animal natural history and life history took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-adw took 2.660478353500366s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.27399325370788574s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004849433898925781s
Believability | Calculation of trust value for Anatomical Entity Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-aeo took 2.5934269428253174s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2663450241088867s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.020229339599609375s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009737014770507812s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-aero took 2.6656265258789062s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.076957702636719e-05s
Availability | VoID file availability check for AI/RHEUM took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.266895055770874s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0003998279571533203s
Believability | Calculation of trust value for AI/RHEUM took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-air took 2.6330862045288086s
Availability | SPARQL endpoint availability check for Amino Acid took 4.172325134277344e-05s
Availability | VoID file availability check for Amino Acid took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.26977968215942383s
Reputation | Calculation of the PageRank for Amino Acid took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00025773048400878906s
Believability | Calculation of trust value for Amino Acid took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.5169246196746826s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.25988054275512695s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020398855209350586s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002789497375488281s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-apo took 2.599013090133667s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.124641418457031e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2698221206665039s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020459651947021484s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.0002346038818359375s
Believability | Calculation of trust value for African Traditional Medicine took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-atmo took 2.6306402683258057s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.458427429199219e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.28562450408935547s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.916854858398438e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ato took 2.6006295680999756s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.26048779487609863s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020188093185424805s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013277530670166016s
Believability | Calculation of trust value for BioAssay Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bao took 2.593559980392456s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.26859331130981445s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.02025914192199707s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00038313865661621094s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.6508946418762207s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2873384952545166s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.0202181339263916s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003345012664794922s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bcgo took 2.6857290267944336s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.27906060218811035s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020195960998535156s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.001363515853881836s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bdo took 2.6674623489379883s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2765655517578125s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020280122756958008s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005044937133789062s
Believability | Calculation of trust value for Basic Formal Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bfo took 2.616563558578491s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.6253204345703125e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.28421902656555176s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007541179656982422s
Believability | Calculation of trust value for Bleeding History Phenotype took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bho took 2.63425874710083s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.7206878662109375e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.28777337074279785s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004355907440185547s
Believability | Calculation of trust value for Bilateria anatomy took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bila took 2.667308807373047s
Availability | SPARQL endpoint availability check for BIRNLex took 5.841255187988281e-05s
Availability | VoID file availability check for BIRNLex took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.27492809295654297s
Reputation | Calculation of the PageRank for BIRNLex took 0.020898103713989258s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014801025390625s
Believability | Calculation of trust value for BIRNLex took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-birnlex took 2.5811710357666016s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 5.1975250244140625e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.28696680068969727s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007719993591308594s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.6180930137634277s
Availability | SPARQL endpoint availability check for BioPAX took 4.2438507080078125e-05s
Availability | VoID file availability check for BioPAX took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for BioPAX took 0.28819799423217773s
Reputation | Calculation of the PageRank for BioPAX took 0.020244836807250977s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0008285045623779297s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.441375732421875e-05s
Believability | Calculation of trust value for BioPAX took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bp took 2.6535136699676514s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 6.580352783203125e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2542853355407715s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003542900085449219s
Believability | Calculation of trust value for Biomedical Resource Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.600532293319702s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.26170921325683594s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00020885467529296875s
Believability | Calculation of trust value for Spatial Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bspo took 2.6549010276794434s
Availability | SPARQL endpoint availability check for BioTop took 4.267692565917969e-05s
Availability | VoID file availability check for BioTop took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for BioTop took 0.2612173557281494s
Reputation | Calculation of the PageRank for BioTop took 0.020021677017211914s
Interlinking | Calculation of Degree of Connection for BioTop took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioTop took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006864070892333984s
Believability | Calculation of trust value for BioTop took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bt took 2.589167594909668s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.315376281738281e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.26917028427124023s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020184040069580078s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008809566497802734s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bto took 2.641124963760376s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3272542953491211s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018351078033447266s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-canco took 3.1531124114990234s
Availability | SPARQL endpoint availability check for CAO took 4.267692565917969e-05s
Availability | VoID file availability check for CAO took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for CAO took 0.2627449035644531s
Reputation | Calculation of the PageRank for CAO took 0.020262956619262695s
Interlinking | Calculation of Degree of Connection for CAO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005736351013183594s
Believability | Calculation of trust value for CAO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cao took 2.7208025455474854s
Availability | SPARQL endpoint availability check for CareLex took 5.650520324707031e-05s
Availability | VoID file availability check for CareLex took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for CareLex took 0.27716898918151855s
Reputation | Calculation of the PageRank for CareLex took 0.02030014991760254s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.887580871582031e-05s
Believability | Calculation of trust value for CareLex took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-carelex took 2.662315845489502s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.29891395568847656s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02029705047607422s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007894039154052734s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cco took 2.641850233078003s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.24561071395874023s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002524852752685547s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cdao took 2.6024980545043945s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.363059997558594e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2592744827270508s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.00081634521484375s
Believability | Calculation of trust value for Chemical entities of biological interest took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-chebi took 2.628105878829956s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.076957702636719e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.26381754875183105s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.02067875862121582s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002765655517578125s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.6192805767059326s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.259899377822876s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007481575012207031s
Believability | Calculation of trust value for Chemical Information Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cheminf took 2.6337976455688477s
Availability | SPARQL endpoint availability check for Cell type took 4.1961669921875e-05s
Availability | VoID file availability check for Cell type took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Cell type took 0.27084851264953613s
Reputation | Calculation of the PageRank for Cell type took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003936290740966797s
Believability | Calculation of trust value for Cell type took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cl took 2.5700955390930176s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.26894640922546387s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020819425582885742s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.000858306884765625s
Believability | Calculation of trust value for Cell Line Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-clo took 2.6196072101593018s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 8.249282836914062e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2757103443145752s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001742839813232422s
Believability | Calculation of trust value for Clinical Measurement Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cmo took 2.6831247806549072s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.27513813972473145s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00021767616271972656s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cno took 2.639357328414917s
Availability | SPARQL endpoint availability check for Wheat trait took 7.390975952148438e-05s
Availability | VoID file availability check for Wheat trait took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.26322031021118164s
Reputation | Calculation of the PageRank for Wheat trait took 0.021002531051635742s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.626678466796875e-05s
Believability | Calculation of trust value for Wheat trait took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.637542724609375s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.124641418457031e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.301713228225708s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003504753112792969s
Believability | Calculation of trust value for Cognitive Atlas took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cogat took 2.718919038772583s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.26265478134155273s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.0202181339263916s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007681846618652344s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cogpo took 2.6378307342529297s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 7.390975952148438e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.26239991188049316s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020277976989746094s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00042057037353515625s
Believability | Calculation of trust value for Current Procedural Terminology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cpt took 2.6114602088928223s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 0.0001709461212158203s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3394482135772705s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017733573913574219s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-csp took 3.143144369125366s
Availability | SPARQL endpoint availability check for COSTART took 4.2438507080078125e-05s
Availability | VoID file availability check for COSTART took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for COSTART took 0.26224184036254883s
Reputation | Calculation of the PageRank for COSTART took 0.02013111114501953s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009942054748535156s
Believability | Calculation of trust value for COSTART took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cst took 2.6138062477111816s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.1961669921875e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.24407601356506348s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004999637603759766s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ctcae took 2.621652364730835s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 7.009506225585938e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0010247230529785156s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.25098252296447754s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004889965057373047s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ctx took 2.5378096103668213s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.267692565917969e-05s
Availability | VoID file availability check for Dendritic cell took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.2661116123199463s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0002918243408203125s
Believability | Calculation of trust value for Dendritic cell took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.6062333583831787s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.28566431999206543s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.893013000488281e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ddanat took 2.635788917541504s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 5.435943603515625e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.27195048332214355s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020193099975585938s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009508132934570312s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ddi took 2.6764485836029053s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.28264784812927246s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.177757263183594e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.565403938293457s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.28797197341918945s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00024580955505371094s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.6249372959136963s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2732510566711426s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006642341613769531s
Believability | Calculation of trust value for Human disease ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-doid took 2.607825994491577s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.27074766159057617s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008232593536376953s
Believability | Calculation of trust value for Electrocardiography Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ecg took 2.601271152496338s
Availability | SPARQL endpoint availability check for Evidence codes took 4.100799560546875e-05s
Availability | VoID file availability check for Evidence codes took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2674753665924072s
Reputation | Calculation of the PageRank for Evidence codes took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.0040740966796875e-05s
Believability | Calculation of trust value for Evidence codes took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-eco took 2.6791083812713623s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.982948303222656e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.33031153678894043s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020586013793945312s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.001741170883178711s
Believability | Calculation of trust value for Experimental Factor Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-efo took 2.9741714000701904s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.124641418457031e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.2866659164428711s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020576000213623047s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011730194091796875s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ehda took 2.63521671295166s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.172325134277344e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.25360822677612305s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007569789886474609s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.645519733428955s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.1484832763671875e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.2588613033294678s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005345344543457031s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.605130434036255s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.3392181396484375e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.2882242202758789s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.0040740966796875e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-emap took 2.695115089416504s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Environment Ontology took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.26017284393310547s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0004069805145263672s
Believability | Calculation of trust value for Environment Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-envo took 2.6549785137176514s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.172325134277344e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2972097396850586s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020615100860595703s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00029015541076660156s
Believability | Calculation of trust value for Plant environmental conditions took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-eo took 2.612846851348877s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.3014371395111084s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012202262878417969s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ep took 2.6536083221435547s
Availability | SPARQL endpoint availability check for Epilepsy took 4.220008850097656e-05s
Availability | VoID file availability check for Epilepsy took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.26990461349487305s
Reputation | Calculation of the PageRank for Epilepsy took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001289844512939453s
Believability | Calculation of trust value for Epilepsy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-epileponto took 2.6284213066101074s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.172325134277344e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0012319087982177734s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.30075502395629883s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011396408081054688s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ero took 2.683821439743042s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.076957702636719e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.2764863967895508s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020364046096801758s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011434555053710938s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ev took 2.642364978790283s
Availability | SPARQL endpoint availability check for ExO took 5.0067901611328125e-05s
Availability | VoID file availability check for ExO took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for ExO took 0.27091312408447266s
Reputation | Calculation of the PageRank for ExO took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for ExO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0002460479736328125s
Believability | Calculation of trust value for ExO took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-exo took 2.663201332092285s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.100799560546875e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2636227607727051s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.000110626220703125s
Believability | Calculation of trust value for Fungal gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fao took 2.5217161178588867s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.291534423828125e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2668642997741699s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.0002086162567138672s
Believability | Calculation of trust value for Biological imaging methods took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-fbbi took 2.6643266677856445s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.27637314796447754s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006437301635742188s
Believability | Calculation of trust value for Drosophila gross anatomy took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-fbbt took 2.6170270442962646s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.220008850097656e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.27370572090148926s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020255565643310547s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004677772521972656s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbcv took 2.6204702854156494s
Availability | SPARQL endpoint availability check for Drosophila development took 4.124641418457031e-05s
Availability | VoID file availability check for Drosophila development took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2693195343017578s
Reputation | Calculation of the PageRank for Drosophila development took 0.020620346069335938s
Interlinking | Calculation of Degree of Connection for Drosophila development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Drosophila development took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.553794860839844e-05s
Believability | Calculation of trust value for Drosophila development took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-fbdv took 2.643024206161499s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.1961669921875e-05s
Availability | VoID file availability check for Fly taxonomy took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.26871490478515625s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.00038051605224609375s
Believability | Calculation of trust value for Fly taxonomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-fbsp took 2.62756609916687s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.38690185546875e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.3551952838897705s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022292137145996094s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.7965805530548096s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2668125629425049s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020240068435668945s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00039577484130859375s
Believability | Calculation of trust value for Family Health History Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fhho took 2.5878944396972656s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.27019190788269043s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.0203397274017334s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.001043081283569336s
Believability | Calculation of trust value for Influenza Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-flu took 2.635542631149292s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.2703399658203125s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020176172256469727s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.031990051269531e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fma took 2.610506534576416s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2763853073120117s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001289844512939453s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fypo took 2.728440284729004s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.27544403076171875s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.131431579589844e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-geospecies took 2.6633238792419434s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2661628723144531s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020301103591918945s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016951560974121094s
Believability | Calculation of trust value for General Formal Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gfo took 2.6738224029541016s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.315376281738281e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2881619930267334s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020231962203979492s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005965232849121094s
Believability | Calculation of trust value for General Formal Ontology: Biology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.702501058578491s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.100799560546875e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.27053332328796387s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008740425109863281s
Believability | Calculation of trust value for Gene Ontology Extension took 3.075599670410156e-05s
INFO | --- Analysis for bioportal-go_x1 took 2.6623854637145996s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.26926255226135254s
Reputation | Calculation of the PageRank for Gene Ontology took 0.02113795280456543s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0008640289306640625s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008790493011474609s
Believability | Calculation of trust value for Gene Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.644961357116699s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.029273986816406e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.25899839401245117s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020395517349243164s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 2.8133392333984375e-05s
Believability | Calculation of trust value for Cereal Plant Development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-gro took 2.5684187412261963s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.57763671875e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2497420310974121s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00045609474182128906s
Believability | Calculation of trust value for Cereal plant gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.6701390743255615s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2760334014892578s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007379055023193359s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.6409525871276855s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 8.273124694824219e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.000301361083984375s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.27529406547546387s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02027726173400879s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005779266357421875s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hao took 2.605949878692627s
Availability | SPARQL endpoint availability check for HCPCS took 4.076957702636719e-05s
Availability | VoID file availability check for HCPCS took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for HCPCS took 0.27992844581604004s
Reputation | Calculation of the PageRank for HCPCS took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for HCPCS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HCPCS took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00022530555725097656s
Believability | Calculation of trust value for HCPCS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.7093324661254883s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.1484832763671875e-05s
Availability | VoID file availability check for Health Level Seven took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.26918721199035645s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012731552124023438s
Believability | Calculation of trust value for Health Level Seven took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-hl7 took 2.640364646911621s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.291534423828125e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.25633883476257324s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.021007537841796875s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00035858154296875s
Believability | Calculation of trust value for HEALTH_INDICATORS took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.637455701828003s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 7.319450378417969e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.27613329887390137s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 2.8133392333984375e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hom took 2.735461473464966s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.267692565917969e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.2831101417541504s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020812273025512695s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 2.9802322387695312e-05s
Believability | Calculation of trust value for HOM-HARVARD took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.659317970275879s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.27729320526123047s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006356239318847656s
Believability | Calculation of trust value for Human Phenotype Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.6589419841766357s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.256420373916626s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020148754119873047s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.001031637191772461s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hpio took 2.6911110877990723s
Availability | SPARQL endpoint availability check for HUGO took 4.410743713378906e-05s
Availability | VoID file availability check for HUGO took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for HUGO took 0.2551140785217285s
Reputation | Calculation of the PageRank for HUGO took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for HUGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0008425712585449219s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.653236389160156e-05s
Believability | Calculation of trust value for HUGO took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hugo took 2.670022964477539s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.26856136322021484s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006470680236816406s
Believability | Calculation of trust value for Information Artifact Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-iao took 2.586069107055664s
Availability | SPARQL endpoint availability check for ICD10 took 4.124641418457031e-05s
Availability | VoID file availability check for ICD10 took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for ICD10 took 0.26951122283935547s
Reputation | Calculation of the PageRank for ICD10 took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.00083160400390625s
Believability | Calculation of trust value for ICD10 took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icd10 took 2.65817928314209s
Availability | SPARQL endpoint availability check for ICD10CM took 4.1961669921875e-05s
Availability | VoID file availability check for ICD10CM took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.26550841331481934s
Reputation | Calculation of the PageRank for ICD10CM took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for ICD10CM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006034374237060547s
Believability | Calculation of trust value for ICD10CM took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.643446445465088s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.172325134277344e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.2502932548522949s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.0001583099365234375s
Believability | Calculation of trust value for ICD-10-PCS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.554859161376953s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.4345855712890625e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.284771203994751s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006558895111083984s
Believability | Calculation of trust value for International Classification of Diseases took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.6700243949890137s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.57763671875e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.26197290420532227s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004782676696777344s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.615316152572632s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.1484832763671875e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.27573251724243164s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012459754943847656s
Believability | Calculation of trust value for International Classification for Nursing Practice took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icnp took 2.638035774230957s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.220008850097656e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.27457451820373535s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.000438690185546875s
Believability | Calculation of trust value for International Classification of Primary Care took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icpc took 2.696319341659546s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.458427429199219e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2534964084625244s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008766651153564453s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.7106082439422607s
Availability | SPARQL endpoint availability check for ICPS Network took 7.939338684082031e-05s
Availability | VoID file availability check for ICPS Network took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2613406181335449s
Reputation | Calculation of the PageRank for ICPS Network took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00023174285888671875s
Believability | Calculation of trust value for ICPS Network took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-icps took 2.6106467247009277s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.3029823303222656s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008707046508789062s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ido took 2.639448404312134s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2738344669342041s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020493745803833008s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011272430419921875s
Believability | Calculation of trust value for Brucellosis Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-idobru took 2.66441011428833s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.25922513008117676s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013170242309570312s
Believability | Calculation of trust value for Malaria Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-idomal took 2.6958518028259277s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.124641418457031e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.27451372146606445s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00031375885009765625s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-iev took 2.626603364944458s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 5.078315734863281e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.2877979278564453s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.02134084701538086s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0008246898651123047s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00021076202392578125s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-imgt took 2.6721365451812744s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.1961669921875e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.28533053398132324s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005216598510742188s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-imr took 2.765639066696167s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2685825824737549s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008041858673095703s
Believability | Calculation of trust value for Interaction Network Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ino took 2.660861015319824s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.315376281738281e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2470567226409912s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 2.956390380859375e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.5796797275543213s
Availability | SPARQL endpoint availability check for IxnO took 4.1961669921875e-05s
Availability | VoID file availability check for IxnO took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for IxnO took 0.2879676818847656s
Reputation | Calculation of the PageRank for IxnO took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.0002009868621826172s
Believability | Calculation of trust value for IxnO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ixno took 2.6914985179901123s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.291534423828125e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2626967430114746s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003771781921386719s
Believability | Calculation of trust value for SysMO-JERM took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-jerm took 2.580789566040039s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.2657792568206787s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-kisao took 2.662630796432495s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 3.9577484130859375e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.3012509346008301s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00024271011352539062s
Believability | Calculation of trust value for Loggerhead nesting took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-lhn took 2.6568496227264404s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Lipid Ontology took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.27768373489379883s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020599365234375s
Believability | Calculation of trust value for Lipid Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-lipro took 2.6878509521484375s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 3.9577484130859375e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.31699180603027344s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018558502197265625s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lnc took 3.0369455814361572s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.076957702636719e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2761545181274414s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006365776062011719s
Believability | Calculation of trust value for Mouse adult gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ma took 2.610548734664917s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.0531158447265625e-05s
Availability | VoID file availability check for Multiple alignment took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2585728168487549s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002028942108154297s
Believability | Calculation of trust value for Multiple alignment took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mao took 2.5943169593811035s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.172325134277344e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2646911144256592s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020404815673828125s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0008382797241210938s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006914138793945312s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mat took 2.5896217823028564s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.076957702636719e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.27153635025024414s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004222393035888672s
Believability | Calculation of trust value for Breast tissue cell lines took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.607178211212158s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2637333869934082s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007772445678710938s
Believability | Calculation of trust value for Cell line ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mccl took 2.5487053394317627s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2728543281555176s
Reputation | Calculation of the PageRank for Cell line ontology took 0.0211334228515625s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0008087158203125s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014674663543701172s
Believability | Calculation of trust value for Cell line ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.587414026260376s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.124641418457031e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.2977733612060547s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02028036117553711s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00024437904357910156s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-mcv took 2.696564197540283s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.100799560546875e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2716336250305176s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0008339881896972656s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00022554397583007812s
Believability | Calculation of trust value for Master Drug Data Base took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mddb took 2.603433609008789s
Availability | SPARQL endpoint availability check for MedDRA took 4.1484832763671875e-05s
Availability | VoID file availability check for MedDRA took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2726616859436035s
Reputation | Calculation of the PageRank for MedDRA took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011668205261230469s
Believability | Calculation of trust value for MedDRA took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mdr took 2.5965397357940674s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 3.981590270996094e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2598733901977539s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009250640869140625s
Believability | Calculation of trust value for MedlinePlus Health Topics took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.6225898265838623s
Availability | SPARQL endpoint availability check for MeGO took 4.1484832763671875e-05s
Availability | VoID file availability check for MeGO took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for MeGO took 0.2858130931854248s
Reputation | Calculation of the PageRank for MeGO took 0.02032184600830078s
Interlinking | Calculation of Degree of Connection for MeGO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001647472381591797s
Believability | Calculation of trust value for MeGO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mego took 2.6242995262145996s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.029273986816406e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.31751251220703125s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018191337585449219s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.0996463298797607s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2679412364959717s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006389617919921875s
Believability | Calculation of trust value for Mental Functioning Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mf took 2.6007232666015625s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 5.650520324707031e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2856142520904541s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.02042675018310547s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005769729614257812s
Believability | Calculation of trust value for Medaka fish anatomy and development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mfo took 2.700979471206665s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2541952133178711s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.000751495361328125s
Believability | Calculation of trust value for Emotion Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mfoem took 2.572075843811035s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.27817392349243164s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010538101196289062s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-mhc took 2.6649112701416016s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.220008850097656e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2970869541168213s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020112037658691406s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006954669952392578s
Believability | Calculation of trust value for Protein-protein interaction took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mi took 2.6908462047576904s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.1484832763671875e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.26734209060668945s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007309913635253906s
Believability | Calculation of trust value for Mosquito insecticide resistance took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-miro took 2.5853195190429688s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.29101085662841797s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001418590545654297s
Believability | Calculation of trust value for Measurement Method Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mmo took 2.6434736251831055s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.27346014976501465s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.00037860870361328125s
Believability | Calculation of trust value for MGED Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mo took 2.594223976135254s
Availability | SPARQL endpoint availability check for Protein modification took 4.2438507080078125e-05s
Availability | VoID file availability check for Protein modification took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Protein modification took 0.25851011276245117s
Reputation | Calculation of the PageRank for Protein modification took 0.020488262176513672s
Interlinking | Calculation of Degree of Connection for Protein modification took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00023031234741210938s
Believability | Calculation of trust value for Protein modification took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mod took 2.5138070583343506s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.076957702636719e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.27610206604003906s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006566047668457031s
Believability | Calculation of trust value for Mammalian phenotype took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mp took 2.7122325897216797s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.124641418457031e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.27355480194091797s
Reputation | Calculation of the PageRank for Mouse pathology took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004782676696777344s
Believability | Calculation of trust value for Mouse pathology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mpath took 2.669528007507324s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.863739013671875e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2638876438140869s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003783702850341797s
Believability | Calculation of trust value for Mass spectrometry took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ms took 2.5937917232513428s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.363059997558594e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3245723247528076s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020561695098876953s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0020132064819335938s
Believability | Calculation of trust value for Medical Subject Headings took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-msh took 3.0878446102142334s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.649162292480469e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2595181465148926s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0001773834228515625s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mthch took 2.5749804973602295s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.2651805877685547s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007824897766113281s
Believability | Calculation of trust value for Natural Products Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-natpro took 2.6199288368225098s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.124641418457031e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0013606548309326172s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.27159786224365234s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008294582366943359s
Believability | Calculation of trust value for NCBI organismal classification took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.7133002281188965s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.32033562660217285s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.002048492431640625s
Believability | Calculation of trust value for NCI Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ncit took 3.064793348312378s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.220008850097656e-05s
Availability | VoID file availability check for National Drug Data File took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.2679100036621094s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006253719329833984s
Believability | Calculation of trust value for National Drug Data File took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-nddf took 2.609821081161499s
Availability | SPARQL endpoint availability check for National Drug File took 4.220008850097656e-05s
Availability | VoID file availability check for National Drug File took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2471294403076172s
Reputation | Calculation of the PageRank for National Drug File took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.001283884048461914s
Believability | Calculation of trust value for National Drug File took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.5487234592437744s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.124641418457031e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.27782654762268066s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0012078285217285156s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.6909143924713135s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.2835264205932617s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006871223449707031s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-neomark took 2.690964460372925s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.24737858772277832s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012874603271484375s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.6269912719726562s
Availability | SPARQL endpoint availability check for NIFSTD took 4.1961669921875e-05s
Availability | VoID file availability check for NIFSTD took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.3182969093322754s
Reputation | Calculation of the PageRank for NIFSTD took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.001888275146484375s
Believability | Calculation of trust value for NIFSTD took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-nif took 3.073443651199341s
Availability | SPARQL endpoint availability check for NIF Cell took 4.172325134277344e-05s
Availability | VoID file availability check for NIF Cell took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.27759504318237305s
Reputation | Calculation of the PageRank for NIF Cell took 0.02080392837524414s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0014853477478027344s
Believability | Calculation of trust value for NIF Cell took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.6299383640289307s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 8.511543273925781e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.24484705924987793s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.001394510269165039s
Believability | Calculation of trust value for NIF Dysfunction took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.652423620223999s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.00033974647521972656s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.25386524200439453s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02101898193359375s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0009143352508544922s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0006337165832519531s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nigo took 2.560527801513672s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.100799560546875e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2817575931549072s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0006005764007568359s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nmr took 2.655543088912964s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2540135383605957s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010848045349121094s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 3.147125244140625e-05s
INFO | --- Analysis for bioportal-nonrctontology took 2.5521328449249268s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.25950121879577637s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0012106895446777344s
Believability | Calculation of trust value for NanoParticle Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-npo took 2.6014041900634766s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2574031352996826s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007352828979492188s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-oae took 2.608304500579834s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.26674866676330566s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020667314529418945s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0008981227874755859s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0015113353729248047s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-obi took 2.6524498462677s
Availability | SPARQL endpoint availability check for OBOE took 4.220008850097656e-05s
Availability | VoID file availability check for OBOE took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for OBOE took 0.2850041389465332s
Reputation | Calculation of the PageRank for OBOE took 0.02078843116760254s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011420249938964844s
Believability | Calculation of trust value for OBOE took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-oboe took 2.6774353981018066s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.291534423828125e-05s
Availability | VoID file availability check for OBOE SBC took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2708587646484375s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020938634872436523s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008256435394287109s
Believability | Calculation of trust value for OBOE SBC took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.5961105823516846s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2655296325683594s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020227670669555664s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005993843078613281s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ocre took 2.547916889190674s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.076957702636719e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.27805566787719727s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008616447448730469s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-odgi took 2.635789155960083s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2865128517150879s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020247220993041992s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008885860443115234s
Believability | Calculation of trust value for Ontology for Genetic Interval took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ogi took 2.571462631225586s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 5.435943603515625e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.27790069580078125s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002982616424560547s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ogmd took 2.6752307415008545s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.27855896949768066s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.021263599395751953s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0009222030639648438s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0007681846618652344s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ogms took 2.7067463397979736s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.2438507080078125e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.27231431007385254s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011258125305175781s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-omim took 2.611105442047119s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.029273986816406e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.28502535820007324s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0005018711090087891s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-omit took 2.6234989166259766s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.1484832763671875e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.24890851974487305s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.0202181339263916s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005853176116943359s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omrse took 2.3565640449523926s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.28160834312438965s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020221471786499023s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007719993591308594s
Believability | Calculation of trust value for Ontology of Data Mining took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ontodm took 2.674913167953491s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.26678013801574707s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020504236221313477s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002455711364746094s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ontodt took 2.661081552505493s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.5299530029296875e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.25699543952941895s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020842790603637695s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006206035614013672s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.604063034057617s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2889878749847412s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020442485809326172s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009281635284423828s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-opl took 2.6951606273651123s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.220008850097656e-05s
Availability | VoID file availability check for Phenotypic quality took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.272857666015625s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008842945098876953s
Believability | Calculation of trust value for Phenotypic quality took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pato took 2.666776418685913s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.1484832763671875e-05s
Availability | VoID file availability check for Physician Data Query took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2769606113433838s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0007982254028320312s
Believability | Calculation of trust value for Physician Data Query took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pdq took 2.6593661308288574s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.4345855712890625e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.29540324211120605s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.0211031436920166s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0008108615875244141s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0009162425994873047s
Believability | Calculation of trust value for Pediatric Terminology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-pedterm took 2.744119644165039s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.2820565700531006s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0001938343048095703s
Believability | Calculation of trust value for Parasite Experiment Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-peo took 2.603790283203125s
Availability | SPARQL endpoint availability check for PHARE took 4.029273986816406e-05s
Availability | VoID file availability check for PHARE took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for PHARE took 0.2911844253540039s
Reputation | Calculation of the PageRank for PHARE took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for PHARE took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006325244903564453s
Believability | Calculation of trust value for PHARE took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-phare took 2.7824881076812744s
Availability | SPARQL endpoint availability check for PKO_Re took 4.315376281738281e-05s
Availability | VoID file availability check for PKO_Re took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.24771523475646973s
Reputation | Calculation of the PageRank for PKO_Re took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001742839813232422s
Believability | Calculation of trust value for PKO_Re took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pko took 2.74607253074646s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.172325134277344e-05s
Availability | VoID file availability check for PMA 2010 took 0.000354766845703125s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2722666263580322s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009033679962158203s
Believability | Calculation of trust value for PMA 2010 took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pma took 2.6592695713043213s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.38690185546875e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2558772563934326s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.02100396156311035s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.000179290771484375s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pmr took 2.60581374168396s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2864034175872803s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00040268898010253906s
Believability | Calculation of trust value for Plant Anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-po took 2.5832395553588867s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 5.340576171875e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2688264846801758s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.985664367675781e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.6790666580200195s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.2753438949584961s
Reputation | Calculation of the PageRank for Plant Ontology took 0.0201876163482666s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.000446319580078125s
Believability | Calculation of trust value for Plant Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.7023367881774902s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.2438507080078125e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.26556849479675293s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006601810455322266s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pr took 2.556666135787964s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.076957702636719e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.25519418716430664s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020139217376708984s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00026535987854003906s
Believability | Calculation of trust value for Proteomics data and process provenance took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-propreo took 2.6408889293670654s
Availability | SPARQL endpoint availability check for Pathway ontology took 7.677078247070312e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.24866342544555664s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020137548446655273s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012111663818359375s
Believability | Calculation of trust value for Pathway ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pw took 2.669593572616577s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.24832558631896973s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020198345184326172s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-qibo took 2.592535972595215s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 5.030632019042969e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3094348907470703s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017714500427246094s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rcd took 3.0441551208496094s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.26637697219848633s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012612342834472656s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rctontology took 2.590545892715454s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2438194751739502s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020268917083740234s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.584426879882812e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-repo took 2.6173410415649414s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.1961669921875e-05s
Availability | VoID file availability check for Physico-chemical process took 0.00036215782165527344s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.26804661750793457s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020319700241088867s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0001952648162841797s
Believability | Calculation of trust value for Physico-chemical process took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rex took 2.637005090713501s
Availability | SPARQL endpoint availability check for RadLex took 4.124641418457031e-05s
Availability | VoID file availability check for RadLex took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for RadLex took 0.27919650077819824s
Reputation | Calculation of the PageRank for RadLex took 0.02084636688232422s
Interlinking | Calculation of Degree of Connection for RadLex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0008320808410644531s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015156269073486328s
Believability | Calculation of trust value for RadLex took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rid took 2.6507391929626465s
Availability | SPARQL endpoint availability check for RNA ontology took 4.1961669921875e-05s
Availability | VoID file availability check for RNA ontology took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.28221583366394043s
Reputation | Calculation of the PageRank for RNA ontology took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005600452423095703s
Believability | Calculation of trust value for RNA ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-rnao took 2.7062087059020996s
Availability | SPARQL endpoint availability check for Role Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Role Ontology took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.28376007080078125s
Reputation | Calculation of the PageRank for Role Ontology took 0.020209789276123047s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.0001926422119140625s
Believability | Calculation of trust value for Role Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-roleo took 2.5895729064941406s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.26010608673095703s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00016927719116210938s
Believability | Calculation of trust value for Rat Strain Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-rs took 2.6626932621002197s
Availability | SPARQL endpoint availability check for RxNORM took 4.220008850097656e-05s
Availability | VoID file availability check for RxNORM took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2592918872833252s
Reputation | Calculation of the PageRank for RxNORM took 0.020248889923095703s
Interlinking | Calculation of Degree of Connection for RxNORM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006206035614013672s
Believability | Calculation of trust value for RxNORM took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.7285757064819336s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.0531158447265625e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.2736811637878418s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020218849182128906s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010476112365722656s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sao took 2.6452152729034424s
Availability | SPARQL endpoint availability check for Systems Biology took 4.1961669921875e-05s
Availability | VoID file availability check for Systems Biology took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.2559926509857178s
Reputation | Calculation of the PageRank for Systems Biology took 0.02055525779724121s
Interlinking | Calculation of Degree of Connection for Systems Biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004634857177734375s
Believability | Calculation of trust value for Systems Biology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sbo took 2.609170436859131s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 5.5789947509765625e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.25430798530578613s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020283937454223633s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 9.942054748535156e-05s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sbro took 2.6160776615142822s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.2667107582092285s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.02017951011657715s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013260841369628906s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sdo took 2.622199058532715s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.267692565917969e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2512505054473877s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.020272254943847656s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00033926963806152344s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sep took 2.6897456645965576s
Availability | SPARQL endpoint availability check for Student Health Record took 4.1484832763671875e-05s
Availability | VoID file availability check for Student Health Record took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.26965975761413574s
Reputation | Calculation of the PageRank for Student Health Record took 0.02023911476135254s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0008177757263183594s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004782676696777344s
Believability | Calculation of trust value for Student Health Record took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-shr took 2.667271852493286s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2638223171234131s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012590885162353516s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sio took 3.434819221496582s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.100799560546875e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2892436981201172s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00021386146545410156s
Believability | Calculation of trust value for Situation-Based Access Control took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sitbac took 2.6436190605163574s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.220008850097656e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.33631062507629395s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0018889904022216797s
Believability | Calculation of trust value for SNOMED Clinical Terms took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-snomedct took 3.098703622817993s
Availability | SPARQL endpoint availability check for SNP-Ontology took 5.4836273193359375e-05s
Availability | VoID file availability check for SNP-Ontology took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.262073278427124s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006747245788574219s
Believability | Calculation of trust value for SNP-Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-snpo took 2.6144134998321533s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.076957702636719e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2775540351867676s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020519256591796875s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005846023559570312s
Believability | Calculation of trust value for Sequence types and features took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.6091582775115967s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.410743713378906e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.3058958053588867s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020807981491088867s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015625953674316406s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sopharm took 3.112400770187378s
Availability | SPARQL endpoint availability check for SoyOntology took 4.0531158447265625e-05s
Availability | VoID file availability check for SoyOntology took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.2685360908508301s
Reputation | Calculation of the PageRank for SoyOntology took 0.020274877548217773s
Interlinking | Calculation of Degree of Connection for SoyOntology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001266002655029297s
Believability | Calculation of trust value for SoyOntology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-soy took 2.655998468399048s
Availability | SPARQL endpoint availability check for Spider Ontology took 6.651878356933594e-05s
Availability | VoID file availability check for Spider Ontology took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.23417234420776367s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00033092498779296875s
Believability | Calculation of trust value for Spider Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-spd took 2.618043899536133s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.26453542709350586s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.021399497985839844s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00029206275939941406s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-spto took 2.648958444595337s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 5.340576171875e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.2769758701324463s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004565715789794922s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sso took 2.614028215408325s
Availability | SPARQL endpoint availability check for Software Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Software Ontology took 0.0004036426544189453s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2984945774078369s
Reputation | Calculation of the PageRank for Software Ontology took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for Software Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00040912628173828125s
Believability | Calculation of trust value for Software Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-swo took 2.65574049949646s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.1961669921875e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2887990474700928s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00023889541625976562s
Believability | Calculation of trust value for Tick gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tads took 2.780776023864746s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.28800487518310547s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0009009838104248047s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tao took 2.564458131790161s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.5299530029296875e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.25179100036621094s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 0.00010800361633300781s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-taxrank took 2.6642744541168213s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.363059997558594e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.25559163093566895s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.224082946777344e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-teddy took 2.5893497467041016s
Availability | SPARQL endpoint availability check for Time Event Ontology took 6.341934204101562e-05s
Availability | VoID file availability check for Time Event Ontology took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.25266528129577637s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.02139115333557129s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0015189647674560547s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0010304450988769531s
Believability | Calculation of trust value for Time Event Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-teo took 2.595297336578369s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 3.981590270996094e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.26494669914245605s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00039196014404296875s
Believability | Calculation of trust value for Mosquito gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tgma took 2.664130449295044s
Availability | SPARQL endpoint availability check for thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for thesaurus took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for thesaurus took 0.2746109962463379s
Reputation | Calculation of the PageRank for thesaurus took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.842613220214844e-05s
Believability | Calculation of trust value for thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.646937608718872s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 5.602836608886719e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.2836034297943115s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003502368927001953s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.6414918899536133s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2452094554901123s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008482933044433594s
Believability | Calculation of trust value for Translational Medicine Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-tmo took 2.590080499649048s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.26378512382507324s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0008249282836914062s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00016045570373535156s
Believability | Calculation of trust value for Plant Trait Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-to took 2.68315052986145s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2764441967010498s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.000186920166015625s
Believability | Calculation of trust value for TOK_Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tok took 2.57832407951355s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.267692565917969e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.27265429496765137s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020565271377563477s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00018858909606933594s
Believability | Calculation of trust value for Teleost taxonomy took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-tto took 2.607367992401123s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.27321743965148926s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020209550857543945s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0016484260559082031s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0019233226776123047s
Believability | Calculation of trust value for Uber anatomy ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-uberon took 2.5602619647979736s
Availability | SPARQL endpoint availability check for Units Ontology took 4.887580871582031e-05s
Availability | VoID file availability check for Units Ontology took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.24948549270629883s
Reputation | Calculation of the PageRank for Units Ontology took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00022745132446289062s
Believability | Calculation of trust value for Units Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.637974500656128s
Availability | SPARQL endpoint availability check for Units of measurement took 4.100799560546875e-05s
Availability | VoID file availability check for Units of measurement took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2625916004180908s
Reputation | Calculation of the PageRank for Units of measurement took 0.020235300064086914s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002741813659667969s
Believability | Calculation of trust value for Units of measurement took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-uo took 2.5982518196105957s
Availability | SPARQL endpoint availability check for VANDF took 4.124641418457031e-05s
Availability | VoID file availability check for VANDF took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for VANDF took 0.26924896240234375s
Reputation | Calculation of the PageRank for VANDF took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for VANDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006740093231201172s
Believability | Calculation of trust value for VANDF took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vandf took 2.634474277496338s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2638840675354004s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020126819610595703s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00041866302490234375s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vao took 2.595223903656006s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.00543212890625e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.26851654052734375s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020404815673828125s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006232261657714844s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vhog took 2.6655373573303223s
Availability | SPARQL endpoint availability check for VIVO took 5.3882598876953125e-05s
Availability | VoID file availability check for VIVO took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for VIVO took 0.28154850006103516s
Reputation | Calculation of the PageRank for VIVO took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003597736358642578s
Believability | Calculation of trust value for VIVO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vivo took 2.613510847091675s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.25191617012023926s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012695789337158203s
Believability | Calculation of trust value for Vaccine Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vo took 2.562791347503662s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2675156593322754s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020432472229003906s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vt took 2.574967861175537s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 5.2928924560546875e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2578248977661133s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005099773406982422s
Believability | Calculation of trust value for C. elegans gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-wbbt took 2.657844066619873s
Availability | SPARQL endpoint availability check for C. elegans development took 4.076957702636719e-05s
Availability | VoID file availability check for C. elegans development took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.274916410446167s
Reputation | Calculation of the PageRank for C. elegans development took 0.02002739906311035s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.506111145019531e-05s
Believability | Calculation of trust value for C. elegans development took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-wbls took 2.6863937377929688s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.220008850097656e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2847452163696289s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.821487426757812e-05s
Believability | Calculation of trust value for C. elegans phenotype took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.633181571960449s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.506111145019531e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2706301212310791s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020186424255371094s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005812644958496094s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-who took 2.6418604850769043s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.8160552978515625e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2572352886199951s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.000682830810546875s
Believability | Calculation of trust value for Xenopus anatomy and development took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-xao took 2.578467607498169s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.25510692596435547s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02026820182800293s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00023937225341796875s
Believability | Calculation of trust value for Experimental Conditions Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-xco took 2.641831159591675s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.1961669921875e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.28421592712402344s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00027632713317871094s
Believability | Calculation of trust value for Yeast phenotypes took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ypo took 2.6298534870147705s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.172325134277344e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.2669868469238281s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020229339599609375s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007681846618652344s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-zfa took 2.6346631050109863s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.172325134277344e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.2673299312591553s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 6.9141387939453125e-06s
INFO | --- Analysis for Bioportal_link took 3.438274621963501s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.5407185554504395s
Availability | VoID file availability check for BioSamples RDF took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.2549104690551758s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.3855438232421875e-05s
Believability | Calculation of trust value for BioSamples RDF took 7.867813110351562e-06s
INFO | --- Analysis for biosamples-rdf took 3.8009934425354004s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 1.1411232948303223s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2525522708892822s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011348724365234375s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for bis-linked-data took 3.566516637802124s
Availability | SPARQL endpoint availability check for Bitzi took 4.982948303222656e-05s
Availability | VoID file availability check for Bitzi took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Bitzi took 0.2595376968383789s
Reputation | Calculation of the PageRank for Bitzi took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for Bitzi took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bitzi took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bitzi took 6.9141387939453125e-06s
INFO | --- Analysis for bitzi took 2.87029767036438s
Availability | SPARQL endpoint availability check for BizkaiSense took 3.981590270996094e-05s
Availability | VoID file availability check for BizkaiSense took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.2593989372253418s
Reputation | Calculation of the PageRank for BizkaiSense took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 2.9325485229492188e-05s
Believability | Calculation of trust value for BizkaiSense took 7.62939453125e-06s
INFO | --- Analysis for bizkaisense took 2.9658992290496826s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.076957702636719e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.287261962890625s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.8133392333984375e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.152557373046875e-06s
INFO | --- Analysis for blabla-itemlist took 2.93605637550354s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.6253204345703125e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2612011432647705s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020440340042114258s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.1948089599609375e-05s
Believability | Calculation of trust value for blabla.itemlist took 6.9141387939453125e-06s
INFO | --- Analysis for blabla_itemlist took 2.982167959213257s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.987022399902344e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.27051782608032227s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.02045154571533203s
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.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.981590270996094e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for bll-thesaurus took 3.6609690189361572s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 0.6755576133728027s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.27542924880981445s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.604194641113281e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for bluk-bnb took 13.403846979141235s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.26650500297546387s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006604194641113281s
Extra | Recovery of all triples for Thesaurus BNCF took 51.80208349227905s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6402842998504639s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6303105354309082s
Interoperability | New terms check for Thesaurus BNCF took 1.4871017932891846s
Versatility | Languages check for Thesaurus BNCF took 7.320151090621948s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.9254007339477539s
Security | Check HTTPS for Thesaurus BNCF took 0.09063148498535156s
Interpretability | RDF structures check for Thesaurus BNCF took 0.1302778720855713s
Versatility | Serialization formats check for Thesaurus BNCF took 0.12355566024780273s
Availability | RDF dump link check for Thesaurus BNCF took 0.12467074394226074s
License | MR license check for Thesaurus BNCF took 0.11633491516113281s
License | HR license check for Thesaurus BNCF took 0.20864653587341309s
Amount of data | Number of property check for Thesaurus BNCF took 0.1268610954284668s
Understandability | Number of label check for Thesaurus BNCF took 0.35825443267822266s
Understandability | URI regex check for Thesaurus BNCF took 0.24527502059936523s
Understandability | Vocabs check for Thesaurus BNCF took 0.12203383445739746s
Verifiability | Authors check for Thesaurus BNCF took 0.12815356254577637s
Verifiability | Publishers check for Thesaurus BNCF took 0.12260150909423828s
Performance | Throughput check for Thesaurus BNCF took 10.853454113006592s
Amount of data | Check the number of entities for Thesaurus BNCF took 0.00010848045349121094s
Verifiability | Contribs. check for Thesaurus BNCF took 0.12804627418518066s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.13083219528198242s
Interlinking | skos check for Thesaurus BNCF took 0.1826479434967041s
Interlinking | skos check for Thesaurus BNCF took 0.15576624870300293s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.13028860092163086s
Currency | Creation date check for Thesaurus BNCF took 0.24887776374816895s
Currency | Modification date check for Thesaurus BNCF took 0.26101016998291016s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.263662099838257s
Interoperability | New vocabularies check for Thesaurus BNCF took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.1146547794342041s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.12097430229187012s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.12509775161743164s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 11.413379192352295s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5124881267547607s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 4.043991327285767s
Consistency | Disjoint class check for Thesaurus BNCF took 0.15217256546020508s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8432815074920654s
Consistency | Misplaced classes for Thesaurus BNCF took 6.922180414199829s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.964979887008667s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4012596607208252s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.247892379760742s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4292612075805664s
Security | Sign check for Thesaurus BNCF took 0.12328624725341797s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 17.643918991088867s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.37061214447021484s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.605552673339844e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.430511474609375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 8.344650268554688e-06s
INFO | --- Analysis for bncf-ns took 188.28102016448975s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.064391851425171s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006313323974609375s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.110275506973267s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9920084476470947s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.2524237632751465s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.084578275680542s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.48074436187744s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.147075653076172s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5222303867340088s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.911339521408081s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6464855670928955s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5963971614837646s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6003468036651611s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.50910472869873s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3097846508026123s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6902673244476318s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0100252628326416s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5953304767608643s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6342611312866211s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.32833218574523926s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.732737302780151s
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.5080256462097168s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1184217929840088s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3178575038909912s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.26543712615966797s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5752112865447998s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8089213371276855s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7504136562347412s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 18.135613441467285s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5295736789703369s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2945699691772461s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7797830104827881s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.964076519012451s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02465534210205078s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02960944175720215s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5250558853149414s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.077481269836426s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9585404396057129s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.330000162124634s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.66837477684021s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.097728490829468s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.032034873962402344s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4901008605957031s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5285089015960693s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.793001413345337s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.831127405166626s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.62939453125e-06s
INFO | --- Analysis for bpr took 489.0480372905731s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.410743713378906e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.7018287181854248s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020984888076782227s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.961822509765625e-05s
Believability | Calculation of trust value for Brazilian Politicians took 5.4836273193359375e-06s
INFO | --- Analysis for brazilian-politicians took 5.563512086868286s
Availability | SPARQL endpoint availability check for BrazilianCities took 5.030632019042969e-05s
Availability | VoID file availability check for BrazilianCities took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.280336856842041s
Reputation | Calculation of the PageRank for BrazilianCities took 0.022134780883789062s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0008614063262939453s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.528594970703125e-05s
Believability | Calculation of trust value for BrazilianCities took 8.344650268554688e-06s
INFO | --- Analysis for braziliancities took 4.179384708404541s
Availability | SPARQL endpoint availability check for Bricklink took 1.8298451900482178s
Availability | VoID file availability check for Bricklink took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Bricklink took 0.28826141357421875s
Reputation | Calculation of the PageRank for Bricklink took 0.020245790481567383s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.651878356933594e-05s
Believability | Calculation of trust value for Bricklink took 1.0013580322265625e-05s
INFO | --- Analysis for bricklink took 9.135479211807251s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.138790130615234s
Availability | VoID file availability check for British Museum Collection took 0.000782012939453125s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.701019287109375s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.2901763916015625e-05s
Believability | Calculation of trust value for British Museum Collection took 7.62939453125e-06s
INFO | --- Analysis for british-museum-collection took 73.07280898094177s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 7.510185241699219e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.2483680248260498s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.021196365356445312s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.000995635986328125s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 5.054473876953125e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 7.867813110351562e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 4.624651670455933s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.267692565917969e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.2785210609436035s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.0206606388092041s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 3.0279159545898438e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 7.867813110351562e-06s
INFO | --- Analysis for bsv took 4.3491575717926025s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5446765422821045s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2828695774078369s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.020332813262939453s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3589859008789062e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 8.106231689453125e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 6.4457783699035645s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.172325134277344e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.270169734954834s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.021435976028442383s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0009138584136962891s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.719329833984375e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 7.867813110351562e-06s
INFO | --- Analysis for bund-offener-haushalt took 2.908501148223877s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.0531158447265625e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.2698795795440674s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.170967102050781e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 9.059906005859375e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 3.308897018432617s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.2889072895050049s
Availability | VoID file availability check for business.data.gov.uk took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2518343925476074s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020223140716552734s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0008127689361572266s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.412101745605469e-05s
Believability | Calculation of trust value for business.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for business-data-gov-uk took 2.865255832672119s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 1.5553317070007324s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.00040602684020996094s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.5515730381011963s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.2782273292541504s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.46398329734802246s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.5806574821472168s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 30.229675769805908s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.4456138610839844s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.12638306617736816s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.4986121654510498s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.400667667388916s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.2730879783630371s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.3861818313598633s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 22.883980989456177s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.2998011112213135s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.6422021389007568s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.6239380836486816s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.22391152381896973s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.3603954315185547s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.33956146240234375s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.43865966796875e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.2526569366455078s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.21731305122375488s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.24384427070617676s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.2520871162414551s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.2552173137664795s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.5241038799285889s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.4847545623779297s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 0.4901237487792969s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.27884912490844727s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.03184318542480469s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.23749089241027832s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 0.18801021575927734s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 1.551990032196045s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.0360870361328125s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.4062826633453369s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 6.380260467529297s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.7015411853790283s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02004218101501465s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.0067901611328125e-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 9.059906005859375e-06s
INFO | --- Analysis for BVMC took 102.316903591156s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.1961669921875e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.27385830879211426s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.020151853561401367s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.0279159545898438e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 8.58306884765625e-06s
INFO | --- Analysis for cabbage took 4.274730920791626s
Availability | SPARQL endpoint availability check for cablegate took 1.884739875793457s
Availability | VoID file availability check for cablegate took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for cablegate took 0.2566699981689453s
Reputation | Calculation of the PageRank for cablegate took 0.021326303482055664s
Interlinking | Calculation of Degree of Connection for cablegate took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0008640289306640625s
Interlinking | Calculation of Clustering coefficient for cablegate took 7.867813110351562e-05s
Believability | Calculation of trust value for cablegate took 7.867813110351562e-06s
INFO | --- Analysis for cablegate took 7.449958562850952s
Availability | SPARQL endpoint availability check for Calames took 4.506111145019531e-05s
Availability | VoID file availability check for Calames took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for Calames took 0.2631540298461914s
Reputation | Calculation of the PageRank for Calames took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for Calames took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Calames took 3.552436828613281e-05s
Believability | Calculation of trust value for Calames took 8.344650268554688e-06s
INFO | --- Analysis for calames took 4.860306978225708s
Availability | SPARQL endpoint availability check for CaLiGraph took 6.480912446975708s
Availability | VoID file availability check for CaLiGraph took 0.0003056526184082031s
Extra | Recovery of all triples for CaLiGraph took 18.104488611221313s
Performance | Total latancy measurement for CaLiGraph took 55.494487285614014s
Amount of data | Number of triples check for CaLiGraph took 36.96646070480347s
Interoperability | New terms check for CaLiGraph took 16.520949840545654s
Versatility | Languages check for CaLiGraph took 75.21749234199524s
Interpretability | Number of blank nodes check for CaLiGraph took 33.14475154876709s
Security | Check HTTPS for CaLiGraph took 0.1365678310394287s
Interpretability | RDF structures check for CaLiGraph took 0.5333025455474854s
Versatility | Serialization formats check for CaLiGraph took 0.40727901458740234s
Availability | RDF dump link check for CaLiGraph took 0.24429059028625488s
License | MR license check for CaLiGraph took 0.47254061698913574s
License | HR license check for CaLiGraph took 60.286720752716064s
Amount of data | Number of property check for CaLiGraph took 0.2532172203063965s
Understandability | Number of label check for CaLiGraph took 3.3702940940856934s
Understandability | URI regex check for CaLiGraph took 0.5395290851593018s
Understandability | Vocabs check for CaLiGraph took 0.25397539138793945s
Verifiability | Authors check for CaLiGraph took 0.27434277534484863s
Verifiability | Publishers check for CaLiGraph took 0.24038338661193848s
Performance | Throughput check for CaLiGraph took 10.879779815673828s
Amount of data | Check the number of entities for CaLiGraph took 0.014915227890014648s
Verifiability | Contribs. check for CaLiGraph took 0.2592630386352539s
Interlinking | sameAs chians check for CaLiGraph took 2.0891077518463135s
Interlinking | skos check for CaLiGraph took 0.37238097190856934s
Interlinking | skos check for CaLiGraph took 0.21480417251586914s
Timeliness | dataset update frequency check for CaLiGraph took 0.29676246643066406s
Currency | Creation date check for CaLiGraph took 0.5235226154327393s
Currency | Modification date check for CaLiGraph took 0.4817228317260742s
Rep.Conc. | URIs length for CaLiGraph took 62.46007513999939s
Interoperability | New vocabularies check for CaLiGraph took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2473924160003662s
Accuracy | Check Functional Property for CaLiGraph took 0.2829709053039551s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.282604455947876s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6359193325042725s
Accuracy | Check White space in annotation for CaLiGraph took 0.026566028594970703s
Accuracy | Check Datatype consistency for CaLiGraph took 0.028865575790405273s
Consistency | Disjoint class check for CaLiGraph took 0.2359938621520996s
Consistency | Check Misplaced properties for CaLiGraph took 60.96373796463013s
Consistency | Misplaced classes for CaLiGraph took 0.4842832088470459s
Consistency | Check Ontology hijacking for CaLiGraph took 2.06913685798645s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.302548885345459s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.52173709869385s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03284955024719238s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.43503665924072266s
Security | Sign check for CaLiGraph took 0.40576958656311035s
Availability | Check URIs Dereferenciability for CaLiGraph took 6.445260763168335s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.8618834018707275s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02036309242248535s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.719329833984375e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 7.152557373046875e-06s
INFO | --- Analysis for CaLiGraph took 1800.3201251029968s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2518889904022217s
Availability | VoID file availability check for CaLiGraph took 0.0006349086761474609s
Extra | Recovery of all triples for CaLiGraph took 2.0973823070526123s
Performance | Total latancy measurement for CaLiGraph took 1.0366325378417969s
Amount of data | Number of triples check for CaLiGraph took 12.506998538970947s
Interoperability | New terms check for CaLiGraph took 1.9657068252563477s
Versatility | Languages check for CaLiGraph took 60.29543089866638s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2352759838104248s
Security | Check HTTPS for CaLiGraph took 0.12325835227966309s
Interpretability | RDF structures check for CaLiGraph took 0.2512960433959961s
Versatility | Serialization formats check for CaLiGraph took 0.26906704902648926s
Availability | RDF dump link check for CaLiGraph took 0.24312829971313477s
License | MR license check for CaLiGraph took 0.25380992889404297s
License | HR license check for CaLiGraph took 60.29931831359863s
Amount of data | Number of property check for CaLiGraph took 0.25202465057373047s
Understandability | Number of label check for CaLiGraph took 3.037163734436035s
Understandability | URI regex check for CaLiGraph took 0.48728132247924805s
Understandability | Vocabs check for CaLiGraph took 0.2362229824066162s
Verifiability | Authors check for CaLiGraph took 0.23174428939819336s
Verifiability | Publishers check for CaLiGraph took 0.2362363338470459s
Performance | Throughput check for CaLiGraph took 11.295117855072021s
Amount of data | Check the number of entities for CaLiGraph took 0.011220216751098633s
Verifiability | Contribs. check for CaLiGraph took 0.228163480758667s
Interlinking | sameAs chians check for CaLiGraph took 0.6153981685638428s
Interlinking | skos check for CaLiGraph took 0.25719261169433594s
Interlinking | skos check for CaLiGraph took 0.2151775360107422s
Timeliness | dataset update frequency check for CaLiGraph took 0.22167396545410156s
Currency | Creation date check for CaLiGraph took 0.47421717643737793s
Currency | Modification date check for CaLiGraph took 0.48389434814453125s
Rep.Conc. | URIs length for CaLiGraph took 62.48869037628174s
Interoperability | New vocabularies check for CaLiGraph took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.25536417961120605s
Accuracy | Check Functional Property for CaLiGraph took 0.22551274299621582s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2155153751373291s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5591411590576172s
Accuracy | Check White space in annotation for CaLiGraph took 0.026877641677856445s
Accuracy | Check Datatype consistency for CaLiGraph took 0.026860713958740234s
Consistency | Disjoint class check for CaLiGraph took 0.2450101375579834s
Consistency | Check Misplaced properties for CaLiGraph took 60.95060181617737s
Consistency | Misplaced classes for CaLiGraph took 0.44617700576782227s
Consistency | Check Ontology hijacking for CaLiGraph took 2.017070770263672s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2935445308685303s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.55892896652222s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03250598907470703s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.396773099899292s
Security | Sign check for CaLiGraph took 0.23572301864624023s
Availability | Check URIs Dereferenciability for CaLiGraph took 6.1509621143341064s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.36930251121520996s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.414817810058594e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 9.5367431640625e-06s
INFO | --- Analysis for caligraph took 1693.61665725708s
Availability | SPARQL endpoint availability check for can-link took 4.1961669921875e-05s
Availability | VoID file availability check for can-link took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for can-link took 0.7367804050445557s
Reputation | Calculation of the PageRank for can-link took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for can-link took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for can-link took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for can-link took 3.170967102050781e-05s
Believability | Calculation of trust value for can-link took 8.106231689453125e-06s
INFO | --- Analysis for can-link took 6.556053161621094s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.08071351051330566s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2855336666107178s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.02075362205505371s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 8.106231689453125e-06s
INFO | --- Analysis for cap-italy-rdf took 4.404699087142944s
Availability | SPARQL endpoint availability check for person took 4.2438507080078125e-05s
Availability | VoID file availability check for person took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for person took 0.27041149139404297s
Reputation | Calculation of the PageRank for person took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for person took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for person took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for person took 2.9087066650390625e-05s
Believability | Calculation of trust value for person took 7.867813110351562e-06s
INFO | --- Analysis for card took 2.37894344329834s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 7.939338684082031e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.29272007942199707s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.100799560546875e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 8.344650268554688e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.4080278873443604s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.029273986816406e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.27740955352783203s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.0994415283203125e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 7.62939453125e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.9554343223571777s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.6092574596405029s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.00026607513427734375s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 126.71775603294373s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9909873008728027s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.672021389007568s
Interoperability | New terms check for Norway catch records dataset @PSNC took 16.468333959579468s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.19583082199097s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 3.0991532802581787s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.25420665740966797s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 10.683681726455688s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.2808537483215332s
License | MR license check for Norway catch records dataset @PSNC took 0.6143472194671631s
License | HR license check for Norway catch records dataset @PSNC took 300.1970143318176s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.4554598331451416s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.991936445236206s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.8930327892303467s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.4508829116821289s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.20269107818603516s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.27104854583740234s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.335515975952148s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 4.00543212890625e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.2149505615234375s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.19978594779968262s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4346432685852051s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4493720531463623s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 7.010711908340454s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.503685712814331s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.22678184509277344s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 156.257563829422s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 1.2159347534179688e-05s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.1963787078857422s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.38925766944885254s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.3749370574951172s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 39.25652360916138s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.681363821029663s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.6023638248443604s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.19182896614074707s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 80.08783483505249s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.608668804168701s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 41.503788471221924s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.3385233879089355s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 101.95825219154358s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.736598014831543s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5832316875457764s
Security | Sign check for Norway catch records dataset @PSNC took 0.9755182266235352s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 6.03831672668457s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 1.4145317077636719s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.553794860839844e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2306.5402188301086s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.291534423828125e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.6862437725067139s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020798683166503906s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010180473327636719s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 7.3909759521484375e-06s
INFO | --- Analysis for ce4r took 6.838246822357178s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3977925777435303s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0002722740173339844s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.8975410461425781s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7083842754364014s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.27118563652038574s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6241838932037354s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.13012075424194s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16483449935913086s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2498478889465332s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1585676670074463s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15496134757995605s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24875426292419434s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2817065715789795s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1259140968322754s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26283764839172363s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.30661869049072266s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1376349925994873s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16994333267211914s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20195341110229492s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.91430950164795s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.176399230957031e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1946413516998291s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18178224563598633s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.33602046966552734s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14125299453735352s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22031760215759277s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.39421916007995605s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3398451805114746s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.248669147491455s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15645408630371094s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.1505897045135498s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.15759944915771484s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6345908641815186s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.027963876724243164s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.028173446655273438s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19811224937438965s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.263012409210205s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9973933696746826s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.2959880828857422s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.4901483058929443s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03375506401062012s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.17876100540161133s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15787124633789062s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 1733.5979900360107s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.3803434371948242s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 5.6743621826171875e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.049041748046875e-05s
INFO | --- Analysis for ceo took 1859.0536515712738s
Availability | SPARQL endpoint availability check for Charging Stations took 4.267692565917969e-05s
Availability | VoID file availability check for Charging Stations took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.2776477336883545s
Reputation | Calculation of the PageRank for Charging Stations took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.409385681152344e-05s
Believability | Calculation of trust value for Charging Stations took 8.58306884765625e-06s
INFO | --- Analysis for charging-stations took 4.304197549819946s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.172325134277344e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.26142263412475586s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.409385681152344e-05s
Believability | Calculation of trust value for Chat Game corpus took 8.821487426757812e-06s
INFO | --- Analysis for chat-game-corpus took 13.435335874557495s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 4.00543212890625e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.7085080146789551s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.3855438232421875e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 8.106231689453125e-06s
INFO | --- Analysis for chebi took 3.412505865097046s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 7.05718994140625e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008938312530517578s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.6980926990509033s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 6.29425048828125e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 7.62939453125e-06s
INFO | --- Analysis for chem2bio2rdf took 137.62263107299805s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.7693502902984619s
Availability | VoID file availability check for ChEMBL RDF took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.7118582725524902s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02034616470336914s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0008203983306884766s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.1021575927734375e-05s
Believability | Calculation of trust value for ChEMBL RDF took 7.62939453125e-06s
INFO | --- Analysis for chembl-rdf took 6.170003175735474s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.1247169971466064s
Availability | VoID file availability check for chemdb  dataset took 0.00027108192443847656s
Extra | Recovery of all triples for chemdb  dataset took 7.2300732135772705s
Performance | Total latancy measurement for chemdb  dataset took 2.5155344009399414s
Amount of data | Number of triples check for chemdb  dataset took 0.5338587760925293s
Interoperability | New terms check for chemdb  dataset took 1.8256418704986572s
Versatility | Languages check for chemdb  dataset took 0.5346148014068604s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5319409370422363s
Interpretability | RDF structures check for chemdb  dataset took 0.5411293506622314s
Versatility | Serialization formats check for chemdb  dataset took 0.5269484519958496s
Availability | RDF dump link check for chemdb  dataset took 0.48545241355895996s
License | MR license check for chemdb  dataset took 0.5045621395111084s
License | HR license check for chemdb  dataset took 0.49684953689575195s
Amount of data | Number of property check for chemdb  dataset took 0.5350427627563477s
Understandability | Number of label check for chemdb  dataset took 0.5292830467224121s
Understandability | URI regex check for chemdb  dataset took 0.9808320999145508s
Understandability | Vocabs check for chemdb  dataset took 0.5039222240447998s
Verifiability | Authors check for chemdb  dataset took 0.5008323192596436s
Verifiability | Publishers check for chemdb  dataset took 0.4953622817993164s
Performance | Throughput check for chemdb  dataset took 13.012516736984253s
Amount of data | Check the number of entities for chemdb  dataset took 7.605552673339844e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.5005950927734375s
Interlinking | sameAs chians check for chemdb  dataset took 0.5296204090118408s
Interlinking | skos check for chemdb  dataset took 0.48107218742370605s
Interlinking | skos check for chemdb  dataset took 0.5044543743133545s
Timeliness | dataset update frequency check for chemdb  dataset took 0.49999356269836426s
Currency | Creation date check for chemdb  dataset took 1.0319342613220215s
Currency | Modification date check for chemdb  dataset took 1.0309922695159912s
Rep.Conc. | URIs length for chemdb  dataset took 1.8495285511016846s
Interoperability | New vocabularies check for chemdb  dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5213165283203125s
Accuracy | Check Functional Property for chemdb  dataset took 0.5316262245178223s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.4803318977355957s
Accuracy | Check Empty annotation labels for chemdb  dataset took 0.5204083919525146s
Accuracy | Check White space in annotation for chemdb  dataset took 0.0002598762512207031s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03306698799133301s
Consistency | Disjoint class check for chemdb  dataset took 0.4926018714904785s
Consistency | Check Misplaced properties for chemdb  dataset took 1.018956184387207s
Consistency | Misplaced classes for chemdb  dataset took 0.5635383129119873s
Consistency | Check Ontology hijacking for chemdb  dataset took 2.0287885665893555s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.2591822147369385s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 1.7534899711608887s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.01911473274230957s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5296683311462402s
Security | Sign check for chemdb  dataset took 0.4872298240661621s
Availability | Check URIs Dereferenciability for chemdb  dataset took 515.6082501411438s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.8003883361816406s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 6.747245788574219e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb  dataset took 7.3909759521484375e-06s
INFO | --- Analysis for chemdb-basicInfo took 602.6346294879913s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.4956498146057129s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0002739429473876953s
Extra | Recovery of all triples for chemdb estimated properties dataset took 7.209874391555786s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.5051333904266357s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5289483070373535s
Interoperability | New terms check for chemdb estimated properties dataset took 1.816603422164917s
Versatility | Languages check for chemdb estimated properties dataset took 0.5341167449951172s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5275752544403076s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.526235818862915s
Versatility | Serialization formats check for chemdb estimated properties dataset took 0.515310525894165s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.5038840770721436s
License | MR license check for chemdb estimated properties dataset took 0.4843008518218994s
License | HR license check for chemdb estimated properties dataset took 0.49724268913269043s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5410749912261963s
Understandability | Number of label check for chemdb estimated properties dataset took 0.5416874885559082s
Understandability | URI regex check for chemdb estimated properties dataset took 1.0132508277893066s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.5010786056518555s
Verifiability | Authors check for chemdb estimated properties dataset took 0.49263477325439453s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.4914369583129883s
Performance | Throughput check for chemdb estimated properties dataset took 12.492052793502808s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 7.414817810058594e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.5006504058837891s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.5267937183380127s
Interlinking | skos check for chemdb estimated properties dataset took 0.4977843761444092s
Interlinking | skos check for chemdb estimated properties dataset took 0.5094223022460938s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.4898228645324707s
Currency | Creation date check for chemdb estimated properties dataset took 1.0388343334197998s
Currency | Modification date check for chemdb estimated properties dataset took 1.0336260795593262s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 1.8340480327606201s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.4898066520690918s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.5400204658508301s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.4900195598602295s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 0.5373926162719727s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.00031256675720214844s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03365683555603027s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.494915246963501s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.0350267887115479s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.5828604698181152s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 2.035943031311035s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.2555222511291504s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.754026174545288s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.019432544708251953s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5351037979125977s
Security | Sign check for chemdb estimated properties dataset took 0.48178911209106445s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 369.71313548088074s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.7687106132507324s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.021049976348876953s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.1205673217773438e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 455.49959325790405s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5001993179321289s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0002815723419189453s
Extra | Recovery of all triples for chemdb phase transition dataset took 7.218328237533569s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.5137908458709717s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5273864269256592s
Interoperability | New terms check for chemdb phase transition dataset took 1.7864878177642822s
Versatility | Languages check for chemdb phase transition dataset took 0.5287790298461914s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5406451225280762s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.542809009552002s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.5280368328094482s
Availability | RDF dump link check for chemdb phase transition dataset took 0.490217924118042s
License | MR license check for chemdb phase transition dataset took 0.498699426651001s
License | HR license check for chemdb phase transition dataset took 0.496701717376709s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5352506637573242s
Understandability | Number of label check for chemdb phase transition dataset took 0.5298624038696289s
Understandability | URI regex check for chemdb phase transition dataset took 1.000124454498291s
Understandability | Vocabs check for chemdb phase transition dataset took 0.5013401508331299s
Verifiability | Authors check for chemdb phase transition dataset took 0.48499584197998047s
Verifiability | Publishers check for chemdb phase transition dataset took 0.5004594326019287s
Performance | Throughput check for chemdb phase transition dataset took 12.477052211761475s
Amount of data | Check the number of entities for chemdb phase transition dataset took 7.462501525878906e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.5007903575897217s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.5308868885040283s
Interlinking | skos check for chemdb phase transition dataset took 0.5012166500091553s
Interlinking | skos check for chemdb phase transition dataset took 0.4989132881164551s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.49654269218444824s
Currency | Creation date check for chemdb phase transition dataset took 1.032656192779541s
Currency | Modification date check for chemdb phase transition dataset took 1.0173609256744385s
Rep.Conc. | URIs length for chemdb phase transition dataset took 1.8202710151672363s
Interoperability | New vocabularies check for chemdb phase transition dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.4881594181060791s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.5115501880645752s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.49046897888183594s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 0.5361711978912354s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.0003108978271484375s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.04338693618774414s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.502446174621582s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.0412864685058594s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.5761582851409912s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 2.052595376968384s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.2761733531951904s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 1.781273603439331s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.02208113670349121s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.535165548324585s
Security | Sign check for chemdb phase transition dataset took 0.49900031089782715s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 273.78610706329346s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.3423898220062256s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.696846008300781e-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 7.62939453125e-06s
INFO | --- Analysis for chemdb-phaseTransition took 358.83113169670105s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5029733180999756s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0002598762512207031s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 7.135480642318726s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.5352582931518555s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5346882343292236s
Interoperability | New terms check for chemdb thermochemistry dataset took 1.8633408546447754s
Versatility | Languages check for chemdb thermochemistry dataset took 0.5358438491821289s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5284438133239746s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.525130033493042s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.5268845558166504s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.4853651523590088s
License | MR license check for chemdb thermochemistry dataset took 0.48540210723876953s
License | HR license check for chemdb thermochemistry dataset took 0.503056526184082s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5278458595275879s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.5326263904571533s
Understandability | URI regex check for chemdb thermochemistry dataset took 0.9851112365722656s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.5016613006591797s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.50138258934021s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.49907636642456055s
Performance | Throughput check for chemdb thermochemistry dataset took 13.457635879516602s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 0.00011754035949707031s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.5042874813079834s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.5308589935302734s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5003142356872559s
Interlinking | skos check for chemdb thermochemistry dataset took 0.48561882972717285s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.49764156341552734s
Currency | Creation date check for chemdb thermochemistry dataset took 1.0293114185333252s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0346667766571045s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 1.828629493713379s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.49098682403564453s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.5313515663146973s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.4985063076019287s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 0.5402894020080566s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.00030684471130371094s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03868913650512695s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.4958188533782959s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.00868558883667s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.5807714462280273s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 2.0712296962738037s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.3049232959747314s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 1.8150606155395508s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.0250091552734375s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5437018871307373s
Security | Sign check for chemdb thermochemistry dataset took 0.48502492904663086s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 247.8349130153656s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 1.5559289455413818s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.628036499023438e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 8.58306884765625e-06s
INFO | --- Analysis for chemdb-thermochemistry took 335.1097445487976s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.363059997558594e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.25840282440185547s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for ChemPedia RDF took 7.867813110351562e-06s
INFO | --- Analysis for chempedia-rdf took 9.242135524749756s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.3392181396484375e-05s
Availability | VoID file availability check for Chiman Maru took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.2916679382324219s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020648717880249023s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.0279159545898438e-05s
Believability | Calculation of trust value for Chiman Maru took 7.3909759521484375e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 3.662132978439331s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.0523192882538s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 1.2029764652252197s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.023936748504638672s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.886222839355469e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 8.344650268554688e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 802.6202569007874s
Availability | SPARQL endpoint availability check for Chronicling America took 4.2438507080078125e-05s
Availability | VoID file availability check for Chronicling America took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.7278347015380859s
Reputation | Calculation of the PageRank for Chronicling America took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010943412780761719s
Believability | Calculation of trust value for Chronicling America took 7.3909759521484375e-06s
INFO | --- Analysis for chronicling-america took 8.607497453689575s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.7080366611480713s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006546974182128906s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 117.8849949836731s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.650296926498413s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.8945672512054443s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.2162415981292725s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.948096752166748s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.654761791229248s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3348069190979004s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.31501317024230957s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 10.063290119171143s
License | MR license check for Cultural Heritage Thesaurus took 0.33754420280456543s
License | HR license check for Cultural Heritage Thesaurus took 0.3991429805755615s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.3427436351776123s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.4080393314361572s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.6861057281494141s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.3055870532989502s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.3245222568511963s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.274458646774292s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.84160327911377s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.605552673339844e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.3106868267059326s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.29189038276672363s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.32053542137145996s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3302161693572998s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.368211030960083s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6170790195465088s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6250355243682861s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 13.420900106430054s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.303638219833374s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.32799696922302246s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.3097221851348877s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 3.609349489212036s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.2243807315826416s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3323523998260498s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.110701084136963s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.3047966957092285s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.837291717529297s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.0209522247314453s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.033635616302490234s
Security | Sign check for Cultural Heritage Thesaurus took 0.33941149711608887s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 259.69395327568054s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 1.3295996189117432s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.16761517524719238s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0014297962188720703s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.0001125335693359375s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for cht took 473.84993052482605s
Availability | SPARQL endpoint availability check for ciard-ring took 9.942054748535156e-05s
Availability | VoID file availability check for ciard-ring took 0.00734710693359375s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.6823647022247314s
Reputation | Calculation of the PageRank for ciard-ring took 0.10877752304077148s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0008795261383056641s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.863739013671875e-05s
Believability | Calculation of trust value for ciard-ring took 7.3909759521484375e-06s
INFO | --- Analysis for ciard-ring took 5.852559566497803s
Availability | SPARQL endpoint availability check for Cine Figure took 4.3392181396484375e-05s
Availability | VoID file availability check for Cine Figure took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.29078054428100586s
Reputation | Calculation of the PageRank for Cine Figure took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.482269287109375e-05s
Believability | Calculation of trust value for Cine Figure took 7.62939453125e-06s
INFO | --- Analysis for Cine_Figure took 4.218066930770874s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 21.2155864238739s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0008447170257568359s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.27028918266296387s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.02086472511291504s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.9114227294921875e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 175.00438499450684s
Availability | SPARQL endpoint availability check for CIPFA took 4.220008850097656e-05s
Availability | VoID file availability check for CIPFA took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for CIPFA took 0.7184758186340332s
Reputation | Calculation of the PageRank for CIPFA took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.52587890625e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.00107574462890625s
Interlinking | Calculation of Clustering coefficient for CIPFA took 4.315376281738281e-05s
Believability | Calculation of trust value for CIPFA took 5.7220458984375e-06s
INFO | --- Analysis for cipfa took 4.688520669937134s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.05340933799744s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.7298469543457031s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.021099328994750977s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0003979206085205078s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 8.344650268554688e-06s
INFO | --- Analysis for ckan took 264.23487877845764s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.4881293773651123s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.2792689800262451s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020607471466064453s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for CLaSSES took 5.211779832839966s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.172325134277344e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2769181728363037s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.147125244140625e-05s
Believability | Calculation of trust value for Temples of the Classical World took 6.4373016357421875e-06s
INFO | --- Analysis for classical_temples took 3.7333126068115234s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.9844317436218262s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.7002692222595215s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.02027297019958496s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.535385131835938e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 5.245208740234375e-06s
INFO | --- Analysis for clean-energy-data-reegle took 9.834255456924438s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.28104639053344727s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 8.559226989746094e-05s
Believability | Calculation of trust value for CLLD-afbo took 7.867813110351562e-06s
INFO | --- Analysis for clld-afbo took 4.387777805328369s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.506111145019531e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.2731959819793701s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.62939453125e-05s
Believability | Calculation of trust value for CLLD-APICS took 6.198883056640625e-06s
INFO | --- Analysis for clld-apics took 3.6413562297821045s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 9.179115295410156e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.26615238189697266s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.886222839355469e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 6.9141387939453125e-06s
INFO | --- Analysis for clld-ewave took 3.653174877166748s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.1484832763671875e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.26059770584106445s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.751319885253906e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 5.9604644775390625e-06s
INFO | --- Analysis for clld-glottolog took 3.882826566696167s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.220008850097656e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.2897942066192627s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.130073547363281e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 6.4373016357421875e-06s
INFO | --- Analysis for clld-phoible took 3.4725396633148193s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.2970719337463379s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.177757263183594e-05s
Believability | Calculation of trust value for CLLD-SAILS took 7.867813110351562e-06s
INFO | --- Analysis for clld-sails took 3.6033527851104736s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-WALS took 0.000324249267578125s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.24567008018493652s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 0.00018858909606933594s
Believability | Calculation of trust value for CLLD-WALS took 6.9141387939453125e-06s
INFO | --- Analysis for clld-wals took 3.6363325119018555s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.2438507080078125e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.25875258445739746s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.891654968261719e-05s
Believability | Calculation of trust value for CLLD-WOLD took 6.9141387939453125e-06s
INFO | --- Analysis for clld-wold took 3.566795825958252s
Availability | SPARQL endpoint availability check for COD inventory took 4.100799560546875e-05s
Availability | VoID file availability check for COD inventory took 0.0002167224884033203s
Completeness | Calculation of interlinking completeness for COD inventory took 0.25713181495666504s
Reputation | Calculation of the PageRank for COD inventory took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.147125244140625e-05s
Believability | Calculation of trust value for COD inventory took 6.9141387939453125e-06s
INFO | --- Analysis for cod-inventory took 2.8954317569732666s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.13140606880187988s
Availability | VoID file availability check for Cooperation Databank took 0.00034236907958984375s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.26373982429504395s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.814697265625e-05s
Believability | Calculation of trust value for Cooperation Databank took 5.7220458984375e-06s
INFO | --- Analysis for CoDa took 2.582911729812622s
Availability | SPARQL endpoint availability check for CODE Endpoint took 6.699562072753906e-05s
Availability | VoID file availability check for CODE Endpoint took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.278134822845459s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.170967102050781e-05s
Believability | Calculation of trust value for CODE Endpoint took 7.867813110351562e-06s
INFO | --- Analysis for code-endpoint took 2.9622926712036133s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.7346820831298828s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.2737908363342285s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.1948089599609375e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 4.76837158203125e-06s
INFO | --- Analysis for coins-openuplabs took 3.159571409225464s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.4299161434173584s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.00031065940856933594s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.26872944831848145s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.225440979003906e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 7.152557373046875e-06s
INFO | --- Analysis for CoLChina_sp2000 took 7.2848687171936035s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.04797673225402832s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.28525876998901367s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.933906555175781e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for colinda took 2.580533504486084s
Availability | SPARQL endpoint availability check for CN  2012 took 31.792988300323486s
Availability | VoID file availability check for CN  2012 took 0.0008862018585205078s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.32738280296325684s
Reputation | Calculation of the PageRank for CN  2012 took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for CN  2012 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.4332275390625e-05s
Believability | Calculation of trust value for CN  2012 took 5.245208740234375e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 161.02537894248962s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.0531158447265625e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.27242207527160645s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.075599670410156e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 6.198883056640625e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 3.814892053604126s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.0531158447265625e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.3173253536224365s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.170967102050781e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 7.152557373046875e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 3.893070697784424s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.220008850097656e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.27724552154541016s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.170967102050781e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 6.198883056640625e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.9754958152770996s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.1484832763671875e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.28783655166625977s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.02075338363647461s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.9325485229492188e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 6.198883056640625e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.9850401878356934s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 5.602836608886719e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.2664494514465332s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.0279159545898438e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 7.867813110351562e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.92305850982666s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.34772205352783203s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006544589996337891s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.29738759994506836s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.021027088165283203s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.001077890396118164s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 4.649162292480469e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for CompHistSem took 4.0534281730651855s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 21.954107522964478s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.7338390350341797s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02061295509338379s
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.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.076957702636719e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.3589859008789062e-05s
INFO | --- Analysis for comsode-d3-2 took 118.46046113967896s
Availability | SPARQL endpoint availability check for ConceptNet took 4.076957702636719e-05s
Availability | VoID file availability check for ConceptNet took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.2737405300140381s
Reputation | Calculation of the PageRank for ConceptNet took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for ConceptNet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.9087066650390625e-05s
Believability | Calculation of trust value for ConceptNet took 7.3909759521484375e-06s
INFO | --- Analysis for conceptnet took 3.260075807571411s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 7.176399230957031e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0003876686096191406s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2875039577484131s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.02019357681274414s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.130073547363281e-05s
Believability | Calculation of trust value for 2011 US Congress People took 4.76837158203125e-06s
INFO | --- Analysis for congresspeople took 4.301297664642334s
Availability | SPARQL endpoint availability check for MIMO took 0.313934326171875s
Availability | VoID file availability check for MIMO took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for MIMO took 0.27205848693847656s
Reputation | Calculation of the PageRank for MIMO took 0.02081918716430664s
Interlinking | Calculation of Degree of Connection for MIMO took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.1920928955078125e-05s
Believability | Calculation of trust value for MIMO took 7.3909759521484375e-06s
INFO | --- Analysis for CONNECTED took 3.846588611602783s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.2747011184692383s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.123283386230469e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.8882663249969482s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.1961669921875e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.2693774700164795s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.1948089599609375e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 6.9141387939453125e-06s
INFO | --- Analysis for copac-library-catalogue took 2.98093318939209s
Availability | SPARQL endpoint availability check for Copyright Free Music took 6.29425048828125e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.27565860748291016s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.314018249511719e-05s
Believability | Calculation of trust value for Copyright Free Music took 5.7220458984375e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.108292579650879s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.029273986816406e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.33584070205688477s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.390975952148438e-05s
Believability | Calculation of trust value for CopyrightTermBank took 6.9141387939453125e-06s
INFO | --- Analysis for copyrighttermbank took 34.20059013366699s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.235003709793091s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.29849886894226074s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.0204775333404541s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.814697265625e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 7.3909759521484375e-06s
INFO | --- Analysis for core took 7.168478965759277s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.49187660217285156s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0002543926239013672s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 127.52379751205444s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9850442409515381s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 8.784865617752075s
Interoperability | New terms check for Corine linked dataset @PSNC took 16.300975561141968s
Versatility | Languages check for Corine linked dataset @PSNC took 300.1783170700073s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.7799017429351807s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.22533702850341797s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 11.239705562591553s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.2912867069244385s
License | MR license check for Corine linked dataset @PSNC took 0.5031144618988037s
License | HR license check for Corine linked dataset @PSNC took 300.2462842464447s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.30672264099121094s
Understandability | Number of label check for Corine linked dataset @PSNC took 3.05253267288208s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.8937795162200928s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.43959808349609375s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.18899822235107422s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.26035428047180176s
Performance | Throughput check for Corine linked dataset @PSNC took 11.495996236801147s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.891654968261719e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.17990565299987793s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.19724798202514648s
Interlinking | skos check for Corine linked dataset @PSNC took 0.5297887325286865s
Interlinking | skos check for Corine linked dataset @PSNC took 0.46874308586120605s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 6.3054540157318115s
Currency | Creation date check for Corine linked dataset @PSNC took 0.5084750652313232s
Currency | Modification date check for Corine linked dataset @PSNC took 0.21644020080566406s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 159.1000030040741s
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.1811823844909668s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.3433876037597656s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.32287120819091797s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 47.109182357788086s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.69934344291687s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.600144147872925s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.19438505172729492s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 81.14417886734009s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.505148887634277s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 35.4258975982666s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.3784770965576172s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 93.55299234390259s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.8041062355041504s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.5140843391418457s
Security | Sign check for Corine linked dataset @PSNC took 0.8983182907104492s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 18.617742776870728s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 1.6021432876586914s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021126985549926758s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.266334533691406e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 4.5299530029296875e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 7.62939453125e-06s
INFO | --- Analysis for Corine_linked_dataset took 2312.9440405368805s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.57763671875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.7767593860626221s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 2.9325485229492188e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 7.3909759521484375e-06s
INFO | --- Analysis for corn took 5.020570278167725s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 5.1975250244140625e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.7197494506835938s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 2.8848648071289062e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 7.152557373046875e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 4.617091178894043s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 5.221366882324219e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.2712860107421875s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.9325485229492188e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 8.106231689453125e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 4.157041311264038s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.1484832763671875e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0007464885711669922s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.24784255027770996s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.888938903808594e-05s
Believability | Calculation of trust value for Cornetto1.2 took 8.106231689453125e-06s
INFO | --- Analysis for cornetto took 107.66729187965393s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.17443609237670898s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005161762237548828s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 587.5688536167145s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5801403522491455s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 92.0597517490387s
Interoperability | New terms check for Corporate Body Named Authority List  took 108.82251310348511s
Versatility | Languages check for Corporate Body Named Authority List  took 300.09866762161255s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 5.810429811477661s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.3330497741699219s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.49112558364868164s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 17.9534969329834s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.2647571563720703s
License | MR license check for Corporate Body Named Authority List  took 0.24884891510009766s
License | HR license check for Corporate Body Named Authority List  took 300.0477569103241s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.22585272789001465s
Understandability | Number of label check for Corporate Body Named Authority List  took 5.554967880249023s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.26609206199645996s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.11608314514160156s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.27892494201660156s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.2647686004638672s
Performance | Throughput check for Corporate Body Named Authority List  took 10.581921815872192s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 3.147125244140625e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.14221787452697754s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 11.196377754211426s
Interlinking | skos check for Corporate Body Named Authority List  took 0.4658656120300293s
Interlinking | skos check for Corporate Body Named Authority List  took 0.47830939292907715s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.30585217475891113s
Currency | Creation date check for Corporate Body Named Authority List  took 0.585700273513794s
Currency | Modification date check for Corporate Body Named Authority List  took 0.27043700218200684s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 597.4478724002838s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.18616008758544922s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.16130828857421875s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.13655424118041992s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 100.658456325531s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.1802127361297607s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.645573377609253s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.20213937759399414s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.7372536659241s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.841288566589355s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 118.36796879768372s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.5259661674499512s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.493421792984s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.0230677127838135s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.8543756008148193s
Security | Sign check for Corporate Body Named Authority List  took 0.1609947681427002s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 4.089400291442871s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.596813678741455s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.53131103515625e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.430511474609375e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 9.298324584960938e-06s
INFO | --- Analysis for corporate-body took 15856.228325366974s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.5159733295440674s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.27207183837890625s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020478487014770508s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.528594970703125e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for CorpusFibonacci took 5.775439023971558s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.0531158447265625e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.24884271621704102s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for corscheck took 4.1930646896362305s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.14516115188598633s
Availability | VoID file availability check for Country Name Authority List took 0.0007505416870117188s
Extra | Recovery of all triples for Country Name Authority List took 579.760383605957s
Performance | Total latancy measurement for Country Name Authority List took 0.6102440357208252s
Amount of data | Number of triples check for Country Name Authority List took 103.05626201629639s
Interoperability | New terms check for Country Name Authority List took 110.77769541740417s
Versatility | Languages check for Country Name Authority List took 300.14250230789185s
Interpretability | Number of blank nodes check for Country Name Authority List took 1.539867877960205s
Security | Check HTTPS for Country Name Authority List took 0.21352815628051758s
Interpretability | RDF structures check for Country Name Authority List took 0.31065917015075684s
Versatility | Serialization formats check for Country Name Authority List took 16.823809146881104s
Availability | RDF dump link check for Country Name Authority List took 0.21063637733459473s
License | MR license check for Country Name Authority List took 0.16602659225463867s
License | HR license check for Country Name Authority List took 300.04932260513306s
Amount of data | Number of property check for Country Name Authority List took 0.21929001808166504s
Understandability | Number of label check for Country Name Authority List took 5.762278318405151s
Understandability | URI regex check for Country Name Authority List took 0.2521390914916992s
Understandability | Vocabs check for Country Name Authority List took 0.10745668411254883s
Verifiability | Authors check for Country Name Authority List took 0.11764645576477051s
Verifiability | Publishers check for Country Name Authority List took 0.16713476181030273s
Performance | Throughput check for Country Name Authority List took 10.451618671417236s
Amount of data | Check the number of entities for Country Name Authority List took 7.867813110351562e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.17324376106262207s
Interlinking | sameAs chians check for Country Name Authority List took 8.266895771026611s
Interlinking | skos check for Country Name Authority List took 0.2797060012817383s
Interlinking | skos check for Country Name Authority List took 0.26145410537719727s
Timeliness | dataset update frequency check for Country Name Authority List took 0.24886202812194824s
Currency | Creation date check for Country Name Authority List took 0.4828205108642578s
Currency | Modification date check for Country Name Authority List took 0.22596526145935059s
Rep.Conc. | URIs length for Country Name Authority List took 572.4518451690674s
Interoperability | New vocabularies check for Country Name Authority List took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.1972951889038086s
Accuracy | Check Functional Property for Country Name Authority List took 0.17377018928527832s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.14238619804382324s
Accuracy | Check Empty annotation labels for Country Name Authority List took 120.25157570838928s
Accuracy | Check White space in annotation for Country Name Authority List took 3.121975898742676s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6261754035949707s
Consistency | Disjoint class check for Country Name Authority List took 0.1749880313873291s
Consistency | Check Misplaced properties for Country Name Authority List took 300.86550641059875s
Consistency | Misplaced classes for Country Name Authority List took 8.746706485748291s
Consistency | Check Ontology hijacking for Country Name Authority List took 141.27539920806885s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.4928479194641113s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.53089356422424s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.0178020000457764s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.7001399993896484s
Security | Sign check for Country Name Authority List took 0.16509199142456055s
Availability | Check URIs Dereferenciability for Country Name Authority List took 4.037012577056885s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.1563808917999268s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.02071547508239746s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.841255187988281e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 4.291534423828125e-06s
Believability | Calculation of trust value for Country Name Authority List took 8.106231689453125e-06s
INFO | --- Analysis for country-authority-list took 15882.93053817749s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.1523723602294922s
Availability | VoID file availability check for Courts thesaurus took 0.00020956993103027344s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.270160436630249s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.461143493652344e-05s
Believability | Calculation of trust value for Courts thesaurus took 7.62939453125e-06s
INFO | --- Analysis for courts-thesaurus took 3.107652187347412s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.530335187911987s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.7089695930480957s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.724761962890625e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 7.62939453125e-06s
INFO | --- Analysis for Covid-on-the-Web took 58.137288093566895s
Availability | SPARQL endpoint availability check for CPA 2008 took 28.609467267990112s
Availability | VoID file availability check for CPA 2008 took 0.0009245872497558594s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.7135517597198486s
Reputation | Calculation of the PageRank for CPA 2008 took 0.027089595794677734s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 3.528594970703125e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.001367330551147461s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 6.127357482910156e-05s
Believability | Calculation of trust value for CPA 2008 took 5.4836273193359375e-06s
INFO | --- Analysis for cpa-2008 took 126.97165942192078s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.39526891708374023s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005900859832763672s
Extra | Recovery of all triples for Cooperative Patent Classification took 81.68699526786804s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.9613289833068848s
Amount of data | Number of triples check for Cooperative Patent Classification took 91.53781151771545s
Versatility | Languages check for Cooperative Patent Classification took 120.16103029251099s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.29574632644653s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.40296220779418945s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.3166830539703369s
Availability | RDF dump link check for Cooperative Patent Classification took 0.3313283920288086s
License | MR license check for Cooperative Patent Classification took 0.2956058979034424s
License | HR license check for Cooperative Patent Classification took 90.23286652565002s
Amount of data | Number of property check for Cooperative Patent Classification took 5.569939613342285s
Understandability | Number of label check for Cooperative Patent Classification took 92.09826731681824s
Understandability | URI regex check for Cooperative Patent Classification took 0.9247772693634033s
Understandability | Vocabs check for Cooperative Patent Classification took 0.26841235160827637s
Verifiability | Authors check for Cooperative Patent Classification took 0.2451038360595703s
Verifiability | Publishers check for Cooperative Patent Classification took 0.42217040061950684s
Performance | Throughput check for Cooperative Patent Classification took 31.845341682434082s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.271766662597656e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.25476765632629395s
Interlinking | sameAs chians check for Cooperative Patent Classification took 1.114842414855957s
Interlinking | skos check for Cooperative Patent Classification took 0.34870290756225586s
Interlinking | skos check for Cooperative Patent Classification took 0.28783249855041504s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.37009572982788086s
Currency | Creation date check for Cooperative Patent Classification took 8.576656341552734s
Currency | Modification date check for Cooperative Patent Classification took 0.49922704696655273s
Rep.Conc. | URIs length for Cooperative Patent Classification took 192.8291003704071s
Interoperability | New vocabularies check for Cooperative Patent Classification took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 3.494506359100342s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 48.00823903083801s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9706947803497314s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.831516742706299s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.9652001857757568s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 121.02951860427856s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 30.74045443534851s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.6266276836395264s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.55289149284363s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.8698301315307617s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.63238525390625s
Security | Sign check for Cooperative Patent Classification took 0.26723647117614746s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 2.9800198078155518s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 1.067870855331421s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02123117446899414s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 2.1457672119140625e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 8.58306884765625e-06s
INFO | --- Analysis for CPC took 1486.6907272338867s
Availability | SPARQL endpoint availability check for CPC 2008 took 44.02983641624451s
Availability | VoID file availability check for CPC 2008 took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.7532393932342529s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.649162292480469e-05s
Believability | Calculation of trust value for CPC 2008 took 5.245208740234375e-06s
INFO | --- Analysis for cpc-2008 took 188.79906821250916s
Availability | SPARQL endpoint availability check for CPV  2003 took 21.04512310028076s
Availability | VoID file availability check for CPV  2003 took 0.0008444786071777344s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.29469990730285645s
Reputation | Calculation of the PageRank for CPV  2003 took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.291534423828125e-05s
Believability | Calculation of trust value for CPV  2003 took 6.9141387939453125e-06s
INFO | --- Analysis for cpv-2003 took 153.16944074630737s
Availability | SPARQL endpoint availability check for CPV 2008 took 39.71674656867981s
Availability | VoID file availability check for CPV 2008 took 0.013416051864624023s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.7215001583099365s
Reputation | Calculation of the PageRank for CPV 2008 took 0.05129861831665039s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.2928924560546875e-05s
Believability | Calculation of trust value for CPV 2008 took 5.7220458984375e-06s
INFO | --- Analysis for cpv-2008 took 168.52965450286865s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.24752712249756s
Availability | VoID file availability check for crowdsourcing-fb took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.698047399520874s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.2509126663208008s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0012688636779785156s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 5.435943603515625e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 7.62939453125e-06s
INFO | --- Analysis for crowdsourcing-fb took 538.7131009101868s
Availability | SPARQL endpoint availability check for CRTM took 4.172325134277344e-05s
Availability | VoID file availability check for CRTM took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for CRTM took 0.746002197265625s
Reputation | Calculation of the PageRank for CRTM took 0.050521135330200195s
Interlinking | Calculation of Degree of Connection for CRTM took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.075599670410156e-05s
Believability | Calculation of trust value for CRTM took 7.3909759521484375e-06s
INFO | --- Analysis for crtm took 5.892760753631592s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.2438507080078125e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.274686336517334s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.037928104400634766s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0018520355224609375s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 6.270408630371094e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 6.9141387939453125e-06s
INFO | --- Analysis for crystal-eye took 3.7944998741149902s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 7.166466236114502s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.2742581367492676s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.08003354072570801s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 2.288818359375e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0016918182373046875s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 8.702278137207031e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 1.0251998901367188e-05s
INFO | --- Analysis for ctic-public-dataset took 44.34351181983948s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.00543212890625e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0004105567932128906s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.2475132942199707s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.04437708854675293s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.0994415283203125e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 8.106231689453125e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 3.467352867126465s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 11.11364197731018s
Availability | VoID file availability check for CulturaLinkedData took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.2761969566345215s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.026528596878051758s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.001416921615600586s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 4.124641418457031e-05s
Believability | Calculation of trust value for CulturaLinkedData took 7.3909759521484375e-06s
INFO | --- Analysis for culturalinkeddata took 24.308830976486206s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 30.581530332565308s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2717931270599365s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.035454511642456055s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.3392181396484375e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ares-or took 105.59238409996033s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 30.121578216552734s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0010135173797607422s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.7221026420593262s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020246267318725586s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.838539123535156e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ares-rzp took 104.35363364219666s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 30.139677047729492s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.26624393463134766s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.021327495574951172s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 4.220008850097656e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 5.7220458984375e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 134.43878602981567s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 30.028159856796265s
Availability | VoID file availability check for Integrated pollution registry took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.7148373126983643s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.03730607032775879s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.814697265625e-05s
Believability | Calculation of trust value for Integrated pollution registry took 5.9604644775390625e-06s
INFO | --- Analysis for cz-cenia-pollution took 124.67486929893494s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 30.07714867591858s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.27373480796813965s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02092146873474121s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.814697265625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 5.7220458984375e-06s
INFO | --- Analysis for cz-contracts took 104.54573798179626s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 3.9577484130859375e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.272383451461792s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 2.7894973754882812e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-courts took 4.900315046310425s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 30.065511226654053s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.6912474632263184s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.021326065063476562s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0008101463317871094s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.933906555175781e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-bans took 108.15079951286316s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 30.073287963867188s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0010807514190673828s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.28204774856567383s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.0341646671295166s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 2.8848648071289062e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0016281604766845703s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 6.628036499023438e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ctia-confiscations took 103.87562227249146s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 30.011990308761597s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.8163957595825195s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.02206277847290039s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0009186267852783203s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 4.172325134277344e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 5.9604644775390625e-06s
INFO | --- Analysis for cz-ctia-focus took 105.38722157478333s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 30.113311052322388s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0007660388946533203s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.7206900119781494s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.039020538330078125s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0010673999786376953s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.935264587402344e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ctia-inspections took 104.03728723526001s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 30.238754987716675s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.7036542892456055s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.02153325080871582s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 4.172325134277344e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 5.7220458984375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 105.85316896438599s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 20.298454999923706s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.36750054359436035s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020877361297607422s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0017087459564208984s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 7.843971252441406e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 5.245208740234375e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 94.13087034225464s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 20.100610494613647s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.7205984592437744s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.03887367248535156s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 5.364418029785156e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 5.245208740234375e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 95.02983260154724s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 21.17617702484131s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2653999328613281s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.030721664428710938s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-average-salaries took 95.22588062286377s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 20.523683547973633s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.6826362609863281s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.03673434257507324s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0008559226989746094s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.6253204345703125e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 94.97835111618042s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 20.430066108703613s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.6848564147949219s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.023530006408691406s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0008130073547363281s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.981590270996094e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 94.86826348304749s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 20.415782690048218s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.25583696365356445s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.1961669921875e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-czso-job-applicants took 94.55413889884949s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 20.431050062179565s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.6977627277374268s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.410743713378906e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 94.67801547050476s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 20.40316081047058s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.26231980323791504s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 4.100799560546875e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-regions took 93.47138857841492s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 20.36402416229248s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.698033332824707s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.363059997558594e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 96.15379977226257s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 20.491445064544678s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2566070556640625s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02250814437866211s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.410743713378906e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 94.53563380241394s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 20.459710597991943s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.750779390335083s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.695487976074219e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 94.76625728607178s
Availability | SPARQL endpoint availability check for ATC groups took 30.147351026535034s
Availability | VoID file availability check for ATC groups took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for ATC groups took 0.7029581069946289s
Reputation | Calculation of the PageRank for ATC groups took 0.021074533462524414s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.009506225585938e-05s
Believability | Calculation of trust value for ATC groups took 7.867813110351562e-06s
INFO | --- Analysis for cz-eh-1-atc took 103.86206412315369s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 30.022241830825806s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0008027553558349609s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2996847629547119s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.3855438232421875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.245208740234375e-06s
INFO | --- Analysis for cz-fulfillments took 103.97019839286804s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.04383111000061035s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0007636547088623047s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.3694636821746826s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.02107691764831543s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.553794860839844e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 5.245208740234375e-06s
INFO | --- Analysis for cz-ic took 23.986821174621582s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 20.013625860214233s
Availability | VoID file availability check for List of Czech data boxes took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.3034398555755615s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.05308389663696289s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 3.0279159545898438e-05s
Believability | Calculation of trust value for List of Czech data boxes took 4.76837158203125e-06s
INFO | --- Analysis for cz-list-of-databoxes took 94.34226512908936s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 20.038597106933594s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.28409481048583984s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.060109615325927734s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.4836273193359375e-06s
INFO | --- Analysis for cz-nace took 95.05014896392822s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5150346755981445s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0006020069122314453s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 173.15732765197754s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8141844272613525s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4047434329986572s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.2848665714263916s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 82.10925221443176s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.48352622985839844s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2579231262207031s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.750430107116699s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2935760021209717s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3899686336517334s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5500380992889404s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17606902122497559s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5047092437744141s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3732278347015381s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16364383697509766s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.21170496940612793s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2981550693511963s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.64137077331543s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.58306884765625e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16096973419189453s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.21985721588134766s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.33672261238098145s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17094945907592773s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.876605272293091s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.41618871688842773s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.36433887481689453s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 62.80838418006897s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.14969944953918457s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18947815895080566s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1696927547454834s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 40.65874743461609s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.3861711025238037s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6906752586364746s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18164539337158203s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.2371153831481934s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.129920482635498s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 72.49645066261292s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7527308464050293s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.5250420570373535s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.544332981109619s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24740266799926758s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3941373825073242s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 941.5930833816528s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6607239246368408s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.022133827209472656s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.5762786865234375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.0067901611328125e-06s
INFO | --- Analysis for cz-nkod took 69342.11135554314s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 30.157735347747803s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.001173257827758789s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.6905014514923096s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.02085137367248535s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.552436828613281e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 6.4373016357421875e-06s
INFO | --- Analysis for cz-orders took 104.86062788963318s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 20.03734588623047s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.7103922367095947s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 4.124641418457031e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ovm took 95.35114765167236s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 30.034706592559814s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.7734153270721436s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.886222839355469e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-ovm-agendas took 104.4498393535614s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.36678433418273926s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2761528491973877s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.020395517349243164s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.604194641113281e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-ruian took 6.325037002563477s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 20.701712369918823s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7113792896270752s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 8.153915405273438e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 95.37070870399475s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 20.32880687713623s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.3795602321624756s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.600120544433594e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 6.198883056640625e-06s
INFO | --- Analysis for cz-sao-check-actions took 96.16750812530518s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 20.36281108856201s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.7070822715759277s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.02044391632080078s
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.0007748603820800781s
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 4.0531158447265625e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 94.67135310173035s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 30.155925035476685s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.2890326976776123s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020635366439819336s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.0040740966796875e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 103.17070889472961s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 30.06507444381714s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007336139678955078s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.6915163993835449s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02092266082763672s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 6.937980651855469e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 6.198883056640625e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 104.98120999336243s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 30.19241189956665s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0007596015930175781s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.41631007194519043s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 4.887580871582031e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-sidc-drugs took 123.4525625705719s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 20.197661876678467s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0007562637329101562s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.7128052711486816s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02087116241455078s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 3.457069396972656e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 9.059906005859375e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 115.37101554870605s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 30.033273696899414s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2899816036224365s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020780563354492188s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.814697265625e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 112.73901128768921s
Availability | SPARQL endpoint availability check for State funding providers took 30.026212692260742s
Availability | VoID file availability check for State funding providers took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for State funding providers took 0.7991645336151123s
Reputation | Calculation of the PageRank for State funding providers took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.267692565917969e-05s
Believability | Calculation of trust value for State funding providers took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 114.07100176811218s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 30.107666730880737s
Availability | VoID file availability check for Organizations active in R&D took 0.0007734298706054688s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.7197356224060059s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.506111145019531e-05s
Believability | Calculation of trust value for Organizations active in R&D took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-organizations took 154.94501161575317s
Availability | SPARQL endpoint availability check for R&D Programmes took 29.9989972114563s
Availability | VoID file availability check for R&D Programmes took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.2521493434906006s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.076957702636719e-05s
Believability | Calculation of trust value for R&D Programmes took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-programmes took 114.07575297355652s
Availability | SPARQL endpoint availability check for R&D Projects took 30.189465045928955s
Availability | VoID file availability check for R&D Projects took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.26711320877075195s
Reputation | Calculation of the PageRank for R&D Projects took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 3.838539123535156e-05s
Believability | Calculation of trust value for R&D Projects took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-projects took 113.56716108322144s
Availability | SPARQL endpoint availability check for Institutional research plans took 30.199925422668457s
Availability | VoID file availability check for Institutional research plans took 0.0009920597076416016s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.26958179473876953s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020839452743530273s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.1961669921875e-05s
Believability | Calculation of trust value for Institutional research plans took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-research-plans took 115.07659602165222s
Availability | SPARQL endpoint availability check for Results of R&D took 30.112001419067383s
Availability | VoID file availability check for Results of R&D took 0.00067138671875s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.7298719882965088s
Reputation | Calculation of the PageRank for Results of R&D took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.7206878662109375e-05s
Believability | Calculation of trust value for Results of R&D took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-results took 114.87091660499573s
Availability | SPARQL endpoint availability check for Tenders in R&D took 30.2899432182312s
Availability | VoID file availability check for Tenders in R&D took 0.0009741783142089844s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2538914680480957s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.291534423828125e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-tenders took 115.18316698074341s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.458427429199219e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.24704504013061523s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.4332275390625e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 7.62939453125e-06s
INFO | --- Analysis for czech_addresses took 5.541598081588745s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.5337479114532471s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.26195383071899414s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for DanteLatinLoanwords took 5.027048110961914s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.4220249652862549s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0005664825439453125s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 134.77855372428894s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0429913997650146s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 7.104324579238892s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 2.9998815059661865s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.31366062164307s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.2455883026123047s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.1187436580657959s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.48169803619384766s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.3972742557525635s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.29743123054504395s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.8385627269744873s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 66.26696562767029s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.27814459800720215s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 0.4860880374908447s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.48378992080688477s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.253781795501709s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.22759795188903809s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.21623802185058594s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.525676965713501s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.319450378417969e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.23278355598449707s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.44633960723876953s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.4313833713531494s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.6326258182525635s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2625577449798584s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.1210203170776367s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.2205464839935303s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 79.53524971008301s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.20682835578918457s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.37419605255126953s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3110015392303467s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 39.46126341819763s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.2648463249206543s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.6681933403015137s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.335193395614624s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.6155686378479s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.794982194900513s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 40.867225885391235s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.3462443351745605s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 13.62885046005249s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8854217529296875s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2562375068664551s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.23615741729736328s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 4.966730356216431s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 1.2518112659454346s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02368783950805664s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.0001456737518310547s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.9073486328125e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 8.344650268554688e-06s
INFO | --- Analysis for data-bnf-fr took 742.0370433330536s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.1396636962890625s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005817413330078125s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.3434295654296875s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 6.286802530288696s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.08209848403930664s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.08188343048095703s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.08335685729980469s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.08188509941101074s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.08303451538085938s
License | MR license check for Open Data from the Italian National Research Council took 0.08370590209960938s
License | HR license check for Open Data from the Italian National Research Council took 0.0825352668762207s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.0903925895690918s
Understandability | Number of label check for Open Data from the Italian National Research Council took 0.08484792709350586s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.1673736572265625s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.08369326591491699s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.08426070213317871s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.08306884765625s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 9.489059448242188e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.08211517333984375s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.0832676887512207s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.08284735679626465s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.05186057090759277s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.08387470245361328s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.16573476791381836s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.16515326499938965s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 0.16522502899169922s
Interoperability | New vocabularies check for Open Data from the Italian National Research Council took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.08275580406188965s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.08260107040405273s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 0.08160400390625s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 12.063619375228882s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.00015735626220703125s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.11283040046691895s
Security | Sign check for Open Data from the Italian National Research Council took 0.09235286712646484s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 648.330127954483s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 1.2661311626434326s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.021233320236206055s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 0.00011444091796875s
Interoperability | Check the re-using of existing vocabs for Open Data from the Italian National Research Council took 4.76837158203125e-07s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.245208740234375e-06s
INFO | --- Analysis for data-cnr-it took 691.4442014694214s
Availability | SPARQL endpoint availability check for Data.gov took 1.7424073219299316s
Availability | VoID file availability check for Data.gov took 0.00033974647521972656s
Completeness | Calculation of interlinking completeness for Data.gov took 0.23851799964904785s
Reputation | Calculation of the PageRank for Data.gov took 0.020809650421142578s
Interlinking | Calculation of Degree of Connection for Data.gov took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.0040740966796875e-05s
Believability | Calculation of trust value for Data.gov took 4.76837158203125e-06s
INFO | --- Analysis for data-gov took 19.15354609489441s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.11613059043884277s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.00021696090698242188s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.2760324478149414s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.02064967155456543s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.937980651855469e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 4.76837158203125e-06s
INFO | --- Analysis for data-gov-ie took 2.992324113845825s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.124641418457031e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2571146488189697s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02086615562438965s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.343292236328125e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 5.0067901611328125e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.8194751739501953s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 22.02397656440735s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.9953205585479736s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02080988883972168s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.67572021484375e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 8.344650268554688e-06s
INFO | --- Analysis for data-hnm-hu took 168.0140962600708s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.19519901275634766s
Availability | VoID file availability check for Climb Dataincubator took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.28085899353027344s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.033348083496094e-05s
Believability | Calculation of trust value for Climb Dataincubator took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-climb took 4.379664182662964s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.267692565917969e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0007660388946533203s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2774515151977539s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.021116971969604492s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0008018016815185547s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.560585021972656e-05s
Believability | Calculation of trust value for Discogs in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for data-incubator-discogs took 7.570019006729126s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.05420398712158203s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.2712986469268799s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020166873931884766s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.1021575927734375e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 5.0067901611328125e-06s
INFO | --- Analysis for data-incubator-metoffice took 6.434232711791992s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.05454444885253906s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0003972053527832031s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.24112582206726074s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0008971691131591797s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 9.441375732421875e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-moseley took 8.398195743560791s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.06098437309265137s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.2616097927093506s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.249282836914062e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 9.059906005859375e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.568972587585449s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.841449499130249s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.2836496829986572s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 7.796287536621094e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 4.76837158203125e-06s
INFO | --- Analysis for data-incubator-nasa took 8.09015154838562s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.054862022399902344s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.24962902069091797s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.009506225585938e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.484391927719116s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.06136465072631836s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2530984878540039s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02018117904663086s
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.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 8.654594421386719e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.434839248657227s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.055611610412597656s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.28697681427001953s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.344650268554688e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.5045738220214844s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 1.3176047801971436s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0012214183807373047s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.2692093849182129s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.413459777832031e-05s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 5.9604644775390625e-06s
INFO | --- Analysis for data-open-ac-uk took 5.4648754596710205s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8323545455932617s
Availability | VoID file availability check for Persée in RDF took 0.0007987022399902344s
Extra | Recovery of all triples for Persée in RDF took 1.7219212055206299s
Performance | Total latancy measurement for Persée in RDF took 0.7016079425811768s
Amount of data | Number of triples check for Persée in RDF took 11.870104551315308s
Interoperability | New terms check for Persée in RDF took 1.72239089012146s
Versatility | Languages check for Persée in RDF took 121.2598180770874s
Interpretability | Number of blank nodes check for Persée in RDF took 0.9056751728057861s
Interpretability | RDF structures check for Persée in RDF took 1.3188447952270508s
Versatility | Serialization formats check for Persée in RDF took 0.9943652153015137s
Availability | RDF dump link check for Persée in RDF took 0.3085148334503174s
License | MR license check for Persée in RDF took 1.5744359493255615s
License | HR license check for Persée in RDF took 41.09732365608215s
Amount of data | Number of property check for Persée in RDF took 0.17406845092773438s
Understandability | Number of label check for Persée in RDF took 2.341261148452759s
Understandability | URI regex check for Persée in RDF took 0.8978972434997559s
Understandability | Vocabs check for Persée in RDF took 0.41899871826171875s
Verifiability | Authors check for Persée in RDF took 0.14025211334228516s
Verifiability | Publishers check for Persée in RDF took 0.2180798053741455s
Performance | Throughput check for Persée in RDF took 10.452912092208862s
Amount of data | Check the number of entities for Persée in RDF took 0.00010919570922851562s
Verifiability | Contribs. check for Persée in RDF took 0.2878134250640869s
Interlinking | sameAs chians check for Persée in RDF took 0.37642693519592285s
Interlinking | skos check for Persée in RDF took 0.6922934055328369s
Interlinking | skos check for Persée in RDF took 0.11837172508239746s
Timeliness | dataset update frequency check for Persée in RDF took 0.6567952632904053s
Currency | Creation date check for Persée in RDF took 0.4478945732116699s
Currency | Modification date check for Persée in RDF took 0.9751479625701904s
Rep.Conc. | URIs length for Persée in RDF took 3.6540424823760986s
Interoperability | New vocabularies check for Persée in RDF took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.12176299095153809s
Accuracy | Check Functional Property for Persée in RDF took 0.14303946495056152s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.1569838523864746s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.9555063247680664s
Accuracy | Check White space in annotation for Persée in RDF took 0.03934311866760254s
Accuracy | Check Datatype consistency for Persée in RDF took 0.02876138687133789s
Consistency | Disjoint class check for Persée in RDF took 0.276714563369751s
Consistency | Check Misplaced properties for Persée in RDF took 2.65092134475708s
Consistency | Misplaced classes for Persée in RDF took 0.22467613220214844s
Consistency | Check Ontology hijacking for Persée in RDF took 1.9765689373016357s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.1662800312042236s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.663034439086914s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.033208370208740234s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.14139294624328613s
Security | Sign check for Persée in RDF took 0.8711245059967041s
Availability | Check URIs Dereferenciability for Persée in RDF took 1375.9758036136627s
Completeness | Calculation of interlinking completeness for Persée in RDF took 1.3585467338562012s
Reputation | Calculation of the PageRank for Persée in RDF took 0.02082991600036621s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010848045349121094s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Persée in RDF took 8.344650268554688e-06s
INFO | --- Analysis for data-persee-fr took 1639.0585854053497s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.363059997558594e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.2708420753479004s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.020982742309570312s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.170967102050781e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 6.67572021484375e-06s
INFO | --- Analysis for data-southampton-ac-uk took 4.321443796157837s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 0.7682371139526367s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.2919003963470459s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011157989501953125s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 9.5367431640625e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 8.64218544960022s
Availability | SPARQL endpoint availability check for Open Data Web took 0.11845970153808594s
Availability | VoID file availability check for Open Data Web took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.28275060653686523s
Reputation | Calculation of the PageRank for Open Data Web took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 2.86102294921875e-05s
Believability | Calculation of trust value for Open Data Web took 7.152557373046875e-06s
INFO | --- Analysis for data.odw.tw took 2.5569300651550293s
Availability | SPARQL endpoint availability check for DataFAQs took 4.00543212890625e-05s
Availability | VoID file availability check for DataFAQs took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.25406765937805176s
Reputation | Calculation of the PageRank for DataFAQs took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for DataFAQs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 2.8848648071289062e-05s
Believability | Calculation of trust value for DataFAQs took 7.62939453125e-06s
INFO | --- Analysis for datafaqs took 2.959768056869507s
Availability | SPARQL endpoint availability check for datahub took 4.124641418457031e-05s
Availability | VoID file availability check for datahub took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for datahub took 0.2760157585144043s
Reputation | Calculation of the PageRank for datahub took 0.02037668228149414s
Interlinking | Calculation of Degree of Connection for datahub took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for datahub took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for datahub took 4.3392181396484375e-05s
Believability | Calculation of trust value for datahub took 7.3909759521484375e-06s
INFO | --- Analysis for datahub took 3.2789785861968994s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 6.204328775405884s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0007662773132324219s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.2839546203613281s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.337860107421875e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 6.198883056640625e-06s
INFO | --- Analysis for datahub-kr-datamap took 16.479379653930664s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.40846705436706543s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.30296778678894043s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.82012939453125e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.152557373046875e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.136901617050171s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.332292795181274s
Availability | VoID file availability check for datos-artium-org took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.3833003044128418s
Reputation | Calculation of the PageRank for datos-artium-org took 0.021499156951904297s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0008921623229980469s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00012922286987304688s
Believability | Calculation of trust value for datos-artium-org took 8.344650268554688e-06s
INFO | --- Analysis for datos-artium-org took 165.37493443489075s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8518340587615967s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006818771362304688s
Extra | Recovery of all triples for Datos.bcn.cl took 57.658445596694946s
Performance | Total latancy measurement for Datos.bcn.cl took 5.955396890640259s
Amount of data | Number of triples check for Datos.bcn.cl took 3.544788122177124s
Interoperability | New terms check for Datos.bcn.cl took 3.5333149433135986s
Versatility | Languages check for Datos.bcn.cl took 301.00553154945374s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 4.061161041259766s
Security | Check HTTPS for Datos.bcn.cl took 0.7227435111999512s
Interpretability | RDF structures check for Datos.bcn.cl took 1.6754405498504639s
Versatility | Serialization formats check for Datos.bcn.cl took 1.3244481086730957s
Availability | RDF dump link check for Datos.bcn.cl took 1.1878256797790527s
License | MR license check for Datos.bcn.cl took 1.197282075881958s
License | HR license check for Datos.bcn.cl took 65.78398966789246s
Amount of data | Number of property check for Datos.bcn.cl took 1.2010750770568848s
Understandability | Number of label check for Datos.bcn.cl took 2.378192901611328s
Understandability | URI regex check for Datos.bcn.cl took 2.387986898422241s
Understandability | Vocabs check for Datos.bcn.cl took 1.203768253326416s
Verifiability | Authors check for Datos.bcn.cl took 1.217970371246338s
Verifiability | Publishers check for Datos.bcn.cl took 1.2060399055480957s
Performance | Throughput check for Datos.bcn.cl took 11.841055631637573s
Amount of data | Check the number of entities for Datos.bcn.cl took 3.24249267578125e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.1840729713439941s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.3187015056610107s
Interlinking | skos check for Datos.bcn.cl took 1.228869915008545s
Interlinking | skos check for Datos.bcn.cl took 1.2048215866088867s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.1855061054229736s
Currency | Creation date check for Datos.bcn.cl took 2.418297290802002s
Currency | Modification date check for Datos.bcn.cl took 1.1928937435150146s
Rep.Conc. | URIs length for Datos.bcn.cl took 59.258541107177734s
Interoperability | New vocabularies check for Datos.bcn.cl took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.1937503814697266s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.1712193489074707s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.2112221717834473s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 21.25235104560852s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.24171924591064453s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2673032283782959s
Consistency | Disjoint class check for Datos.bcn.cl took 1.193824052810669s
Consistency | Check Misplaced properties for Datos.bcn.cl took 6.315062046051025s
Consistency | Misplaced classes for Datos.bcn.cl took 2.0391111373901367s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 26.228717803955078s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.2069916725158691s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 10.820395708084106s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.30414724349975586s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 12.32010555267334s
Security | Sign check for Datos.bcn.cl took 1.8068163394927979s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 8964.443014144897s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.219700813293457s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.021425724029541016s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 6.198883056640625e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 2.1457672119140625e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 6.198883056640625e-06s
INFO | --- Analysis for datos-bcn-cl took 9900.065078020096s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.33258724212646484s
Availability | VoID file availability check for datos.bne.es took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.2647130489349365s
Reputation | Calculation of the PageRank for datos.bne.es took 0.02066349983215332s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011372566223144531s
Believability | Calculation of trust value for datos.bne.es took 7.3909759521484375e-06s
INFO | --- Analysis for datos-bne-es took 5.278440952301025s
Availability | SPARQL endpoint availability check for dbacademic took 0.17083525657653809s
Availability | VoID file availability check for dbacademic took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for dbacademic took 0.7143795490264893s
Reputation | Calculation of the PageRank for dbacademic took 0.020891904830932617s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.170967102050781e-05s
Believability | Calculation of trust value for dbacademic took 5.9604644775390625e-06s
INFO | --- Analysis for dbacademic took 4.3037989139556885s
Availability | SPARQL endpoint availability check for DBkWik took 0.24098944664001465s
Availability | VoID file availability check for DBkWik took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for DBkWik took 0.2721421718597412s
Reputation | Calculation of the PageRank for DBkWik took 0.021274328231811523s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for DBkWik took 6.937980651855469e-05s
Believability | Calculation of trust value for DBkWik took 8.106231689453125e-06s
INFO | --- Analysis for dbkwik took 6.562476396560669s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 7.367134094238281e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.2767500877380371s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00010180473327636719s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 43.33351373672485s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.45424389839172363s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0006313323974609375s
Extra | Recovery of all triples for dblp Knowledge Graph took 66.474680185318s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.8204903602600098s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.16846132278442383s
Interoperability | New terms check for dblp Knowledge Graph took 1.752134084701538s
Versatility | Languages check for dblp Knowledge Graph took 30.29493498802185s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.5947976112365723s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.17290425300598145s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.1748950481414795s
Availability | RDF dump link check for dblp Knowledge Graph took 0.1674962043762207s
License | MR license check for dblp Knowledge Graph took 0.15745091438293457s
License | HR license check for dblp Knowledge Graph took 30.13558340072632s
Amount of data | Number of property check for dblp Knowledge Graph took 0.17698931694030762s
Understandability | Number of label check for dblp Knowledge Graph took 0.5238442420959473s
Understandability | URI regex check for dblp Knowledge Graph took 0.30668163299560547s
Understandability | Vocabs check for dblp Knowledge Graph took 0.1308426856994629s
Verifiability | Authors check for dblp Knowledge Graph took 0.19861698150634766s
Verifiability | Publishers check for dblp Knowledge Graph took 0.18215322494506836s
Performance | Throughput check for dblp Knowledge Graph took 11.092810869216919s
Amount of data | Check the number of entities for dblp Knowledge Graph took 6.937980651855469e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.16437911987304688s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.2359163761138916s
Interlinking | skos check for dblp Knowledge Graph took 0.1520535945892334s
Interlinking | skos check for dblp Knowledge Graph took 0.1273798942565918s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.17716383934020996s
Currency | Creation date check for dblp Knowledge Graph took 0.32778000831604004s
Currency | Modification date check for dblp Knowledge Graph took 0.31165242195129395s
Rep.Conc. | URIs length for dblp Knowledge Graph took 24.513160228729248s
Interoperability | New vocabularies check for dblp Knowledge Graph took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.20044660568237305s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.13160133361816406s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.12501311302185059s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 17.332098722457886s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.0986359119415283s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.1529407501220703s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.3223559856414795s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 20.87304973602295s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 1.35323166847229s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 0.0001437664031982422s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.16578960418701172s
Security | Sign check for dblp Knowledge Graph took 0.1503617763519287s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.7971487045288086s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.021085023880004883s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.9073486328125e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 8.58306884765625e-06s
INFO | --- Analysis for dblp-kg took 282.77006125450134s
Availability | SPARQL endpoint availability check for dbnary took 0.31921863555908203s
Availability | VoID file availability check for dbnary took 0.0005939006805419922s
Extra | Recovery of all triples for dbnary took 1.9511327743530273s
Performance | Total latancy measurement for dbnary took 0.422619104385376s
Amount of data | Number of triples check for dbnary took 1.263434886932373s
Interoperability | New terms check for dbnary took 3.595958709716797s
Versatility | Languages check for dbnary took 61.28115200996399s
Interpretability | Number of blank nodes check for dbnary took 1.7041780948638916s
Security | Check HTTPS for dbnary took 0.17238092422485352s
Interpretability | RDF structures check for dbnary took 0.1639716625213623s
Versatility | Serialization formats check for dbnary took 0.22110772132873535s
Availability | RDF dump link check for dbnary took 0.07961750030517578s
License | MR license check for dbnary took 0.2903881072998047s
License | HR license check for dbnary took 60.729653120040894s
Amount of data | Number of property check for dbnary took 0.11639523506164551s
Understandability | Number of label check for dbnary took 0.7848398685455322s
Understandability | URI regex check for dbnary took 0.1472773551940918s
Understandability | Vocabs check for dbnary took 0.15874004364013672s
Verifiability | Authors check for dbnary took 0.20786547660827637s
Verifiability | Publishers check for dbnary took 0.19356012344360352s
Performance | Throughput check for dbnary took 10.521745204925537s
Amount of data | Check the number of entities for dbnary took 7.843971252441406e-05s
Verifiability | Contribs. check for dbnary took 0.19464492797851562s
Interlinking | sameAs chians check for dbnary took 0.10772180557250977s
Interlinking | skos check for dbnary took 0.16902613639831543s
Interlinking | skos check for dbnary took 0.3037993907928467s
Timeliness | dataset update frequency check for dbnary took 0.1477665901184082s
Currency | Creation date check for dbnary took 0.20907330513000488s
Currency | Modification date check for dbnary took 0.2218008041381836s
Rep.Conc. | URIs length for dbnary took 11.572965860366821s
Interoperability | New vocabularies check for dbnary took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.10361242294311523s
Accuracy | Check Functional Property for dbnary took 0.17199468612670898s
Accuracy | Check Inverse Functional Property for dbnary took 0.10058093070983887s
Accuracy | Check Empty annotation labels for dbnary took 0.9756219387054443s
Accuracy | Check White space in annotation for dbnary took 0.024983644485473633s
Accuracy | Check Datatype consistency for dbnary took 0.027884960174560547s
Consistency | Disjoint class check for dbnary took 0.14168047904968262s
Consistency | Check Misplaced properties for dbnary took 8.989598512649536s
Consistency | Misplaced classes for dbnary took 0.22481155395507812s
Consistency | Check Ontology hijacking for dbnary took 1.763672113418579s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.2484064102172852s
Consistency | Check Invalid usage of undefined properties for dbnary took 10.046382665634155s
Conciseness | Check Extensional conciseness for dbnary took 0.03156566619873047s
Conciseness | Check Intensional conciseness for dbnary took 0.2088310718536377s
Security | Sign check for dbnary took 0.08616876602172852s
Availability | Check URIs Dereferenciability for dbnary took 5.288577318191528s
Completeness | Calculation of interlinking completeness for dbnary took 0.30205631256103516s
Reputation | Calculation of the PageRank for dbnary took 0.020939350128173828s
Interlinking | Calculation of Degree of Connection for dbnary took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.14984130859375e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.6689300537109375e-06s
Believability | Calculation of trust value for dbnary took 6.4373016357421875e-06s
INFO | --- Analysis for dbnary took 285.03794503211975s
Availability | SPARQL endpoint availability check for DBpedia took 24.445603370666504s
Availability | VoID file availability check for DBpedia took 0.0006861686706542969s
Extra | Recovery of all triples for DBpedia took 13.430718421936035s
Performance | Total latancy measurement for DBpedia took 25.959776163101196s
Amount of data | Number of triples check for DBpedia took 20.327574729919434s
Interoperability | New terms check for DBpedia took 32.54304575920105s
Versatility | Languages check for DBpedia took 39.906660079956055s
Interpretability | Number of blank nodes check for DBpedia took 14.073368310928345s
Security | Check HTTPS for DBpedia took 4.151228904724121s
Interpretability | RDF structures check for DBpedia took 17.656872749328613s
Versatility | Serialization formats check for DBpedia took 4.533059597015381s
Availability | RDF dump link check for DBpedia took 15.601486444473267s
License | MR license check for DBpedia took 4.042089462280273s
License | HR license check for DBpedia took 39.90324306488037s
Amount of data | Number of property check for DBpedia took 23.68602705001831s
Understandability | Number of label check for DBpedia took 19.603028059005737s
Understandability | URI regex check for DBpedia took 29.617721796035767s
Understandability | Vocabs check for DBpedia took 11.956490278244019s
Verifiability | Authors check for DBpedia took 24.320613622665405s
Verifiability | Publishers check for DBpedia took 17.635713815689087s
Performance | Throughput check for DBpedia took 86.58726596832275s
Amount of data | Check the number of entities for DBpedia took 7.414817810058594e-05s
Verifiability | Contribs. check for DBpedia took 0.48392224311828613s
Interlinking | sameAs chians check for DBpedia took 17.611525774002075s
Interlinking | skos check for DBpedia took 19.37615442276001s
Interlinking | skos check for DBpedia took 10.650045156478882s
Timeliness | dataset update frequency check for DBpedia took 20.459677934646606s
Currency | Creation date check for DBpedia took 22.621274948120117s
Currency | Modification date check for DBpedia took 24.110572338104248s
Rep.Conc. | URIs length for DBpedia took 124.9834930896759s
Interoperability | New vocabularies check for DBpedia took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 23.276983499526978s
Accuracy | Check Functional Property for DBpedia took 13.715335369110107s
Accuracy | Check Inverse Functional Property for DBpedia took 17.77426791191101s
Accuracy | Check Empty annotation labels for DBpedia took 49.5696017742157s
Accuracy | Check White space in annotation for DBpedia took 0.03059077262878418s
Consistency | Disjoint class check for DBpedia took 13.245414018630981s
Consistency | Check Misplaced properties for DBpedia took 100.46266579627991s
Consistency | Misplaced classes for DBpedia took 69.15358829498291s
Consistency | Check Ontology hijacking for DBpedia took 82.98713779449463s
Consistency | Check Invalid usage of undefined properties for DBpedia took 76.32232618331909s
Conciseness | Check Extensional conciseness for DBpedia took 0.0001571178436279297s
Conciseness | Check Intensional conciseness for DBpedia took 56.66718554496765s
Security | Sign check for DBpedia took 12.436946868896484s
Availability | Check URIs Dereferenciability for DBpedia took 10372.71549654007s
Completeness | Calculation of interlinking completeness for DBpedia took 1.2131645679473877s
Reputation | Calculation of the PageRank for DBpedia took 0.02119135856628418s
Interlinking | Calculation of Degree of Connection for DBpedia took 6.127357482910156e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.000873565673828125s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia took 12253.503758192062s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 5.817413330078125e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.7587127685546875s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020785093307495117s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.4849853515625e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 9.969265460968018s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.073292970657349s
Availability | VoID file availability check for DBpedia Commons took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.27649545669555664s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020395517349243164s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.508827209472656e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-commons took 17.25373911857605s
Availability | SPARQL endpoint availability check for DBpedia in German took 3.910064697265625e-05s
Availability | VoID file availability check for DBpedia in German took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.2772550582885742s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 5.91278076171875e-05s
Believability | Calculation of trust value for DBpedia in German took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-de took 4.2659592628479s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 10.50702452659607s
Availability | VoID file availability check for DBpedia in Greek took 0.00038909912109375s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.6865534782409668s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020733356475830078s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00019788742065429688s
Believability | Calculation of trust value for DBpedia in Greek took 4.76837158203125e-06s
INFO | --- Analysis for dbpedia-el took 44.65167188644409s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.4510624408721924s
Availability | VoID file availability check for DBpedia in Spanish took 0.0005652904510498047s
Extra | Recovery of all triples for DBpedia in Spanish took 2.6039059162139893s
Performance | Total latancy measurement for DBpedia in Spanish took 1.1745884418487549s
Amount of data | Number of triples check for DBpedia in Spanish took 0.914731502532959s
Interoperability | New terms check for DBpedia in Spanish took 2.764404535293579s
Versatility | Languages check for DBpedia in Spanish took 30.323514461517334s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.4354417324066162s
Security | Check HTTPS for DBpedia in Spanish took 0.15095758438110352s
Interpretability | RDF structures check for DBpedia in Spanish took 1.1709470748901367s
Versatility | Serialization formats check for DBpedia in Spanish took 0.6360230445861816s
Availability | RDF dump link check for DBpedia in Spanish took 0.37389683723449707s
License | MR license check for DBpedia in Spanish took 0.8998978137969971s
License | HR license check for DBpedia in Spanish took 30.325507640838623s
Amount of data | Number of property check for DBpedia in Spanish took 0.33182454109191895s
Understandability | Number of label check for DBpedia in Spanish took 1.8577299118041992s
Understandability | URI regex check for DBpedia in Spanish took 0.8395884037017822s
Understandability | Vocabs check for DBpedia in Spanish took 0.5166440010070801s
Verifiability | Authors check for DBpedia in Spanish took 0.31081581115722656s
Verifiability | Publishers check for DBpedia in Spanish took 0.2842707633972168s
Performance | Throughput check for DBpedia in Spanish took 11.478158473968506s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.319450378417969e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.31485867500305176s
Interlinking | sameAs chians check for DBpedia in Spanish took 1.419297218322754s
Interlinking | skos check for DBpedia in Spanish took 0.6475529670715332s
Interlinking | skos check for DBpedia in Spanish took 0.25384974479675293s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.48437952995300293s
Currency | Creation date check for DBpedia in Spanish took 0.6232445240020752s
Currency | Modification date check for DBpedia in Spanish took 0.627659797668457s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.718805313110352s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.30225372314453125s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.4618844985961914s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.4698915481567383s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.13999342918396s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.03095412254333496s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.0281217098236084s
Consistency | Disjoint class check for DBpedia in Spanish took 0.2971072196960449s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.153292894363403s
Consistency | Misplaced classes for DBpedia in Spanish took 1.2480480670928955s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 3.263862133026123s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.162121295928955s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.740612983703613s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03551077842712402s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.4196460247039795s
Security | Sign check for DBpedia in Spanish took 0.34452080726623535s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 9.190012454986572s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.29143714904785156s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010156631469726562s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-es took 1660.1032755374908s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.375084638595581s
Availability | VoID file availability check for DBpedia in Basque took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.27538108825683594s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.361701965332031e-05s
Believability | Calculation of trust value for DBpedia in Basque took 6.4373016357421875e-06s
INFO | --- Analysis for dbpedia-eu took 7.955178737640381s
Availability | SPARQL endpoint availability check for DBpedia in French took 30.149651765823364s
Availability | VoID file availability check for DBpedia in French took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.26288866996765137s
Reputation | Calculation of the PageRank for DBpedia in French took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 8.463859558105469e-05s
Believability | Calculation of trust value for DBpedia in French took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-fr took 125.23989295959473s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.9563252925872803s
Availability | VoID file availability check for DBpedia in Japanese took 4.079911470413208s
Extra | Recovery of all triples for DBpedia in Japanese took 1.323578119277954s
Amount of data | Number of triples check for DBpedia in Japanese took 61.316893339157104s
Versatility | Languages check for DBpedia in Japanese took 1.322533130645752s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.334881067276001s
Interpretability | RDF structures check for DBpedia in Japanese took 1.3756763935089111s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3362503051757812s
Availability | RDF dump link check for DBpedia in Japanese took 1.3152740001678467s
License | MR license check for DBpedia in Japanese took 1.32319974899292s
License | HR license check for DBpedia in Japanese took 1.3323745727539062s
Amount of data | Number of property check for DBpedia in Japanese took 1.3300979137420654s
Understandability | Number of label check for DBpedia in Japanese took 9.774065017700195s
Understandability | URI regex check for DBpedia in Japanese took 2.648235559463501s
Understandability | Vocabs check for DBpedia in Japanese took 1.3210182189941406s
Verifiability | Authors check for DBpedia in Japanese took 1.3493435382843018s
Verifiability | Publishers check for DBpedia in Japanese took 1.324892282485962s
Amount of data | Check the number of entities for DBpedia in Japanese took 0.00016117095947265625s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3153512477874756s
Interlinking | sameAs chians check for DBpedia in Japanese took 1.3241539001464844s
Interlinking | skos check for DBpedia in Japanese took 1.3165278434753418s
Interlinking | skos check for DBpedia in Japanese took 1.3279798030853271s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3246376514434814s
Currency | Creation date check for DBpedia in Japanese took 2.6284658908843994s
Currency | Modification date check for DBpedia in Japanese took 2.655651569366455s
Rep.Conc. | URIs length for DBpedia in Japanese took 62.65739321708679s
Interoperability | New vocabularies check for DBpedia in Japanese took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.318401575088501s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4710876941680908s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.826607942581177s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 62.48413395881653s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.00013780593872070312s
Security | Sign check for DBpedia in Japanese took 1.3232734203338623s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 1.2416729927062988s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.021129131317138672s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.0001049041748046875s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 7.152557373046875e-07s
Believability | Calculation of trust value for DBpedia in Japanese took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-ja took 362.1827311515808s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.2438507080078125e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.6954011917114258s
Reputation | Calculation of the PageRank for dbpedia lite took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.584426879882812e-05s
Believability | Calculation of trust value for dbpedia lite took 4.5299530029296875e-06s
INFO | --- Analysis for dbpedia-lite took 23.733302354812622s
Availability | SPARQL endpoint availability check for DBpedia-Live took 3.9577484130859375e-05s
Availability | VoID file availability check for DBpedia-Live took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.26846766471862793s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 2.7894973754882812e-05s
Believability | Calculation of trust value for DBpedia-Live took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-live took 3.0035910606384277s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.24440884590148926s
Availability | VoID file availability check for DBpedia in Dutch took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2772984504699707s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00017023086547851562s
Believability | Calculation of trust value for DBpedia in Dutch took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-nl took 4.1630260944366455s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 30.24630618095398s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.2840263843536377s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.153915405273438e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-pt took 73.68697023391724s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.076957702636719e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.7276358604431152s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.0279159545898438e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-spotlight took 4.743893146514893s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.1484832763671875e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.2906522750854492s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.02071356773376465s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0010182857513427734s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 8.153915405273438e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 15.100637435913086s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.291534423828125e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.27784299850463867s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 2.9087066650390625e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-wikidata took 3.05218768119812s
Availability | SPARQL endpoint availability check for DBpedia took 4.649162292480469e-05s
Availability | VoID file availability check for DBpedia took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for DBpedia took 0.26106691360473633s
Reputation | Calculation of the PageRank for DBpedia took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for DBpedia took 3.123283386230469e-05s
Believability | Calculation of trust value for DBpedia took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia_ took 3.4310665130615234s
Availability | SPARQL endpoint availability check for DBTropes took 4.315376281738281e-05s
Availability | VoID file availability check for DBTropes took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for DBTropes took 0.2555656433105469s
Reputation | Calculation of the PageRank for DBTropes took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for DBTropes took 8.869171142578125e-05s
Believability | Calculation of trust value for DBTropes took 5.9604644775390625e-06s
INFO | --- Analysis for dbtropes took 3.5651228427886963s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.029273986816406e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.27153587341308594s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 7.867813110351562e-06s
INFO | --- Analysis for dbtune took 3.008777379989624s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.124641418457031e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.2727506160736084s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 6.103515625e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 8.58306884765625e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 8.633386850357056s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.2438507080078125e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.27760791778564453s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.838539123535156e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.62939453125e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 5.96703028678894s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.852392673492432s
Availability | VoID file availability check for DBTune.org/classical took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.2769951820373535s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.867813110351562e-05s
Believability | Calculation of trust value for DBTune.org/classical took 8.106231689453125e-06s
INFO | --- Analysis for dbtune-classical took 22.42520236968994s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.34488034248352s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.26807355880737305s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.02076101303100586s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.628036499023438e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 6.9141387939453125e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 27.228270769119263s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.325278997421265s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2704129219055176s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020523786544799805s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.628036499023438e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-magnatune took 23.899478435516357s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.334563970565796s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.28186511993408203s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020601987838745117s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010180473327636719s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 8.106231689453125e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.904204845428467s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.314386367797852s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.27791690826416016s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.173683166503906e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 7.62939453125e-06s
INFO | --- Analysis for dbtune-myspace took 17.88512396812439s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.124641418457031e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.2800405025482178s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 2.956390380859375e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 7.867813110351562e-06s
INFO | --- Analysis for dclg-openuplabs took 3.4340715408325195s
Availability | SPARQL endpoint availability check for data.dcs took 4.267692565917969e-05s
Availability | VoID file availability check for data.dcs took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for data.dcs took 0.26557230949401855s
Reputation | Calculation of the PageRank for data.dcs took 0.020717620849609375s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.532669067382812e-05s
Believability | Calculation of trust value for data.dcs took 7.867813110351562e-06s
INFO | --- Analysis for dcs-sheffield took 2.647711753845215s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.1484832763671875e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.2735633850097656s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 3.0040740966796875e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 7.62939453125e-06s
INFO | --- Analysis for de-budget took 2.9852068424224854s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 0.00033402442932128906s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2742726802825928s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0008132457733154297s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.910064697265625e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 8.106231689453125e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.291616201400757s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.2438507080078125e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.26966023445129395s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020696401596069336s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007662773132324219s
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 7.3909759521484375e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.772308826446533s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.1961669921875e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.2773153781890869s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 2.9325485229492188e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.152557373046875e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.8567445278167725s
Availability | SPARQL endpoint availability check for Demografie took 4.00543212890625e-05s
Availability | VoID file availability check for Demografie took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for Demografie took 0.2648298740386963s
Reputation | Calculation of the PageRank for Demografie took 0.021136999130249023s
Interlinking | Calculation of Degree of Connection for Demografie took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Demografie took 2.9325485229492188e-05s
Believability | Calculation of trust value for Demografie took 7.3909759521484375e-06s
INFO | --- Analysis for demografie took 2.9954402446746826s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.3392181396484375e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.27278661727905273s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.3855438232421875e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 7.62939453125e-06s
INFO | --- Analysis for desaparecidos took 2.8592031002044678s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.506111145019531e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.27289628982543945s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.021152734756469727s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0008530616760253906s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00011014938354492188s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 7.3909759521484375e-06s
INFO | --- Analysis for deustoentrepreneurship took 3.789066791534424s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.2438507080078125e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.27277565002441406s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.0001049041748046875s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 6.4373016357421875e-06s
INFO | --- Analysis for deustotech took 3.5573439598083496s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.373610019683838s
Availability | VoID file availability check for Deutsche Biographie took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.28199291229248047s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.021008729934692383s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.00543212890625e-05s
Believability | Calculation of trust value for Deutsche Biographie took 7.3909759521484375e-06s
INFO | --- Analysis for deutsche-biographie took 4.242764949798584s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.38690185546875e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2685108184814453s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.626678466796875e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 7.867813110351562e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.822267770767212s
Availability | SPARQL endpoint availability check for dev8d took 5.650520324707031e-05s
Availability | VoID file availability check for dev8d took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for dev8d took 0.2657136917114258s
Reputation | Calculation of the PageRank for dev8d took 0.020758390426635742s
Interlinking | Calculation of Degree of Connection for dev8d took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.771087646484375e-05s
Believability | Calculation of trust value for dev8d took 8.106231689453125e-06s
INFO | --- Analysis for dev8d took 2.7639288902282715s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.329439163208008s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007228851318359375s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.2908661365509033s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.6743621826171875e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 7.3909759521484375e-06s
INFO | --- Analysis for dewey_decimal_classification took 92.98310112953186s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 5.269050598144531e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.26538634300231934s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 2.8848648071289062e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 7.867813110351562e-06s
INFO | --- Analysis for DHSVM took 21.689385175704956s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 3.981590270996094e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.26955676078796387s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.021077632904052734s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.266334533691406e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 5.9604644775390625e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 3.3745150566101074s
Availability | SPARQL endpoint availability check for Diavgeia took 4.506111145019531e-05s
Availability | VoID file availability check for Diavgeia took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.2779726982116699s
Reputation | Calculation of the PageRank for Diavgeia took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for Diavgeia took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 7.843971252441406e-05s
Believability | Calculation of trust value for Diavgeia took 5.4836273193359375e-06s
INFO | --- Analysis for diavgeia took 5.541194677352905s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.220008850097656e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.27930235862731934s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02100372314453125s
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.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011873245239257812s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 9.775161743164062e-06s
INFO | --- Analysis for didactalia took 4.212071657180786s
Availability | SPARQL endpoint availability check for diigo.feed took 4.38690185546875e-05s
Availability | VoID file availability check for diigo.feed took 0.000274658203125s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.27579426765441895s
Reputation | Calculation of the PageRank for diigo.feed took 0.02057194709777832s
Interlinking | Calculation of Degree of Connection for diigo.feed took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.8133392333984375e-05s
Believability | Calculation of trust value for diigo.feed took 7.3909759521484375e-06s
INFO | --- Analysis for diigo-feed took 2.969162702560425s
Availability | SPARQL endpoint availability check for DisGeNET took 0.8193879127502441s
Availability | VoID file availability check for DisGeNET took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.26255345344543457s
Reputation | Calculation of the PageRank for DisGeNET took 0.02010631561279297s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00014734268188476562s
Believability | Calculation of trust value for DisGeNET took 7.3909759521484375e-06s
INFO | --- Analysis for disgenet took 8.471433401107788s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.00543212890625e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.27040553092956543s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 2.6702880859375e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 3.457069396972656e-05s
INFO | --- Analysis for disk took 2.930124044418335s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.00543212890625e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.30153584480285645s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 2.6464462280273438e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 8.106231689453125e-06s
INFO | --- Analysis for distritos-zaragoza took 2.9024641513824463s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.5299530029296875e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2614421844482422s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 2.7179718017578125e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 7.3909759521484375e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 6.401150226593018s
Availability | SPARQL endpoint availability check for DM2E took 4.1484832763671875e-05s
Availability | VoID file availability check for DM2E took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for DM2E took 0.28142356872558594s
Reputation | Calculation of the PageRank for DM2E took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011420249938964844s
Believability | Calculation of trust value for DM2E took 7.3909759521484375e-06s
INFO | --- Analysis for dm2e took 3.1683285236358643s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.100799560546875e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.27730345726013184s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.02035689353942871s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 2.7179718017578125e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 7.152557373046875e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.986701488494873s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.6952109336853027s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.3268928527832031s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020879268646240234s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015592575073242188s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 8.58306884765625e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 10.864506721496582s
Availability | SPARQL endpoint availability check for DOAP Store took 4.029273986816406e-05s
Availability | VoID file availability check for DOAP Store took 0.00037789344787597656s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.24540400505065918s
Reputation | Calculation of the PageRank for DOAP Store took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.0517578125e-05s
Believability | Calculation of trust value for DOAP Store took 7.152557373046875e-06s
INFO | --- Analysis for doap_store took 2.9648234844207764s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.172325134277344e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.2739593982696533s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.198883056640625e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 5.0067901611328125e-06s
INFO | --- Analysis for doi took 8.693170309066772s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.1484832763671875e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.25768446922302246s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.8371810913085938e-05s
Believability | Calculation of trust value for Driggu Florentino took 7.152557373046875e-06s
INFO | --- Analysis for Driggu took 3.4196465015411377s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 6.333947420120239s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.25521206855773926s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.4809112548828125e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 7.152557373046875e-06s
INFO | --- Analysis for drug-data-hifm took 36.53624629974365s
Availability | SPARQL endpoint availability check for dspace took 4.0531158447265625e-05s
Availability | VoID file availability check for dspace took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for dspace took 0.29261136054992676s
Reputation | Calculation of the PageRank for dspace took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for dspace took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for dspace took 2.956390380859375e-05s
Believability | Calculation of trust value for dspace took 6.198883056640625e-06s
INFO | --- Analysis for dspace took 2.939103364944458s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.458427429199219e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.2669332027435303s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.027065515518188477s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0011796951293945312s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.5762786865234375e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 7.867813110351562e-06s
INFO | --- Analysis for duraark-linked-building-data took 3.026931047439575s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 270.9019498825073s
Availability | VoID file availability check for MetaLex Document Server took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.7330138683319092s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020949363708496094s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.409385681152344e-05s
Believability | Calculation of trust value for MetaLex Document Server took 9.298324584960938e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 556.2703986167908s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.1518919467926025s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.6890175342559814s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.790855407714844e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.152557373046875e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 14.601620197296143s
Availability | SPARQL endpoint availability check for DWS-Group took 4.267692565917969e-05s
Availability | VoID file availability check for DWS-Group took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.2584953308105469s
Reputation | Calculation of the PageRank for DWS-Group took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010228157043457031s
Believability | Calculation of trust value for DWS-Group took 7.152557373046875e-06s
INFO | --- Analysis for dws-group took 4.320212125778198s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.2438507080078125e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.721627950668335s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.020189523696899414s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.86102294921875e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 7.152557373046875e-06s
INFO | --- Analysis for E1 took 5.022202014923096s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.05653691291809082s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.2729148864746094s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.0001125335693359375s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 5.7220458984375e-06s
INFO | --- Analysis for eagle-i-alaska took 3.88287615776062s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.04080915451049805s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0009095668792724609s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.2724018096923828s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.054473876953125e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-cau took 2.8345956802368164s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.039615631103515625s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.26694703102111816s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.151199340820312e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.556950092315674s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.05101752281188965s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.26271867752075195s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020512104034423828s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.298324584960938e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.474973201751709s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.039991140365600586s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.2785933017730713s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.020635604858398438s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013446807861328125s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.5723559856414795s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04012179374694824s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2645752429962158s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.020244598388671875s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.225440979003906e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-famu took 2.5064783096313477s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04700207710266113s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.2479865550994873s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020474910736083984s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012612342834472656s
Believability | Calculation of trust value for eagle-i @ Harvard University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-harvard took 2.490076780319214s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.03990912437438965s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.25162744522094727s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001246929168701172s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-hawaii took 3.01739764213562s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.044586896896362305s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2878568172454834s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 7.081031799316406e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-howard took 2.5916545391082764s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.04940366744995117s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0003428459167480469s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2807128429412842s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.486343383789062e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.543872117996216s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.057648658752441406s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.27461671829223633s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011539459228515625s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-jsu took 2.553825616836548s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.04457807540893555s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.2519564628601074s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.62396240234375e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i-meharry took 2.510881185531616s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.037537336349487305s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2579362392425537s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02129054069519043s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.751319885253906e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-montana took 2.4459962844848633s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.057215213775634766s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0002193450927734375s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.2631504535675049s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.560585021972656e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-msm took 2.5068469047546387s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.056401968002319336s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.24384236335754395s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02097177505493164s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00014019012451171875s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.4930386543273926s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.05499076843261719s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2659437656402588s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.842613220214844e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-psm took 2.438664197921753s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.044628143310546875s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.26045703887939453s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020905733108520508s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.67572021484375e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 5.9604644775390625e-06s
INFO | --- Analysis for eagle-i-tsu took 2.4624862670898438s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.057187557220458984s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.26640963554382324s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020821571350097656s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007455348968505859s
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 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.4350292682647705s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.0430908203125s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.26213502883911133s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.020745038986206055s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.918212890625e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.4428207874298096s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.06225156784057617s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.26772427558898926s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00011992454528808594s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-upr took 2.524454116821289s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.04857206344604492s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.26343464851379395s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.02099466323852539s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.031990051269531e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 5.4836273193359375e-06s
INFO | --- Analysis for eagle-i-utep took 2.5435032844543457s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.043772220611572266s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.26412367820739746s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.02061295509338379s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.866455078125e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-utsa took 2.5241522789001465s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.17650222778320312s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.26374101638793945s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.021095752716064453s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.846687316894531e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.6558730602264404s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.04649639129638672s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.28276658058166504s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020899295806884766s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 8.606910705566406e-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.514179229736328s
Availability | SPARQL endpoint availability check for Emergency situation took 0.9233508110046387s
Availability | VoID file availability check for Emergency situation took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.2651665210723877s
Reputation | Calculation of the PageRank for Emergency situation took 0.021087646484375s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.8160552978515625e-05s
Believability | Calculation of trust value for Emergency situation took 6.4373016357421875e-06s
INFO | --- Analysis for Earthquake took 4.5744099617004395s
Availability | SPARQL endpoint availability check for ESO took 0.6746950149536133s
Availability | VoID file availability check for ESO took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for ESO took 0.26996803283691406s
Reputation | Calculation of the PageRank for ESO took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for ESO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for ESO took 8.988380432128906e-05s
Believability | Calculation of trust value for ESO took 6.198883056640625e-06s
INFO | --- Analysis for Earthquake_case took 4.113866567611694s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.34705042839050293s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.26694440841674805s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010085105895996094s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for ecb-linked-data took 2.818025827407837s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 4.919534921646118s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.27188754081726074s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.504753112792969e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 5.9604644775390625e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 11.434681177139282s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.8030545711517334s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.28030872344970703s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.4849853515625e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 6.022796154022217s
Availability | SPARQL endpoint availability check for ECLAP took 30.003702640533447s
Availability | VoID file availability check for ECLAP took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for ECLAP took 0.2676703929901123s
Reputation | Calculation of the PageRank for ECLAP took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.528594970703125e-05s
Believability | Calculation of trust value for ECLAP took 6.4373016357421875e-06s
INFO | --- Analysis for eclap took 62.65920615196228s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.267692565917969e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.2794930934906006s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 2.0503997802734375e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 7.62939453125e-06s
INFO | --- Analysis for ECNU-GISer took 7.3884596824646s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.315376281738281e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2705419063568115s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.412101745605469e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.3909759521484375e-06s
INFO | --- Analysis for ecs took 2.8662610054016113s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 5.2928924560546875e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.27239441871643066s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.0279159545898438e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 6.9141387939453125e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 3.4627766609191895s
Availability | SPARQL endpoint availability check for Edublogs took 8.440017700195312e-05s
Availability | VoID file availability check for Edublogs took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Edublogs took 0.2550337314605713s
Reputation | Calculation of the PageRank for Edublogs took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for Edublogs took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Edublogs took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.632110595703125e-05s
Believability | Calculation of trust value for Edublogs took 7.152557373046875e-06s
INFO | --- Analysis for edublogs took 3.46809458732605s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.5795199871063232s
Availability | VoID file availability check for education.data.gov.uk took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.28380441665649414s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.797645568847656e-05s
Believability | Calculation of trust value for education.data.gov.uk took 6.198883056640625e-06s
INFO | --- Analysis for education-data-gov-uk took 4.642125129699707s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 5.245208740234375e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2757580280303955s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 2.9087066650390625e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.152557373046875e-06s
INFO | --- Analysis for education-openuplabs took 2.968374729156494s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.75801491737366s
Availability | VoID file availability check for Educational programs - SISVU took 0.000881195068359375s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 1.2989165782928467s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.0212862491607666s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.2928924560546875e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.4066696166992188e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1325.153971672058s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 25.618948698043823s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.26587390899658203s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.029273986816406e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.7220458984375e-06s
INFO | --- Analysis for eea took 89.28137183189392s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5321910381317139s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.2929813861846924s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.02101302146911621s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.7697296142578125e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 4.76837158203125e-06s
INFO | --- Analysis for eea-rod took 6.45499849319458s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.19720101356506348s
Availability | VoID file availability check for EEA Vocabularies took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.26927757263183594s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.344650268554688e-05s
Believability | Calculation of trust value for EEA Vocabularies took 8.106231689453125e-06s
INFO | --- Analysis for eea-vocabularies took 7.055001258850098s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 5.1975250244140625e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.26749110221862793s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.170967102050781e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for ege-university-linked-open-data took 4.258721590042114s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.49344730377197266s
Availability | VoID file availability check for E-Government Ontology took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.2598598003387451s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.023065805435180664s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0009429454803466797s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 4.100799560546875e-05s
Believability | Calculation of trust value for E-Government Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for EGovOntology took 3.8014602661132812s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5717945098876953s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0006489753723144531s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.2378201484680176s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.401339054107666s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6789727210998535s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8356127738952637s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.39825630187988s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.906435251235962s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7454977035522461s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8400349617004395s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.35341858863830566s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.49213552474975586s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.501171112060547s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.290252685546875s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4512028694152832s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7194206714630127s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3475053310394287s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25100207328796387s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27109336853027344s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.292722940444946s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 6.937980651855469e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3897523880004883s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2991044521331787s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5404298305511475s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24995017051696777s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3883087635040283s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.7488348484039307s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2639133930206299s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.934123754501343s
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.25142955780029297s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.36705589294433594s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3711397647857666s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.4016101360321045s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02768683433532715s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.029958248138427734s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24730682373046875s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.388731479644775s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.44677734375s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.6014723777770996s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1715869903564453s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.776907682418823s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.034307241439819336s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5115764141082764s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5903744697570801s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3385.5709409713745s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.712364673614502s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.021341800689697266s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.3882598876953125e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 4.76837158203125e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 7.867813110351562e-06s
INFO | --- Analysis for ei2a took 18904.101163625717s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.315376281738281e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.25713372230529785s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020206212997436523s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010609626770019531s
Believability | Calculation of trust value for EIONET RDF Data took 5.245208740234375e-06s
INFO | --- Analysis for eionet-rdf took 4.4498772621154785s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.220008850097656e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.6844165325164795s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.020559310913085938s
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.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 2.8848648071289062e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 7.62939453125e-06s
INFO | --- Analysis for ElgooG_ took 3.6809442043304443s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.076957702636719e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.2613942623138428s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 2.9802322387695312e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 7.3909759521484375e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 3.8474066257476807s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 30.46706485748291s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.29640936851501465s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 8.058547973632812e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 7.62939453125e-06s
INFO | --- Analysis for elviajero took 154.57951879501343s
Availability | SPARQL endpoint availability check for EMN took 4.2438507080078125e-05s
Availability | VoID file availability check for EMN took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for EMN took 0.2865641117095947s
Reputation | Calculation of the PageRank for EMN took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for EMN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for EMN took 4.029273986816406e-05s
Believability | Calculation of trust value for EMN took 7.3909759521484375e-06s
INFO | --- Analysis for emn took 3.5752389430999756s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.7384529113769531s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.030632019042969e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 4.291534423828125e-06s
INFO | --- Analysis for enakting-co2emission took 3.4106059074401855s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.124641418457031e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.2928135395050049s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.910064697265625e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-crime took 2.9290237426757812s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.2611265182495117s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.838539123535156e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-energy took 2.912088632583618s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.267692565917969e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.26755547523498535s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.036064147949219e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-mortality took 2.8657736778259277s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.263045072555542s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.7670135498046875e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-nhs took 2.5508365631103516s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.26380133628845215s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.269050598144531e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 5.7220458984375e-06s
INFO | --- Analysis for enakting-population took 2.508291482925415s
Availability | SPARQL endpoint availability check for Enel Shops took 3.9577484130859375e-05s
Availability | VoID file availability check for Enel Shops took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.2753419876098633s
Reputation | Calculation of the PageRank for Enel Shops took 0.021809816360473633s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0009632110595703125s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.838539123535156e-05s
Believability | Calculation of trust value for Enel Shops took 7.867813110351562e-06s
INFO | --- Analysis for enel-shops took 2.999732494354248s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.172325134277344e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.24571752548217773s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.0994415283203125e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 6.4373016357421875e-06s
INFO | --- Analysis for energy-efficiency took 2.9725942611694336s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.26753735542297363s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0008077621459960938s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.170967102050781e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.9204471111297607s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.029273986816406e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.00030922889709472656s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.2776753902435303s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.218650817871094e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.9685637950897217s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.2783982753753662s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0008227825164794922s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.361701965332031e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 3.0342702865600586s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 3.910064697265625e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00021457672119140625s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.2897157669067383s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020700693130493164s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 2.8848648071289062e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.9177770614624023s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.2789342403411865s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 2.956390380859375e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.956418514251709s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.2441399097442627s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.020710468292236328s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.337860107421875e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.9679760932922363s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.00543212890625e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.27452993392944336s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.123283386230469e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 3.433228015899658s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 1.0246930122375488s
Availability | VoID file availability check for English Heritage Periods List took 0.0007476806640625s
Extra | Recovery of all triples for English Heritage Periods List took 0.3989999294281006s
Performance | Total latancy measurement for English Heritage Periods List took 2.0754263401031494s
Amount of data | Number of triples check for English Heritage Periods List took 0.5122890472412109s
Versatility | Languages check for English Heritage Periods List took 0.3388078212738037s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5556490421295166s
Security | Check HTTPS for English Heritage Periods List took 0.36079883575439453s
Interpretability | RDF structures check for English Heritage Periods List took 0.3446171283721924s
Versatility | Serialization formats check for English Heritage Periods List took 1.2308869361877441s
Availability | RDF dump link check for English Heritage Periods List took 0.38452911376953125s
License | MR license check for English Heritage Periods List took 0.45465517044067383s
License | HR license check for English Heritage Periods List took 0.4140324592590332s
Amount of data | Number of property check for English Heritage Periods List took 0.6190409660339355s
Understandability | Number of label check for English Heritage Periods List took 0.5916130542755127s
Understandability | URI regex check for English Heritage Periods List took 0.9388573169708252s
Understandability | Vocabs check for English Heritage Periods List took 0.44660401344299316s
Verifiability | Authors check for English Heritage Periods List took 0.4509422779083252s
Verifiability | Publishers check for English Heritage Periods List took 0.40701842308044434s
Performance | Throughput check for English Heritage Periods List took 12.590764284133911s
Amount of data | Check the number of entities for English Heritage Periods List took 6.985664367675781e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.41869401931762695s
Interlinking | sameAs chians check for English Heritage Periods List took 0.430448055267334s
Interlinking | skos check for English Heritage Periods List took 0.439774751663208s
Interlinking | skos check for English Heritage Periods List took 0.39609432220458984s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.5406007766723633s
Currency | Creation date check for English Heritage Periods List took 0.8215305805206299s
Currency | Modification date check for English Heritage Periods List took 0.9459941387176514s
Rep.Conc. | URIs length for English Heritage Periods List took 0.8189823627471924s
Interoperability | New vocabularies check for English Heritage Periods List took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.43064260482788086s
Accuracy | Check Functional Property for English Heritage Periods List took 0.4146692752838135s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.4167451858520508s
Consistency | Disjoint class check for English Heritage Periods List took 0.417161226272583s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.4020040035247803s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6233603954315186s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0006375312805175781s
Security | Sign check for English Heritage Periods List took 0.4407327175140381s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.3928794860839844s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Periods List took 8.106231689453125e-06s
INFO | --- Analysis for english-heritage-periods-list took 85.14137554168701s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.7673852443695068s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.2851886749267578s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.457069396972656e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 5.9604644775390625e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 3.926729917526245s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.2821226119995117s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.26761531829833984s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020956993103027344s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.457069396972656e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.7220458984375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 3.829580545425415s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 3.886222839355469e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.00030517578125s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.2969660758972168s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.020783185958862305s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.337860107421875e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 1.9073486328125e-05s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 3.07035493850708s
Availability | SPARQL endpoint availability check for English WordNet took 4.2438507080078125e-05s
Availability | VoID file availability check for English WordNet took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for English WordNet took 0.28851819038391113s
Reputation | Calculation of the PageRank for English WordNet took 0.02091693878173828s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.62396240234375e-05s
Believability | Calculation of trust value for English WordNet took 6.4373016357421875e-06s
INFO | --- Analysis for english-wordnet took 3.556692123413086s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.1484832763671875e-05s
Availability | VoID file availability check for English Heritage Places took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.28635239601135254s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020951032638549805s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.0517578125e-05s
Believability | Calculation of trust value for English Heritage Places took 6.198883056640625e-06s
INFO | --- Analysis for englishheritage_places took 3.050948143005371s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.16675114631652832s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.2691612243652344s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.726119995117188e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 8.58306884765625e-06s
INFO | --- Analysis for enipedia took 2.608781099319458s
Availability | SPARQL endpoint availability check for Enslaved.org took 4.8160552978515625e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2886195182800293s
Reputation | Calculation of the PageRank for Enslaved.org took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 2.9802322387695312e-05s
Believability | Calculation of trust value for Enslaved.org took 8.106231689453125e-06s
INFO | --- Analysis for enslaved.org took 5.329493284225464s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 60.0537850856781s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.29456329345703125s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020952224731445312s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.221366882324219e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 6.198883056640625e-06s
INFO | --- Analysis for entice-graph took 142.66442561149597s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.38690185546875e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008165836334228516s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.2633507251739502s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020490646362304688s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.790855407714844e-05s
Believability | Calculation of trust value for Entrez Gene took 7.62939453125e-06s
INFO | --- Analysis for entrez_gene took 38.09150958061218s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.220008850097656e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0003376007080078125s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.28392481803894043s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0008871555328369141s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.337860107421875e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.62939453125e-06s
INFO | --- Analysis for entrez_gene_extract took 2.9694671630859375s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.2130498886108398s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.26639223098754883s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020348548889160156s
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.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 4.9591064453125e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 5.7220458984375e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 12.293519020080566s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.34642934799194336s
Availability | VoID file availability check for environment.data.gov.uk took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.2757077217102051s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020358800888061523s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.363059997558594e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.9244544506073s
Availability | SPARQL endpoint availability check for EARTh took 272.08032870292664s
Availability | VoID file availability check for EARTh took 0.0003783702850341797s
Completeness | Calculation of interlinking completeness for EARTh took 0.6709084510803223s
Reputation | Calculation of the PageRank for EARTh took 0.020456314086914062s
Interlinking | Calculation of Degree of Connection for EARTh took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010180473327636719s
Believability | Calculation of trust value for EARTh took 1.71661376953125e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 563.515683889389s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.5908222198486328s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0002617835998535156s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 114.21781969070435s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.9423744678497314s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 8.529332876205444s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 15.306139945983887s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.2340466976166s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.696871519088745s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.2624526023864746s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 9.489985227584839s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.33443498611450195s
License | MR license check for Micka (EO metadata) @PSNC took 0.6293866634368896s
License | HR license check for Micka (EO metadata) @PSNC took 300.22598457336426s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.5258750915527344s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 2.5842764377593994s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.8653671741485596s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.4608147144317627s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.20417237281799316s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.2546215057373047s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.4520583152771s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 6.842613220214844e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.2046971321105957s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.20162010192871094s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.46929335594177246s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4509260654449463s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 6.7205376625061035s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.4611387252807617s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.24383783340454102s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 173.37628722190857s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.19811034202575684s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.30921196937561035s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.323544979095459s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 39.00081205368042s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.6824774742126465s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.593534231185913s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.20805621147155762s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 102.06423115730286s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.486635684967041s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 38.658860206604004s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.27601957321167s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 87.359783411026s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.7872862815856934s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5750527381896973s
Security | Sign check for Micka (EO metadata) @PSNC took 0.7185325622558594s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 5.840744495391846s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.9705288410186768s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021024465560913086s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 3.218650817871094e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for EO_metadata took 2308.065339565277s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.7206878662109375e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.001455068588256836s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.7004590034484863s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.24249267578125e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 5.7220458984375e-06s
INFO | --- Analysis for EOKP-Datasets took 4.966518878936768s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.315376281738281e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.24944400787353516s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.62396240234375e-05s
Believability | Calculation of trust value for EPA-CDR took 5.4836273193359375e-06s
INFO | --- Analysis for epa-cdr took 10.205987930297852s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.267692565917969e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.27899789810180664s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020885467529296875s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.224082946777344e-05s
Believability | Calculation of trust value for EPA-FRS took 5.0067901611328125e-06s
INFO | --- Analysis for epa-frs took 7.154486656188965s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.220008850097656e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.7224268913269043s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020938396453857422s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.2901763916015625e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.0067901611328125e-06s
INFO | --- Analysis for epa-rcra took 6.128076076507568s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.1961669921875e-05s
Availability | VoID file availability check for EPA-SRS took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.2878735065460205s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020865440368652344s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.414817810058594e-05s
Believability | Calculation of trust value for EPA-SRS took 5.0067901611328125e-06s
INFO | --- Analysis for epa-srs took 6.240646123886108s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.220008850097656e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2740747928619385s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020920753479003906s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.5762786865234375e-05s
Believability | Calculation of trust value for EPA-TRI took 6.4373016357421875e-06s
INFO | --- Analysis for epa-tri took 5.788384914398193s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 5.5789947509765625e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.25071144104003906s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.200241088867188e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 6.9141387939453125e-06s
INFO | --- Analysis for epo took 3.367673873901367s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.05227231979370117s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.26947522163391113s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.021552562713623047s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001308917999267578s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 5.4836273193359375e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 3.0255777835845947s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.4310617446899414s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.27350640296936035s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.02087998390197754s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 7.939338684082031e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 5.9604644775390625e-06s
INFO | --- Analysis for eprtr took 3.6213033199310303s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.8849730491638184s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.2702455520629883s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.337860107421875e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 6.9141387939453125e-06s
INFO | --- Analysis for ERAKG took 3.3350212574005127s
Availability | SPARQL endpoint availability check for reg took 4.220008850097656e-05s
Availability | VoID file availability check for reg took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for reg took 0.26816534996032715s
Reputation | Calculation of the PageRank for reg took 0.020705461502075195s
Interlinking | Calculation of Degree of Connection for reg took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for reg took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for reg took 1.2874603271484375e-05s
Believability | Calculation of trust value for reg took 6.198883056640625e-06s
INFO | --- Analysis for erg took 2.396453380584717s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 30.15975594520569s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007758140563964844s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2887997627258301s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.0279159545898438e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 5.9604644775390625e-06s
INFO | --- Analysis for es-msssi-drug-prices took 103.78476786613464s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.267692565917969e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.294278621673584s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.702278137207031e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 5.9604644775390625e-06s
INFO | --- Analysis for esd-standards took 4.621545791625977s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.1961669921875e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.2741084098815918s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.081031799316406e-05s
Believability | Calculation of trust value for ESD-Toolkit took 5.0067901611328125e-06s
INFO | --- Analysis for esd-toolkit took 4.105121850967407s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.267692565917969e-05s
Availability | VoID file availability check for Dataset Esis took 0.0011107921600341797s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.29326486587524414s
Reputation | Calculation of the PageRank for Dataset Esis took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 2.9087066650390625e-05s
Believability | Calculation of trust value for Dataset Esis took 6.9141387939453125e-06s
INFO | --- Analysis for esislearning took 2.8220627307891846s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 5.459785461425781e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.29123973846435547s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.743171691894531e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 6.9141387939453125e-06s
INFO | --- Analysis for ESV took 4.116703748703003s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.5638308525085449s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.26107263565063477s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0008080005645751953s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 4.029273986816406e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.1444091796875e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.0390260219573975s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 4.694671869277954s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.27533650398254395s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020589113235473633s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.224082946777344e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 6.67572021484375e-06s
INFO | --- Analysis for eu-agencies-bodies took 13.15030574798584s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 5.1975250244140625e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.26149868965148926s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.0517578125e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 5.4836273193359375e-06s
INFO | --- Analysis for eu-dgt-tm took 3.0074498653411865s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.100799560546875e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.3065500259399414s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.02076268196105957s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.05718994140625e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 4.76837158203125e-06s
INFO | --- Analysis for eu-institutions took 6.132188558578491s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.8705699443817139s
Availability | VoID file availability check for EU Parliament Media Library took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.28176379203796387s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020662546157836914s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.4809112548828125e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 5.245208740234375e-06s
INFO | --- Analysis for eu-parliament-media took 6.416291952133179s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.8368823528289795s
Availability | VoID file availability check for EU Who Is Who took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2701687812805176s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.790855407714844e-05s
Believability | Calculation of trust value for EU Who Is Who took 5.245208740234375e-06s
INFO | --- Analysis for eu-who-is-who took 9.792028427124023s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.8000874519348145s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.2617483139038086s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.029273986816406e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 4.5299530029296875e-06s
INFO | --- Analysis for eumida-linked-data took 7.684323787689209s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.36447739601135254s
Availability | VoID file availability check for European Nature Information System took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.27702927589416504s
Reputation | Calculation of the PageRank for European Nature Information System took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010704994201660156s
Believability | Calculation of trust value for European Nature Information System took 6.198883056640625e-06s
INFO | --- Analysis for eunis took 8.391211748123169s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 4.420691251754761s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.26260900497436523s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020589113235473633s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 8.940696716308594e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for eur-lex-rdf took 12.573418140411377s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.7808277606964111s
Availability | VoID file availability check for Standard Eurobarometer took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.26065802574157715s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.1961669921875e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 4.291534423828125e-06s
INFO | --- Analysis for eurobarometer-standard took 7.477809190750122s
Availability | SPARQL endpoint availability check for European Election Results took 0.8961598873138428s
Availability | VoID file availability check for European Election Results took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2787492275238037s
Reputation | Calculation of the PageRank for European Election Results took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.695487976074219e-05s
Believability | Calculation of trust value for European Election Results took 5.0067901611328125e-06s
INFO | --- Analysis for european-election-results took 7.586767196655273s
Availability | SPARQL endpoint availability check for EPO patents took 0.4623901844024658s
Availability | VoID file availability check for EPO patents took 0.0005443096160888672s
Extra | Recovery of all triples for EPO patents took 45.595951557159424s
Performance | Total latancy measurement for EPO patents took 1.040419340133667s
Amount of data | Number of triples check for EPO patents took 90.17651844024658s
Versatility | Languages check for EPO patents took 120.10338497161865s
Interpretability | Number of blank nodes check for EPO patents took 90.30221271514893s
Interpretability | RDF structures check for EPO patents took 0.16213035583496094s
Versatility | Serialization formats check for EPO patents took 0.368086576461792s
Availability | RDF dump link check for EPO patents took 0.26362013816833496s
License | MR license check for EPO patents took 0.1686687469482422s
License | HR license check for EPO patents took 90.3337333202362s
Amount of data | Number of property check for EPO patents took 0.27217578887939453s
Understandability | Number of label check for EPO patents took 90.21660709381104s
Understandability | URI regex check for EPO patents took 0.6168539524078369s
Understandability | Vocabs check for EPO patents took 0.17711377143859863s
Verifiability | Authors check for EPO patents took 0.19602108001708984s
Verifiability | Publishers check for EPO patents took 0.3094472885131836s
Performance | Throughput check for EPO patents took 11.28588080406189s
Amount of data | Check the number of entities for EPO patents took 7.963180541992188e-05s
Verifiability | Contribs. check for EPO patents took 0.21087336540222168s
Interlinking | sameAs chians check for EPO patents took 0.17776131629943848s
Interlinking | skos check for EPO patents took 0.3326272964477539s
Interlinking | skos check for EPO patents took 0.27187275886535645s
Timeliness | dataset update frequency check for EPO patents took 0.31122708320617676s
Currency | Creation date check for EPO patents took 0.4972813129425049s
Currency | Modification date check for EPO patents took 0.3336617946624756s
Rep.Conc. | URIs length for EPO patents took 153.92947244644165s
Interoperability | New vocabularies check for EPO patents took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.19762659072875977s
Accuracy | Check Empty annotation labels for EPO patents took 17.824633359909058s
Accuracy | Check White space in annotation for EPO patents took 2.985769033432007s
Accuracy | Check Datatype consistency for EPO patents took 4.916509389877319s
Consistency | Disjoint class check for EPO patents took 0.2705669403076172s
Consistency | Check Misplaced properties for EPO patents took 120.46740484237671s
Consistency | Check Ontology hijacking for EPO patents took 21.289790153503418s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.4409563541412354s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.45383644104004s
Conciseness | Check Extensional conciseness for EPO patents took 2.8547580242156982s
Conciseness | Check Intensional conciseness for EPO patents took 0.40123867988586426s
Security | Sign check for EPO patents took 0.1881399154663086s
Availability | Check URIs Dereferenciability for EPO patents took 1.9762768745422363s
Completeness | Calculation of interlinking completeness for EPO patents took 0.6513817310333252s
Reputation | Calculation of the PageRank for EPO patents took 0.021259307861328125s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 2.384185791015625e-06s
Believability | Calculation of trust value for EPO patents took 8.344650268554688e-06s
INFO | --- Analysis for European_Patent_Information took 1313.2099294662476s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 6.651878356933594e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.6803855895996094s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.4332275390625e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 8.821487426757812e-06s
INFO | --- Analysis for europeana-lod took 6.0402867794036865s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.220008850097656e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.31723952293395996s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 0.00010752677917480469s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 7.152557373046875e-06s
INFO | --- Analysis for europeana-lod-v1 took 8.089354991912842s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.05925941467285156s
Availability | VoID file availability check for Europeana SPARQL took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.27205610275268555s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.6253204345703125e-05s
Believability | Calculation of trust value for Europeana SPARQL took 7.152557373046875e-06s
INFO | --- Analysis for europeana-sparql took 4.686713457107544s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07737088203430176s
Availability | VoID file availability check for EuroSentiment took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.32671356201171875s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.62396240234375e-05s
Believability | Calculation of trust value for EuroSentiment took 7.62939453125e-06s
INFO | --- Analysis for eurosentiment took 4.261662006378174s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.1961669921875e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.28145527839660645s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.724761962890625e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.7220458984375e-06s
INFO | --- Analysis for eurostat-rdf took 13.444216012954712s
Availability | SPARQL endpoint availability check for EuroVoc took 0.440443754196167s
Availability | VoID file availability check for EuroVoc took 0.0006396770477294922s
Extra | Recovery of all triples for EuroVoc took 601.2130556106567s
Performance | Total latancy measurement for EuroVoc took 0.5841152667999268s
Amount of data | Number of triples check for EuroVoc took 98.26741170883179s
Interoperability | New terms check for EuroVoc took 114.39286923408508s
Versatility | Languages check for EuroVoc took 300.1286838054657s
Interpretability | Number of blank nodes check for EuroVoc took 1.568192958831787s
Security | Check HTTPS for EuroVoc took 0.30359315872192383s
Interpretability | RDF structures check for EuroVoc took 0.4821460247039795s
Versatility | Serialization formats check for EuroVoc took 17.690675973892212s
Availability | RDF dump link check for EuroVoc took 0.20565247535705566s
License | MR license check for EuroVoc took 0.23610687255859375s
License | HR license check for EuroVoc took 300.10273265838623s
Amount of data | Number of property check for EuroVoc took 0.23009252548217773s
Understandability | Number of label check for EuroVoc took 6.387984275817871s
Understandability | URI regex check for EuroVoc took 0.26268839836120605s
Understandability | Vocabs check for EuroVoc took 0.11932229995727539s
Verifiability | Authors check for EuroVoc took 0.16785287857055664s
Verifiability | Publishers check for EuroVoc took 0.24737834930419922s
Performance | Throughput check for EuroVoc took 10.55790901184082s
Amount of data | Check the number of entities for EuroVoc took 7.557868957519531e-05s
Verifiability | Contribs. check for EuroVoc took 0.13906478881835938s
Interlinking | sameAs chians check for EuroVoc took 9.021932125091553s
Interlinking | skos check for EuroVoc took 0.43914794921875s
Interlinking | skos check for EuroVoc took 0.44936203956604004s
Timeliness | dataset update frequency check for EuroVoc took 0.25862574577331543s
Currency | Creation date check for EuroVoc took 0.49692320823669434s
Currency | Modification date check for EuroVoc took 0.22097134590148926s
Rep.Conc. | URIs length for EuroVoc took 598.0281660556793s
Interoperability | New vocabularies check for EuroVoc took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.18316411972045898s
Accuracy | Check Functional Property for EuroVoc took 0.16305971145629883s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.12978482246398926s
Accuracy | Check Empty annotation labels for EuroVoc took 114.67876315116882s
Accuracy | Check White space in annotation for EuroVoc took 3.1768200397491455s
Accuracy | Check Datatype consistency for EuroVoc took 2.611098051071167s
Consistency | Disjoint class check for EuroVoc took 0.19561314582824707s
Consistency | Check Misplaced properties for EuroVoc took 300.79730439186096s
Consistency | Misplaced classes for EuroVoc took 8.606454849243164s
Consistency | Check Ontology hijacking for EuroVoc took 119.24678587913513s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.3871326446533203s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.487863779068s
Conciseness | Check Extensional conciseness for EuroVoc took 3.0238730907440186s
Conciseness | Check Intensional conciseness for EuroVoc took 0.7861928939819336s
Security | Sign check for EuroVoc took 0.16400694847106934s
Availability | Check URIs Dereferenciability for EuroVoc took 4.0576698780059814s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.5762240886688232s
Reputation | Calculation of the PageRank for EuroVoc took 0.02110886573791504s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 7.605552673339844e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.9073486328125e-06s
Believability | Calculation of trust value for EuroVoc took 6.67572021484375e-06s
INFO | --- Analysis for eurovoc took 15969.714076757431s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.267692565917969e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.7002978324890137s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020913362503051758s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.4345855712890625e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 6.67572021484375e-06s
INFO | --- Analysis for eurovoc-in-skos took 5.22824501991272s
Availability | SPARQL endpoint availability check for European Television Heritage took 5.14984130859375e-05s
Availability | VoID file availability check for European Television Heritage took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.2519059181213379s
Reputation | Calculation of the PageRank for European Television Heritage took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 2.8133392333984375e-05s
Believability | Calculation of trust value for European Television Heritage took 7.152557373046875e-06s
INFO | --- Analysis for euscreen took 4.30869197845459s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.220008850097656e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.6922552585601807s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.2438507080078125e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 5.0067901611328125e-06s
INFO | --- Analysis for euskadi-farmacias took 6.209090948104858s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7684423923492432s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.2664530277252197s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 2.9325485229492188e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 6.9141387939453125e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.856184720993042s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.2918100357055664s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.26198792457580566s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.128715515136719e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 6.9141387939453125e-06s
INFO | --- Analysis for eutc-productions took 7.794637441635132s
Availability | SPARQL endpoint availability check for EventMedia took 0.40132761001586914s
Availability | VoID file availability check for EventMedia took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for EventMedia took 0.27252912521362305s
Reputation | Calculation of the PageRank for EventMedia took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for EventMedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EventMedia took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010967254638671875s
Believability | Calculation of trust value for EventMedia took 7.152557373046875e-06s
INFO | --- Analysis for event-media took 10.516547679901123s
Availability | SPARQL endpoint availability check for EventKG took 8.535385131835938e-05s
Availability | VoID file availability check for EventKG took 0.0003542900085449219s
Completeness | Calculation of interlinking completeness for EventKG took 0.25780558586120605s
Reputation | Calculation of the PageRank for EventKG took 0.020162582397460938s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.034706115722656e-05s
Believability | Calculation of trust value for EventKG took 6.9141387939453125e-06s
INFO | --- Analysis for eventkg took 4.750591993331909s
Availability | SPARQL endpoint availability check for Eventseer took 0.6001744270324707s
Availability | VoID file availability check for Eventseer took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Eventseer took 0.2805750370025635s
Reputation | Calculation of the PageRank for Eventseer took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for Eventseer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eventseer took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.4345855712890625e-05s
Believability | Calculation of trust value for Eventseer took 6.9141387939453125e-06s
INFO | --- Analysis for eventseer took 3.1681156158447266s
Availability | SPARQL endpoint availability check for Face Link took 4.172325134277344e-05s
Availability | VoID file availability check for Face Link took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for Face Link took 0.2565441131591797s
Reputation | Calculation of the PageRank for Face Link took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for Face Link took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Face Link took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.0279159545898438e-05s
Believability | Calculation of trust value for Face Link took 6.198883056640625e-06s
INFO | --- Analysis for Face_Link took 2.394223213195801s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 3.933906555175781e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.24898934364318848s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 2.6702880859375e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 7.152557373046875e-06s
INFO | --- Analysis for facebook-lids took 3.894061326980591s
Availability | SPARQL endpoint availability check for Fact Forge took 4.00543212890625e-05s
Availability | VoID file availability check for Fact Forge took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.27089571952819824s
Reputation | Calculation of the PageRank for Fact Forge took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for Fact Forge took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 2.6702880859375e-05s
Believability | Calculation of trust value for Fact Forge took 6.9141387939453125e-06s
INFO | --- Analysis for fact-forge took 2.9535675048828125s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5707409381866455s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0002796649932861328s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 123.98313808441162s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9533698558807373s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.372722625732422s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.53176236152649s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.17445635795593s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6055901050567627s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.24799585342407227s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.92511773109436s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2794666290283203s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5198228359222412s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.1836884021759s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4876112937927246s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.668675661087036s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.8277201652526855s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4543881416320801s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2298591136932373s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.27028393745422363s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.402200698852539s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0001380443572998047s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19882893562316895s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2118818759918213s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4830002784729004s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4806392192840576s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.753035545349121s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.49139928817749023s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22799253463745117s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 168.39656615257263s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19659137725830078s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.37847018241882324s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3832249641418457s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 40.60390496253967s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.684459924697876s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6569321155548096s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.195098876953125s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 84.63642740249634s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.390888214111328s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 41.6280198097229s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2104198932647705s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 88.15393543243408s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.7626233100891113s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5968704223632812s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.8456346988677979s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.793152809143066s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3948757648468018s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020839214324951172s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.173683166503906e-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 8.344650268554688e-06s
INFO | --- Analysis for FADN_(2019) took 2304.63570189476s
Availability | SPARQL endpoint availability check for FAMEData took 4.315376281738281e-05s
Availability | VoID file availability check for FAMEData took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for FAMEData took 0.7115890979766846s
Reputation | Calculation of the PageRank for FAMEData took 0.0214235782623291s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.147125244140625e-05s
Believability | Calculation of trust value for FAMEData took 9.5367431640625e-06s
INFO | --- Analysis for famedata took 65.12751984596252s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 6.508827209472656e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.2766387462615967s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020870208740234375s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00010180473327636719s
Believability | Calculation of trust value for FAO geopolitical ontology took 5.0067901611328125e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 10.797138690948486s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.5528185367584229s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.28481268882751465s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.02016925811767578s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.775161743164062e-05s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for fao-linked-data took 4.81550669670105s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.1961669921875e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.2551755905151367s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 2.8371810913085938e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for FAO_species took 3.7253644466400146s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.651535034179688s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.25884532928466797s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020606040954589844s
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.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.38690185546875e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 8.106231689453125e-06s
INFO | --- Analysis for farmbio-chembl took 66.65001821517944s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 7.724761962890625e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.25321173667907715s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 2.765655517578125e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 6.67572021484375e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 4.279835224151611s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.0531158447265625e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.7637360095977783s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020753860473632812s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 4.1961669921875e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 7.152557373046875e-06s
INFO | --- Analysis for farolapp-dataset took 4.7651002407073975s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.124641418457031e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.27161455154418945s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 2.765655517578125e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 5.9604644775390625e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 3.4219772815704346s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.291534423828125e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.2778160572052002s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.0994415283203125e-05s
Believability | Calculation of trust value for I4.0-Onto took 8.821487426757812e-06s
INFO | --- Analysis for fatimazahra took 2.375684976577759s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.7206878662109375e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.26431989669799805s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0008203983306884766s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.0279159545898438e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 7.152557373046875e-06s
INFO | --- Analysis for federal-economic-rdf took 3.2715933322906494s
Availability | SPARQL endpoint availability check for Feed Wrapper took 7.414817810058594e-05s
Availability | VoID file availability check for Feed Wrapper took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.2787032127380371s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.0203399658203125s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 2.8371810913085938e-05s
Believability | Calculation of trust value for Feed Wrapper took 7.3909759521484375e-06s
INFO | --- Analysis for feedwrapper-lids took 3.4121217727661133s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.1961669921875e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.27774715423583984s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.02032327651977539s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.6702880859375e-05s
Believability | Calculation of trust value for FHIR STU3 took 6.9141387939453125e-06s
INFO | --- Analysis for FHIR_STU3 took 2.7608001232147217s
Availability | SPARQL endpoint availability check for FiESTA took 4.1961669921875e-05s
Availability | VoID file availability check for FiESTA took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for FiESTA took 0.2623288631439209s
Reputation | Calculation of the PageRank for FiESTA took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for FiESTA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FiESTA took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.790855407714844e-05s
Believability | Calculation of trust value for FiESTA took 7.152557373046875e-06s
INFO | --- Analysis for fiesta took 12.674753427505493s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 5.173683166503906e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00034546852111816406s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.2946436405181885s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.8133392333984375e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.3909759521484375e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.428945302963257s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 6.985664367675781e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.7891342639923096s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020455598831176758s
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.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.43865966796875e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.245208740234375e-06s
INFO | --- Analysis for finnish-municipalities took 134.5797140598297s
Availability | SPARQL endpoint availability check for firmao took 4.267692565917969e-05s
Availability | VoID file availability check for firmao took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for firmao took 0.704399585723877s
Reputation | Calculation of the PageRank for firmao took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for firmao took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for firmao took 2.8848648071289062e-05s
Believability | Calculation of trust value for firmao took 7.867813110351562e-06s
INFO | --- Analysis for firmao took 3.9111523628234863s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.2913081645965576s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.02258777618408203s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.337860107421875e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 3.0177841186523438s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.18334150314331055s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0002830028533935547s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 114.06055164337158s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.9667248725891113s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 8.92209506034851s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 16.219332695007324s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.25621700286865s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.95344614982605s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.26423192024230957s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 12.114416360855103s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.318617582321167s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.5418610572814941s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.23266768455505s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.2013096809387207s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 2.7023239135742188s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.7438437938690186s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.39591550827026367s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.21608781814575195s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.25406885147094727s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.498310327529907s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 7.343292236328125e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.20498251914978027s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.18337535858154297s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.5025537014007568s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4686429500579834s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 6.051288843154907s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.5131816864013672s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.24271845817565918s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 173.12223291397095s
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.2020573616027832s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.31013059616088867s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.18140673637390137s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 36.10448384284973s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.673938274383545s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.5982162952423096s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.21013808250427246s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 91.36092901229858s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.512954711914062s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 33.25276255607605s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.2139568328857422s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 86.36306738853455s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.7904977798461914s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.5659041404724121s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.19518303871154785s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 9.427780866622925s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 1.6227929592132568s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.020854711532592773s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0009124279022216797s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.790855407714844e-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 7.3909759521484375e-06s
INFO | --- Analysis for Fishery_Stock_Dataset took 2251.6563272476196s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.315376281738281e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.2833895683288574s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.654594421386719e-05s
Believability | Calculation of trust value for Fishes of Texas took 9.059906005859375e-06s
INFO | --- Analysis for fishes-of-texas took 4.724179744720459s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.124641418457031e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.29157280921936035s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.02077960968017578s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.298324584960938e-05s
Believability | Calculation of trust value for flickr? wrappr took 6.9141387939453125e-06s
INFO | --- Analysis for flickr-wrappr took 4.104370355606079s
Availability | SPARQL endpoint availability check for flickr.person took 4.029273986816406e-05s
Availability | VoID file availability check for flickr.person took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for flickr.person took 0.7178871631622314s
Reputation | Calculation of the PageRank for flickr.person took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for flickr.person took 2.8371810913085938e-05s
Believability | Calculation of trust value for flickr.person took 7.867813110351562e-06s
INFO | --- Analysis for flickr_person took 3.483480215072632s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.0531158447265625e-05s
Availability | VoID file availability check for flickr.videoobject took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.7668766975402832s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.075599670410156e-05s
Believability | Calculation of trust value for flickr.videoobject took 7.867813110351562e-06s
INFO | --- Analysis for flickr_videoobject took 3.959303855895996s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.5299530029296875e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.2709364891052246s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0010044574737548828s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.814697265625e-05s
Believability | Calculation of trust value for Future land use simulation model took 7.3909759521484375e-06s
INFO | --- Analysis for FLUS took 8.803529500961304s
Availability | SPARQL endpoint availability check for Fly-TED took 3.9577484130859375e-05s
Availability | VoID file availability check for Fly-TED took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.29087114334106445s
Reputation | Calculation of the PageRank for Fly-TED took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.075599670410156e-05s
Believability | Calculation of trust value for Fly-TED took 7.152557373046875e-06s
INFO | --- Analysis for fly-ted took 3.0719761848449707s
Availability | SPARQL endpoint availability check for FlyAtlas took 3.981590270996094e-05s
Availability | VoID file availability check for FlyAtlas took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.2877328395843506s
Reputation | Calculation of the PageRank for FlyAtlas took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.0517578125e-05s
Believability | Calculation of trust value for FlyAtlas took 8.106231689453125e-06s
INFO | --- Analysis for flyatlas took 2.9921798706054688s
Availability | SPARQL endpoint availability check for Flybase took 15.705479383468628s
Availability | VoID file availability check for Flybase took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Flybase took 0.2691042423248291s
Reputation | Calculation of the PageRank for Flybase took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.504753112792969e-05s
Believability | Calculation of trust value for Flybase took 8.106231689453125e-06s
INFO | --- Analysis for flybase took 24.260875463485718s
Availability | SPARQL endpoint availability check for Flyted took 12.625920295715332s
Availability | VoID file availability check for Flyted took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Flyted took 0.2812826633453369s
Reputation | Calculation of the PageRank for Flyted took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Flyted took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Flyted took 2.8848648071289062e-05s
Believability | Calculation of trust value for Flyted took 8.344650268554688e-06s
INFO | --- Analysis for flyted took 23.191844940185547s
Availability | SPARQL endpoint availability check for Foodista took 1.0745446681976318s
Availability | VoID file availability check for Foodista took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Foodista took 0.7077658176422119s
Reputation | Calculation of the PageRank for Foodista took 0.02064204216003418s
Interlinking | Calculation of Degree of Connection for Foodista took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.9802322387695312e-05s
Believability | Calculation of trust value for Foodista took 7.867813110351562e-06s
INFO | --- Analysis for foodista took 12.42120361328125s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.17774605751037598s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2698652744293213s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.033348083496094e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 5.9604644775390625e-06s
INFO | --- Analysis for foodpedia took 3.038649320602417s
Availability | SPARQL endpoint availability check for FORGE Course information took 3.981590270996094e-05s
Availability | VoID file availability check for FORGE Course information took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.2726626396179199s
Reputation | Calculation of the PageRank for FORGE Course information took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 2.9325485229492188e-05s
Believability | Calculation of trust value for FORGE Course information took 6.4373016357421875e-06s
INFO | --- Analysis for forge-course-information took 3.0117595195770264s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.57763671875e-05s
Availability | VoID file availability check for FrameBase schema took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.27072787284851074s
Reputation | Calculation of the PageRank for FrameBase schema took 0.020704269409179688s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.458427429199219e-05s
Believability | Calculation of trust value for FrameBase schema took 6.4373016357421875e-06s
INFO | --- Analysis for framebase-schema took 3.5230295658111572s
Availability | SPARQL endpoint availability check for FrameNet took 3.981590270996094e-05s
Availability | VoID file availability check for FrameNet took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for FrameNet took 0.2877213954925537s
Reputation | Calculation of the PageRank for FrameNet took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for FrameNet took 2.8848648071289062e-05s
Believability | Calculation of trust value for FrameNet took 6.4373016357421875e-06s
INFO | --- Analysis for framenet took 3.4172303676605225s
Availability | SPARQL endpoint availability check for Framester took 4.1961669921875e-05s
Availability | VoID file availability check for Framester took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for Framester took 0.2551846504211426s
Reputation | Calculation of the PageRank for Framester took 0.02062201499938965s
Interlinking | Calculation of Degree of Connection for Framester took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Framester took 7.295608520507812e-05s
Believability | Calculation of trust value for Framester took 6.4373016357421875e-06s
INFO | --- Analysis for framester took 3.541658878326416s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.15845751762390137s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0003495216369628906s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2500581741333008s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.416175842285156e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for frb-linked-data took 2.9949119091033936s
Availability | SPARQL endpoint availability check for Freebase took 4.220008850097656e-05s
Availability | VoID file availability check for Freebase took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Freebase took 0.2875382900238037s
Reputation | Calculation of the PageRank for Freebase took 0.02020263671875s
Interlinking | Calculation of Degree of Connection for Freebase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00026917457580566406s
Believability | Calculation of trust value for Freebase took 7.867813110351562e-06s
INFO | --- Analysis for freebase took 4.064402103424072s
Availability | SPARQL endpoint availability check for Freeyork took 4.482269287109375e-05s
Availability | VoID file availability check for Freeyork took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Freeyork took 0.27933359146118164s
Reputation | Calculation of the PageRank for Freeyork took 0.020534515380859375s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010395050048828125s
Believability | Calculation of trust value for Freeyork took 6.9141387939453125e-06s
INFO | --- Analysis for freeyork-org took 3.0757622718811035s
Availability | SPARQL endpoint availability check for French School Program took 4.291534423828125e-05s
Availability | VoID file availability check for French School Program took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for French School Program took 0.28250622749328613s
Reputation | Calculation of the PageRank for French School Program took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for French School Program took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for French School Program took 2.8133392333984375e-05s
Believability | Calculation of trust value for French School Program took 6.9141387939453125e-06s
INFO | --- Analysis for french-school-program took 3.0135011672973633s
Availability | SPARQL endpoint availability check for French School System took 3.910064697265625e-05s
Availability | VoID file availability check for French School System took 0.00022172927856445312s
Completeness | Calculation of interlinking completeness for French School System took 0.2553577423095703s
Reputation | Calculation of the PageRank for French School System took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for French School System took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for French School System took 2.956390380859375e-05s
Believability | Calculation of trust value for French School System took 7.62939453125e-06s
INFO | --- Analysis for french-school-system took 2.954955816268921s
Availability | SPARQL endpoint availability check for French TimeBank took 4.1484832763671875e-05s
Availability | VoID file availability check for French TimeBank took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.2895801067352295s
Reputation | Calculation of the PageRank for French TimeBank took 0.020350933074951172s
Interlinking | Calculation of Degree of Connection for French TimeBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for French TimeBank took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.3855438232421875e-05s
Believability | Calculation of trust value for French TimeBank took 8.344650268554688e-06s
INFO | --- Analysis for french-timebank took 2.9861907958984375s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7158224582672119s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.2529008388519287s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.02087712287902832s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.414817810058594e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.28437876701355s
Availability | SPARQL endpoint availability check for DailyMed took 0.6654055118560791s
Availability | VoID file availability check for DailyMed took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for DailyMed took 0.25503015518188477s
Reputation | Calculation of the PageRank for DailyMed took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.369850158691406e-05s
Believability | Calculation of trust value for DailyMed took 6.4373016357421875e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.306514263153076s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.6870088577270508s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.2707397937774658s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.02064967155456543s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.797645568847656e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 5.9604644775390625e-06s
INFO | --- Analysis for fu-berlin-dblp took 4.33674693107605s
Availability | SPARQL endpoint availability check for Diseasome took 0.6864807605743408s
Availability | VoID file availability check for Diseasome took 0.00039839744567871094s
Completeness | Calculation of interlinking completeness for Diseasome took 0.2751045227050781s
Reputation | Calculation of the PageRank for Diseasome took 0.020676374435424805s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010824203491210938s
Believability | Calculation of trust value for Diseasome took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.425227403640747s
Availability | SPARQL endpoint availability check for DrugBank took 0.6658236980438232s
Availability | VoID file availability check for DrugBank took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for DrugBank took 0.27226829528808594s
Reputation | Calculation of the PageRank for DrugBank took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011801719665527344s
Believability | Calculation of trust value for DrugBank took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.3952956199646s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.6977729797363281s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2987053394317627s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 2.9087066650390625e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 4.3467183113098145s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6692147254943848s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2565476894378662s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020535707473754883s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.43865966796875e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.289342403411865s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.713904857635498s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2835383415222168s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020908117294311523s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.605552673339844e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-eures took 4.355902194976807s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6912186145782471s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.26611804962158203s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.560585021972656e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 4.898805141448975s
Availability | SPARQL endpoint availability check for MediCare took 0.7003679275512695s
Availability | VoID file availability check for MediCare took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for MediCare took 0.2610907554626465s
Reputation | Calculation of the PageRank for MediCare took 0.0205385684967041s
Interlinking | Calculation of Degree of Connection for MediCare took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for MediCare took 3.814697265625e-05s
Believability | Calculation of trust value for MediCare took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-medicare took 4.874948024749756s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.669187068939209s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.26369667053222656s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020270586013793945s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.081031799316406e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.34040093421936s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6839599609375s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.30126190185546875s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 8.869171142578125e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-sider took 5.337232351303101s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.6714737415313721s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2680473327636719s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020449399948120117s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.2479248046875e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 5.9604644775390625e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.329870939254761s
Availability | SPARQL endpoint availability check for fvdb took 4.124641418457031e-05s
Availability | VoID file availability check for fvdb took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for fvdb took 0.2799694538116455s
Reputation | Calculation of the PageRank for fvdb took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for fvdb took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for fvdb took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for fvdb took 2.7179718017578125e-05s
Believability | Calculation of trust value for fvdb took 6.67572021484375e-06s
INFO | --- Analysis for fv took 12.544742584228516s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.792213439941406e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.28478050231933594s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.8133392333984375e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 7.62939453125e-06s
INFO | --- Analysis for GACS took 3.093823194503784s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.076957702636719e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.26905202865600586s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.0202178955078125s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 2.8371810913085938e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 6.198883056640625e-06s
INFO | --- Analysis for galen_from_co-odeorg took 3.0247597694396973s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0006337165832519531s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0008132457733154297s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.27767324447631836s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0008406639099121094s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 3.814697265625e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 6.4373016357421875e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.268526315689087s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 6.29425048828125e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.25592827796936035s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.775161743164062e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 6.67572021484375e-06s
INFO | --- Analysis for garnicaplywood took 2.593904495239258s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 5.4836273193359375e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.26326775550842285s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02095508575439453s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.441375732421875e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 8.58306884765625e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.0204925537109375s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.31144118309020996s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.276355504989624s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 8.96453857421875e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for gemet took 4.622077465057373s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.1961669921875e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.2734811305999756s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020926237106323242s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.4332275390625e-05s
Believability | Calculation of trust value for gemet-annotated took 7.3909759521484375e-06s
INFO | --- Analysis for gemet-annotated took 2.9953439235687256s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 1.001363754272461s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.28561854362487793s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020267248153686523s
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.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.504753112792969e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 7.3909759521484375e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.414966344833374s
Availability | SPARQL endpoint availability check for Super Ontology took 0.9683141708374023s
Availability | VoID file availability check for Super Ontology took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2827932834625244s
Reputation | Calculation of the PageRank for Super Ontology took 0.02023911476135254s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for Super Ontology took 7.62939453125e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 3.8268277645111084s
Availability | SPARQL endpoint availability check for geo.place took 5.1975250244140625e-05s
Availability | VoID file availability check for geo.place took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for geo.place took 0.29030632972717285s
Reputation | Calculation of the PageRank for geo.place took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for geo.place took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for geo.place took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for geo.place took 2.6464462280273438e-05s
Believability | Calculation of trust value for geo.place took 6.4373016357421875e-06s
INFO | --- Analysis for geo_place took 3.033292531967163s
Availability | SPARQL endpoint availability check for Geographic detector model took 7.081031799316406e-05s
Availability | VoID file availability check for Geographic detector model took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.263519287109375s
Reputation | Calculation of the PageRank for Geographic detector model took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 2.9802322387695312e-05s
Believability | Calculation of trust value for Geographic detector model took 7.62939453125e-06s
INFO | --- Analysis for GeoDetector took 12.734667539596558s
Availability | SPARQL endpoint availability check for geodomainwn took 4.076957702636719e-05s
Availability | VoID file availability check for geodomainwn took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.9956011772155762s
Reputation | Calculation of the PageRank for geodomainwn took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for geodomainwn took 7.987022399902344e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 5.054473876953125e-05s
Believability | Calculation of trust value for geodomainwn took 7.62939453125e-06s
INFO | --- Analysis for geodomainwn took 966.7518126964569s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.1961669921875e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2612118721008301s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02119755744934082s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0008549690246582031s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 7.82012939453125e-05s
Believability | Calculation of trust value for GeoEcuador took 7.152557373046875e-06s
INFO | --- Analysis for geoecuador took 15.264408349990845s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.04274845123291s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.7138805389404297s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.461143493652344e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 7.152557373046875e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 49.45535588264465s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.2438507080078125e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.00035262107849121094s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.27741122245788574s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020774364471435547s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.123283386230469e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 8.821487426757812e-06s
INFO | --- Analysis for geographic-openuplabs took 3.829866409301758s
Availability | SPARQL endpoint availability check for GeoLinkedData took 30.524338722229004s
Availability | VoID file availability check for GeoLinkedData took 0.0008809566497802734s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.26936864852905273s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.58306884765625e-05s
Believability | Calculation of trust value for GeoLinkedData took 5.9604644775390625e-06s
INFO | --- Analysis for geolinkeddata took 94.76491117477417s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.6792075634002686s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.27233386039733887s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.02116703987121582s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.821487426757812e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 6.546818971633911s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 9.5367431640625e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.26868414878845215s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004601478576660156s
Believability | Calculation of trust value for GeoNames Semantic Web took 7.62939453125e-06s
INFO | --- Analysis for geonames-semantic-web took 4.129678726196289s
Availability | SPARQL endpoint availability check for Geospatial World  took 5.698204040527344e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.3039426803588867s
Reputation | Calculation of the PageRank for Geospatial World  took 0.020931005477905273s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010275840759277344s
Believability | Calculation of trust value for Geospatial World  took 8.106231689453125e-06s
INFO | --- Analysis for geospatialworld-net took 3.894624948501587s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5606322288513184s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.28040099143981934s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013399124145507812s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 7.3909759521484375e-06s
INFO | --- Analysis for geospecies took 6.41402268409729s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.363059997558594e-05s
Availability | VoID file availability check for GeoWordNet took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.27583813667297363s
Reputation | Calculation of the PageRank for GeoWordNet took 0.0207517147064209s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 4.887580871582031e-05s
Believability | Calculation of trust value for GeoWordNet took 7.3909759521484375e-06s
INFO | --- Analysis for geowordnet took 7.097155332565308s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.13399910926818848s
Availability | VoID file availability check for German labor law thesaurus took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.28914976119995117s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020832300186157227s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007803440093994141s
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 7.62939453125e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.6360130310058594s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 5.340576171875e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.7200272083282471s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 3.8623809814453125e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 7.62939453125e-06s
INFO | --- Analysis for germlex took 3.1123154163360596s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.7733912467956543s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2701716423034668s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007486343383789062s
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.7404556274414062e-05s
INFO | --- Analysis for gesis-thesoz took 6.435405492782593s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.6411428451538086s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0008261203765869141s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.29834508895874023s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.534027099609375e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for getty-aat took 25.530696392059326s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 2.2293930053710938s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.2577850818634033s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020816326141357422s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.984306335449219e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 7.867813110351562e-06s
INFO | --- Analysis for getty-tgn took 24.212454557418823s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.45839691162109375s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.7124762535095215s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.020252704620361328s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.075599670410156e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 5.9604644775390625e-06s
INFO | --- Analysis for gipuzkoademografia took 3.968911647796631s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.363059997558594e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.27017879486083984s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 2.86102294921875e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 5.7220458984375e-06s
INFO | --- Analysis for glastonbury-2011 took 5.846512079238892s
Availability | SPARQL endpoint availability check for Global Change Information System took 4.100799560546875e-05s
Availability | VoID file availability check for Global Change Information System took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.2629568576812744s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 2.7418136596679688e-05s
Believability | Calculation of trust value for Global Change Information System took 8.106231689453125e-06s
INFO | --- Analysis for global-change-information-system took 2.928483724594116s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.410743713378906e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.26484131813049316s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.38690185546875e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 5.7220458984375e-06s
INFO | --- Analysis for global-hunger-index-2011 took 3.8243446350097656s
Availability | SPARQL endpoint availability check for Glottolog took 4.267692565917969e-05s
Availability | VoID file availability check for Glottolog took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Glottolog took 0.26778078079223633s
Reputation | Calculation of the PageRank for Glottolog took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Glottolog took 4.863739013671875e-05s
Believability | Calculation of trust value for Glottolog took 7.152557373046875e-06s
INFO | --- Analysis for glottolog took 6.28041672706604s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.1961669921875e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.29085683822631836s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010180473327636719s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 5.245208740234375e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 3.5012526512145996s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.029273986816406e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.000217437744140625s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.26938915252685547s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.020576000213623047s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.765655517578125e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 8.106231689453125e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.995915651321411s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.076957702636719e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.27245044708251953s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.0279159545898438e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 8.58306884765625e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.9365434646606445s
Availability | SPARQL endpoint availability check for 1121 took 4.458427429199219e-05s
Availability | VoID file availability check for 1121 took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for 1121 took 0.28372979164123535s
Reputation | Calculation of the PageRank for 1121 took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for 1121 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for 1121 took 2.8848648071289062e-05s
Believability | Calculation of trust value for 1121 took 1.71661376953125e-05s
INFO | --- Analysis for God_ took 3.0736992359161377s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.220008850097656e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2892441749572754s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 4.982948303222656e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 6.198883056640625e-06s
INFO | --- Analysis for gold took 4.263404846191406s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.2438507080078125e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.26963138580322266s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020625829696655273s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.437301635742188e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 6.67572021484375e-06s
INFO | --- Analysis for googleart-wrapper took 2.8412318229675293s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.10052156448364258s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.27173781394958496s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.552436828613281e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 8.58306884765625e-06s
INFO | --- Analysis for govagribus-denmark took 34.56378412246704s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.437147855758667s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.253157377243042s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020865678787231445s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0009169578552246094s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 0.00010585784912109375s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 24.000487089157104s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 3.7812137603759766s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.7057478427886963s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020479917526245117s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 0.00010538101196289062s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 5.4836273193359375e-06s
INFO | --- Analysis for govtrack took 15.64522409439087s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.00543212890625e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.2590363025665283s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.021394729614257812s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0011403560638427734s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 7.605552673339844e-05s
Believability | Calculation of trust value for greek-administrative-geography took 5.4836273193359375e-06s
INFO | --- Analysis for greek-administrative-geography took 2.6095545291900635s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.38437485694885254s
Availability | VoID file availability check for Greek Wordnet took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.26981258392333984s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.02036738395690918s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 3.838539123535156e-05s
Believability | Calculation of trust value for Greek Wordnet took 7.62939453125e-06s
INFO | --- Analysis for greek-wordnet took 2.806874990463257s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 4.389794111251831s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.25379276275634766s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.239776611328125e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 7.3909759521484375e-06s
INFO | --- Analysis for greek_prisons_releases took 9.329627513885498s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.9135608673095703s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.27873682975769043s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.82012939453125e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 5.4836273193359375e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.572207450866699s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.410743713378906e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.29029083251953125s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 9.942054748535156e-05s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 3.473921060562134s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.8776113986968994s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.2676832675933838s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.744529724121094e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 6.67572021484375e-06s
INFO | --- Analysis for grrp took 4.460223436355591s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.7345740795135498s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.2524685859680176s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.818771362304688e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.0067901611328125e-06s
INFO | --- Analysis for grrt took 4.247511386871338s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1167123317718506s
Availability | VoID file availability check for Geological Timescale took 0.0011417865753173828s
Extra | Recovery of all triples for Geological Timescale took 2.1035735607147217s
Performance | Total latancy measurement for Geological Timescale took 2.6415112018585205s
Amount of data | Number of triples check for Geological Timescale took 0.9956929683685303s
Interoperability | New terms check for Geological Timescale took 1.630582332611084s
Versatility | Languages check for Geological Timescale took 0.5087788105010986s
Interpretability | Number of blank nodes check for Geological Timescale took 1.0737223625183105s
Security | Check HTTPS for Geological Timescale took 0.917151689529419s
Interpretability | RDF structures check for Geological Timescale took 0.4229567050933838s
Versatility | Serialization formats check for Geological Timescale took 0.4044768810272217s
Availability | RDF dump link check for Geological Timescale took 1.6463260650634766s
License | MR license check for Geological Timescale took 0.9996631145477295s
License | HR license check for Geological Timescale took 0.43159055709838867s
Amount of data | Number of property check for Geological Timescale took 0.3686103820800781s
Understandability | Number of label check for Geological Timescale took 0.9896843433380127s
Understandability | URI regex check for Geological Timescale took 0.83620285987854s
Understandability | Vocabs check for Geological Timescale took 0.44211459159851074s
Verifiability | Authors check for Geological Timescale took 0.4121897220611572s
Verifiability | Publishers check for Geological Timescale took 0.4169161319732666s
Performance | Throughput check for Geological Timescale took 13.931618213653564s
Amount of data | Check the number of entities for Geological Timescale took 0.020751476287841797s
Verifiability | Contribs. check for Geological Timescale took 0.4459824562072754s
Interlinking | sameAs chians check for Geological Timescale took 0.3808591365814209s
Interlinking | skos check for Geological Timescale took 0.9448666572570801s
Interlinking | skos check for Geological Timescale took 0.9570674896240234s
Timeliness | dataset update frequency check for Geological Timescale took 0.40114355087280273s
Currency | Creation date check for Geological Timescale took 1.9085941314697266s
Currency | Modification date check for Geological Timescale took 0.4441697597503662s
Rep.Conc. | URIs length for Geological Timescale took 1.1128413677215576s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.4412710666656494s
Accuracy | Check Functional Property for Geological Timescale took 0.3959617614746094s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.6142034530639648s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.2990808486938477s
Accuracy | Check White space in annotation for Geological Timescale took 0.015811681747436523s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07300972938537598s
Consistency | Disjoint class check for Geological Timescale took 0.960674524307251s
Consistency | Check Misplaced properties for Geological Timescale took 1.932532787322998s
Consistency | Misplaced classes for Geological Timescale took 0.5326530933380127s
Consistency | Check Ontology hijacking for Geological Timescale took 1.5531713962554932s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.1465392112731934s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 1.5908493995666504s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05051565170288086s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.4032478332519531s
Security | Sign check for Geological Timescale took 0.3897819519042969s
Availability | Check URIs Dereferenciability for Geological Timescale took 2.6231744289398193s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.2790336608886719s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 6.890296936035156e-05s
Believability | Calculation of trust value for Geological Timescale took 7.867813110351562e-06s
INFO | --- Analysis for GTS took 97.5741376876831s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.27268218994140625s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.337860107421875e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for GTS-ont took 2.7042250633239746s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.1961669921875e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.2680680751800537s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020792484283447266s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 2.956390380859375e-05s
Believability | Calculation of trust value for GUTSTOK  took 6.198883056640625e-06s
INFO | --- Analysis for Guillaume_Forget took 2.9047698974609375s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.1961669921875e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.2960338592529297s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.747245788574219e-05s
Believability | Calculation of trust value for Project Gutenberg took 6.9141387939453125e-06s
INFO | --- Analysis for gutenberg took 24.444883346557617s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.100799560546875e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.26886916160583496s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.457069396972656e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 9.5367431640625e-06s
INFO | --- Analysis for gwa-ili took 5.563246965408325s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.267692565917969e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.2928497791290283s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 2.9087066650390625e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 7.867813110351562e-06s
INFO | --- Analysis for GWR took 13.719848871231079s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 6.985664367675781e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.2729313373565674s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.0279159545898438e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 7.3909759521484375e-06s
INFO | --- Analysis for HASM took 10.087098598480225s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.076957702636719e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.27225255966186523s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020203113555908203s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 2.86102294921875e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 7.867813110351562e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.9984285831451416s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 2.898167133331299s
Availability | VoID file availability check for HealthCare Ontology took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.2817220687866211s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.02027726173400879s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for HealthCare Ontology took 7.152557373046875e-06s
INFO | --- Analysis for HealthCare_Ontology took 5.785890340805054s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.2438507080078125e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0012912750244140625s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.2799248695373535s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020488262176513672s
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.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 5.91278076171875e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 7.3909759521484375e-06s
INFO | --- Analysis for heartfailure took 3.2471234798431396s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.72061586380005s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0009233951568603516s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.25550341606140137s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020344018936157227s
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.621246337890625e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.9577484130859375e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 7.3909759521484375e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 119.87500381469727s
Availability | SPARQL endpoint availability check for Hedatuz took 0.2277822494506836s
Availability | VoID file availability check for Hedatuz took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.699439525604248s
Reputation | Calculation of the PageRank for Hedatuz took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.719329833984375e-05s
Believability | Calculation of trust value for Hedatuz took 7.152557373046875e-06s
INFO | --- Analysis for hedatuz took 3.4153683185577393s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.12205719947814941s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.27060365676879883s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02087688446044922s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.0001246929168701172s
Believability | Calculation of trust value for Hellenic Fire Brigade took 5.4836273193359375e-06s
INFO | --- Analysis for hellenic-fire-brigade took 3.020134449005127s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.025700092315673828s
Availability | VoID file availability check for Hellenic Police took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.28024744987487793s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012612342834472656s
Believability | Calculation of trust value for Hellenic Police took 5.245208740234375e-06s
INFO | --- Analysis for hellenic-police took 2.585923194885254s
Availability | SPARQL endpoint availability check for Hermos took 4.1484832763671875e-05s
Availability | VoID file availability check for Hermos took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Hermos took 0.26366662979125977s
Reputation | Calculation of the PageRank for Hermos took 0.02038407325744629s
Interlinking | Calculation of Degree of Connection for Hermos took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Hermos took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.7418136596679688e-05s
Believability | Calculation of trust value for Hermos took 7.152557373046875e-06s
INFO | --- Analysis for Hermos took 3.0127367973327637s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.0531158447265625e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.27726030349731445s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.7179718017578125e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 7.3909759521484375e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.4733965396881104s
Availability | SPARQL endpoint availability check for HITO took 0.45131421089172363s
Availability | VoID file availability check for HITO took 0.0005850791931152344s
Extra | Recovery of all triples for HITO took 4.313460826873779s
Performance | Total latancy measurement for HITO took 0.9568815231323242s
Amount of data | Number of triples check for HITO took 0.1989297866821289s
Interoperability | New terms check for HITO took 1.3506207466125488s
Versatility | Languages check for HITO took 0.2611379623413086s
Interpretability | Number of blank nodes check for HITO took 0.20772695541381836s
Interpretability | RDF structures check for HITO took 0.23439383506774902s
Versatility | Serialization formats check for HITO took 0.19050812721252441s
Availability | RDF dump link check for HITO took 0.19713640213012695s
License | MR license check for HITO took 0.20285820960998535s
License | HR license check for HITO took 0.24022960662841797s
Amount of data | Number of property check for HITO took 0.199676513671875s
Understandability | Number of label check for HITO took 0.21630120277404785s
Understandability | URI regex check for HITO took 0.3858520984649658s
Understandability | Vocabs check for HITO took 0.20645928382873535s
Verifiability | Authors check for HITO took 0.20125985145568848s
Verifiability | Publishers check for HITO took 0.196702241897583s
Performance | Throughput check for HITO took 11.454793214797974s
Amount of data | Check the number of entities for HITO took 5.602836608886719e-05s
Verifiability | Contribs. check for HITO took 0.2119596004486084s
Interlinking | sameAs chians check for HITO took 0.19565486907958984s
Interlinking | skos check for HITO took 0.22468996047973633s
Interlinking | skos check for HITO took 0.19849443435668945s
Timeliness | dataset update frequency check for HITO took 0.20042991638183594s
Currency | Creation date check for HITO took 0.4180591106414795s
Currency | Modification date check for HITO took 0.40828871726989746s
Rep.Conc. | URIs length for HITO took 1.346095323562622s
Interoperability | New vocabularies check for HITO took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.18543791770935059s
Accuracy | Check Functional Property for HITO took 0.19758105278015137s
Accuracy | Check Inverse Functional Property for HITO took 0.21079325675964355s
Accuracy | Check Empty annotation labels for HITO took 0.5855369567871094s
Accuracy | Check White space in annotation for HITO took 0.013577461242675781s
Accuracy | Check Datatype consistency for HITO took 0.08998990058898926s
Consistency | Disjoint class check for HITO took 0.19548654556274414s
Consistency | Check Misplaced properties for HITO took 0.5186619758605957s
Consistency | Misplaced classes for HITO took 0.39159226417541504s
Consistency | Check Ontology hijacking for HITO took 1.6245756149291992s
Consistency | Check Invalid usage of undefined classes for HITO took 1.136101484298706s
Consistency | Check Invalid usage of undefined properties for HITO took 1.4128930568695068s
Conciseness | Check Extensional conciseness for HITO took 0.06871438026428223s
Conciseness | Check Intensional conciseness for HITO took 0.2012801170349121s
Security | Sign check for HITO took 0.1978926658630371s
Availability | Check URIs Dereferenciability for HITO took 2149.175492286682s
Completeness | Calculation of interlinking completeness for HITO took 1.622889518737793s
Reputation | Calculation of the PageRank for HITO took 0.020879507064819336s
Interlinking | Calculation of Degree of Connection for HITO took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for HITO took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for HITO took 8.130073547363281e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.1920928955078125e-06s
Believability | Calculation of trust value for HITO took 7.867813110351562e-06s
INFO | --- Analysis for hito took 2205.879584789276s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 19.652456521987915s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.2696723937988281s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 2.8371810913085938e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 7.152557373046875e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 38.99909520149231s
Availability | SPARQL endpoint availability check for Homologene took 4.0531158447265625e-05s
Availability | VoID file availability check for Homologene took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Homologene took 0.2581939697265625s
Reputation | Calculation of the PageRank for Homologene took 0.020331621170043945s
Interlinking | Calculation of Degree of Connection for Homologene took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Homologene took 2.6702880859375e-05s
Believability | Calculation of trust value for Homologene took 7.62939453125e-06s
INFO | --- Analysis for homologene took 3.782697916030884s
Availability | SPARQL endpoint availability check for gseg took 4.076957702636719e-05s
Availability | VoID file availability check for gseg took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for gseg took 0.2730441093444824s
Reputation | Calculation of the PageRank for gseg took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for gseg took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for gseg took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for gseg took 2.7179718017578125e-05s
Believability | Calculation of trust value for gseg took 6.198883056640625e-06s
INFO | --- Analysis for hongse took 3.6096079349517822s
Availability | SPARQL endpoint availability check for Noticias Universia took 4.029273986816406e-05s
Availability | VoID file availability check for Noticias Universia took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.25875139236450195s
Reputation | Calculation of the PageRank for Noticias Universia took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 2.6226043701171875e-05s
Believability | Calculation of trust value for Noticias Universia took 7.152557373046875e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 2.9624011516571045s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.0531158447265625e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.2680020332336426s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.020583391189575195s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 2.7894973754882812e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 7.152557373046875e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.9479875564575195s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.8594725131988525s
Availability | VoID file availability check for COURAGE Dataset took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.29010796546936035s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 2.6464462280273438e-05s
Believability | Calculation of trust value for COURAGE Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 5.471987009048462s
Availability | SPARQL endpoint availability check for RoadTrb took 5.054473876953125e-05s
Availability | VoID file availability check for RoadTrb took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.27313709259033203s
Reputation | Calculation of the PageRank for RoadTrb took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for RoadTrb took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 2.7418136596679688e-05s
Believability | Calculation of trust value for RoadTrb took 7.3909759521484375e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 3.007138729095459s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.25536608695983887s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.765655517578125e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 6.67572021484375e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 24.63480281829834s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 4.0531158447265625e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.28970885276794434s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.218650817871094e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 6.67572021484375e-06s
INFO | --- Analysis for http:pakistan.com took 2.4605329036712646s
Availability | SPARQL endpoint availability check for CEDICT took 4.0531158447265625e-05s
Availability | VoID file availability check for CEDICT took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for CEDICT took 0.28978419303894043s
Reputation | Calculation of the PageRank for CEDICT took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for CEDICT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CEDICT took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for CEDICT took 2.7418136596679688e-05s
Believability | Calculation of trust value for CEDICT took 7.152557373046875e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.457530736923218s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.3065974712371826s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2799222469329834s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020996809005737305s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.794929504394531e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.198883056640625e-06s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 4.380064249038696s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.29146552085876465s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 2.7894973754882812e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 6.198883056640625e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.9960808753967285s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 5.2928924560546875e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.27640295028686523s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 2.8133392333984375e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 7.152557373046875e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.427849292755127s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.124641418457031e-05s
Availability | VoID file availability check for Soccer Dataset took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.27581357955932617s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.765655517578125e-05s
Believability | Calculation of trust value for Soccer Dataset took 6.198883056640625e-06s
INFO | --- Analysis for http:www.msm.com took 2.4419362545013428s
Availability | SPARQL endpoint availability check for Game Ontology took 3.8623809814453125e-05s
Availability | VoID file availability check for Game Ontology took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.29334497451782227s
Reputation | Calculation of the PageRank for Game Ontology took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.170967102050781e-05s
Believability | Calculation of trust value for Game Ontology took 8.344650268554688e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 3.036433696746826s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.291534423828125e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0003898143768310547s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.27541351318359375s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.7404556274414062e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.2261455059051514s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.009506225585938e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2780148983001709s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02060556411743164s
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.0008134841918945312s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.67572021484375e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.4064478874206543s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.291534423828125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26816320419311523s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020514249801635742s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.152557373046875e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.379180908203125s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.291534423828125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.27895665168762207s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0279159545898438e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.152557373046875e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.4087560176849365s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.124641418457031e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2791311740875244s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7894973754882812e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.198883056640625e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.4187769889831543s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.7220458984375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.001399993896484375s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.273406982421875s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9802322387695312e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.4373016357421875e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.3996639251708984s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.38690185546875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2799384593963623s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020655393600463867s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9802322387695312e-05s
Believability | Calculation of trust value for Indian Biodiversity took 5.9604644775390625e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.4639923572540283s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 5.698204040527344e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.27182841300964355s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 2.9325485229492188e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 6.198883056640625e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 3.8802859783172607s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.121467113494873s
Availability | VoID file availability check for Bookkeeping took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.26665234565734863s
Reputation | Calculation of the PageRank for Bookkeeping took 0.02065587043762207s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bookkeeping took 7.3909759521484375e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 3.880002498626709s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Legal Ontology took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.259906530380249s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020556211471557617s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Legal Ontology took 6.198883056640625e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.9628779888153076s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.363059997558594e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2616865634918213s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.702278137207031e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.67572021484375e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.735727310180664s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.267692565917969e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.28023505210876465s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.0994415283203125e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 6.198883056640625e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.6681768894195557s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.506111145019531e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.2895655632019043s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 2.8371810913085938e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 6.9141387939453125e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 3.039513111114502s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.0531158447265625e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2515547275543213s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 7.867813110351562e-06s
INFO | --- Analysis for hud-library-usagedata took 2.9258878231048584s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.5681850910186768s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.263059139251709s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010514259338378906s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 6.67572021484375e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.411179780960083s
Availability | SPARQL endpoint availability check for IATE RDF took 4.1961669921875e-05s
Availability | VoID file availability check for IATE RDF took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.2855074405670166s
Reputation | Calculation of the PageRank for IATE RDF took 0.021492481231689453s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.457069396972656e-05s
Believability | Calculation of trust value for IATE RDF took 7.3909759521484375e-06s
INFO | --- Analysis for iate-rdf took 2.543699264526367s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 0.842454195022583s
Availability | VoID file availability check for IATI as Linked Data took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.2811274528503418s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.559226989746094e-05s
Believability | Calculation of trust value for IATI as Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for iati-as-linked-data took 7.685946464538574s
Availability | SPARQL endpoint availability check for ICANE took 1.1910467147827148s
Availability | VoID file availability check for ICANE took 0.0008165836334228516s
Completeness | Calculation of interlinking completeness for ICANE took 0.26877331733703613s
Reputation | Calculation of the PageRank for ICANE took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for ICANE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.320808410644531e-05s
Believability | Calculation of trust value for ICANE took 5.4836273193359375e-06s
INFO | --- Analysis for icane took 4.554242134094238s
Availability | SPARQL endpoint availability check for ichoose took 0.16518640518188477s
Availability | VoID file availability check for ichoose took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for ichoose took 0.37909388542175293s
Reputation | Calculation of the PageRank for ichoose took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for ichoose took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.772445678710938e-05s
Believability | Calculation of trust value for ichoose took 7.3909759521484375e-06s
INFO | --- Analysis for ichoose took 117.18997526168823s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.5205934047698975s
Availability | VoID file availability check for The Iconology Dataset took 0.0006844997406005859s
Extra | Recovery of all triples for The Iconology Dataset took 4.632900953292847s
Performance | Total latancy measurement for The Iconology Dataset took 0.41469383239746094s
Amount of data | Number of triples check for The Iconology Dataset took 0.19051098823547363s
Interoperability | New terms check for The Iconology Dataset took 1.259861946105957s
Versatility | Languages check for The Iconology Dataset took 0.567967414855957s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.21726179122924805s
Interpretability | RDF structures check for The Iconology Dataset took 0.14917349815368652s
Versatility | Serialization formats check for The Iconology Dataset took 0.10025429725646973s
Availability | RDF dump link check for The Iconology Dataset took 0.08386468887329102s
License | MR license check for The Iconology Dataset took 0.09462809562683105s
License | HR license check for The Iconology Dataset took 0.2303638458251953s
Amount of data | Number of property check for The Iconology Dataset took 0.09517741203308105s
Understandability | Number of label check for The Iconology Dataset took 0.12842917442321777s
Understandability | URI regex check for The Iconology Dataset took 0.17271828651428223s
Understandability | Vocabs check for The Iconology Dataset took 0.08622956275939941s
Verifiability | Authors check for The Iconology Dataset took 0.09613227844238281s
Verifiability | Publishers check for The Iconology Dataset took 0.08562994003295898s
Performance | Throughput check for The Iconology Dataset took 10.368853569030762s
Amount of data | Check the number of entities for The Iconology Dataset took 9.059906005859375e-05s
Verifiability | Contribs. check for The Iconology Dataset took 0.0846865177154541s
Interlinking | sameAs chians check for The Iconology Dataset took 0.08823847770690918s
Interlinking | skos check for The Iconology Dataset took 0.08763241767883301s
Interlinking | skos check for The Iconology Dataset took 0.08634424209594727s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.08480143547058105s
Currency | Creation date check for The Iconology Dataset took 0.17603492736816406s
Currency | Modification date check for The Iconology Dataset took 0.17319011688232422s
Rep.Conc. | URIs length for The Iconology Dataset took 1.3304429054260254s
Interoperability | New vocabularies check for The Iconology Dataset took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.07969975471496582s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.25052952766418457s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016383647918701172s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.43627262115478516s
Consistency | Disjoint class check for The Iconology Dataset took 0.07983803749084473s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.15302705764770508s
Consistency | Misplaced classes for The Iconology Dataset took 0.8595294952392578s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.5140912532806396s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.142148733139038s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.221726894378662s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.2950706481933594s
Security | Sign check for The Iconology Dataset took 0.08262133598327637s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2553.7113666534424s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 1.0598759651184082s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The Iconology Dataset took 1.7642974853515625e-05s
INFO | --- Analysis for iconology-dataset took 2612.715511083603s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.100799560546875e-05s
Availability | VoID file availability check for Identifiers.org took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.2615067958831787s
Reputation | Calculation of the PageRank for Identifiers.org took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.9577484130859375e-05s
Believability | Calculation of trust value for Identifiers.org took 8.106231689453125e-06s
INFO | --- Analysis for identifiers-org took 4.2811408042907715s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.553794860839844e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.6814982891082764s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 8.0108642578125e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 8.344650268554688e-06s
INFO | --- Analysis for idreffr took 4.44092869758606s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.9962081909179688s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.2908315658569336s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.839897155761719e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 8.106231689453125e-06s
INFO | --- Analysis for ids took 4.441314697265625s
Availability | SPARQL endpoint availability check for ietflang took 5.555152893066406e-05s
Availability | VoID file availability check for ietflang took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for ietflang took 0.7272059917449951s
Reputation | Calculation of the PageRank for ietflang took 0.02081131935119629s
Interlinking | Calculation of Degree of Connection for ietflang took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.696846008300781e-05s
Believability | Calculation of trust value for ietflang took 8.58306884765625e-06s
INFO | --- Analysis for ietflang took 13.57411789894104s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.49729013442993164s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0007519721984863281s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.27824997901916504s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 4.3392181396484375e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for IGVLL took 3.9518537521362305s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.5126268863677979s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0006573200225830078s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.9305133819580078s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9913830757141113s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.19765686988830566s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.3687019348144531s
Versatility | Languages check for 3LGM² IHE Ontology took 0.18863773345947266s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.20674681663513184s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.19692730903625488s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.1849815845489502s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.19516253471374512s
License | MR license check for 3LGM² IHE Ontology took 0.19673562049865723s
License | HR license check for 3LGM² IHE Ontology took 0.21421313285827637s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.18533587455749512s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.200272798538208s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.39215087890625s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.20653176307678223s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.18471741676330566s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.1850583553314209s
Performance | Throughput check for 3LGM² IHE Ontology took 11.509973764419556s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.176399230957031e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.1947646141052246s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.20767736434936523s
Interlinking | skos check for 3LGM² IHE Ontology took 0.1847238540649414s
Interlinking | skos check for 3LGM² IHE Ontology took 0.1946554183959961s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.18403148651123047s
Currency | Creation date check for 3LGM² IHE Ontology took 0.4036860466003418s
Currency | Modification date check for 3LGM² IHE Ontology took 0.4032869338989258s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8043136596679688s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.19770264625549316s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.19414877891540527s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.20759034156799316s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.33136630058288574s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.003710031509399414s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.05240917205810547s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.19725894927978516s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4291834831237793s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2926640510559082s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.4887127876281738s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.1312880516052246s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.4354526996612549s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.030512094497680664s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.2023458480834961s
Security | Sign check for 3LGM² IHE Ontology took 0.20612549781799316s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 326.50454473495483s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.7945871353149414s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.020246028900146484s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 2.7418136596679688e-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 7.62939453125e-06s
INFO | --- Analysis for IHE took 373.78328347206116s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.08829426765441895s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.2764554023742676s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.314018249511719e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 6.9141387939453125e-06s
INFO | --- Analysis for iislod-test took 2.5555672645568848s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.5299530029296875e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.27600884437561035s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.695487976074219e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 7.62939453125e-06s
INFO | --- Analysis for ILUSOC took 20.8334002494812s
Availability | SPARQL endpoint availability check for im@sparql took 7.637751579284668s
Availability | VoID file availability check for im@sparql took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for im@sparql took 0.2546250820159912s
Reputation | Calculation of the PageRank for im@sparql took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for im@sparql took 2.9802322387695312e-05s
Believability | Calculation of trust value for im@sparql took 7.152557373046875e-06s
INFO | --- Analysis for im@sparql took 14.633268117904663s
Availability | SPARQL endpoint availability check for imagery bailingniao took 6.651878356933594e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2676677703857422s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.075599670410156e-05s
Believability | Calculation of trust value for imagery bailingniao took 7.152557373046875e-06s
INFO | --- Analysis for imagery_bailingniao took 3.41390061378479s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.0853867530822754s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006525516510009766s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 24.23372173309326s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.486097574234009s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 10.35498857498169s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.4819226264953613s
Versatility | Languages check for Imagesnippets Image Descriptions took 10.728144884109497s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.525614738464355s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.682666540145874s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7464582920074463s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.6998324394226074s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7079830169677734s
License | MR license check for Imagesnippets Image Descriptions took 0.7315194606781006s
License | HR license check for Imagesnippets Image Descriptions took 10.711852312088013s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7246303558349609s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.827179431915283s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.4119696617126465s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7321865558624268s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.6968095302581787s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.760565996170044s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.871562480926514s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.939338684082031e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7003874778747559s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7251119613647461s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6954562664031982s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6758632659912109s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.6940288543701172s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.426332950592041s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.4491422176361084s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 26.99193048477173s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7089998722076416s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7202792167663574s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7446010112762451s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7255778312683105s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.674970626831055s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 16.83968472480774s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.245023727416992s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.00015974044799804688s
Security | Sign check for Imagesnippets Image Descriptions took 0.7534902095794678s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.7260758876800537s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 8.559226989746094e-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 8.106231689453125e-06s
INFO | --- Analysis for imagesnippets took 262.4941556453705s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.979142427444458s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.2831730842590332s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.821487426757812e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for imf-linked-data took 4.784492492675781s
Availability | SPARQL endpoint availability check for IMGpedia took 4.1961669921875e-05s
Availability | VoID file availability check for IMGpedia took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.2649219036102295s
Reputation | Calculation of the PageRank for IMGpedia took 0.020615100860595703s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.147125244140625e-05s
Believability | Calculation of trust value for IMGpedia took 7.152557373046875e-06s
INFO | --- Analysis for imgpedia took 3.378319263458252s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.100799560546875e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.27519917488098145s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.8371810913085938e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 7.62939453125e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 3.821446418762207s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.315376281738281e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.302901029586792s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.02138042449951172s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0011451244354248047s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.3113021850585938e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 7.62939453125e-06s
INFO | --- Analysis for Imtiaz took 2.4021108150482178s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.8160552978515625e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2808072566986084s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 2.86102294921875e-05s
Believability | Calculation of trust value for Royalty Free Music took 7.62939453125e-06s
INFO | --- Analysis for inaudio.org took 3.685399293899536s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.100799560546875e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.2780880928039551s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 2.8848648071289062e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 6.9141387939453125e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.9073243141174316s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 3.933906555175781e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.29274916648864746s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020610809326171875s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 2.8848648071289062e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 8.106231689453125e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 3.000352382659912s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.3729991912841797s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.25890207290649414s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 5.9604644775390625e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 3.804763078689575s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.00543212890625e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.2699241638183594s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 2.8371810913085938e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 6.9141387939453125e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 3.0294103622436523s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.3392181396484375e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.3034553527832031s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010132789611816406s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 7.152557373046875e-06s
INFO | --- Analysis for ineverycrea took 18.23409938812256s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.1961669921875e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0013492107391357422s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2957639694213867s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020127296447753906s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.702278137207031e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 7.152557373046875e-06s
INFO | --- Analysis for ineverycrea-argentina took 10.227343797683716s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 522.8398163318634s
Availability | VoID file availability check for Influence Tracker Dataset took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.7712056636810303s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02085399627685547s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.62939453125e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for influence-tracker-dataset took 1082.118796825409s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.0531158447265625e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.698408842086792s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.02090144157409668s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.457069396972656e-05s
Believability | Calculation of trust value for INSEMTIVES took 9.059906005859375e-06s
INFO | --- Analysis for insemtives took 6.6189045906066895s
Availability | SPARQL endpoint availability check for instagram.person took 4.00543212890625e-05s
Availability | VoID file availability check for instagram.person took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for instagram.person took 0.2891840934753418s
Reputation | Calculation of the PageRank for instagram.person took 0.02082967758178711s
Interlinking | Calculation of Degree of Connection for instagram.person took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for instagram.person took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for instagram.person took 2.9325485229492188e-05s
Believability | Calculation of trust value for instagram.person took 8.821487426757812e-06s
INFO | --- Analysis for instagram_person took 3.894273519515991s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.100799560546875e-05s
Availability | VoID file availability check for instagram.videoobject took 0.0007805824279785156s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.2522292137145996s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020745515823364258s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 3.0279159545898438e-05s
Believability | Calculation of trust value for instagram.videoobject took 8.344650268554688e-06s
INFO | --- Analysis for instagram_videoobject took 3.8200619220733643s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.1961669921875e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.28473615646362305s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.020982027053833008s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 4.2438507080078125e-05s
Believability | Calculation of trust value for Instance Hub Countries took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-countries took 3.461015462875366s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 5.602836608886719e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2595677375793457s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.8371810913085938e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.4583001136779785s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 3.9577484130859375e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.28686976432800293s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 2.8848648071289062e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-organizations took 2.991163730621338s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub People took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.2597184181213379s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 2.956390380859375e-05s
Believability | Calculation of trust value for Instance Hub People took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-people took 2.9401016235351562s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.363059997558594e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.27837634086608887s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 3.0105199813842773s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.0531158447265625e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.2686326503753662s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 2.956390380859375e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 6.4373016357421875e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.94565749168396s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.4345855712890625e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.2684042453765869s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020574092864990234s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 2.8371810913085938e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 3.0243194103240967s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.029273986816406e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.2799093723297119s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 8.344650268554688e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.970304250717163s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.2896862030029297s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 2.956390380859375e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.9384963512420654s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.315376281738281e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.2613365650177002s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.024611234664916992s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0011839866638183594s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.6716461181640625e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 3.046247959136963s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 3.981590270996094e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.27926206588745117s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 2.86102294921875e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 9.5367431640625e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 3.00777530670166s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.7206878662109375e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.2666049003601074s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.02071213722229004s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.0517578125e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.867813110351562e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.9846978187561035s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.172325134277344e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.29511356353759766s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02062082290649414s
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.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00010013580322265625s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for interactivemaps-gnoss took 6.952232599258423s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.0531158447265625e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.269761323928833s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 2.9087066650390625e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 6.67572021484375e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.9498226642608643s
Availability | SPARQL endpoint availability check for intervalue took 0.2322220802307129s
Availability | VoID file availability check for intervalue took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for intervalue took 0.2607741355895996s
Reputation | Calculation of the PageRank for intervalue took 0.020772218704223633s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.67572021484375e-05s
Believability | Calculation of trust value for intervalue took 8.58306884765625e-06s
INFO | --- Analysis for intervalue took 2.6192362308502197s
Availability | SPARQL endpoint availability check for Inztrow took 4.100799560546875e-05s
Availability | VoID file availability check for Inztrow took 0.0003654956817626953s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2851285934448242s
Reputation | Calculation of the PageRank for Inztrow took 0.021044015884399414s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.0994415283203125e-05s
Believability | Calculation of trust value for Inztrow took 7.3909759521484375e-06s
INFO | --- Analysis for Inztrow took 3.914522886276245s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.2721412181854248s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 6.67572021484375e-06s
INFO | --- Analysis for ipbes took 3.6578404903411865s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.100799560546875e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.2513422966003418s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 5.1975250244140625e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 7.62939453125e-06s
INFO | --- Analysis for iptc-newscodes took 3.352022171020508s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.9577484130859375e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.27429866790771484s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.147125244140625e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 6.4373016357421875e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.9451205730438232s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 1.9048824310302734s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.265242338180542s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020827531814575195s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.894371032714844e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 7.3909759521484375e-06s
INFO | --- Analysis for iserve took 6.899106979370117s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.626675844192505s
Availability | VoID file availability check for ISIC V4 took 0.0009353160858154297s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.6911201477050781s
Reputation | Calculation of the PageRank for ISIC V4 took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.981590270996094e-05s
Believability | Calculation of trust value for ISIC V4 took 5.245208740234375e-06s
INFO | --- Analysis for isic-v4 took 116.27795481681824s
Availability | SPARQL endpoint availability check for Isidore took 4.00543212890625e-05s
Availability | VoID file availability check for Isidore took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for Isidore took 0.26017308235168457s
Reputation | Calculation of the PageRank for Isidore took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for Isidore took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Isidore took 3.337860107421875e-05s
Believability | Calculation of trust value for Isidore took 7.867813110351562e-06s
INFO | --- Analysis for isidore took 3.4282829761505127s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 6.008148193359375e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.30495238304138184s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020629167556762695s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 6.723403930664062e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 5.0067901611328125e-06s
INFO | --- Analysis for isil-dbpedia took 4.741930246353149s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 4.553794860839844e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.00030159950256347656s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.3012220859527588s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020897865295410156s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.24249267578125e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 7.867813110351562e-06s
INFO | --- Analysis for iso-3166-2-data took 3.881056308746338s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 5.221366882324219e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.26618480682373047s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.02083444595336914s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.62396240234375e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.1682510375976562e-05s
INFO | --- Analysis for iso-639-oasis took 3.39107084274292s
Availability | SPARQL endpoint availability check for ISOcat took 4.267692565917969e-05s
Availability | VoID file availability check for ISOcat took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for ISOcat took 0.30411696434020996s
Reputation | Calculation of the PageRank for ISOcat took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for ISOcat took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ISOcat took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for ISOcat took 5.817413330078125e-05s
Believability | Calculation of trust value for ISOcat took 5.9604644775390625e-06s
INFO | --- Analysis for isocat took 33.78277826309204s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.291534423828125e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.29006028175354004s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 4.363059997558594e-05s
Believability | Calculation of trust value for ISOcat-metadata took 5.9604644775390625e-06s
INFO | --- Analysis for isocat-metadata took 4.867746114730835s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.0531158447265625e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.2940800189971924s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 2.7179718017578125e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 5.9604644775390625e-06s
INFO | --- Analysis for ispra-lod-ihi took 3.0028188228607178s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.300931930541992s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2685434818267822s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.916854858398438e-05s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.62939453125e-06s
INFO | --- Analysis for ispra-lod-place took 22.05616807937622s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.1961669921875e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.25655364990234375s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0008363723754882812s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 2.956390380859375e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-rmn took 3.408457040786743s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 8.86832332611084s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.3740274906158447s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.0994415283203125e-05s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-ron took 27.42171025276184s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.00543212890625e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.29738688468933105s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 2.6464462280273438e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 6.4373016357421875e-06s
INFO | --- Analysis for ispra-lod-sc took 2.9465529918670654s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 20.469613075256348s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0013685226440429688s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.25284790992736816s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 8.940696716308594e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 7.152557373046875e-06s
INFO | --- Analysis for issa-agritrop took 54.272133350372314s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 5.1975250244140625e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2658956050872803s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.6226043701171875e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.62939453125e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.898314952850342s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.363059997558594e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2560262680053711s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.7179718017578125e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.3909759521484375e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 2.8889334201812744s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 5.1975250244140625e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.2732870578765869s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.0517578125e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 8.821487426757812e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 2.596158981323242s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.7419965267181396s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.26530957221984863s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.021303892135620117s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0009477138519287109s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 0.00010466575622558594s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 5.7220458984375e-06s
INFO | --- Analysis for istat-immigration took 4.2399821281433105s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 3.910064697265625e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.00032901763916015625s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.3039736747741699s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 2.9087066650390625e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 7.3909759521484375e-06s
INFO | --- Analysis for istat-immigrazione took 2.9721693992614746s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 30.105832815170288s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.27740025520324707s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.86102294921875e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 5.0067901611328125e-06s
INFO | --- Analysis for it-aifa-drug-prices took 102.58088421821594s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.5947182178497314s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.24877238273620605s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.02048659324645996s
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.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.271766662597656e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 7.62939453125e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 4.926458120346069s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 3.933906555175781e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.26945066452026367s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 2.7894973754882812e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 6.67572021484375e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.981422185897827s
Availability | SPARQL endpoint availability check for Global Data on PFAS Contamination in Organisms took 4.124641418457031e-05s
Availability | VoID file availability check for Global Data on PFAS Contamination in Organisms took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for Global Data on PFAS Contamination in Organisms took 0.24809837341308594s
Reputation | Calculation of the PageRank for Global Data on PFAS Contamination in Organisms took 0.02030491828918457s
Interlinking | Calculation of Degree of Connection for Global Data on PFAS Contamination in Organisms took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Global Data on PFAS Contamination in Organisms took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Global Data on PFAS Contamination in Organisms took 1.2874603271484375e-05s
Believability | Calculation of trust value for Global Data on PFAS Contamination in Organisms took 7.867813110351562e-06s
INFO | --- Analysis for iue-PFASData took 2.3899996280670166s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.00543212890625e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.25525808334350586s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 2.9087066650390625e-05s
Believability | Calculation of trust value for IWMI Research Reports took 6.198883056640625e-06s
INFO | --- Analysis for iwmi-research-reports took 2.975247621536255s
Availability | SPARQL endpoint availability check for IWN took 4.076957702636719e-05s
Availability | VoID file availability check for IWN took 0.0008718967437744141s
Completeness | Calculation of interlinking completeness for IWN took 0.8210756778717041s
Reputation | Calculation of the PageRank for IWN took 0.02112865447998047s
Interlinking | Calculation of Degree of Connection for IWN took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for IWN took 4.172325134277344e-05s
Believability | Calculation of trust value for IWN took 8.344650268554688e-06s
INFO | --- Analysis for iwn took 364.68934178352356s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 3.981590270996094e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.28992795944213867s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.02075934410095215s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.170967102050781e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 7.152557373046875e-06s
INFO | --- Analysis for j-global-knowledge took 4.488946199417114s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 3.9577484130859375e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.7209088802337646s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 2.9325485229492188e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 6.67572021484375e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 3.411673069000244s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.171672582626343s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.26554131507873535s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 5.9604644775390625e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 7.867813110351562e-06s
INFO | --- Analysis for jamendo-dbtune took 24.933764219284058s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.100799560546875e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.25604891777038574s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 5.125999450683594e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.759562015533447s
Availability | SPARQL endpoint availability check for JEL Classification took 4.100799560546875e-05s
Availability | VoID file availability check for JEL Classification took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.26944684982299805s
Reputation | Calculation of the PageRank for JEL Classification took 0.020830631256103516s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.0517578125e-05s
Believability | Calculation of trust value for JEL Classification took 7.152557373046875e-06s
INFO | --- Analysis for jel-classification took 4.741616487503052s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 0.3862428665161133s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.2626638412475586s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020601272583007812s
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.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.0517578125e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 6.9141387939453125e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 6.213134288787842s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.7737362384796s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.32870936393737793s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.022508621215820312s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0009112358093261719s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 9.131431579589844e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.0013580322265625e-05s
INFO | --- Analysis for jita took 540.6041679382324s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.482269287109375e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.3015713691711426s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 2.8133392333984375e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 7.3909759521484375e-06s
INFO | --- Analysis for jmdict took 4.298997163772583s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.071398735046387s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.6958756446838379s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.249282836914062e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.3909759521484375e-06s
INFO | --- Analysis for john-goodwins-family-tree took 64.33319234848022s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.6253204345703125e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.26581454277038574s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.02080082893371582s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.6716461181640625e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 8.344650268554688e-06s
INFO | --- Analysis for jp-cos took 6.0499773025512695s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.2438507080078125e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.2638123035430908s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.814697265625e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 8.821487426757812e-06s
INFO | --- Analysis for jp-textbook took 5.050167798995972s
Availability | SPARQL endpoint availability check for JRC-Names took 4.1484832763671875e-05s
Availability | VoID file availability check for JRC-Names took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.2803986072540283s
Reputation | Calculation of the PageRank for JRC-Names took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for JRC-Names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.123283386230469e-05s
Believability | Calculation of trust value for JRC-Names took 9.298324584960938e-06s
INFO | --- Analysis for jrc-names-ec took 4.882298231124878s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.1169233322143555s
Availability | VoID file availability check for JRC-Names-MLODE took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.272874116897583s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020911216735839844s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.580352783203125e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.8358230590820312e-05s
INFO | --- Analysis for jrc-names-mlode took 3.68316388130188s
Availability | SPARQL endpoint availability check for JudaicaLink took 7.271766662597656e-05s
Availability | VoID file availability check for JudaicaLink took 0.0007374286651611328s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2627127170562744s
Reputation | Calculation of the PageRank for JudaicaLink took 0.021200180053710938s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00011444091796875s
Believability | Calculation of trust value for JudaicaLink took 7.867813110351562e-06s
INFO | --- Analysis for judaicalink took 5.9025959968566895s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.029273986816406e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.27878499031066895s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.020813941955566406s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 2.9087066650390625e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 8.106231689453125e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.872938632965088s
Availability | SPARQL endpoint availability check for KAKEN took 4.3392181396484375e-05s
Availability | VoID file availability check for KAKEN took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for KAKEN took 0.30064940452575684s
Reputation | Calculation of the PageRank for KAKEN took 0.021349668502807617s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.123283386230469e-05s
Believability | Calculation of trust value for KAKEN took 8.58306884765625e-06s
INFO | --- Analysis for kaken took 2.959888458251953s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.08116960525512695s
Availability | VoID file availability check for Kallikratis municipalities took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.2591989040374756s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 8.797645568847656e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 4.76837158203125e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.528428077697754s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.0531158447265625e-05s
Availability | VoID file availability check for Openflights Routes took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.272352933883667s
Reputation | Calculation of the PageRank for Openflights Routes took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 2.7894973754882812e-05s
Believability | Calculation of trust value for Openflights Routes took 7.3909759521484375e-06s
INFO | --- Analysis for kasabi-openflights-routes took 2.9842021465301514s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.291534423828125e-05s
Availability | VoID file availability check for EU Soccer League took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2530786991119385s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020815134048461914s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 2.9325485229492188e-05s
Believability | Calculation of trust value for EU Soccer League took 7.867813110351562e-06s
INFO | --- Analysis for KG:Course_Submission took 3.7613260746002197s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.124641418457031e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0011203289031982422s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.2657918930053711s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.049041748046875e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 8.106231689453125e-06s
INFO | --- Analysis for KING took 2.6453022956848145s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.124641418457031e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2756350040435791s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.175041198730469e-05s
Believability | Calculation of trust value for Klappstuhlclub took 5.245208740234375e-06s
INFO | --- Analysis for klappstuhlclub took 12.530776977539062s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 11.64099645614624s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.2738831043243408s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 5.626678466796875e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 7.152557373046875e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 24.172249794006348s
Availability | SPARQL endpoint availability check for Knowledge Forest took 3.886222839355469e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2797694206237793s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.4557113647460938e-05s
Believability | Calculation of trust value for Knowledge Forest took 8.344650268554688e-06s
INFO | --- Analysis for knowledge-map took 3.008972644805908s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.1484832763671875e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.27017641067504883s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.7894973754882812e-05s
Believability | Calculation of trust value for Knowledge Forest took 7.152557373046875e-06s
INFO | --- Analysis for KnowledgeFusion took 2.3502540588378906s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.1484832763671875e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.27698850631713867s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0008029937744140625s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.771087646484375e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 6.67572021484375e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.7037832736969s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 6.008148193359375e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.2670605182647705s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.020903587341308594s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 7.62939453125e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.9603307247161865s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.553794860839844e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.2895174026489258s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020183801651000977s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.6464462280273438e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.5367431640625e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.4554195404052734s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 3.9577484130859375e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.2785823345184326s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.528594970703125e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 8.106231689453125e-06s
INFO | --- Analysis for ktr took 2.954885244369507s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.1484832763671875e-05s
Availability | VoID file availability check for Informatics Studies took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.2740318775177002s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.6941299438476562e-05s
Believability | Calculation of trust value for Informatics Studies took 9.298324584960938e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.0048086643218994s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 1.5548303127288818s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.4206390380859375s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.27808499336242676s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.02028942108154297s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.4809112548828125e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 7.867813110351562e-06s
INFO | --- Analysis for kupkb took 7.178201198577881s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.172325134277344e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.25611352920532227s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.020070791244506836s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 2.6702880859375e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 7.62939453125e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.9613547325134277s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 10.23717737197876s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.2716071605682373s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 9.369850158691406e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 6.198883056640625e-06s
INFO | --- Analysis for l3s-dblp took 48.93218517303467s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.777158737182617s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.6942474842071533s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020909786224365234s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0009243488311767578s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 7.915496826171875e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 8.344650268554688e-06s
INFO | --- Analysis for lak-dataset took 67.74822473526001s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.229841947555542s
Availability | VoID file availability check for  Language Name Authority List  took 0.000518798828125s
Extra | Recovery of all triples for  Language Name Authority List  took 591.9803230762482s
Performance | Total latancy measurement for  Language Name Authority List  took 0.6476478576660156s
Amount of data | Number of triples check for  Language Name Authority List  took 86.7548360824585s
Interoperability | New terms check for  Language Name Authority List  took 100.5440137386322s
Versatility | Languages check for  Language Name Authority List  took 300.09544825553894s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 5.870331048965454s
Security | Check HTTPS for  Language Name Authority List  took 0.3335261344909668s
Interpretability | RDF structures check for  Language Name Authority List  took 0.23858213424682617s
Versatility | Serialization formats check for  Language Name Authority List  took 14.378862857818604s
Availability | RDF dump link check for  Language Name Authority List  took 0.23386240005493164s
License | MR license check for  Language Name Authority List  took 0.2066209316253662s
License | HR license check for  Language Name Authority List  took 300.01245760917664s
Amount of data | Number of property check for  Language Name Authority List  took 0.18073773384094238s
Understandability | Number of label check for  Language Name Authority List  took 5.382125377655029s
Understandability | URI regex check for  Language Name Authority List  took 0.6209816932678223s
Understandability | Vocabs check for  Language Name Authority List  took 0.10657119750976562s
Verifiability | Authors check for  Language Name Authority List  took 0.21191930770874023s
Verifiability | Publishers check for  Language Name Authority List  took 0.2429676055908203s
Performance | Throughput check for  Language Name Authority List  took 10.666330099105835s
Amount of data | Check the number of entities for  Language Name Authority List  took 0.0001087188720703125s
Verifiability | Contribs. check for  Language Name Authority List  took 0.10779571533203125s
Interlinking | sameAs chians check for  Language Name Authority List  took 9.1160306930542s
Interlinking | skos check for  Language Name Authority List  took 0.46048426628112793s
Interlinking | skos check for  Language Name Authority List  took 0.44251346588134766s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.191328763961792s
Currency | Creation date check for  Language Name Authority List  took 0.8364393711090088s
Currency | Modification date check for  Language Name Authority List  took 0.23606657981872559s
Rep.Conc. | URIs length for  Language Name Authority List  took 540.6145660877228s
Interoperability | New vocabularies check for  Language Name Authority List  took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.17656397819519043s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.15484881401062012s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.15897750854492188s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 117.43867588043213s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.1070778369903564s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.5966179370880127s
Consistency | Disjoint class check for  Language Name Authority List  took 0.2095048427581787s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.8711612224579s
Consistency | Misplaced classes for  Language Name Authority List  took 8.679164409637451s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 119.261146068573s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.4915971755981445s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.25016140937805s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.021599769592285s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.745988130569458s
Security | Sign check for  Language Name Authority List  took 0.14965248107910156s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 4.1347455978393555s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 1.6890614032745361s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021022319793701172s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.107589721679688e-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 7.62939453125e-06s
INFO | --- Analysis for language-authority-list took 15651.559013605118s
Availability | SPARQL endpoint availability check for Lark took 385.78834867477417s
Availability | VoID file availability check for Lark took 0.0008308887481689453s
Completeness | Calculation of interlinking completeness for Lark took 0.977877140045166s
Reputation | Calculation of the PageRank for Lark took 0.021260499954223633s
Interlinking | Calculation of Degree of Connection for Lark took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Lark took 7.414817810058594e-05s
Believability | Calculation of trust value for Lark took 9.298324584960938e-06s
INFO | --- Analysis for LARK took 1681.6276342868805s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.42943739891052246s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.26195311546325684s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LASLA took 5.648790121078491s
Availability | SPARQL endpoint availability check for LATC Linksets took 6.532669067382812e-05s
Availability | VoID file availability check for LATC Linksets took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.27635931968688965s
Reputation | Calculation of the PageRank for LATC Linksets took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 2.6226043701171875e-05s
Believability | Calculation of trust value for LATC Linksets took 7.152557373046875e-06s
INFO | --- Analysis for latc-linksets took 5.653320789337158s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.3645751476287842s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.27496790885925293s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020093441009521484s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 7.62939453125e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 5.731926918029785s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.3675835132598877s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.27655506134033203s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020140409469604492s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.314018249511719e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for LatinAffectus took 5.159238576889038s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.36904072761535645s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.2601451873779297s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.020102262496948242s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for LatinWordnetLiLa took 4.024292707443237s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.0531158447265625e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0007290840148925781s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.25954747200012207s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 2.7179718017578125e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 7.867813110351562e-06s
INFO | --- Analysis for lcc took 3.0394957065582275s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 6.0558319091796875e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.28070783615112305s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011372566223144531s
Believability | Calculation of trust value for Library of Congress Subject Headings took 7.152557373046875e-06s
INFO | --- Analysis for lcsh took 5.694063425064087s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.0531158447265625e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.2716186046600342s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.058547973632812e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 7.152557373046875e-06s
INFO | --- Analysis for lcsubjects took 2.6460318565368652s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.029273986816406e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.26124095916748047s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.020282268524169922s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 2.6464462280273438e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 6.198883056640625e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.9490015506744385s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 7.277872562408447s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.2523922920227051s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.506111145019531e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 5.9604644775390625e-06s
INFO | --- Analysis for ldt@library took 32.68596577644348s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.00543212890625e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.2736785411834717s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 2.956390380859375e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 1.0013580322265625e-05s
INFO | --- Analysis for learned-genre-ontology-eng took 2.9520821571350098s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.124641418457031e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.2911696434020996s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 3.24249267578125e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 8.821487426757812e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 3.4888155460357666s
Availability | SPARQL endpoint availability check for U ime Legije took 4.315376281738281e-05s
Availability | VoID file availability check for U ime Legije took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.2883636951446533s
Reputation | Calculation of the PageRank for U ime Legije took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 2.9087066650390625e-05s
Believability | Calculation of trust value for U ime Legije took 6.198883056640625e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.4060373306274414s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 3.8623809814453125e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.27905797958374023s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 2.8133392333984375e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 6.9141387939453125e-06s
INFO | --- Analysis for legislation-openuplabs took 2.9766414165496826s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.37122678756713867s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0011756420135498047s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.26746082305908203s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 6.937980651855469e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 7.152557373046875e-06s
INFO | --- Analysis for LemmaBank took 4.228097200393677s
Availability | SPARQL endpoint availability check for lemonUby took 4.220008850097656e-05s
Availability | VoID file availability check for lemonUby took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2686750888824463s
Reputation | Calculation of the PageRank for lemonUby took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for lemonUby took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for lemonUby took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.175041198730469e-05s
Believability | Calculation of trust value for lemonUby took 5.9604644775390625e-06s
INFO | --- Analysis for lemonuby took 3.282866954803467s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.124641418457031e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.27202558517456055s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.218650817871094e-05s
Believability | Calculation of trust value for LemonWiktionary took 7.62939453125e-06s
INFO | --- Analysis for lemonwiktionary took 4.448554277420044s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.3347136974334717s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0007815361022949219s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.27893733978271484s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.457069396972656e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for LewisShort took 3.6362974643707275s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.1153335571289062s
Availability | VoID file availability check for LEXIN-RDF took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.2876577377319336s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.01999497413635254s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 2.9087066650390625e-05s
Believability | Calculation of trust value for LEXIN-RDF took 3.24249267578125e-05s
INFO | --- Analysis for lexin-rdf took 5.679497957229614s
Availability | SPARQL endpoint availability check for lexinfo took 5.2928924560546875e-05s
Availability | VoID file availability check for lexinfo took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for lexinfo took 0.3086271286010742s
Reputation | Calculation of the PageRank for lexinfo took 0.020194053649902344s
Interlinking | Calculation of Degree of Connection for lexinfo took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for lexinfo took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.58306884765625e-05s
Believability | Calculation of trust value for lexinfo took 7.3909759521484375e-06s
INFO | --- Analysis for lexinfo took 3.0026979446411133s
Availability | SPARQL endpoint availability check for Lexvo took 4.100799560546875e-05s
Availability | VoID file availability check for Lexvo took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Lexvo took 0.28175806999206543s
Reputation | Calculation of the PageRank for Lexvo took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for Lexvo took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lexvo took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017070770263671875s
Believability | Calculation of trust value for Lexvo took 6.198883056640625e-06s
INFO | --- Analysis for lexvo took 3.2771120071411133s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.2438507080078125e-05s
Availability | VoID file availability check for Lexvo.org took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.28690218925476074s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 6.890296936035156e-05s
Believability | Calculation of trust value for Lexvo.org took 6.4373016357421875e-06s
INFO | --- Analysis for lexvo-org took 2.587165117263794s
Availability | SPARQL endpoint availability check for LIBRIS took 0.3671853542327881s
Availability | VoID file availability check for LIBRIS took 0.0006475448608398438s
Extra | Recovery of all triples for LIBRIS took 18.45257878303528s
Performance | Total latancy measurement for LIBRIS took 0.7051620483398438s
Amount of data | Number of triples check for LIBRIS took 31.26311755180359s
Interoperability | New terms check for LIBRIS took 16.12856149673462s
Versatility | Languages check for LIBRIS took 0.18050074577331543s
Interpretability | Number of blank nodes check for LIBRIS took 300.0683970451355s
Security | Check HTTPS for LIBRIS took 0.3323025703430176s
Interpretability | RDF structures check for LIBRIS took 0.24688506126403809s
Versatility | Serialization formats check for LIBRIS took 0.24312591552734375s
Availability | RDF dump link check for LIBRIS took 0.14530467987060547s
License | MR license check for LIBRIS took 0.27323222160339355s
License | HR license check for LIBRIS took 0.2029404640197754s
Amount of data | Number of property check for LIBRIS took 0.19960403442382812s
Understandability | Number of label check for LIBRIS took 0.44426703453063965s
Understandability | URI regex check for LIBRIS took 0.3094937801361084s
Understandability | Vocabs check for LIBRIS took 0.14475417137145996s
Verifiability | Authors check for LIBRIS took 0.18349170684814453s
Verifiability | Publishers check for LIBRIS took 0.1531832218170166s
Performance | Throughput check for LIBRIS took 10.443939447402954s
Amount of data | Check the number of entities for LIBRIS took 0.00010085105895996094s
Verifiability | Contribs. check for LIBRIS took 0.1521611213684082s
Interlinking | sameAs chians check for LIBRIS took 0.1698312759399414s
Interlinking | skos check for LIBRIS took 0.20256543159484863s
Interlinking | skos check for LIBRIS took 0.12897992134094238s
Timeliness | dataset update frequency check for LIBRIS took 0.16722798347473145s
Currency | Creation date check for LIBRIS took 0.3329794406890869s
Currency | Modification date check for LIBRIS took 0.6705901622772217s
Rep.Conc. | URIs length for LIBRIS took 85.4154326915741s
Interoperability | New vocabularies check for LIBRIS took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.17233848571777344s
Accuracy | Check Functional Property for LIBRIS took 0.18692731857299805s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.15239286422729492s
Accuracy | Check Datatype consistency for LIBRIS took 0.2749667167663574s
Consistency | Disjoint class check for LIBRIS took 0.1716446876525879s
Consistency | Check Misplaced properties for LIBRIS took 62.6509165763855s
Consistency | Misplaced classes for LIBRIS took 1.133826732635498s
Consistency | Check Ontology hijacking for LIBRIS took 6.107813358306885s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.1447954177856445s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 63.754159688949585s
Conciseness | Check Extensional conciseness for LIBRIS took 0.28151988983154297s
Conciseness | Check Intensional conciseness for LIBRIS took 0.3697035312652588s
Security | Sign check for LIBRIS took 0.2086477279663086s
Availability | Check URIs Dereferenciability for LIBRIS took 5.265434503555298s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.7925148010253906s
Reputation | Calculation of the PageRank for LIBRIS took 0.020130395889282227s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.250640869140625e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.430511474609375e-06s
Believability | Calculation of trust value for LIBRIS took 7.152557373046875e-06s
INFO | --- Analysis for libris took 1096.8965122699738s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06345868110656738s
Availability | VoID file availability check for Public Library of Veroia took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.6978738307952881s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02353191375732422s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.2479248046875e-05s
Believability | Calculation of trust value for Public Library of Veroia took 7.62939453125e-06s
INFO | --- Analysis for libver took 4.517333269119263s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.14191603660583496s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.25423669815063477s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.130073547363281e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 5.245208740234375e-06s
INFO | --- Analysis for lichfield-spending took 4.481031656265259s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.863739013671875e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.28084516525268555s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.504753112792969e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 6.9141387939453125e-06s
INFO | --- Analysis for lime took 8.410731315612793s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.172325134277344e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0010538101196289062s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.2775745391845703s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02077507972717285s
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.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010561943054199219s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 6.9141387939453125e-06s
INFO | --- Analysis for lingvoj took 6.628649950027466s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.26111459732055664s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.0108642578125e-05s
Believability | Calculation of trust value for Linked Crunchbase took 7.3909759521484375e-06s
INFO | --- Analysis for linked-crunchbase took 3.337066888809204s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.051009893417358s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2762455940246582s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.319450378417969e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 5.4836273193359375e-06s
INFO | --- Analysis for linked-drugs took 20.42328453063965s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.363059997558594e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.2682030200958252s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.512901306152344e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 5.0067901611328125e-06s
INFO | --- Analysis for linked-edgar took 4.59284782409668s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 5.030632019042969e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.2774467468261719s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.584426879882812e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-eurostat took 4.63765025138855s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.410743713378906e-05s
Availability | VoID file availability check for linked hypernyms took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2619810104370117s
Reputation | Calculation of the PageRank for linked hypernyms took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 6.890296936035156e-05s
Believability | Calculation of trust value for linked hypernyms took 6.9141387939453125e-06s
INFO | --- Analysis for linked-hypernyms took 5.097135305404663s
Availability | SPARQL endpoint availability check for Linked Life Data took 239.20808959007263s
Availability | VoID file availability check for Linked Life Data took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.46118807792663574s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.650520324707031e-05s
Believability | Calculation of trust value for Linked Life Data took 7.3909759521484375e-06s
INFO | --- Analysis for linked-life-data took 700.2509999275208s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.3089334964752197s
Availability | VoID file availability check for Linked Logainm took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.25977444648742676s
Reputation | Calculation of the PageRank for Linked Logainm took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 7.43865966796875e-05s
Believability | Calculation of trust value for Linked Logainm took 8.344650268554688e-06s
INFO | --- Analysis for linked-logainm took 4.551811218261719s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.267692565917969e-05s
Availability | VoID file availability check for Linked NUTS took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.26425623893737793s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020332813262939453s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 4.863739013671875e-05s
Believability | Calculation of trust value for Linked NUTS took 4.76837158203125e-06s
INFO | --- Analysis for linked-nuts took 4.718076229095459s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.1961669921875e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.2596564292907715s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 2.765655517578125e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 7.152557373046875e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 3.4204280376434326s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 2.2708957195281982s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.713752269744873s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020287275314331055s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.2901763916015625e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.4836273193359375e-06s
INFO | --- Analysis for linked-open-camera took 5.6735429763793945s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 0.6512131690979004s
Availability | VoID file availability check for Linked Open Commerce took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.3045156002044678s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 2.7894973754882812e-05s
Believability | Calculation of trust value for Linked Open Commerce took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-commerce took 5.217306613922119s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.2054011821746826s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.2682836055755615s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.000102996826171875s
Believability | Calculation of trust value for Linked Open Data of Ecology took 8.821487426757812e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 4.568439722061157s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.1961669921875e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.25719308853149414s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020130634307861328s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.845329284667969e-05s
Believability | Calculation of trust value for Linked Open Numbers took 6.198883056640625e-06s
INFO | --- Analysis for linked-open-numbers took 2.5310921669006348s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 6.937980651855469e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2719604969024658s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.8848648071289062e-05s
Believability | Calculation of trust value for Linked Open Piracy took 5.4836273193359375e-06s
INFO | --- Analysis for linked-open-piracy took 6.186792850494385s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.124641418457031e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.2759861946105957s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 7.152557373046875e-06s
INFO | --- Analysis for linked-open-senate took 2.986802577972412s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 1.227733850479126s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.2505362033843994s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020345687866210938s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.673004150390625e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 6.4373016357421875e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 11.09539794921875s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.2524869441986084s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.218650817871094e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 7.3909759521484375e-06s
INFO | --- Analysis for linked-periodicals took 2.47812557220459s
Availability | SPARQL endpoint availability check for Linked Index took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Index took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Linked Index took 0.27811098098754883s
Reputation | Calculation of the PageRank for Linked Index took 0.0202178955078125s
Interlinking | Calculation of Degree of Connection for Linked Index took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Index took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.082389831542969e-05s
Believability | Calculation of trust value for Linked Index took 7.152557373046875e-06s
INFO | --- Analysis for linked-stockindex took 2.428896903991699s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.876815557479858s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2617483139038086s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.021126508712768555s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 4.172325134277344e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 8.106231689453125e-06s
INFO | --- Analysis for linked-structured-product-labels took 30.782676696777344s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.6440300941467285s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.2640831470489502s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.0517578125e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 6.9141387939453125e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 3.696423053741455s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.301705598831177s
Availability | VoID file availability check for Linked TCGA took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.6920690536499023s
Reputation | Calculation of the PageRank for Linked TCGA took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.58306884765625e-05s
Believability | Calculation of trust value for Linked TCGA took 6.9141387939453125e-06s
INFO | --- Analysis for linked-tcga took 63.60753417015076s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.21590375900268555s
Availability | VoID file availability check for Linked User Feedback took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.2599494457244873s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.020132780075073242s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.504753112792969e-05s
Believability | Calculation of trust value for Linked User Feedback took 7.62939453125e-06s
INFO | --- Analysis for linked-user-feedback took 3.7160544395446777s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.0531158447265625e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2930264472961426s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.486343383789062e-05s
Believability | Calculation of trust value for USPTO Patent data took 2.2172927856445312e-05s
INFO | --- Analysis for linked-uspto-patent-data took 59.36597657203674s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 3.9577484130859375e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.27761054039001465s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 8.344650268554688e-06s
INFO | --- Analysis for linked-web-apis took 3.416912317276001s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.076957702636719e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.00037550926208496094s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.2896420955657959s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.021648883819580078s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.0994415283203125e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 8.344650268554688e-06s
INFO | --- Analysis for linkedarc took 2.9654102325439453s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.04915189743041992s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2906060218811035s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.314018249511719e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 8.344650268554688e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 3.2668261528015137s
Availability | SPARQL endpoint availability check for LinkedCT took 0.6810324192047119s
Availability | VoID file availability check for LinkedCT took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.2794802188873291s
Reputation | Calculation of the PageRank for LinkedCT took 0.021275758743286133s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.965896606445312e-05s
Believability | Calculation of trust value for LinkedCT took 8.106231689453125e-06s
INFO | --- Analysis for linkedct took 5.492430925369263s
Availability | SPARQL endpoint availability check for LinkedGeoData took 7.244882106781006s
Availability | VoID file availability check for LinkedGeoData took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.2654848098754883s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.0001239776611328125s
Believability | Calculation of trust value for LinkedGeoData took 8.821487426757812e-06s
INFO | --- Analysis for linkedgeodata took 23.689463138580322s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 4.124641418457031e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.28719425201416016s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 2.9802322387695312e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 7.62939453125e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 3.0110926628112793s
Availability | SPARQL endpoint availability check for LinkedLCCN took 0.7625589370727539s
Availability | VoID file availability check for LinkedLCCN took 0.0007848739624023438s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.30654358863830566s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020474672317504883s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010514259338378906s
Believability | Calculation of trust value for LinkedLCCN took 9.298324584960938e-06s
INFO | --- Analysis for linkedlccn took 10.38420057296753s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.267692565917969e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.3032801151275635s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.933906555175781e-05s
Believability | Calculation of trust value for LinkedMarkMail took 9.059906005859375e-06s
INFO | --- Analysis for linkedmarkmail took 2.630786418914795s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.621243953704834s
Availability | VoID file availability check for Linked Movie DataBase took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2800719738006592s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.02089858055114746s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013375282287597656s
Believability | Calculation of trust value for Linked Movie DataBase took 6.67572021484375e-06s
INFO | --- Analysis for linkedmdb took 133.48776149749756s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 8.086796998977661s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007946491241455078s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.29146575927734375s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.020773649215698242s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.128715515136719e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for linkedspending took 24.39994168281555s
Availability | SPARQL endpoint availability check for LinkedStats took 3.886222839355469e-05s
Availability | VoID file availability check for LinkedStats took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.2605299949645996s
Reputation | Calculation of the PageRank for LinkedStats took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0008075237274169922s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 2.7894973754882812e-05s
Believability | Calculation of trust value for LinkedStats took 6.4373016357421875e-06s
INFO | --- Analysis for linkedstats took 2.9750475883483887s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.029273986816406e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.2794950008392334s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.552436828613281e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 9.059906005859375e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 3.01320743560791s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.076957702636719e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.28091955184936523s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 8.821487426757812e-06s
INFO | --- Analysis for linking-open-drug-data took 2.9718356132507324s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.033379316329956055s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0003287792205810547s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.2588620185852051s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010633468627929688s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 9.059906005859375e-06s
INFO | --- Analysis for linklion took 2.5074567794799805s
Availability | SPARQL endpoint availability check for Lion's Den took 4.029273986816406e-05s
Availability | VoID file availability check for Lion's Den took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.28278160095214844s
Reputation | Calculation of the PageRank for Lion's Den took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 2.9087066650390625e-05s
Believability | Calculation of trust value for Lion's Den took 8.106231689453125e-06s
INFO | --- Analysis for lionsden took 2.9760191440582275s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 43.73113393783569s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.29980945587158203s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 4.6253204345703125e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 49.42653965950012s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 3.981590270996094e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.25194215774536133s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 2.7179718017578125e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 7.3909759521484375e-06s
INFO | --- Analysis for livtdm took 3.408923387527466s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 3.933906555175781e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.26825737953186035s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.0203096866607666s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 2.6702880859375e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 8.344650268554688e-06s
INFO | --- Analysis for livtdm2017 took 3.007572889328003s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 5.7220458984375e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.2789914608001709s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.020839452743530273s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 2.765655517578125e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 7.3909759521484375e-06s
INFO | --- Analysis for lobi took 2.984276056289673s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.1389079093933105s
Availability | VoID file availability check for lobid-organisations took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.2653207778930664s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.298324584960938e-05s
Believability | Calculation of trust value for lobid-organisations took 7.3909759521484375e-06s
INFO | --- Analysis for lobid-organisations took 5.7620768547058105s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.8475596904754639s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0012047290802001953s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.26455163955688477s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020745038986206055s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010275840759277344s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 6.9141387939453125e-06s
INFO | --- Analysis for lobid-resources took 7.951624631881714s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.100799560546875e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.2635691165924072s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 6.866455078125e-05s
Believability | Calculation of trust value for Linked Open Colors took 6.9141387939453125e-06s
INFO | --- Analysis for loc took 6.063708543777466s
Availability | SPARQL endpoint availability check for Location Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Location Ontology took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.254838228225708s
Reputation | Calculation of the PageRank for Location Ontology took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for Location Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Location_Ontology took 3.7132925987243652s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.28788328170776367s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020771265029907227s
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.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.695487976074219e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 7.62939453125e-06s
INFO | --- Analysis for locv took 35.07224726676941s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7297842502593994s
Availability | VoID file availability check for LOD-a-lot took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2601945400238037s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 2.9325485229492188e-05s
Believability | Calculation of trust value for LOD-a-lot took 6.67572021484375e-06s
INFO | --- Analysis for lod-a-lot took 13.959807872772217s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.00543212890625e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.28906702995300293s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 2.6702880859375e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 7.62939453125e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 2.973630905151367s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.0531158447265625e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.29090452194213867s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 7.62939453125e-06s
INFO | --- Analysis for lod-taiwan took 3.0231189727783203s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.100799560546875e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2739391326904297s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.02065134048461914s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 9.965896606445312e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 6.67572021484375e-06s
INFO | --- Analysis for lod2-project-wiki took 2.463676929473877s
Availability | SPARQL endpoint availability check for LODAC BDLS took 3.1329076290130615s
Availability | VoID file availability check for LODAC BDLS took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2729945182800293s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.152557373046875e-05s
Believability | Calculation of trust value for LODAC BDLS took 6.9141387939453125e-06s
INFO | --- Analysis for lodac-bdls took 14.097147226333618s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.00543212890625e-05s
Availability | VoID file availability check for LODRussia Math took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.2685089111328125s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.86102294921875e-05s
Believability | Calculation of trust value for LODRussia Math took 8.58306884765625e-06s
INFO | --- Analysis for lodrussia-math took 2.9971580505371094s
Availability | SPARQL endpoint availability check for LODRussia Nano took 3.8623809814453125e-05s
Availability | VoID file availability check for LODRussia Nano took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.2628312110900879s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.020839214324951172s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 3.0040740966796875e-05s
Believability | Calculation of trust value for LODRussia Nano took 7.867813110351562e-06s
INFO | --- Analysis for lodrussia-nano took 3.0223283767700195s
Availability | SPARQL endpoint availability check for LODStats took 3.933906555175781e-05s
Availability | VoID file availability check for LODStats took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for LODStats took 0.2962219715118408s
Reputation | Calculation of the PageRank for LODStats took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for LODStats took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for LODStats took 3.0517578125e-05s
Believability | Calculation of trust value for LODStats took 7.3909759521484375e-06s
INFO | --- Analysis for lodstats took 3.027562379837036s
Availability | SPARQL endpoint availability check for LODUM took 4.029273986816406e-05s
Availability | VoID file availability check for LODUM took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for LODUM took 0.28997111320495605s
Reputation | Calculation of the PageRank for LODUM took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for LODUM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LODUM took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for LODUM took 2.7894973754882812e-05s
Believability | Calculation of trust value for LODUM took 7.62939453125e-06s
INFO | --- Analysis for lodum took 3.017859935760498s
Availability | SPARQL endpoint availability check for lofd took 0.13237237930297852s
Availability | VoID file availability check for lofd took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for lofd took 0.25299668312072754s
Reputation | Calculation of the PageRank for lofd took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for lofd took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lofd took 0.0008027553558349609s
Interlinking | Calculation of Clustering coefficient for lofd took 3.600120544433594e-05s
Believability | Calculation of trust value for lofd took 7.867813110351562e-06s
INFO | --- Analysis for lofd took 2.63504695892334s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 272.2759687900543s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0010688304901123047s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.25859761238098145s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.022821903228759766s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.4836273193359375e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 6.198883056640625e-06s
INFO | --- Analysis for loius took 586.3195381164551s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.076957702636719e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.7427129745483398s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.02082061767578125s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 2.7418136596679688e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 7.152557373046875e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 5.810373306274414s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 2.019968032836914s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.2739715576171875s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.3882598876953125e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.7220458984375e-06s
INFO | --- Analysis for london-gazette took 9.009848833084106s
Availability | SPARQL endpoint availability check for Weather Stations took 5.5789947509765625e-05s
Availability | VoID file availability check for Weather Stations took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.716332197189331s
Reputation | Calculation of the PageRank for Weather Stations took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0010287761688232422s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 9.751319885253906e-05s
Believability | Calculation of trust value for Weather Stations took 8.106231689453125e-06s
INFO | --- Analysis for los_metar took 14.819067478179932s
Availability | SPARQL endpoint availability check for Lotico took 0.9254519939422607s
Availability | VoID file availability check for Lotico took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Lotico took 0.24758648872375488s
Reputation | Calculation of the PageRank for Lotico took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for Lotico took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Lotico took 7.987022399902344e-05s
Believability | Calculation of trust value for Lotico took 6.4373016357421875e-06s
INFO | --- Analysis for lotico took 7.885888576507568s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.32077574729919434s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.2638428211212158s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.0517578125e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 6.4373016357421875e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 4.837440729141235s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5900955200195312s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0002586841583251953s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 124.02482175827026s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.997229814529419s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.586736679077148s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 15.649854898452759s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2183177471161s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.775810480117798s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.27767062187194824s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.558175086975098s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3094346523284912s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6046195030212402s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2479953765869s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.399261474609375s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.793084144592285s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.7738809585571289s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4128849506378174s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.206268310546875s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.25737881660461426s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.306285619735718s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 6.699562072753906e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.18424701690673828s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19695639610290527s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4716966152191162s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.47075414657592773s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 6.618592977523804s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.504497766494751s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.22577404975891113s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 165.11717653274536s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19157838821411133s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.38524484634399414s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.38828015327453613s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 45.40706944465637s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.691727876663208s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6588430404663086s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19603490829467773s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 95.71100878715515s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.443792343139648s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 37.58964729309082s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2116599082946777s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 94.59957337379456s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7584316730499268s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6235299110412598s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.8028488159179688s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.087465524673462s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9995267391204834s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.02349090576171875s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.528594970703125e-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 2318.425089597702s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1755213737487793s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0002605915069580078s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 115.64108610153198s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.953632116317749s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.184376239776611s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 13.574702739715576s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.22072529792786s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.828578472137451s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.24605131149291992s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.930086135864258s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.26587629318237305s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4700326919555664s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2475128173828s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2936990261077881s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.8591880798339844s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.6748614311218262s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.35526132583618164s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20366525650024414s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.254047155380249s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.40160083770752s
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.2126302719116211s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1821737289428711s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4465038776397705s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4671053886413574s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.012232065200806s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.47239208221435547s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21855592727661133s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 159.15282583236694s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19365143775939941s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3254718780517578s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3286135196685791s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 44.26013708114624s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.722848653793335s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.755004405975342s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19568610191345215s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 89.90503787994385s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.47715449333191s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 36.091309547424316s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2588739395141602s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 99.60619282722473s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.839449405670166s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5466670989990234s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.7423415184020996s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.41838264465332s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.4495811462402344s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.719329833984375e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2293.805111169815s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.696846008300781e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.7216393947601318s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.02097034454345703s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 2.9087066650390625e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 8.106231689453125e-06s
INFO | --- Analysis for lremap-auth took 6.411407709121704s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.2438507080078125e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2761399745941162s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.021518230438232422s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0009829998016357422s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.2901763916015625e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 7.3909759521484375e-06s
INFO | --- Analysis for lremap-conf took 3.53958797454834s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.220008850097656e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.26637983322143555s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 2.956390380859375e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.8835067749023438e-05s
INFO | --- Analysis for lremap-ri took 3.6439664363861084s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.363059997558594e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.27805376052856445s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.021265506744384766s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.409385681152344e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 8.106231689453125e-06s
INFO | --- Analysis for lremap-sub took 3.0185089111328125s
Availability | SPARQL endpoint availability check for LSQ took 4.1961669921875e-05s
Availability | VoID file availability check for LSQ took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for LSQ took 0.24712038040161133s
Reputation | Calculation of the PageRank for LSQ took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for LSQ took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.0040740966796875e-05s
Believability | Calculation of trust value for LSQ took 7.867813110351562e-06s
INFO | --- Analysis for lsq took 6.28542423248291s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.4877800941467285s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.30895090103149414s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020848512649536133s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 4.1484832763671875e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 8.344650268554688e-06s
INFO | --- Analysis for LucaniPharsalia took 4.911984443664551s
Availability | SPARQL endpoint availability check for Linked rules took 4.124641418457031e-05s
Availability | VoID file availability check for Linked rules took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2833259105682373s
Reputation | Calculation of the PageRank for Linked rules took 0.02023935317993164s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Linked rules took 2.765655517578125e-05s
Believability | Calculation of trust value for Linked rules took 6.9141387939453125e-06s
INFO | --- Analysis for Luminaires_senlis took 2.4195854663848877s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.0531158447265625e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.28618669509887695s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 2.765655517578125e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 6.67572021484375e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.966158866882324s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.133316040039062s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.29409289360046387s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020867586135864258s
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.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 2.8848648071289062e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 7.152557373046875e-06s
INFO | --- Analysis for makg took 63.382811069488525s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 5.245208740234375e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.2728300094604492s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.218650817871094e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 6.9141387939453125e-06s
INFO | --- Analysis for manchester-university-reading-lists took 3.4966368675231934s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.172325134277344e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2519381046295166s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02030634880065918s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.6941299438476562e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.62939453125e-06s
INFO | --- Analysis for manish took 3.687645435333252s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.124641418457031e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.2992284297943115s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 2.9325485229492188e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 7.62939453125e-06s
INFO | --- Analysis for mapa-referencia-bogota took 3.458066940307617s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.100799560546875e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.28568410873413086s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.0994415283203125e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 6.9141387939453125e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 3.3659303188323975s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.1484832763671875e-05s
Availability | VoID file availability check for MARC Codes List took 0.0008351802825927734s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.26694464683532715s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020756959915161133s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012254714965820312s
Believability | Calculation of trust value for MARC Codes List took 7.62939453125e-06s
INFO | --- Analysis for marc-codes took 13.950075149536133s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.3392181396484375e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.26230835914611816s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02045750617980957s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.814697265625e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 7.62939453125e-06s
INFO | --- Analysis for masc took 6.854929447174072s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.124641418457031e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.29526734352111816s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020676136016845703s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.528594970703125e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 5.9604644775390625e-06s
INFO | --- Analysis for masc-bn-nif took 5.490068435668945s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.226686716079712s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.27492833137512207s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020478010177612305s
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.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.9087066650390625e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 7.3909759521484375e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 4.6030848026275635s
Availability | SPARQL endpoint availability check for medline took 4.172325134277344e-05s
Availability | VoID file availability check for medline took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for medline took 0.2889573574066162s
Reputation | Calculation of the PageRank for medline took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for medline took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for medline took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for medline took 3.361701965332031e-05s
Believability | Calculation of trust value for medline took 1.1205673217773438e-05s
INFO | --- Analysis for medline took 6.1209800243377686s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.7001063823699951s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.2699129581451416s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020086288452148438s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.604194641113281e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 6.198883056640625e-06s
INFO | --- Analysis for meducator took 13.873263359069824s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 3.981590270996094e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.290863037109375s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.86102294921875e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 5.9604644775390625e-06s
INFO | --- Analysis for mesh-finnish took 3.4039013385772705s
Availability | SPARQL endpoint availability check for MeSH headings took 5.221366882324219e-05s
Availability | VoID file availability check for MeSH headings took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.250826358795166s
Reputation | Calculation of the PageRank for MeSH headings took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for MeSH headings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MeSH headings took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 2.8371810913085938e-05s
Believability | Calculation of trust value for MeSH headings took 6.4373016357421875e-06s
INFO | --- Analysis for mesh_headings took 2.896655321121216s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 3.886222839355469e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.24928569793701172s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.1948089599609375e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 6.4373016357421875e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.981949806213379s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.935264587402344e-05s
Availability | VoID file availability check for MeSH pairs took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.2596418857574463s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.6226043701171875e-05s
Believability | Calculation of trust value for MeSH pairs took 6.198883056640625e-06s
INFO | --- Analysis for mesh_pairs took 2.927342414855957s
Availability | SPARQL endpoint availability check for MeSH titles took 4.076957702636719e-05s
Availability | VoID file availability check for MeSH titles took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.26838135719299316s
Reputation | Calculation of the PageRank for MeSH titles took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 3.0040740966796875e-05s
Believability | Calculation of trust value for MeSH titles took 9.059906005859375e-06s
INFO | --- Analysis for mesh_titles took 2.8864219188690186s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 9.965896606445312e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0003273487091064453s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2793135643005371s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.021681785583496094s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.075599670410156e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 7.867813110351562e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 3.0098187923431396s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 7.343292236328125e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.26395702362060547s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.075599670410156e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 8.106231689453125e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.9557807445526123s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.1484832763671875e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.27367401123046875s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.021435260772705078s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 0.00013446807861328125s
Believability | Calculation of trust value for MetaShare metadata model took 8.344650268554688e-06s
INFO | --- Analysis for metashare took 2.6129226684570312s
Availability | SPARQL endpoint availability check for MExiCo took 6.866455078125e-05s
Availability | VoID file availability check for MExiCo took 0.0008420944213867188s
Completeness | Calculation of interlinking completeness for MExiCo took 0.26935362815856934s
Reputation | Calculation of the PageRank for MExiCo took 0.020863056182861328s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.3882598876953125e-05s
Believability | Calculation of trust value for MExiCo took 8.821487426757812e-06s
INFO | --- Analysis for mexico took 22.92941975593567s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.0418627262115479s
Availability | VoID file availability check for Coronavirus dataset took 0.00030493736267089844s
Extra | Recovery of all triples for Coronavirus dataset took 130.78600788116455s
Performance | Total latancy measurement for Coronavirus dataset took 2.486586809158325s
Amount of data | Number of triples check for Coronavirus dataset took 1.2045238018035889s
Interoperability | New terms check for Coronavirus dataset took 2.408475875854492s
Versatility | Languages check for Coronavirus dataset took 60.51347780227661s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.145150661468506s
Interpretability | RDF structures check for Coronavirus dataset took 0.5328521728515625s
Versatility | Serialization formats check for Coronavirus dataset took 0.550539493560791s
Availability | RDF dump link check for Coronavirus dataset took 0.5019824504852295s
License | MR license check for Coronavirus dataset took 1.5976808071136475s
License | HR license check for Coronavirus dataset took 40.10348033905029s
Amount of data | Number of property check for Coronavirus dataset took 0.5539736747741699s
Understandability | Number of label check for Coronavirus dataset took 1.3029088973999023s
Understandability | URI regex check for Coronavirus dataset took 1.0266551971435547s
Understandability | Vocabs check for Coronavirus dataset took 0.4966871738433838s
Verifiability | Authors check for Coronavirus dataset took 0.8449068069458008s
Verifiability | Publishers check for Coronavirus dataset took 0.51798415184021s
Performance | Throughput check for Coronavirus dataset took 13.659013509750366s
Amount of data | Check the number of entities for Coronavirus dataset took 9.775161743164062e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.5039770603179932s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5699741840362549s
Interlinking | skos check for Coronavirus dataset took 0.5630347728729248s
Interlinking | skos check for Coronavirus dataset took 0.4926464557647705s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.509915828704834s
Currency | Creation date check for Coronavirus dataset took 1.0192961692810059s
Currency | Modification date check for Coronavirus dataset took 1.021852970123291s
Rep.Conc. | URIs length for Coronavirus dataset took 30.378324031829834s
Interoperability | New vocabularies check for Coronavirus dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5298933982849121s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7979798316955566s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.8271725177764893s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 19.526726245880127s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.02295660972595215s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.029311656951904297s
Consistency | Disjoint class check for Coronavirus dataset took 1.1206810474395752s
Consistency | Check Misplaced properties for Coronavirus dataset took 35.85525465011597s
Consistency | Misplaced classes for Coronavirus dataset took 0.6264917850494385s
Consistency | Check Ontology hijacking for Coronavirus dataset took 31.30388617515564s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.184962272644043s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.676357269287109s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03440213203430176s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5201084613800049s
Security | Sign check for Coronavirus dataset took 0.5337138175964355s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3416.626672267914s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.204157829284668s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 6.985664367675781e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 7.152557373046875e-06s
INFO | --- Analysis for micro-coronavirus took 3870.726970911026s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.7206878662109375e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.24765753746032715s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.019857406616210938s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00011038780212402344s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 6.4373016357421875e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 5.338494300842285s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.27064037322998047s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.021685361862182617s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00014019012451171875s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for mismuseos-gnoss took 5.073282957077026s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.10389113426208496s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.25675058364868164s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.38690185546875e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 6.198883056640625e-06s
INFO | --- Analysis for mlsa took 3.8772900104522705s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.267692565917969e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.27547168731689453s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.314018249511719e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 6.198883056640625e-06s
INFO | --- Analysis for model took 38.23900485038757s
Availability | SPARQL endpoint availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 4.1484832763671875e-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.000606536865234375s
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.30045056343078613s
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.02032923698425293s
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 9.5367431640625e-06s
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.0007517337799072266s
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.8848648071289062e-05s
Believability | Calculation of trust value for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 6.67572021484375e-06s
INFO | --- Analysis for model1 took 25.25000786781311s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.124641418457031e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.28867554664611816s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.020541906356811523s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 3.0994415283203125e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 1.049041748046875e-05s
INFO | --- Analysis for mond took 3.8552372455596924s
Availability | SPARQL endpoint availability check for MONDIS took 4.1484832763671875e-05s
Availability | VoID file availability check for MONDIS took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for MONDIS took 0.26026344299316406s
Reputation | Calculation of the PageRank for MONDIS took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for MONDIS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MONDIS took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.7418136596679688e-05s
Believability | Calculation of trust value for MONDIS took 6.67572021484375e-06s
INFO | --- Analysis for mondis took 3.45036244392395s
Availability | SPARQL endpoint availability check for Monumentos took 4.100799560546875e-05s
Availability | VoID file availability check for Monumentos took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Monumentos took 0.2829930782318115s
Reputation | Calculation of the PageRank for Monumentos took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for Monumentos took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Monumentos took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Monumentos took 2.956390380859375e-05s
Believability | Calculation of trust value for Monumentos took 6.67572021484375e-06s
INFO | --- Analysis for monumentos-zaragoza took 3.433422088623047s
Availability | SPARQL endpoint availability check for MORElab took 0.9855494499206543s
Availability | VoID file availability check for MORElab took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for MORElab took 0.2783799171447754s
Reputation | Calculation of the PageRank for MORElab took 0.02025747299194336s
Interlinking | Calculation of Degree of Connection for MORElab took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for MORElab took 0.00010466575622558594s
Believability | Calculation of trust value for MORElab took 1.049041748046875e-05s
INFO | --- Analysis for morelab took 4.995047092437744s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 2.058438539505005s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.6922914981842041s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.702278137207031e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 8.344650268554688e-06s
INFO | --- Analysis for msc took 7.166643142700195s
Availability | SPARQL endpoint availability check for Multext-East took 8.368492126464844e-05s
Availability | VoID file availability check for Multext-East took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Multext-East took 0.292957067489624s
Reputation | Calculation of the PageRank for Multext-East took 0.020821809768676758s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.528594970703125e-05s
Believability | Calculation of trust value for Multext-East took 8.106231689453125e-06s
INFO | --- Analysis for multext-east took 2.911663293838501s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.220008850097656e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.2681694030761719s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.02158665657043457s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.409385681152344e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 7.62939453125e-06s
INFO | --- Analysis for multilingualeulaw took 2.9965128898620605s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.291534423828125e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.27718162536621094s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.361701965332031e-05s
Believability | Calculation of trust value for Multimedia Lab took 8.344650268554688e-06s
INFO | --- Analysis for multimedia-lab took 2.4876363277435303s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.029273986816406e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.2724342346191406s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020823955535888672s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 3.0517578125e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 8.821487426757812e-06s
INFO | --- Analysis for munich-offener-haushalt took 3.0267367362976074s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.8178493976593018s
Availability | VoID file availability check for Muninn World War I took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.2803993225097656s
Reputation | Calculation of the PageRank for Muninn World War I took 0.021545886993408203s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.153915405273438e-05s
Believability | Calculation of trust value for Muninn World War I took 6.198883056640625e-06s
INFO | --- Analysis for muninn-world-war-i took 10.59254240989685s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.076957702636719e-05s
Availability | VoID file availability check for Musei Italiani took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.2653806209564209s
Reputation | Calculation of the PageRank for Musei Italiani took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 2.86102294921875e-05s
Believability | Calculation of trust value for Musei Italiani took 6.9141387939453125e-06s
INFO | --- Analysis for musei-italiani took 3.0025746822357178s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2768070697784424s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.02058553695678711s
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.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.000118255615234375s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 8.58306884765625e-06s
INFO | --- Analysis for museosespania-gnoss took 3.133047103881836s
Availability | SPARQL endpoint availability check for Italian Museums took 1.7586326599121094s
Availability | VoID file availability check for Italian Museums took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.26596546173095703s
Reputation | Calculation of the PageRank for Italian Museums took 0.020938396453857422s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.058547973632812e-05s
Believability | Calculation of trust value for Italian Museums took 2.6941299438476562e-05s
INFO | --- Analysis for museums-in-italy took 4.20745062828064s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.076957702636719e-05s
Availability | VoID file availability check for MusicBrainz took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.30775022506713867s
Reputation | Calculation of the PageRank for MusicBrainz took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.2901763916015625e-05s
Believability | Calculation of trust value for MusicBrainz took 7.152557373046875e-06s
INFO | --- Analysis for musicbrainz_ took 3.0099658966064453s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.482269287109375e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.2622804641723633s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.020573139190673828s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.765655517578125e-05s
Believability | Calculation of trust value for MusicNet Codex took 7.3909759521484375e-06s
INFO | --- Analysis for musicnet_codex took 3.010749340057373s
Availability | SPARQL endpoint availability check for Muziekweb took 0.8864994049072266s
Availability | VoID file availability check for Muziekweb took 0.00057220458984375s
Extra | Recovery of all triples for Muziekweb took 1.924722671508789s
Performance | Total latancy measurement for Muziekweb took 1.4692637920379639s
Amount of data | Number of triples check for Muziekweb took 0.40767741203308105s
Interoperability | New terms check for Muziekweb took 1.5696046352386475s
Versatility | Languages check for Muziekweb took 42.061102628707886s
Interpretability | Number of blank nodes check for Muziekweb took 0.31540751457214355s
Interpretability | RDF structures check for Muziekweb took 0.3371579647064209s
Versatility | Serialization formats check for Muziekweb took 0.2794821262359619s
Availability | RDF dump link check for Muziekweb took 0.3158400058746338s
License | MR license check for Muziekweb took 0.30315256118774414s
License | HR license check for Muziekweb took 15.760313987731934s
Amount of data | Number of property check for Muziekweb took 0.31262636184692383s
Understandability | Number of label check for Muziekweb took 0.33302855491638184s
Understandability | URI regex check for Muziekweb took 0.676793098449707s
Understandability | Vocabs check for Muziekweb took 0.26483917236328125s
Verifiability | Authors check for Muziekweb took 0.27353930473327637s
Verifiability | Publishers check for Muziekweb took 0.3309037685394287s
Performance | Throughput check for Muziekweb took 11.61132550239563s
Amount of data | Check the number of entities for Muziekweb took 7.319450378417969e-05s
Verifiability | Contribs. check for Muziekweb took 0.278947114944458s
Interlinking | sameAs chians check for Muziekweb took 0.4285268783569336s
Interlinking | skos check for Muziekweb took 0.370023250579834s
Interlinking | skos check for Muziekweb took 0.2736353874206543s
Timeliness | dataset update frequency check for Muziekweb took 0.3096952438354492s
Currency | Creation date check for Muziekweb took 0.7301874160766602s
Currency | Modification date check for Muziekweb took 0.742546558380127s
Rep.Conc. | URIs length for Muziekweb took 2.177924633026123s
Interoperability | New vocabularies check for Muziekweb took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.29085755348205566s
Accuracy | Check Functional Property for Muziekweb took 0.47184014320373535s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.43961334228515625s
Accuracy | Check Empty annotation labels for Muziekweb took 1.880964994430542s
Accuracy | Check White space in annotation for Muziekweb took 0.03446674346923828s
Accuracy | Check Datatype consistency for Muziekweb took 0.028415203094482422s
Consistency | Disjoint class check for Muziekweb took 0.37726283073425293s
Consistency | Check Misplaced properties for Muziekweb took 1.1060967445373535s
Consistency | Check Ontology hijacking for Muziekweb took 2.2347185611724854s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.173929214477539s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.4534311294555664s
Conciseness | Check Extensional conciseness for Muziekweb took 0.032720327377319336s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3259603977203369s
Security | Sign check for Muziekweb took 0.2965214252471924s
Availability | Check URIs Dereferenciability for Muziekweb took 1689.5426473617554s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.4906542301177979s
Reputation | Calculation of the PageRank for Muziekweb took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.430511474609375e-06s
Believability | Calculation of trust value for Muziekweb took 5.2928924560546875e-05s
INFO | --- Analysis for muziekweb took 1810.7009453773499s
Availability | SPARQL endpoint availability check for myExperiment took 0.2593064308166504s
Availability | VoID file availability check for myExperiment took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for myExperiment took 0.7046878337860107s
Reputation | Calculation of the PageRank for myExperiment took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for myExperiment took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for myExperiment took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for myExperiment took 9.512901306152344e-05s
Believability | Calculation of trust value for myExperiment took 1.0013580322265625e-05s
INFO | --- Analysis for my-experiment took 6.2723119258880615s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.0685739517211914s
Availability | VoID file availability check for My Family Lineage took 0.0012454986572265625s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.2961447238922119s
Reputation | Calculation of the PageRank for My Family Lineage took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.654594421386719e-05s
Believability | Calculation of trust value for My Family Lineage took 8.106231689453125e-06s
INFO | --- Analysis for my-family-lineage took 6.009894847869873s
Availability | SPARQL endpoint availability check for My ontology test took 0.47893190383911133s
Availability | VoID file availability check for My ontology test took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for My ontology test took 0.2895665168762207s
Reputation | Calculation of the PageRank for My ontology test took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.123283386230469e-05s
Believability | Calculation of trust value for My ontology test took 7.152557373046875e-06s
INFO | --- Analysis for myontologytest took 4.434528827667236s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.5299530029296875e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.2698826789855957s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 9.679794311523438e-05s
Believability | Calculation of trust value for myopenlink dataspaces took 6.67572021484375e-06s
INFO | --- Analysis for myopenlink-dataspaces took 13.183302879333496s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 4.849122762680054s
Availability | VoID file availability check for N-Lex as Linked Data took 0.000720977783203125s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.28888988494873047s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 0.0001201629638671875s
Believability | Calculation of trust value for N-Lex as Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for n-lex-as-linked-data took 12.956258773803711s
Availability | SPARQL endpoint availability check for NAICS 2007 took 27.816161632537842s
Availability | VoID file availability check for NAICS 2007 took 0.0009124279022216797s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.2833874225616455s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.02218031883239746s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.887580871582031e-05s
Believability | Calculation of trust value for NAICS 2007 took 5.245208740234375e-06s
INFO | --- Analysis for naics-2007 took 124.27549028396606s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.064351320266724s
Availability | VoID file availability check for NAICS 2012 took 0.0008206367492675781s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.7088148593902588s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 4.887580871582031e-05s
Believability | Calculation of trust value for NAICS 2012 took 5.245208740234375e-06s
INFO | --- Analysis for naics-2012 took 120.12478232383728s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.25256991386413574s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 4.982948303222656e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 9.059906005859375e-06s
INFO | --- Analysis for nalt took 4.1522674560546875s
Availability | SPARQL endpoint availability check for Usernames  took 6.0558319091796875e-05s
Availability | VoID file availability check for Usernames  took 0.00031304359436035156s
Completeness | Calculation of interlinking completeness for Usernames  took 0.2774829864501953s
Reputation | Calculation of the PageRank for Usernames  took 0.020786523818969727s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Usernames  took 2.8848648071289062e-05s
Believability | Calculation of trust value for Usernames  took 7.62939453125e-06s
INFO | --- Analysis for Names took 2.885075807571411s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 2.0954301357269287s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0006771087646484375s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.0119929313659668s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.8987672328948975s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.522723197937012s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 24.64735221862793s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.36153507232666016s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.635201215744019s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.3967928886413574s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.3930227756500244s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.3849318027496338s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.4229881763458252s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.369159460067749s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.8224585056305s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.8628318309783936s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 8.106917142868042s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.7252142429351807s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.3725931644439697s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.37639546394348145s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.3705933094024658s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.455236911773682s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 4.220008850097656e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.37839436531066895s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.5404894351959229s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 2.0107851028442383s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.1009502410888672s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.4022362232208252s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.1322381496429443s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7866358757019043s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 0.9699795246124268s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.36946654319763184s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.4040079116821289s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.386624813079834s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.38429713249206543s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0003345012664794922s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0004813671112060547s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.3668084144592285s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7681975364685059s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3792836666107178s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.6172866821289062s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.165766716003418s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.5281884670257568s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006451606750488281s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.36780667304992676s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.013993263244629s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.255143404006958s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 5.7697296142578125e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.9073486328125e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 5.0067901611328125e-06s
INFO | --- Analysis for national-diet-library-authorities took 239.06099605560303s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.36620497703552246s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0005919933319091797s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.455155611038208s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 1.9834799766540527s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.95385456085205s
Interoperability | New terms check for National Diet Library of Japan subject headings took 19.92962670326233s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.43026018142700195s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.68735647201538s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.41548776626586914s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.35001587867736816s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.4020981788635254s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.4056844711303711s
License | MR license check for National Diet Library of Japan subject headings took 0.40853214263916016s
License | HR license check for National Diet Library of Japan subject headings took 91.81445550918579s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8939003944396973s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.315108060836792s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7858445644378662s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.3937838077545166s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3910336494445801s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.3962559700012207s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.452273607254028s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.821487426757812e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.3708641529083252s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.5312385559082031s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.4531729221343994s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.4728598594665527s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.3914332389831543s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.1788115501403809s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7559292316436768s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 1.0244009494781494s
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.3893873691558838s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.3672327995300293s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.41106104850769043s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.421844482421875s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007586479187011719s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010254383087158203s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.33271050453186035s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7560238838195801s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3660445213317871s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.5681524276733398s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.1433639526367188s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.5465471744537354s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0005905628204345703s
Security | Sign check for National Diet Library of Japan subject headings took 0.3897216320037842s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 4.1229047775268555s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 1.2239916324615479s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 9.5367431640625e-07s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 7.152557373046875e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 231.9349946975708s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 0.9177002906799316s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.28293490409851074s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.1961669921875e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 7.867813110351562e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 7.544159889221191s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.172325134277344e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.7091078758239746s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.723403930664062e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0967254638671875e-05s
INFO | --- Analysis for Naturopathy took 4.310882806777954s
Availability | SPARQL endpoint availability check for Naturopathy took 4.100799560546875e-05s
Availability | VoID file availability check for Naturopathy took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.2788264751434326s
Reputation | Calculation of the PageRank for Naturopathy took 0.020328521728515625s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 2.6941299438476562e-05s
Believability | Calculation of trust value for Naturopathy took 3.314018249511719e-05s
INFO | --- Analysis for naturopathy2 took 4.268998146057129s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 3.981590270996094e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.25562286376953125s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020731210708618164s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 2.956390380859375e-05s
Believability | Calculation of trust value for NCI Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for nci-thesaurus took 3.341067314147949s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.411421537399292s
Availability | VoID file availability check for COVID-19 Data took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.7172002792358398s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020758390426635742s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for COVID-19 Data took 6.9141387939453125e-06s
INFO | --- Analysis for NCMI-COVID-19 took 8.134842872619629s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.4109296798706055s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.26783013343811035s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.1920928955078125e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 6.67572021484375e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.266013145446777s
Availability | SPARQL endpoint availability check for NDF-RT took 4.172325134277344e-05s
Availability | VoID file availability check for NDF-RT took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.2882821559906006s
Reputation | Calculation of the PageRank for NDF-RT took 0.020444393157958984s
Interlinking | Calculation of Degree of Connection for NDF-RT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NDF-RT took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 2.8371810913085938e-05s
Believability | Calculation of trust value for NDF-RT took 7.152557373046875e-06s
INFO | --- Analysis for ndf-rt took 3.0756280422210693s
Availability | SPARQL endpoint availability check for Near took 4.3392181396484375e-05s
Availability | VoID file availability check for Near took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Near took 0.2710530757904053s
Reputation | Calculation of the PageRank for Near took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for Near took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Near took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for Near took 9.822845458984375e-05s
Believability | Calculation of trust value for Near took 7.152557373046875e-06s
INFO | --- Analysis for near took 9.229845762252808s
Availability | SPARQL endpoint availability check for Neel took 4.172325134277344e-05s
Availability | VoID file availability check for Neel took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Neel took 0.24352240562438965s
Reputation | Calculation of the PageRank for Neel took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for Neel took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Neel took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Neel took 2.956390380859375e-05s
Believability | Calculation of trust value for Neel took 8.106231689453125e-06s
INFO | --- Analysis for neel took 2.9637932777404785s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.0531158447265625e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.26807665824890137s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.029041767120361328s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0008635520935058594s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.337860107421875e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 6.67572021484375e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.9780609607696533s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 5.054473876953125e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2506592273712158s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020339488983154297s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 2.6464462280273438e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 7.3909759521484375e-06s
INFO | --- Analysis for neurolex-wiki took 2.4181737899780273s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.124641418457031e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.2690925598144531s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.887580871582031e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 5.9604644775390625e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.5363457202911377s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.124641418457031e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.2937033176422119s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 7.081031799316406e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 6.67572021484375e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 6.62495756149292s
Availability | SPARQL endpoint availability check for Newsweek took 4.7206878662109375e-05s
Availability | VoID file availability check for Newsweek took 0.0002205371856689453s
Completeness | Calculation of interlinking completeness for Newsweek took 0.27994704246520996s
Reputation | Calculation of the PageRank for Newsweek took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for Newsweek took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Newsweek took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Newsweek took 2.7894973754882812e-05s
Believability | Calculation of trust value for Newsweek took 6.198883056640625e-06s
INFO | --- Analysis for newsweek took 3.0016355514526367s
Availability | SPARQL endpoint availability check for neXtProt took 1.6374397277832031s
Availability | VoID file availability check for neXtProt took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for neXtProt took 0.26725268363952637s
Reputation | Calculation of the PageRank for neXtProt took 0.020479679107666016s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.62396240234375e-05s
Believability | Calculation of trust value for neXtProt took 7.867813110351562e-06s
INFO | --- Analysis for nextprot took 4.752915382385254s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.315376281738281e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.27192187309265137s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020158767700195312s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 9.751319885253906e-05s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 8.58306884765625e-06s
INFO | --- Analysis for nextweb-gnoss took 2.942439317703247s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 5.459785461425781e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.2765657901763916s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 7.557868957519531e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 4.76837158203125e-06s
INFO | --- Analysis for nhs-jargon took 3.4255080223083496s
Availability | SPARQL endpoint availability check for NIT Patna took 4.2438507080078125e-05s
Availability | VoID file availability check for NIT Patna took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.26007962226867676s
Reputation | Calculation of the PageRank for NIT Patna took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.747245788574219e-05s
Believability | Calculation of trust value for NIT Patna took 8.106231689453125e-06s
INFO | --- Analysis for NITP took 3.9593303203582764s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.0531158447265625e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.2921013832092285s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.361701965332031e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 8.58306884765625e-06s
INFO | --- Analysis for nlm_2007_mesh took 3.00909686088562s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.7206878662109375e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2660856246948242s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 2.7894973754882812e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 8.58306884765625e-06s
INFO | --- Analysis for nlr-dataset-mod took 4.200860977172852s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.486480712890625s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2552204132080078s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for NLW took 3.955831527709961s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.3701438903808594s
Availability | VoID file availability check for Nobel Prizes took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.30269646644592285s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02138996124267578s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.608268737792969e-05s
Believability | Calculation of trust value for Nobel Prizes took 5.9604644775390625e-06s
INFO | --- Analysis for nobelprizes took 8.38334035873413s
Availability | SPARQL endpoint availability check for NoiPA took 0.3148796558380127s
Availability | VoID file availability check for NoiPA took 0.00024437904357910156s
Extra | Recovery of all triples for NoiPA took 82.77743577957153s
Performance | Total latancy measurement for NoiPA took 0.9836835861206055s
Amount of data | Number of triples check for NoiPA took 1.5771117210388184s
Interoperability | New terms check for NoiPA took 3.237027883529663s
Versatility | Languages check for NoiPA took 60.23816466331482s
Interpretability | Number of blank nodes check for NoiPA took 0.21752047538757324s
Interpretability | RDF structures check for NoiPA took 0.20143723487854004s
Versatility | Serialization formats check for NoiPA took 0.24146723747253418s
Availability | RDF dump link check for NoiPA took 0.2587125301361084s
License | MR license check for NoiPA took 0.2548794746398926s
License | HR license check for NoiPA took 60.2233567237854s
Amount of data | Number of property check for NoiPA took 0.27722787857055664s
Understandability | Number of label check for NoiPA took 0.5888628959655762s
Understandability | URI regex check for NoiPA took 0.2788424491882324s
Understandability | Vocabs check for NoiPA took 0.15831971168518066s
Verifiability | Authors check for NoiPA took 0.1301431655883789s
Verifiability | Publishers check for NoiPA took 0.11238455772399902s
Performance | Throughput check for NoiPA took 10.514008045196533s
Amount of data | Check the number of entities for NoiPA took 3.361701965332031e-05s
Verifiability | Contribs. check for NoiPA took 0.18198776245117188s
Interlinking | sameAs chians check for NoiPA took 0.2878553867340088s
Interlinking | skos check for NoiPA took 0.6022157669067383s
Interlinking | skos check for NoiPA took 0.08321881294250488s
Timeliness | dataset update frequency check for NoiPA took 0.13137245178222656s
Currency | Creation date check for NoiPA took 0.26074719429016113s
Currency | Modification date check for NoiPA took 0.16349267959594727s
Rep.Conc. | URIs length for NoiPA took 52.33643698692322s
Interoperability | New vocabularies check for NoiPA took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.2656230926513672s
Accuracy | Check Functional Property for NoiPA took 0.39047813415527344s
Accuracy | Check Inverse Functional Property for NoiPA took 0.336961030960083s
Accuracy | Check Empty annotation labels for NoiPA took 25.072853565216064s
Accuracy | Check White space in annotation for NoiPA took 2.247811794281006s
Accuracy | Check Datatype consistency for NoiPA took 1.9839956760406494s
Consistency | Disjoint class check for NoiPA took 0.24970459938049316s
Consistency | Check Misplaced properties for NoiPA took 20.212369680404663s
Consistency | Misplaced classes for NoiPA took 6.422622442245483s
Consistency | Check Ontology hijacking for NoiPA took 26.0476016998291s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.6715843677520752s
Consistency | Check Invalid usage of undefined properties for NoiPA took 21.23685359954834s
Conciseness | Check Extensional conciseness for NoiPA took 2.1920971870422363s
Conciseness | Check Intensional conciseness for NoiPA took 0.4750666618347168s
Security | Sign check for NoiPA took 0.14266324043273926s
Availability | Check URIs Dereferenciability for NoiPA took 13.946918249130249s
Completeness | Calculation of interlinking completeness for NoiPA took 0.33161306381225586s
Reputation | Calculation of the PageRank for NoiPA took 0.021114349365234375s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.719329833984375e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 2.86102294921875e-06s
Believability | Calculation of trust value for NoiPA took 6.67572021484375e-06s
INFO | --- Analysis for NoiPA took 570.9428317546844s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 6.021382570266724s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.00040078163146972656s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.290386438369751s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 8.797645568847656e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 8.106231689453125e-06s
INFO | --- Analysis for nom took 24.798935651779175s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 24.742019176483154s
Availability | VoID file availability check for Nomenclator Asturias took 0.0007956027984619141s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.6971147060394287s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.02094435691833496s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.153915405273438e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 6.198883056640625e-06s
INFO | --- Analysis for nomenclator-asturias took 134.72054719924927s
Availability | SPARQL endpoint availability check for nomisma took 4.124641418457031e-05s
Availability | VoID file availability check for nomisma took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for nomisma took 0.2904393672943115s
Reputation | Calculation of the PageRank for nomisma took 0.020421266555786133s
Interlinking | Calculation of Degree of Connection for nomisma took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for nomisma took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for nomisma took 2.7894973754882812e-05s
Believability | Calculation of trust value for nomisma took 7.867813110351562e-06s
INFO | --- Analysis for nomisma took 6.060544490814209s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.48087620735168457s
Availability | VoID file availability check for Nomisma.org  took 0.0005905628204345703s
Extra | Recovery of all triples for Nomisma.org  took 589.6744291782379s
Performance | Total latancy measurement for Nomisma.org  took 2.116206407546997s
Amount of data | Number of triples check for Nomisma.org  took 43.535319328308105s
Interoperability | New terms check for Nomisma.org  took 9.849722385406494s
Versatility | Languages check for Nomisma.org  took 104.66066813468933s
Interpretability | Number of blank nodes check for Nomisma.org  took 36.99521493911743s
Security | Check HTTPS for Nomisma.org  took 0.8129124641418457s
Interpretability | RDF structures check for Nomisma.org  took 0.3574402332305908s
Versatility | Serialization formats check for Nomisma.org  took 0.38415098190307617s
Availability | RDF dump link check for Nomisma.org  took 649.583261013031s
License | MR license check for Nomisma.org  took 0.4202272891998291s
License | HR license check for Nomisma.org  took 57.567755699157715s
Amount of data | Number of property check for Nomisma.org  took 0.3771326541900635s
Understandability | Number of label check for Nomisma.org  took 8.994920015335083s
Understandability | URI regex check for Nomisma.org  took 0.754774808883667s
Understandability | Vocabs check for Nomisma.org  took 0.3327484130859375s
Verifiability | Authors check for Nomisma.org  took 0.3438112735748291s
Verifiability | Publishers check for Nomisma.org  took 0.34032392501831055s
Performance | Throughput check for Nomisma.org  took 10.732092142105103s
Amount of data | Check the number of entities for Nomisma.org  took 0.0005309581756591797s
Verifiability | Contribs. check for Nomisma.org  took 0.38408827781677246s
Interlinking | sameAs chians check for Nomisma.org  took 0.38066816329956055s
Interlinking | skos check for Nomisma.org  took 1.2061223983764648s
Interlinking | skos check for Nomisma.org  took 0.5003972053527832s
Timeliness | dataset update frequency check for Nomisma.org  took 0.35765528678894043s
Currency | Creation date check for Nomisma.org  took 0.7654075622558594s
Currency | Modification date check for Nomisma.org  took 0.36955857276916504s
Rep.Conc. | URIs length for Nomisma.org  took 528.5041525363922s
Interoperability | New vocabularies check for Nomisma.org  took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.3552875518798828s
Accuracy | Check Functional Property for Nomisma.org  took 0.3874051570892334s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3293018341064453s
Accuracy | Check Empty annotation labels for Nomisma.org  took 393.65500497817993s
Accuracy | Check White space in annotation for Nomisma.org  took 2.8103926181793213s
Consistency | Disjoint class check for Nomisma.org  took 0.4032440185546875s
Consistency | Check Misplaced properties for Nomisma.org  took 28.41304063796997s
Consistency | Check Ontology hijacking for Nomisma.org  took 393.9282603263855s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 34.944528102874756s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.00018095970153808594s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.3936197757720947s
Security | Sign check for Nomisma.org  took 0.40252256393432617s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.6463894844055176s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 2.1457672119140625e-06s
Believability | Calculation of trust value for Nomisma.org  took 7.62939453125e-06s
INFO | --- Analysis for nomisma_org took 7051.64990735054s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.6917028427124023s
Availability | VoID file availability check for Curriculum Vitae took 0.0002846717834472656s
Extra | Recovery of all triples for Curriculum Vitae took 0.7776575088500977s
Performance | Total latancy measurement for Curriculum Vitae took 1.012251377105713s
Amount of data | Number of triples check for Curriculum Vitae took 0.24958157539367676s
Interoperability | New terms check for Curriculum Vitae took 1.425215482711792s
Versatility | Languages check for Curriculum Vitae took 0.11904788017272949s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.23820972442626953s
Interpretability | RDF structures check for Curriculum Vitae took 0.16243767738342285s
Versatility | Serialization formats check for Curriculum Vitae took 0.1311044692993164s
Availability | RDF dump link check for Curriculum Vitae took 0.21927857398986816s
License | MR license check for Curriculum Vitae took 0.3211703300476074s
License | HR license check for Curriculum Vitae took 0.2493598461151123s
Amount of data | Number of property check for Curriculum Vitae took 0.3121225833892822s
Understandability | Number of label check for Curriculum Vitae took 0.20923328399658203s
Understandability | URI regex check for Curriculum Vitae took 0.254225492477417s
Understandability | Vocabs check for Curriculum Vitae took 0.215789794921875s
Verifiability | Authors check for Curriculum Vitae took 0.2060403823852539s
Verifiability | Publishers check for Curriculum Vitae took 0.19711661338806152s
Amount of data | Check the number of entities for Curriculum Vitae took 6.628036499023438e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.24185848236083984s
Interlinking | sameAs chians check for Curriculum Vitae took 0.12897825241088867s
Interlinking | skos check for Curriculum Vitae took 0.22535109519958496s
Interlinking | skos check for Curriculum Vitae took 0.1177363395690918s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.22238373756408691s
Currency | Creation date check for Curriculum Vitae took 0.30929112434387207s
Currency | Modification date check for Curriculum Vitae took 0.47726893424987793s
Rep.Conc. | URIs length for Curriculum Vitae took 0.6810979843139648s
Interoperability | New vocabularies check for Curriculum Vitae took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.21602749824523926s
Accuracy | Check Functional Property for Curriculum Vitae took 0.11990904808044434s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.2525639533996582s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.11633658409118652s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.00010800361633300781s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.003369569778442383s
Consistency | Disjoint class check for Curriculum Vitae took 0.20351505279541016s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.23671817779541016s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.318368911743164s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.1937000751495361s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.4485011100769043s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.001470804214477539s
Security | Sign check for Curriculum Vitae took 0.130340576171875s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 19.796242475509644s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.7312626838684082s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.021088123321533203s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.528594970703125e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.6689300537109375e-06s
Believability | Calculation of trust value for Curriculum Vitae took 8.106231689453125e-06s
INFO | --- Analysis for Nordine_Bittich took 52.35393691062927s
Availability | SPARQL endpoint availability check for NorPark took 0.19075274467468262s
Availability | VoID file availability check for NorPark took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for NorPark took 0.7001688480377197s
Reputation | Calculation of the PageRank for NorPark took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for NorPark took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.482269287109375e-05s
Believability | Calculation of trust value for NorPark took 6.9141387939453125e-06s
INFO | --- Analysis for norpark took 5.914510250091553s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.027144670486450195s
Availability | VoID file availability check for Parking Dataset took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.2763667106628418s
Reputation | Calculation of the PageRank for Parking Dataset took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.458427429199219e-05s
Believability | Calculation of trust value for Parking Dataset took 7.867813110351562e-06s
INFO | --- Analysis for norpark2 took 3.3923752307891846s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.4633173942565918s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.00029778480529785156s
Extra | Recovery of all triples for Norway fishery stocks dataset took 121.29753589630127s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.952455997467041s
Amount of data | Number of triples check for Norway fishery stocks dataset took 8.424139261245728s
Interoperability | New terms check for Norway fishery stocks dataset took 14.743415355682373s
Versatility | Languages check for Norway fishery stocks dataset took 300.1927902698517s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 2.946845769882202s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.2842519283294678s
Versatility | Serialization formats check for Norway fishery stocks dataset took 11.270623207092285s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.2729146480560303s
License | MR license check for Norway fishery stocks dataset took 0.5429117679595947s
License | HR license check for Norway fishery stocks dataset took 300.25738644599915s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.33359265327453613s
Understandability | Number of label check for Norway fishery stocks dataset took 2.6985082626342773s
Understandability | URI regex check for Norway fishery stocks dataset took 0.7427446842193604s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.3867056369781494s
Verifiability | Authors check for Norway fishery stocks dataset took 0.1996631622314453s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.2604365348815918s
Performance | Throughput check for Norway fishery stocks dataset took 11.392688989639282s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 7.462501525878906e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.21155047416687012s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.1974475383758545s
Interlinking | skos check for Norway fishery stocks dataset took 0.4556093215942383s
Interlinking | skos check for Norway fishery stocks dataset took 0.4635031223297119s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 6.290087699890137s
Currency | Creation date check for Norway fishery stocks dataset took 0.48973608016967773s
Currency | Modification date check for Norway fishery stocks dataset took 0.23176288604736328s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 163.2696418762207s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.19716310501098633s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.32311558723449707s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.31485581398010254s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 42.03824043273926s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.7314369678497314s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.654006004333496s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.21051239967346191s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 81.20109176635742s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.562275886535645s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 39.766014099121094s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.265683889389038s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 101.84289193153381s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.7834389209747314s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5621681213378906s
Security | Sign check for Norway fishery stocks dataset took 0.8601973056793213s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 7.956426620483398s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.9062149524688721s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 4.172325134277344e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 2.1457672119140625e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 7.3909759521484375e-06s
INFO | --- Analysis for Norway_Fishery_ took 2300.569130897522s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.30722737312316895s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.7372841835021973s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.8160552978515625e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 7.62939453125e-06s
INFO | --- Analysis for norwegian-geo-divisions took 8.987545251846313s
Availability | SPARQL endpoint availability check for NorwegianSoE took 4.291534423828125e-05s
Availability | VoID file availability check for NorwegianSoE took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.6899223327636719s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 2.6702880859375e-05s
Believability | Calculation of trust value for NorwegianSoE took 6.67572021484375e-06s
INFO | --- Analysis for norwegiansoe took 5.489907503128052s
Availability | SPARQL endpoint availability check for NITP took 4.4345855712890625e-05s
Availability | VoID file availability check for NITP took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for NITP took 0.7073869705200195s
Reputation | Calculation of the PageRank for NITP took 0.020333290100097656s
Interlinking | Calculation of Degree of Connection for NITP took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NITP took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for NITP took 6.0558319091796875e-05s
Believability | Calculation of trust value for NITP took 8.940696716308594e-05s
INFO | --- Analysis for notIdentifier took 5.525892496109009s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 0.00012135505676269531s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.2756490707397461s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.020241737365722656s
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.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.1948089599609375e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 6.9141387939453125e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 3.367865562438965s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.100799560546875e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.28632616996765137s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.02028369903564453s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 2.6702880859375e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 6.9141387939453125e-06s
INFO | --- Analysis for npg took 3.985323667526245s
Availability | SPARQL endpoint availability check for NPM took 4.291534423828125e-05s
Availability | VoID file availability check for NPM took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for NPM took 0.2762584686279297s
Reputation | Calculation of the PageRank for NPM took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for NPM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NPM took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for NPM took 2.9325485229492188e-05s
Believability | Calculation of trust value for NPM took 6.9141387939453125e-06s
INFO | --- Analysis for npm took 4.362252235412598s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.059619903564453125s
Availability | VoID file availability check for NTNU special collections took 0.0011699199676513672s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.2816147804260254s
Reputation | Calculation of the PageRank for NTNU special collections took 0.02028942108154297s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NTNU special collections took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.269050598144531e-05s
Believability | Calculation of trust value for NTNU special collections took 7.3909759521484375e-06s
INFO | --- Analysis for ntnusc took 6.053788661956787s
Availability | SPARQL endpoint availability check for links took 4.220008850097656e-05s
Availability | VoID file availability check for links took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for links took 0.2573082447052002s
Reputation | Calculation of the PageRank for links took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for links took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for links took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for links took 1.1444091796875e-05s
Believability | Calculation of trust value for links took 6.9141387939453125e-06s
INFO | --- Analysis for nugmyanmar took 2.792919397354126s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.6253204345703125e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2920563220977783s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.02031421661376953s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.012222290039062e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 5.7220458984375e-06s
INFO | --- Analysis for nuts-geovocab took 7.000513076782227s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.391432523727417s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.3051424026489258s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.0206601619720459s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.914138793945312e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 9.298324584960938e-06s
INFO | --- Analysis for nvd took 3.9581298828125s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 11.627433776855469s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.25122976303100586s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 7.414817810058594e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 8.344650268554688e-06s
INFO | --- Analysis for nvs took 19.244861125946045s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.172325134277344e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.2619469165802002s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018548965454101562s
Believability | Calculation of trust value for New York Times - Linked Open Data took 8.58306884765625e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.4920108318328857s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.7206878662109375e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.2605912685394287s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 2.86102294921875e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 6.67572021484375e-06s
INFO | --- Analysis for o-anc took 3.4253203868865967s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.1961669921875e-05s
Availability | VoID file availability check for OANetzwerk took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.29146242141723633s
Reputation | Calculation of the PageRank for OANetzwerk took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.0517578125e-05s
Believability | Calculation of trust value for OANetzwerk took 7.3909759521484375e-06s
INFO | --- Analysis for oanetzwerk took 3.033808708190918s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.220008850097656e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.2727627754211426s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 2.956390380859375e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 7.867813110351562e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.9799129962921143s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.4227287769317627s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006449222564697266s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.4752616882324219s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.4232659339904785s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 4.588266372680664s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.7148725986480713s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.29777765274048s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 3.715204954147339s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.2342061996459961s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.29886674880981445s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.5270605087280273s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.3838956356048584s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.4256889820098877s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.27329468727112s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.6424098014831543s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.6619522571563721s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.550445556640625s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.7964541912078857s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.38738012313842773s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.2797055244445801s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 11.28030514717102s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 8.249282836914062e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.3241419792175293s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.30251145362854004s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.23531293869018555s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3166666030883789s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.3571312427520752s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.6002378463745117s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.2905886173248291s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 17.943532943725586s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.28237009048461914s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 1.0289406776428223s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.3030872344970703s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.7139887809753418s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.023737668991088867s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.0292813777923584s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.28476929664611816s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 13.551081657409668s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.3754913806915283s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.2819266319274902s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.1679916381835938s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 14.278082847595215s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03344416618347168s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.31523799896240234s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.2896687984466553s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 9.611266374588013s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.3592798709869385s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.020284652709960938s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 9.846687316894531e-05s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 8.106231689453125e-06s
INFO | --- Analysis for ocd took 388.65573835372925s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.649162292480469e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.28511571884155273s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.019896507263183594s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.695487976074219e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 7.62939453125e-06s
INFO | --- Analysis for oceandrilling-borehole took 3.7645280361175537s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.346250295639038s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.27991366386413574s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.0108642578125e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 6.198883056640625e-06s
INFO | --- Analysis for oceandrilling-codices took 7.533135414123535s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.2784502506256104s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.2641448974609375s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0009191036224365234s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.838539123535156e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 5.9604644775390625e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 5.859992265701294s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.2032296657562256s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.25023794174194336s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0008127689361572266s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.933906555175781e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 8.344650268554688e-06s
INFO | --- Analysis for oceandrilling-forams took 6.182316303253174s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.1869962215423584s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0007364749908447266s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.2668619155883789s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020273447036743164s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.218650817871094e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 6.67572021484375e-06s
INFO | --- Analysis for oceandrilling-janus took 6.952627897262573s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 10.977233648300171s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0008192062377929688s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.3097038269042969s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020452499389648438s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.457069396972656e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-janusamp took 15.703586101531982s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.2655696868896484s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.24931669235229492s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020256519317626953s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.956390380859375e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 6.67572021484375e-06s
INFO | --- Analysis for oceandrilling-ldeo took 5.930081605911255s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.1961669921875e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2822842597961426s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020119190216064453s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.364418029785156e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 7.3909759521484375e-06s
INFO | --- Analysis for oclc-fast took 7.736916542053223s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.100799560546875e-05s
Availability | VoID file availability check for Open Data Communities took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.2891499996185303s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Communities took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 2.8371810913085938e-05s
Believability | Calculation of trust value for Open Data Communities took 7.152557373046875e-06s
INFO | --- Analysis for odc took 3.0051615238189697s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.291534423828125e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.25915074348449707s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 2.7418136596679688e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 5.245208740234375e-06s
INFO | --- Analysis for odc-imd-environment-score took 3.2954728603363037s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.029273986816406e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.27989792823791504s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.6226043701171875e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 6.198883056640625e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 3.0065805912017822s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.2993509769439697s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.2905762195587158s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02052474021911621s
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.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.600120544433594e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.245208740234375e-06s
INFO | --- Analysis for odc-lsoa took 4.3150646686553955s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.124641418457031e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.2629985809326172s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 2.86102294921875e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 8.106231689453125e-06s
INFO | --- Analysis for odc-population-2005 took 3.010284900665283s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.172325134277344e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.29290008544921875s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 8.344650268554688e-06s
INFO | --- Analysis for ods took 2.994086980819702s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.9126625061035156s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.2651395797729492s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.059906005859375e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for oecd-linked-data took 3.3632373809814453s
Availability | SPARQL endpoint availability check for Offener Haushalt took 5.1021575927734375e-05s
Availability | VoID file availability check for Offener Haushalt took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.265899658203125s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.020616769790649414s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 3.123283386230469e-05s
Believability | Calculation of trust value for Offener Haushalt took 5.9604644775390625e-06s
INFO | --- Analysis for offener-haushalt took 3.0111751556396484s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.19099235534668s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.7058570384979248s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.482269287109375e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 7.867813110351562e-06s
INFO | --- Analysis for ogolod took 103.52853441238403s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.100799560546875e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.29012560844421387s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020666122436523438s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.647804260253906e-05s
Believability | Calculation of trust value for OLAC Metadata took 6.67572021484375e-06s
INFO | --- Analysis for olac took 13.190568208694458s
Availability | SPARQL endpoint availability check for OLiA took 4.2438507080078125e-05s
Availability | VoID file availability check for OLiA took 0.000736236572265625s
Completeness | Calculation of interlinking completeness for OLiA took 0.2503972053527832s
Reputation | Calculation of the PageRank for OLiA took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for OLiA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OLiA took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00011754035949707031s
Believability | Calculation of trust value for OLiA took 6.67572021484375e-06s
INFO | --- Analysis for olia took 13.664670944213867s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.220008850097656e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.2767903804779053s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.3392181396484375e-05s
Believability | Calculation of trust value for OLiA Discourse took 6.67572021484375e-06s
INFO | --- Analysis for olia-discourse took 9.186704635620117s
Availability | SPARQL endpoint availability check for Open Land Use took 0.27393078804016113s
Availability | VoID file availability check for Open Land Use took 0.0002448558807373047s
Extra | Recovery of all triples for Open Land Use took 131.5006139278412s
Performance | Total latancy measurement for Open Land Use took 0.9769628047943115s
Amount of data | Number of triples check for Open Land Use took 9.750049114227295s
Interoperability | New terms check for Open Land Use took 13.700800657272339s
Versatility | Languages check for Open Land Use took 300.19556069374084s
Interpretability | Number of blank nodes check for Open Land Use took 2.591489315032959s
Interpretability | RDF structures check for Open Land Use took 0.2592623233795166s
Versatility | Serialization formats check for Open Land Use took 11.040797472000122s
Availability | RDF dump link check for Open Land Use took 0.24934864044189453s
License | MR license check for Open Land Use took 0.5360763072967529s
License | HR license check for Open Land Use took 300.23847103118896s
Amount of data | Number of property check for Open Land Use took 0.2997112274169922s
Understandability | Number of label check for Open Land Use took 2.197748899459839s
Understandability | URI regex check for Open Land Use took 0.6699514389038086s
Understandability | Vocabs check for Open Land Use took 0.39307498931884766s
Verifiability | Authors check for Open Land Use took 0.21143627166748047s
Verifiability | Publishers check for Open Land Use took 0.26662659645080566s
Performance | Throughput check for Open Land Use took 11.582627058029175s
Amount of data | Check the number of entities for Open Land Use took 7.486343383789062e-05s
Verifiability | Contribs. check for Open Land Use took 0.19748234748840332s
Interlinking | sameAs chians check for Open Land Use took 0.18294501304626465s
Interlinking | skos check for Open Land Use took 0.46484875679016113s
Interlinking | skos check for Open Land Use took 0.43555545806884766s
Timeliness | dataset update frequency check for Open Land Use took 5.394794940948486s
Currency | Creation date check for Open Land Use took 0.9390866756439209s
Currency | Modification date check for Open Land Use took 0.2569913864135742s
Rep.Conc. | URIs length for Open Land Use took 157.99204063415527s
Interoperability | New vocabularies check for Open Land Use took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.20908737182617188s
Accuracy | Check Functional Property for Open Land Use took 0.29664158821105957s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.3223285675048828s
Accuracy | Check Empty annotation labels for Open Land Use took 44.72626209259033s
Accuracy | Check White space in annotation for Open Land Use took 2.67764949798584s
Accuracy | Check Datatype consistency for Open Land Use took 2.6773087978363037s
Consistency | Disjoint class check for Open Land Use took 0.19177508354187012s
Consistency | Check Misplaced properties for Open Land Use took 90.56696629524231s
Consistency | Misplaced classes for Open Land Use took 8.49039077758789s
Consistency | Check Ontology hijacking for Open Land Use took 33.66040825843811s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.2778408527374268s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 97.06037878990173s
Conciseness | Check Extensional conciseness for Open Land Use took 2.7878410816192627s
Conciseness | Check Intensional conciseness for Open Land Use took 0.64719557762146s
Security | Sign check for Open Land Use took 0.17936015129089355s
Availability | Check URIs Dereferenciability for Open Land Use took 9.217147827148438s
Completeness | Calculation of interlinking completeness for Open Land Use took 1.6447153091430664s
Reputation | Calculation of the PageRank for Open Land Use took 0.022417783737182617s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 3.743171691894531e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 1.6689300537109375e-06s
Believability | Calculation of trust value for Open Land Use took 7.3909759521484375e-06s
INFO | --- Analysis for OLU took 2304.801810503006s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.076957702636719e-05s
Availability | VoID file availability check for OmegaWiki took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.7824430465698242s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020826101303100586s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 2.956390380859375e-05s
Believability | Calculation of trust value for OmegaWiki took 7.3909759521484375e-06s
INFO | --- Analysis for omegawiki took 7.0964195728302s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.6935214996337891s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.27108025550842285s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020670652389526367s
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.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-als took 4.341186285018921s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.20720410346984863s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.28598952293395996s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.02076864242553711s
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.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-arb took 3.4971773624420166s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.25074148178100586s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.30263304710388184s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-bul took 3.8737125396728516s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2200791835784912s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2731456756591797s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0205838680267334s
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.0007774829864501953s
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 6.4373016357421875e-06s
INFO | --- Analysis for omwn-cow took 2.9625985622406006s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.23448562622070312s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2562546730041504s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020239591598510742s
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.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-cwn took 2.986313581466675s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.20145392417907715s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.3015780448913574s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-dan took 3.4783763885498047s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.21019721031188965s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.28610706329345703s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-ell took 3.464003562927246s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.22670245170593262s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.27834296226501465s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-eng took 2.982560873031616s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.22220516204833984s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.25826144218444824s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.020170927047729492s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-fas took 3.0094568729400635s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2183380126953125s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.25766444206237793s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.020838260650634766s
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.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-fin took 3.021341562271118s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.22258424758911133s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2951383590698242s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020985841751098633s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 4.291534423828125e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-fra took 2.9756293296813965s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.20953655242919922s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.2768557071685791s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-heb took 3.0042078495025635s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2157607078552246s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2660808563232422s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.020822525024414062s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 3.123283386230469e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-hrv took 2.991098642349243s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.23097443580627441s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.25553321838378906s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020534515380859375s
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.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-isl took 2.895735025405884s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.21589040756225586s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.27852535247802734s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020345687866210938s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-ita took 2.9072206020355225s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2193291187286377s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2780001163482666s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020625829696655273s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0008313655853271484s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-iwn took 3.0170536041259766s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.21747446060180664s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2768826484680176s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-jpn took 2.9598171710968018s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.21087121963500977s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2659299373626709s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020441055297851562s
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.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-mcr took 3.2973127365112305s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.40409088134765625s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2561326026916504s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 4.363059997558594e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-msa took 3.140869379043579s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.27405476570129395s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00021958351135253906s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.2613224983215332s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-nld took 3.036118507385254s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.24008679389953613s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.00039076805114746094s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2770233154296875s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 6.198883056640625e-06s
INFO | --- Analysis for omwn-nor took 3.0617611408233643s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2337357997894287s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.27669358253479004s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-pol took 2.990112543106079s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2291734218597412s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2744581699371338s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.020838022232055664s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-por took 3.0779473781585693s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2709341049194336s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2904479503631592s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020595550537109375s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-ron took 2.970942735671997s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.22678804397583008s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2659475803375244s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 6.4373016357421875e-06s
INFO | --- Analysis for omwn-slk took 2.9787890911102295s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.22498440742492676s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2683136463165283s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-slv took 2.977078914642334s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2087407112121582s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2552504539489746s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 5.9604644775390625e-06s
INFO | --- Analysis for omwn-swe took 2.9392356872558594s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.218886137008667s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.00035762786865234375s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2718849182128906s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020811080932617188s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 5.7220458984375e-06s
INFO | --- Analysis for omwn-tha took 2.9446940422058105s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 7.549972772598267s
Availability | VoID file availability check for OntoBeef Domain took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.28594207763671875s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.601478576660156e-05s
Believability | Calculation of trust value for OntoBeef Domain took 7.152557373046875e-06s
INFO | --- Analysis for ontobeef-domain took 34.44218301773071s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.38690185546875e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.7399396896362305s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 8.96453857421875e-05s
Believability | Calculation of trust value for Ontos News Portal took 8.106231689453125e-06s
INFO | --- Analysis for ontos-news-portal took 16.76458430290222s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.1961669921875e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.25054073333740234s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.075599670410156e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 6.9141387939453125e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.5383801460266113s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.1961669921875e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.2818171977996826s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.719329833984375e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 6.67572021484375e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 6.792177200317383s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.2667059898376465s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 2.956390380859375e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 7.867813110351562e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 3.4318761825561523s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.315376281738281e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.00034356117248535156s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.2705991268157959s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020413875579833984s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.482269287109375e-05s
Believability | Calculation of trust value for Open Data Euskadi took 4.76837158203125e-06s
INFO | --- Analysis for open-data-euskadi took 9.430496454238892s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.267692565917969e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.24597883224487305s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 9.799003601074219e-05s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 6.4373016357421875e-06s
INFO | --- Analysis for open-data-risp took 3.3147003650665283s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.3311774730682373s
Availability | VoID file availability check for Open Data Thesaurus took 0.0007236003875732422s
Extra | Recovery of all triples for Open Data Thesaurus took 1.5429596900939941s
Performance | Total latancy measurement for Open Data Thesaurus took 0.5040781497955322s
Amount of data | Number of triples check for Open Data Thesaurus took 0.1527254581451416s
Interoperability | New terms check for Open Data Thesaurus took 1.298220157623291s
Versatility | Languages check for Open Data Thesaurus took 0.1345658302307129s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.1101677417755127s
Security | Check HTTPS for Open Data Thesaurus took 0.3471689224243164s
Interpretability | RDF structures check for Open Data Thesaurus took 0.12524199485778809s
Versatility | Serialization formats check for Open Data Thesaurus took 0.11840176582336426s
Availability | RDF dump link check for Open Data Thesaurus took 1.2171549797058105s
License | MR license check for Open Data Thesaurus took 0.12033271789550781s
License | HR license check for Open Data Thesaurus took 0.0794365406036377s
Amount of data | Number of property check for Open Data Thesaurus took 0.10991621017456055s
Understandability | Number of label check for Open Data Thesaurus took 0.1275327205657959s
Understandability | URI regex check for Open Data Thesaurus took 0.1714329719543457s
Understandability | Vocabs check for Open Data Thesaurus took 0.1102755069732666s
Verifiability | Authors check for Open Data Thesaurus took 0.13246774673461914s
Verifiability | Publishers check for Open Data Thesaurus took 0.1351773738861084s
Performance | Throughput check for Open Data Thesaurus took 10.51035189628601s
Amount of data | Check the number of entities for Open Data Thesaurus took 6.866455078125e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.11040139198303223s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.14067935943603516s
Interlinking | skos check for Open Data Thesaurus took 0.11727070808410645s
Interlinking | skos check for Open Data Thesaurus took 0.100982666015625s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.10283970832824707s
Currency | Creation date check for Open Data Thesaurus took 0.20374536514282227s
Currency | Modification date check for Open Data Thesaurus took 0.22616958618164062s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4780275821685791s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.11169600486755371s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.07820320129394531s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.08647584915161133s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.21415019035339355s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011444091796875s
Consistency | Disjoint class check for Open Data Thesaurus took 0.1109464168548584s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.18782949447631836s
Consistency | Misplaced classes for Open Data Thesaurus took 0.09591364860534668s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.3131296634674072s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.246711015701294s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00015282630920410156s
Security | Sign check for Open Data Thesaurus took 0.09314918518066406s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.27732300758361816s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.02121257781982422s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.487701416015625e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for open-data-thesaurus took 82.32067346572876s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.220008850097656e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.261441707611084s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 3.170967102050781e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 6.67572021484375e-06s
INFO | --- Analysis for open-data-tor-vergata took 4.1408045291900635s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.076957702636719e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.30355286598205566s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.365776062011719e-05s
Believability | Calculation of trust value for Open Election Data Project took 5.245208740234375e-06s
INFO | --- Analysis for open-election-data-project took 4.042846202850342s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.9904773235321045s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.2899935245513916s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020655393600463867s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0009019374847412109s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 0.00010418891906738281s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 3.1948089599609375e-05s
INFO | --- Analysis for open-energy-info-wiki took 11.319922685623169s
Availability | SPARQL endpoint availability check for Open Library took 4.267692565917969e-05s
Availability | VoID file availability check for Open Library took 0.0007894039154052734s
Completeness | Calculation of interlinking completeness for Open Library took 0.3473825454711914s
Reputation | Calculation of the PageRank for Open Library took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Open Library took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.818771362304688e-05s
Believability | Calculation of trust value for Open Library took 8.106231689453125e-06s
INFO | --- Analysis for open-library took 46.15400409698486s
Availability | SPARQL endpoint availability check for Open Directory took 4.1961669921875e-05s
Availability | VoID file availability check for Open Directory took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Open Directory took 0.2871983051300049s
Reputation | Calculation of the PageRank for Open Directory took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.1948089599609375e-05s
Believability | Calculation of trust value for Open Directory took 6.67572021484375e-06s
INFO | --- Analysis for open_directory took 2.9907453060150146s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.20897531509399414s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0002448558807373047s
Extra | Recovery of all triples for Open Land Use @PSNC took 118.65026021003723s
Performance | Total latancy measurement for Open Land Use @PSNC took 1.0183625221252441s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.15679669380188s
Interoperability | New terms check for Open Land Use @PSNC took 13.794673204421997s
Versatility | Languages check for Open Land Use @PSNC took 300.16777515411377s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 3.3301448822021484s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.1911149024963379s
Versatility | Serialization formats check for Open Land Use @PSNC took 10.56152892112732s
Availability | RDF dump link check for Open Land Use @PSNC took 0.2067558765411377s
License | MR license check for Open Land Use @PSNC took 0.6171832084655762s
License | HR license check for Open Land Use @PSNC took 300.1960473060608s
Amount of data | Number of property check for Open Land Use @PSNC took 0.21367216110229492s
Understandability | Number of label check for Open Land Use @PSNC took 1.8745253086090088s
Understandability | URI regex check for Open Land Use @PSNC took 0.6972882747650146s
Understandability | Vocabs check for Open Land Use @PSNC took 0.41155552864074707s
Verifiability | Authors check for Open Land Use @PSNC took 0.1995081901550293s
Verifiability | Publishers check for Open Land Use @PSNC took 0.25606513023376465s
Performance | Throughput check for Open Land Use @PSNC took 11.474716186523438s
Amount of data | Check the number of entities for Open Land Use @PSNC took 7.271766662597656e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.1990208625793457s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.1826460361480713s
Interlinking | skos check for Open Land Use @PSNC took 0.47735166549682617s
Interlinking | skos check for Open Land Use @PSNC took 0.47809553146362305s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 7.7380712032318115s
Currency | Creation date check for Open Land Use @PSNC took 0.5091469287872314s
Currency | Modification date check for Open Land Use @PSNC took 0.22609162330627441s
Rep.Conc. | URIs length for Open Land Use @PSNC took 167.98645758628845s
Interoperability | New vocabularies check for Open Land Use @PSNC took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.21173834800720215s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.3294334411621094s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.32193636894226074s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 42.7281334400177s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.7090871334075928s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.6331169605255127s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.20780038833618164s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 82.80826902389526s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.684981107711792s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 36.27761673927307s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.214829683303833s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 89.0355441570282s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.7797908782958984s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.514115571975708s
Security | Sign check for Open Land Use @PSNC took 0.19458937644958496s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 6.1422553062438965s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 1.4117200374603271s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.021053075790405273s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.029273986816406e-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 7.3909759521484375e-06s
INFO | --- Analysis for Open_Land_Use took 2286.76602101326s
Availability | SPARQL endpoint availability check for flyatlas took 2.119283676147461s
Availability | VoID file availability check for flyatlas took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for flyatlas took 0.26810169219970703s
Reputation | Calculation of the PageRank for flyatlas took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.147125244140625e-05s
Believability | Calculation of trust value for flyatlas took 8.344650268554688e-06s
INFO | --- Analysis for openbiomed-flyatlas took 13.384643316268921s
Availability | SPARQL endpoint availability check for OpenCalais took 4.3392181396484375e-05s
Availability | VoID file availability check for OpenCalais took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.7596676349639893s
Reputation | Calculation of the PageRank for OpenCalais took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010561943054199219s
Believability | Calculation of trust value for OpenCalais took 7.62939453125e-06s
INFO | --- Analysis for opencalais took 7.065623044967651s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.2438507080078125e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.2577517032623291s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.152557373046875e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 5.4836273193359375e-06s
INFO | --- Analysis for opencorporates took 3.288849115371704s
Availability | SPARQL endpoint availability check for OpenCyc took 4.696846008300781e-05s
Availability | VoID file availability check for OpenCyc took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2579352855682373s
Reputation | Calculation of the PageRank for OpenCyc took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010132789611816406s
Believability | Calculation of trust value for OpenCyc took 7.3909759521484375e-06s
INFO | --- Analysis for opencyc took 2.916780471801758s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 6.389617919921875e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.25000882148742676s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.457069396972656e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 2.565011739730835s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.24438881874084473s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.02052450180053711s
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.000762939453125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.36846661567688s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.27985119819641113s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.6232783794403076s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.27655458450317383s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.02088642120361328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.4591991901397705s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.001312255859375s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.25779032707214355s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.021030902862548828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 2.820660352706909s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.2785460948944092s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020814895629882812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.837693452835083s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.887580871582031e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0006346702575683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.2742269039154053s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 3.136805534362793s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.25235724449157715s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0211639404296875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0008442401885986328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.841270923614502s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 5.888938903808594e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0003910064697265625s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.237044095993042s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 2.5853381156921387s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2827436923980713s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 5.507469177246094e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 3.1644930839538574s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.00040650367736816406s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.26388025283813477s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.711092948913574s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 8.177757263183594e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.2801175117492676s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.6904296875s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 5.269050598144531e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.7073276042938232s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020796537399291992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.989933729171753s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.25717926025390625s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.4067604541778564s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.2599947452545166s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.5141561031341553s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 7.939338684082031e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2721555233001709s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.509445905685425s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.2933528423309326s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.6678011417388916s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.26357150077819824s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.515852451324463s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.26201295852661133s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.462893009185791s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.28011131286621094s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.525148391723633s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 6.818771362304688e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.2495424747467041s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.5943305492401123s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2796628475189209s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.4753174781799316s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.27307868003845215s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.5656630992889404s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.2719142436981201s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.02249312400817871s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.576458692550659s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2760932445526123s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020242691040039062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.7559821605682373s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0004100799560546875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.2469489574432373s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020991802215576172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.62322735786438s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 5.364418029785156e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2570955753326416s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020686626434326172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.6954030990600586s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.28745031356811523s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020221710205078125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.805962562561035s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.793571472167969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.26424407958984375s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 2.8775851726531982s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.273453950881958s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.5522329807281494s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2623939514160156s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.5866847038269043s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.26363205909729004s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.543628215789795s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2989332675933838s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.6098484992980957s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.26843786239624023s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.02042675018310547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.4647040367126465s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00021696090698242188s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.2793447971343994s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020488977432250977s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.477546215057373s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2809414863586426s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.574470281600952s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2715935707092285s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.643545389175415s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.2676973342895508s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.021528244018554688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0009081363677978516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 5.507469177246094e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.5235352516174316s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.28130674362182617s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020787477493286133s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.5562100410461426s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2596437931060791s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.5764472484588623s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.26479172706604004s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 2.5962884426116943s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.696846008300781e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2600235939025879s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020541906356811523s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.515373468399048s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2794661521911621s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020370960235595703s
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.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 2.5878350734710693s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 4.43917441368103s
Availability | VoID file availability check for Open Data of Ecuador took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2532336711883545s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020545244216918945s
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.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.606910705566406e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 6.67572021484375e-06s
INFO | --- Analysis for opendataec took 9.177024364471436s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.2764739990234375s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.02085590362548828s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.58306884765625e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.226574182510376s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2624802589416504s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 8.106231689453125e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.551424980163574s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.2609593868255615s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020951271057128906s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.9277822971343994s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.100799560546875e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.27408695220947266s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.936185836791992s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 7.367134094238281e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.2689063549041748s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020629167556762695s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.1444091796875e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.0012242794036865s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 8.487701416015625e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.2683992385864258s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 8.344650268554688e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.999230146408081s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.172325134277344e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.26894044876098633s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.975872039794922s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.29485416412353516s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.552436828613281e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.0047497749328613s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.220008850097656e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.287553071975708s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020882606506347656s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.5762786865234375e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.431671380996704s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.349421501159668s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2587554454803467s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.021495819091796875s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0009446144104003906s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 4.363059997558594e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.4543533325195312e-05s
INFO | --- Analysis for openlink-lod-cache took 62.799901723861694s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.1484832763671875e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.25683093070983887s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.226799011230469e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 6.9141387939453125e-06s
INFO | --- Analysis for openlinksw-dataspaces took 3.2443251609802246s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.839897155761719e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.00034236907958984375s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.27753305435180664s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020363569259643555s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 8.821487426757812e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 5.245208740234375e-06s
INFO | --- Analysis for openlylocal took 6.997113227844238s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 0.9931991100311279s
Availability | VoID file availability check for OpenMobileNetwork took 0.00037169456481933594s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.2671394348144531s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02018904685974121s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.033348083496094e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 7.3909759521484375e-06s
INFO | --- Analysis for openmobilenetwork took 3.9984242916107178s
Availability | SPARQL endpoint availability check for OpenTox took 5.125999450683594e-05s
Availability | VoID file availability check for OpenTox took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for OpenTox took 0.26875901222229004s
Reputation | Calculation of the PageRank for OpenTox took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for OpenTox took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenTox took 6.4373016357421875e-06s
INFO | --- Analysis for opentox took 2.959213972091675s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.1961669921875e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.2727947235107422s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.020629405975341797s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 5.9604644775390625e-06s
INFO | --- Analysis for openuplabs took 3.0903968811035156s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 3.933906555175781e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.00021409988403320312s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.2695329189300537s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 3.123283386230469e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 6.4373016357421875e-06s
INFO | --- Analysis for opus took 2.9518887996673584s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 3.981590270996094e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.000217437744140625s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.25094175338745117s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020885705947875977s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.552436828613281e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 6.198883056640625e-06s
INFO | --- Analysis for orcid took 2.866227149963379s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.9366641044616699s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.27427172660827637s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.322166442871094e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 7.62939453125e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 5.15922999382019s
Availability | SPARQL endpoint availability check for oreilly took 4.38690185546875e-05s
Availability | VoID file availability check for oreilly took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for oreilly took 0.2718770503997803s
Reputation | Calculation of the PageRank for oreilly took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for oreilly took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for oreilly took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.5299530029296875e-05s
Believability | Calculation of trust value for oreilly took 6.9141387939453125e-06s
INFO | --- Analysis for oreilly took 4.953571319580078s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.4014909267425537s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.2546417713165283s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.24249267578125e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 5.9604644775390625e-06s
INFO | --- Analysis for Organchem-Data took 7.264222145080566s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.06630659103393555s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.4058573246002197s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020023345947265625s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.318092346191406e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 8.58306884765625e-06s
INFO | --- Analysis for organic-edunet took 9.123213291168213s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.4536457061767578s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0007157325744628906s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 13.507944822311401s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7651379108428955s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.2028036117553711s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.4892752170562744s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 10.02645754814148s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.14438605308532715s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.3310282230377197s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.130997896194458s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.13989949226379395s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.15538477897644043s
License | HR license check for Open Research Knowledge Graph (ORKG) took 5.5895609855651855s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.16678881645202637s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.2113962173461914s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.3369317054748535s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.14904022216796875s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.13565444946289062s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.17751717567443848s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.512048244476318s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.224082946777344e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.19008278846740723s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.14775609970092773s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.16950368881225586s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.17461323738098145s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.15879416465759277s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.36784887313842773s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.39212489128112793s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 7.888278007507324s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.14417648315429688s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.22952532768249512s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.2408430576324463s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 5.5878074169158936s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.14566874504089355s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.28109264373779297s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.22588181495666504s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 2.284614086151123s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.887718677520752s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 4.941012144088745s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.1640841960906982s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.1571145057678223s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.2895345687866211s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.1710050106048584s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.14191961288452148s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2110.933609724045s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 1.4756696224212646s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.021990060806274414s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 7.152557373046875e-06s
INFO | --- Analysis for orkg took 2403.331410884857s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 4.47063684463501s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.27999258041381836s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.021021127700805664s
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.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.463859558105469e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 7.867813110351562e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 32.7572968006134s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.5813090801239014s
Availability | VoID file availability check for OSM Semantic Network took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.7124853134155273s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020646333694458008s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 4.172325134277344e-05s
Believability | Calculation of trust value for OSM Semantic Network took 7.867813110351562e-06s
INFO | --- Analysis for osm-semantic-network took 9.999009370803833s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.4484543800354004s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00026607513427734375s
Extra | Recovery of all triples for Open Transport Map @PSNC took 111.7321388721466s
Performance | Total latancy measurement for Open Transport Map @PSNC took 1.0090093612670898s
Amount of data | Number of triples check for Open Transport Map @PSNC took 10.18481159210205s
Interoperability | New terms check for Open Transport Map @PSNC took 13.777160167694092s
Versatility | Languages check for Open Transport Map @PSNC took 300.29711151123047s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 2.7503373622894287s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.2710890769958496s
Versatility | Serialization formats check for Open Transport Map @PSNC took 13.001177549362183s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.263714075088501s
License | MR license check for Open Transport Map @PSNC took 0.5372343063354492s
License | HR license check for Open Transport Map @PSNC took 300.2260537147522s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.32478880882263184s
Understandability | Number of label check for Open Transport Map @PSNC took 2.998089551925659s
Understandability | URI regex check for Open Transport Map @PSNC took 0.7270832061767578s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.20906758308410645s
Verifiability | Authors check for Open Transport Map @PSNC took 0.2020864486694336s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.25569868087768555s
Performance | Throughput check for Open Transport Map @PSNC took 11.576238632202148s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 7.2479248046875e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.1955115795135498s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.1972496509552002s
Interlinking | skos check for Open Transport Map @PSNC took 0.46735143661499023s
Interlinking | skos check for Open Transport Map @PSNC took 0.42975592613220215s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 9.412175178527832s
Currency | Creation date check for Open Transport Map @PSNC took 0.4980001449584961s
Currency | Modification date check for Open Transport Map @PSNC took 0.23108506202697754s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 164.03367972373962s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.1839916706085205s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.2804758548736572s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.19129657745361328s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 42.71616339683533s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.7097866535186768s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.637631893157959s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.20119428634643555s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 95.34671258926392s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.562902927398682s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 33.743025064468384s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.2279598712921143s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 95.92458415031433s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.763582468032837s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.5062360763549805s
Security | Sign check for Open Transport Map @PSNC took 0.4627656936645508s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 10.163210391998291s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 2.1286263465881348s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.021620988845825195s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.266334533691406e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 7.62939453125e-06s
INFO | --- Analysis for OTM took 2302.5091280937195s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.124641418457031e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.7039830684661865s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.123283386230469e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 7.867813110351562e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 5.167971611022949s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.2438507080078125e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.25635218620300293s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.6464462280273438e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.62939453125e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 4.264495134353638s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 3.981590270996094e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.26993513107299805s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0008752346038818359s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.266334533691406e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 6.9141387939453125e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 3.884561777114868s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 5.269050598144531e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.2756333351135254s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 2.86102294921875e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 3.9064738750457764s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 3.9577484130859375e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.2665438652038574s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.7418136596679688e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 3.9547951221466064s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.887580871582031e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0008642673492431641s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.260101318359375s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 3.170967102050781e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.947859525680542s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.0531158447265625e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.3022294044494629s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 3.170967102050781e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 8.106231689453125e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.9870827198028564s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.00543212890625e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.00035762786865234375s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.2789433002471924s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 2.8848648071289062e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 7.3909759521484375e-06s
INFO | --- Analysis for oxpoints took 2.9984991550445557s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.7559072971343994s
Availability | VoID file availability check for Pali English Lexicon took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.2763538360595703s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020260334014892578s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.8371810913085938e-05s
Believability | Calculation of trust value for Pali English Lexicon took 6.67572021484375e-06s
INFO | --- Analysis for pali-english-lexicon took 6.936543226242065s
Availability | SPARQL endpoint availability check for PanLex took 0.40236926078796387s
Availability | VoID file availability check for PanLex took 0.000457763671875s
Completeness | Calculation of interlinking completeness for PanLex took 0.2614715099334717s
Reputation | Calculation of the PageRank for PanLex took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for PanLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PanLex took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for PanLex took 6.961822509765625e-05s
Believability | Calculation of trust value for PanLex took 6.9141387939453125e-06s
INFO | --- Analysis for panlex took 2.884617567062378s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.1961669921875e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.28989577293395996s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.409385681152344e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 8.106231689453125e-06s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.708568572998047s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.08327865600585938s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.25093626976013184s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.649162292480469e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 4.76837158203125e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.5165436267852783s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.172325134277344e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.2708396911621094s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020708322525024414s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.62396240234375e-05s
Believability | Calculation of trust value for PDEV-Lemon took 6.9141387939453125e-06s
INFO | --- Analysis for pdev-lemon took 4.078033924102783s
Availability | SPARQL endpoint availability check for pdevlemon took 4.1484832763671875e-05s
Availability | VoID file availability check for pdevlemon took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.2713942527770996s
Reputation | Calculation of the PageRank for pdevlemon took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for pdevlemon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 2.86102294921875e-05s
Believability | Calculation of trust value for pdevlemon took 7.62939453125e-06s
INFO | --- Analysis for pdevlemon took 3.4071097373962402s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.410743713378906e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0007991790771484375s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.28041601181030273s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 7.963180541992188e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 6.4373016357421875e-06s
INFO | --- Analysis for periodo took 19.339454412460327s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.172325134277344e-05s
Availability | VoID file availability check for Personal_Homepages took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.27849340438842773s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0004057884216308594s
Believability | Calculation of trust value for Personal_Homepages took 7.62939453125e-06s
INFO | --- Analysis for personal-homepages took 2.456792116165161s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.076957702636719e-05s
Availability | VoID file availability check for Ontology of University People took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.2867758274078369s
Reputation | Calculation of the PageRank for Ontology of University People took 0.02056407928466797s
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.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 2.5987625122070312e-05s
Believability | Calculation of trust value for Ontology of University People took 8.344650268554688e-06s
INFO | --- Analysis for PersonOnto took 2.343623638153076s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 6.266673564910889s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2631795406341553s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.049041748046875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.152557373046875e-06s
INFO | --- Analysis for PFKHS took 12.58540415763855s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.506227731704712s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.262814998626709s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020530223846435547s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.0251998901367188e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.62939453125e-06s
INFO | --- Analysis for PFRPPH took 10.543713569641113s
Availability | SPARQL endpoint availability check for PGxLOD took 0.44631338119506836s
Availability | VoID file availability check for PGxLOD took 0.0005548000335693359s
Extra | Recovery of all triples for PGxLOD took 2.170022964477539s
Performance | Total latancy measurement for PGxLOD took 0.7937221527099609s
Amount of data | Number of triples check for PGxLOD took 3.2745933532714844s
Interoperability | New terms check for PGxLOD took 1.8859302997589111s
Versatility | Languages check for PGxLOD took 60.23061537742615s
Interpretability | Number of blank nodes check for PGxLOD took 1.8080129623413086s
Interpretability | RDF structures check for PGxLOD took 0.5961730480194092s
Versatility | Serialization formats check for PGxLOD took 0.37180662155151367s
Availability | RDF dump link check for PGxLOD took 53.18638801574707s
License | MR license check for PGxLOD took 0.8739614486694336s
License | HR license check for PGxLOD took 64.26398921012878s
Amount of data | Number of property check for PGxLOD took 0.3340110778808594s
Understandability | Number of label check for PGxLOD took 3.349815845489502s
Understandability | URI regex check for PGxLOD took 0.46681737899780273s
Understandability | Vocabs check for PGxLOD took 0.4131934642791748s
Verifiability | Authors check for PGxLOD took 0.43122076988220215s
Verifiability | Publishers check for PGxLOD took 0.3446183204650879s
Performance | Throughput check for PGxLOD took 10.876296758651733s
Amount of data | Check the number of entities for PGxLOD took 0.11902260780334473s
Verifiability | Contribs. check for PGxLOD took 0.1705341339111328s
Interlinking | sameAs chians check for PGxLOD took 0.3635673522949219s
Interlinking | skos check for PGxLOD took 1.8325011730194092s
Interlinking | skos check for PGxLOD took 0.19939589500427246s
Timeliness | dataset update frequency check for PGxLOD took 0.3665642738342285s
Currency | Creation date check for PGxLOD took 0.5973811149597168s
Currency | Modification date check for PGxLOD took 0.3670005798339844s
Rep.Conc. | URIs length for PGxLOD took 6.9365785121917725s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.16734051704406738s
Accuracy | Check Functional Property for PGxLOD took 0.183349609375s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.19560790061950684s
Accuracy | Check Empty annotation labels for PGxLOD took 1.0881571769714355s
Accuracy | Check White space in annotation for PGxLOD took 0.03708028793334961s
Accuracy | Check Datatype consistency for PGxLOD took 0.028996706008911133s
Consistency | Disjoint class check for PGxLOD took 0.32106828689575195s
Consistency | Check Misplaced properties for PGxLOD took 7.193951368331909s
Consistency | Misplaced classes for PGxLOD took 0.3056821823120117s
Consistency | Check Ontology hijacking for PGxLOD took 2.004210948944092s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.1658430099487305s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.448140621185303s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03610825538635254s
Conciseness | Check Intensional conciseness for PGxLOD took 0.3041574954986572s
Security | Sign check for PGxLOD took 0.18044662475585938s
Availability | Check URIs Dereferenciability for PGxLOD took 24844.82061958313s
Completeness | Calculation of interlinking completeness for PGxLOD took 2.0975451469421387s
Reputation | Calculation of the PageRank for PGxLOD took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 4.9114227294921875e-05s
Believability | Calculation of trust value for PGxLOD took 8.344650268554688e-06s
INFO | --- Analysis for PGxLOD took 223792.13776946068s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1875636577606201s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.24775481224060059s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.337860107421875e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 6.9141387939453125e-06s
INFO | --- Analysis for phoible took 7.1691648960113525s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.291534423828125e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.7110836505889893s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.3855438232421875e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 7.3909759521484375e-06s
INFO | --- Analysis for PISM took 12.220067262649536s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.410743713378906e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.29247164726257324s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.463859558105469e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 7.867813110351562e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.67038893699646s
Availability | SPARQL endpoint availability check for digitized plant specimen took 2.254340887069702s
Availability | VoID file availability check for digitized plant specimen took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.2648742198944092s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 6.580352783203125e-05s
Believability | Calculation of trust value for digitized plant specimen took 6.9141387939453125e-06s
INFO | --- Analysis for plant-specimen took 4.6710333824157715s
Availability | SPARQL endpoint availability check for Pleiades took 4.649162292480469e-05s
Availability | VoID file availability check for Pleiades took 0.0004134178161621094s
Completeness | Calculation of interlinking completeness for Pleiades took 0.2570462226867676s
Reputation | Calculation of the PageRank for Pleiades took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Pleiades took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pleiades took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Pleiades took 7.891654968261719e-05s
Believability | Calculation of trust value for Pleiades took 7.62939453125e-06s
INFO | --- Analysis for pleiades took 16.730268239974976s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.0531158447265625e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.26946568489074707s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 2.6702880859375e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.3909759521484375e-06s
INFO | --- Analysis for podorozhnyk took 3.2444581985473633s
Availability | SPARQL endpoint availability check for Poképédia took 4.100799560546875e-05s
Availability | VoID file availability check for Poképédia took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2823967933654785s
Reputation | Calculation of the PageRank for Poképédia took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for Poképédia took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Poképédia took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Poképédia took 6.914138793945312e-05s
Believability | Calculation of trust value for Poképédia took 7.152557373046875e-06s
INFO | --- Analysis for pokepedia-fr took 2.689161539077759s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.482269287109375e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.27416324615478516s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0203092098236084s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.581710815429688e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 6.9141387939453125e-06s
INFO | --- Analysis for polymath-virtual-library took 6.375855445861816s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6551151275634766s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2698023319244385s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.0967254638671875e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.152557373046875e-06s
INFO | --- Analysis for portuguese_prisons_releases took 5.790489673614502s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 3.933906555175781e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.26856565475463867s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.0204317569732666s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 2.8133392333984375e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.969280958175659s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.1484832763671875e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.2575559616088867s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 2.8848648071289062e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 1.8596649169921875e-05s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.988391160964966s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 4.0531158447265625e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.2522239685058594s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.0203397274017334s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 2.7179718017578125e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 7.152557373046875e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.833066701889038s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 4.4345855712890625e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.2695920467376709s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.021188735961914062s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.170967102050781e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 9.059906005859375e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.88852858543396s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.2803304195404053s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 3.015814781188965s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.0531158447265625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.2788372039794922s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020991802215576172s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.170967102050781e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.975353717803955s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 3.981590270996094e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.2680389881134033s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.9455573558807373s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 0.00012254714965820312s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.2600085735321045s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.021012067794799805s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 9.059906005859375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.9381260871887207s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0003209114074707031s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.269305944442749s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 2.8848648071289062e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.955051898956299s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2660329341888428s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.91613507270813s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 8.368492126464844e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.2655494213104248s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.020946264266967773s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 3.170967102050781e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 3.0218262672424316s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.649162292480469e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.2696068286895752s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 9.059906005859375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.9613120555877686s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 6.628036499023438e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.2663278579711914s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.02066946029663086s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.959756374359131s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.27793335914611816s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.1948089599609375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.9574220180511475s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 3.933906555175781e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2756359577178955s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020225048065185547s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 3.337860107421875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.911074638366699s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2616729736328125s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 2.8133392333984375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.876350164413452s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.25686097145080566s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 2.6941299438476562e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 3.01249361038208s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.2883901596069336s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.02019214630126953s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 2.86102294921875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.9682061672210693s
Availability | SPARQL endpoint availability check for prefix.cc took 4.124641418457031e-05s
Availability | VoID file availability check for prefix.cc took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.28234338760375977s
Reputation | Calculation of the PageRank for prefix.cc took 0.0203397274017334s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.4332275390625e-05s
Believability | Calculation of trust value for prefix.cc took 7.867813110351562e-06s
INFO | --- Analysis for prefix-cc took 3.170722723007202s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.8537137508392334s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2907090187072754s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02016901969909668s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.601478576660156e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 8.392448425292969s
Availability | SPARQL endpoint availability check for PreLex took 4.854334354400635s
Availability | VoID file availability check for PreLex took 0.0007498264312744141s
Completeness | Calculation of interlinking completeness for PreLex took 0.27500486373901367s
Reputation | Calculation of the PageRank for PreLex took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for PreLex took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.605552673339844e-05s
Believability | Calculation of trust value for PreLex took 8.58306884765625e-06s
INFO | --- Analysis for prelex took 13.392568349838257s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.472236394882202s
Availability | VoID file availability check for Prelinger Archives took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.27350449562072754s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020650386810302734s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 2.6941299438476562e-05s
Believability | Calculation of trust value for Prelinger Archives took 7.3909759521484375e-06s
INFO | --- Analysis for prelinger_archives took 11.978432893753052s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.36431002616882324s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0006122589111328125s
Extra | Recovery of all triples for PreMOn (Predicate Model for Ontologies) took 5.818856239318848s
Performance | Total latancy measurement for PreMOn (Predicate Model for Ontologies) took 0.44007444381713867s
Amount of data | Number of triples check for PreMOn (Predicate Model for Ontologies) took 0.07813811302185059s
Interoperability | New terms check for PreMOn (Predicate Model for Ontologies) took 1.9086878299713135s
Versatility | Languages check for PreMOn (Predicate Model for Ontologies) took 58.942832946777344s
Interpretability | Number of blank nodes check for PreMOn (Predicate Model for Ontologies) took 0.08236312866210938s
Security | Check HTTPS for PreMOn (Predicate Model for Ontologies) took 0.07470035552978516s
Interpretability | RDF structures check for PreMOn (Predicate Model for Ontologies) took 0.08476448059082031s
Versatility | Serialization formats check for PreMOn (Predicate Model for Ontologies) took 0.18651652336120605s
Availability | RDF dump link check for PreMOn (Predicate Model for Ontologies) took 0.07935571670532227s
License | MR license check for PreMOn (Predicate Model for Ontologies) took 0.09201574325561523s
License | HR license check for PreMOn (Predicate Model for Ontologies) took 0.8365797996520996s
Amount of data | Number of property check for PreMOn (Predicate Model for Ontologies) took 0.12805867195129395s
Understandability | Number of label check for PreMOn (Predicate Model for Ontologies) took 0.08780932426452637s
Understandability | URI regex check for PreMOn (Predicate Model for Ontologies) took 0.17239093780517578s
Understandability | Vocabs check for PreMOn (Predicate Model for Ontologies) took 0.08511924743652344s
Verifiability | Authors check for PreMOn (Predicate Model for Ontologies) took 0.09340524673461914s
Verifiability | Publishers check for PreMOn (Predicate Model for Ontologies) took 0.08598613739013672s
Performance | Throughput check for PreMOn (Predicate Model for Ontologies) took 10.397840976715088s
Amount of data | Check the number of entities for PreMOn (Predicate Model for Ontologies) took 0.00012183189392089844s
Verifiability | Contribs. check for PreMOn (Predicate Model for Ontologies) took 0.08713340759277344s
Interlinking | sameAs chians check for PreMOn (Predicate Model for Ontologies) took 0.0886232852935791s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.08124756813049316s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.08160066604614258s
Timeliness | dataset update frequency check for PreMOn (Predicate Model for Ontologies) took 0.08625340461730957s
Currency | Creation date check for PreMOn (Predicate Model for Ontologies) took 0.20568060874938965s
Currency | Modification date check for PreMOn (Predicate Model for Ontologies) took 0.22535991668701172s
Rep.Conc. | URIs length for PreMOn (Predicate Model for Ontologies) took 3.7772326469421387s
Interoperability | New vocabularies check for PreMOn (Predicate Model for Ontologies) took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for PreMOn (Predicate Model for Ontologies) took 0.11550259590148926s
Accuracy | Check Empty annotation labels for PreMOn (Predicate Model for Ontologies) took 0.9628019332885742s
Accuracy | Check White space in annotation for PreMOn (Predicate Model for Ontologies) took 0.08160591125488281s
Accuracy | Check Datatype consistency for PreMOn (Predicate Model for Ontologies) took 0.08186912536621094s
Consistency | Disjoint class check for PreMOn (Predicate Model for Ontologies) took 0.1158757209777832s
Consistency | Check Misplaced properties for PreMOn (Predicate Model for Ontologies) took 1.7300999164581299s
Consistency | Misplaced classes for PreMOn (Predicate Model for Ontologies) took 0.36549949645996094s
Consistency | Check Ontology hijacking for PreMOn (Predicate Model for Ontologies) took 2.335620641708374s
Consistency | Check Invalid usage of undefined classes for PreMOn (Predicate Model for Ontologies) took 1.187103509902954s
Consistency | Check Invalid usage of undefined properties for PreMOn (Predicate Model for Ontologies) took 2.7909421920776367s
Conciseness | Check Extensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.09271407127380371s
Conciseness | Check Intensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.12268543243408203s
Security | Sign check for PreMOn (Predicate Model for Ontologies) took 0.04961419105529785s
Availability | Check URIs Dereferenciability for PreMOn (Predicate Model for Ontologies) took 904.1260643005371s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 1.3335411548614502s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.021522998809814453s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 5.888938903808594e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn (Predicate Model for Ontologies) took 2.1457672119140625e-06s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 7.62939453125e-06s
INFO | --- Analysis for premon took 1019.7741572856903s
Availability | SPARQL endpoint availability check for Previsible took 7.319450378417969e-05s
Availability | VoID file availability check for Previsible took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Previsible took 0.6792247295379639s
Reputation | Calculation of the PageRank for Previsible took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for Previsible took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.1205673217773438e-05s
Believability | Calculation of trust value for Previsible took 7.3909759521484375e-06s
INFO | --- Analysis for Previsible took 4.6202392578125s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.1484832763671875e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.2792239189147949s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.841255187988281e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 6.198883056640625e-06s
INFO | --- Analysis for princeton-library-findingaids took 3.678439140319824s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.5425944328308105s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.285778284072876s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020488262176513672s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for PrinParLat took 4.141855478286743s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.4726231098175049s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.282581090927124s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 3.218650817871094e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.843971252441406e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 5.9604644775390625e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.276756525039673s
Availability | SPARQL endpoint availability check for Prior Panel took 4.220008850097656e-05s
Availability | VoID file availability check for Prior Panel took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.23910212516784668s
Reputation | Calculation of the PageRank for Prior Panel took 0.02088165283203125s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.4809112548828125e-05s
Believability | Calculation of trust value for Prior Panel took 5.4836273193359375e-06s
INFO | --- Analysis for Prior_Panel took 2.9802284240722656s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.0531158447265625e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.27217864990234375s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.02075505256652832s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 2.956390380859375e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 8.821487426757812e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 3.344780206680298s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.172325134277344e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.26468324661254883s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.021140575408935547s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.1948089599609375e-05s
Believability | Calculation of trust value for Procomún SPARQL took 6.67572021484375e-06s
INFO | --- Analysis for procomun-sparql took 2.9263663291931152s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 7.581710815429688e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.2717578411102295s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.021033048629760742s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.4332275390625e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 3.0414412021636963s
Availability | SPARQL endpoint availability check for ProductDB took 1.6397616863250732s
Availability | VoID file availability check for ProductDB took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for ProductDB took 0.25676989555358887s
Reputation | Calculation of the PageRank for ProductDB took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.295608520507812e-05s
Believability | Calculation of trust value for ProductDB took 7.3909759521484375e-06s
INFO | --- Analysis for productdb took 6.5343146324157715s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2708408832550049s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.020861387252807617s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.271766662597656e-05s
Believability | Calculation of trust value for Product Types Ontology took 7.152557373046875e-06s
INFO | --- Analysis for productontology took 3.304058790206909s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 5.340576171875e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.27562808990478516s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.021013498306274414s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010156631469726562s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 2.9230399131774902s
Availability | SPARQL endpoint availability check for provenanceweb took 0.028069019317626953s
Availability | VoID file availability check for provenanceweb took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.28780293464660645s
Reputation | Calculation of the PageRank for provenanceweb took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.581710815429688e-05s
Believability | Calculation of trust value for provenanceweb took 7.62939453125e-06s
INFO | --- Analysis for provenanceweb took 77.53743529319763s
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.0005919933319091797s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2699165344238281s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 9.942054748535156e-05s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 6.9141387939453125e-06s
INFO | --- Analysis for proyectoapadrina took 3.6581928730010986s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.58870577812195s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0009963512420654297s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.29735898971557617s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.6716461181640625e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 1.1444091796875e-05s
INFO | --- Analysis for pscs-catalogue took 121.64849376678467s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.315376281738281e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.2780749797821045s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.033348083496094e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 7.62939453125e-06s
INFO | --- Analysis for psh-subject-headings took 3.6447925567626953s
Availability | SPARQL endpoint availability check for Depression took 0.3472425937652588s
Availability | VoID file availability check for Depression took 0.0007846355438232422s
Completeness | Calculation of interlinking completeness for Depression took 0.2590644359588623s
Reputation | Calculation of the PageRank for Depression took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for Depression took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Depression took 3.0517578125e-05s
Believability | Calculation of trust value for Depression took 7.62939453125e-06s
INFO | --- Analysis for Psychology took 2.8289144039154053s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.220008850097656e-05s
Availability | VoID file availability check for PubChem RDF took 0.0010962486267089844s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.2709076404571533s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.220008850097656e-05s
Believability | Calculation of trust value for PubChem RDF took 8.58306884765625e-06s
INFO | --- Analysis for PubChem_RDF took 4.97651481628418s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.100799560546875e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.2977714538574219s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.02127861976623535s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 3.1948089599609375e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 7.3909759521484375e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 3.0456349849700928s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.7341675758361816s
Availability | VoID file availability check for Public Spending in Greece took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.26253533363342285s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007410049438476562s
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 8.106231689453125e-06s
INFO | --- Analysis for public-spending-in-greece took 8.1232430934906s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.315376281738281e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.2792379856109619s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 3.147125244140625e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 8.106231689453125e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 3.418710708618164s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.3086831569671631s
Availability | VoID file availability check for Publications Office Authority tables took 0.0006554126739501953s
Extra | Recovery of all triples for Publications Office Authority tables took 584.6968839168549s
Performance | Total latancy measurement for Publications Office Authority tables took 0.6211235523223877s
Amount of data | Number of triples check for Publications Office Authority tables took 89.61085557937622s
Interoperability | New terms check for Publications Office Authority tables took 113.86187028884888s
Versatility | Languages check for Publications Office Authority tables took 300.13659286499023s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 6.560179233551025s
Security | Check HTTPS for Publications Office Authority tables took 0.34070801734924316s
Interpretability | RDF structures check for Publications Office Authority tables took 0.4916830062866211s
Versatility | Serialization formats check for Publications Office Authority tables took 14.854219198226929s
Availability | RDF dump link check for Publications Office Authority tables took 0.29346561431884766s
License | MR license check for Publications Office Authority tables took 0.20063185691833496s
License | HR license check for Publications Office Authority tables took 300.0820610523224s
Amount of data | Number of property check for Publications Office Authority tables took 0.15982961654663086s
Understandability | Number of label check for Publications Office Authority tables took 4.673919200897217s
Understandability | URI regex check for Publications Office Authority tables took 0.33222174644470215s
Understandability | Vocabs check for Publications Office Authority tables took 0.11117434501647949s
Verifiability | Authors check for Publications Office Authority tables took 0.18243169784545898s
Verifiability | Publishers check for Publications Office Authority tables took 0.19405746459960938s
Performance | Throughput check for Publications Office Authority tables took 10.570427656173706s
Amount of data | Check the number of entities for Publications Office Authority tables took 0.00015592575073242188s
Verifiability | Contribs. check for Publications Office Authority tables took 0.15013408660888672s
Interlinking | sameAs chians check for Publications Office Authority tables took 10.191826343536377s
Interlinking | skos check for Publications Office Authority tables took 0.5185980796813965s
Interlinking | skos check for Publications Office Authority tables took 0.42069458961486816s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.24262166023254395s
Currency | Creation date check for Publications Office Authority tables took 0.45143747329711914s
Currency | Modification date check for Publications Office Authority tables took 0.2386007308959961s
Rep.Conc. | URIs length for Publications Office Authority tables took 568.0476672649384s
Interoperability | New vocabularies check for Publications Office Authority tables took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.15821480751037598s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.15743613243103027s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.13644862174987793s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 121.02550005912781s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.1286091804504395s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.6531941890716553s
Consistency | Disjoint class check for Publications Office Authority tables took 0.19625592231750488s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.77857971191406s
Consistency | Misplaced classes for Publications Office Authority tables took 8.763543605804443s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 115.80613303184509s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.4788038730621338s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.30160117149353s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.0528182983398438s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.7894573211669922s
Security | Sign check for Publications Office Authority tables took 0.1656954288482666s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 4.084758520126343s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 1.5715861320495605s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.020939350128173828s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.2438507080078125e-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 4.76837158203125e-06s
INFO | --- Analysis for publications_office_authority_tables took 15670.147800922394s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.124641418457031e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.7076303958892822s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 2.86102294921875e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 7.3909759521484375e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 5.639361143112183s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.1961669921875e-05s
Availability | VoID file availability check for QBOAirbase took 0.0007755756378173828s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.2528867721557617s
Reputation | Calculation of the PageRank for QBOAirbase took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.915496826171875e-05s
Believability | Calculation of trust value for QBOAirbase took 8.106231689453125e-06s
INFO | --- Analysis for qboairbase took 140.27962970733643s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 3.9577484130859375e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.26279449462890625s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 2.7894973754882812e-05s
Believability | Calculation of trust value for qualitywebdata.org took 7.152557373046875e-06s
INFO | --- Analysis for qualitywebdata-org took 5.6002256870269775s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.2438507080078125e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.2705996036529541s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.8133392333984375e-05s
Believability | Calculation of trust value for Qualité de l'air took 9.059906005859375e-06s
INFO | --- Analysis for Qualité_de_l'air took 2.9138879776000977s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 5.602836608886719e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.27566075325012207s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.0728836059570312e-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 4.172325134277344e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 6.4373016357421875e-06s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 51.651360511779785s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.5131411552429199s
Availability | VoID file availability check for Querolus in LiLa took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.27246689796447754s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Querolus in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for Querolus took 4.452816724777222s
Availability | SPARQL endpoint availability check for Quotations Book took 4.0531158447265625e-05s
Availability | VoID file availability check for Quotations Book took 0.0003819465637207031s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.2885472774505615s
Reputation | Calculation of the PageRank for Quotations Book took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 3.0517578125e-05s
Believability | Calculation of trust value for Quotations Book took 7.62939453125e-06s
INFO | --- Analysis for quotations_book took 3.4408233165740967s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.7310748100280762s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.0205385684967041s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for r4r took 4.2723915576934814s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.9832813739776611s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0012080669403076172s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2999544143676758s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020762920379638672s
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.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.9114227294921875e-05s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.7220458984375e-06s
INFO | --- Analysis for racai-legalnero took 4.655823707580566s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.2438507080078125e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.2811462879180908s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 2.9087066650390625e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 5.9604644775390625e-06s
INFO | --- Analysis for racai-llod-corola-we took 2.9321486949920654s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 2.0741939544677734s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0003693103790283203s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.2696566581726074s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.0994415283203125e-05s
Believability | Calculation of trust value for PARSEME-Ro corpus took 6.67572021484375e-06s
INFO | --- Analysis for racai-llod-parseme-ro took 5.065378904342651s
Availability | SPARQL endpoint availability check for RoLEX took 1.9161059856414795s
Availability | VoID file availability check for RoLEX took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for RoLEX took 0.25293731689453125s
Reputation | Calculation of the PageRank for RoLEX took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for RoLEX took 2.9802322387695312e-05s
Believability | Calculation of trust value for RoLEX took 6.67572021484375e-06s
INFO | --- Analysis for racai-llod-rolex took 4.896527528762817s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2750730514526367s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 2.7894973754882812e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.7188665866851807s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.267692565917969e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.2904508113861084s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.8371810913085938e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 9.298324584960938e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.649862051010132s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.410743713378906e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.26536035537719727s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.02098870277404785s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.075599670410156e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 8.58306884765625e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.5969271659851074s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.029273986816406e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.2750847339630127s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020771026611328125s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.123283386230469e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 6.67572021484375e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.7597670555114746s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.3940436840057373s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.26854968070983887s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 3.0040740966796875e-05s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 6.4373016357421875e-06s
INFO | --- Analysis for racai-llod-rtasc took 3.908736228942871s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.5000371932983398s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.2827179431915283s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0008237361907958984s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 2.9802322387695312e-05s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 6.67572021484375e-06s
INFO | --- Analysis for racai-llod-simonero took 3.5431182384490967s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.2047266960144043s
Availability | VoID file availability check for Rådata nå! took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2886087894439697s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 7.939338684082031e-05s
Believability | Calculation of trust value for Rådata nå! took 6.9141387939453125e-06s
INFO | --- Analysis for radatana took 4.572065591812134s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 4.4345855712890625e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.2697257995605469s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 4.1484832763671875e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 7.62939453125e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 16.105876207351685s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.029273986816406e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.27326083183288574s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.020679473876953125s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 2.956390380859375e-05s
Believability | Calculation of trust value for Raphael Research Resource took 6.9141387939453125e-06s
INFO | --- Analysis for raphaelresearchresource took 2.979933261871338s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 10.752408504486084s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.2978546619415283s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.123283386230469e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 6.9141387939453125e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 23.121492862701416s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 393.2790777683258s
Availability | VoID file availability check for Polish LGU financial statements took 0.00037097930908203125s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.2947959899902344s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021259069442749023s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.719329833984375e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 6.67572021484375e-06s
INFO | --- Analysis for Rb_PL_LGU took 668.2201368808746s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.7167539596557617s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 2.765655517578125e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 5.6933557987213135s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.26267194747924805s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 2.6702880859375e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 5.563793420791626s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.261242151260376s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.020685434341430664s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 2.7418136596679688e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 3.870234251022339s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.2742471694946289s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020638227462768555s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 2.7894973754882812e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 3.8073272705078125s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 4.76837158203125e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.28687524795532227s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 2.765655517578125e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 7.62939453125e-06s
INFO | --- Analysis for rcahmw-periods-list took 2.9451684951782227s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.1484832763671875e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2805821895599365s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.153915405273438e-05s
Believability | Calculation of trust value for RDF Book Mashup took 6.198883056640625e-06s
INFO | --- Analysis for rdf-book-mashup took 3.601708173751831s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.38690185546875e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.27780938148498535s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 9.679794311523438e-05s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 7.62939453125e-06s
INFO | --- Analysis for rdfize-lastfm took 2.9155209064483643s
Availability | SPARQL endpoint availability check for RDFLicense took 260.7741758823395s
Availability | VoID file availability check for RDFLicense took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.2652273178100586s
Reputation | Calculation of the PageRank for RDFLicense took 0.020708322525024414s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.409385681152344e-05s
Believability | Calculation of trust value for RDFLicense took 6.9141387939453125e-06s
INFO | --- Analysis for rdflicense took 535.7607007026672s
Availability | SPARQL endpoint availability check for RDFohloh took 4.363059997558594e-05s
Availability | VoID file availability check for RDFohloh took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.2789344787597656s
Reputation | Calculation of the PageRank for RDFohloh took 0.02107095718383789s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.34600830078125e-05s
Believability | Calculation of trust value for RDFohloh took 7.3909759521484375e-06s
INFO | --- Analysis for rdfohloh took 8.84848928451538s
Availability | SPARQL endpoint availability check for Reactome RDF took 1.7851438522338867s
Availability | VoID file availability check for Reactome RDF took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.24869990348815918s
Reputation | Calculation of the PageRank for Reactome RDF took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.838539123535156e-05s
Believability | Calculation of trust value for Reactome RDF took 5.9604644775390625e-06s
INFO | --- Analysis for reactome-rdf took 5.4134252071380615s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 4.962247371673584s
Availability | VoID file availability check for Rechtspraak.nl took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.270784854888916s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.34600830078125e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 5.0067901611328125e-06s
INFO | --- Analysis for rechtspraak took 11.94840955734253s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 5.125999450683594e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.26438426971435547s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.20159912109375e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 7.3909759521484375e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 7.760004997253418s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.08290410041809082s
Availability | VoID file availability check for reference.data.gov.uk took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2802276611328125s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.0001556873321533203s
Believability | Calculation of trust value for reference.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.609807014465332s
Availability | SPARQL endpoint availability check for Regiony took 4.2438507080078125e-05s
Availability | VoID file availability check for Regiony took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for Regiony took 0.27922916412353516s
Reputation | Calculation of the PageRank for Regiony took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for Regiony took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Regiony took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Regiony took 2.8133392333984375e-05s
Believability | Calculation of trust value for Regiony took 7.3909759521484375e-06s
INFO | --- Analysis for regiony took 3.408825635910034s
Availability | SPARQL endpoint availability check for RELD took 261.86711597442627s
Availability | VoID file availability check for RELD took 0.0003249645233154297s
Completeness | Calculation of interlinking completeness for RELD took 0.7801904678344727s
Reputation | Calculation of the PageRank for RELD took 0.020650625228881836s
Interlinking | Calculation of Degree of Connection for RELD took 1.52587890625e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for RELD took 3.123283386230469e-05s
Believability | Calculation of trust value for RELD took 7.62939453125e-06s
INFO | --- Analysis for RELD took 538.598979473114s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.17343807220458984s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005693435668945312s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.5790612697601318s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.4667482376098633s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.485182285308838s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.6322498321533203s
Versatility | Languages check for Repository for Linked Open Archival Data took 20.65443468093872s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.0623323917388916s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.2813386917114258s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.38002896308898926s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.35571956634521484s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.20071768760681152s
License | MR license check for Repository for Linked Open Archival Data took 0.5370769500732422s
License | HR license check for Repository for Linked Open Archival Data took 9.177388191223145s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.1457676887512207s
Understandability | Number of label check for Repository for Linked Open Archival Data took 1.247328519821167s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.4911656379699707s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.11366462707519531s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.2165982723236084s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.1776721477508545s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.42908763885498s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 7.343292236328125e-05s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.08132743835449219s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.1381068229675293s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.2451019287109375s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.07251286506652832s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.2715575695037842s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.19261455535888672s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.20032525062561035s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.9099795818328857s
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.089019775390625s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.12929606437683105s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.09570550918579102s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.8907470703125s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.028621435165405273s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.029364347457885742s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.18065810203552246s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 2.110541820526123s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.18877387046813965s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.5699636936187744s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.1639900207519531s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.18940806388855s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.033278465270996094s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.15596699714660645s
Security | Sign check for Repository for Linked Open Archival Data took 0.8598902225494385s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1083.831181049347s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 2.5476598739624023s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.021142244338989258s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.9073486328125e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 8.344650268554688e-06s
INFO | --- Analysis for reload took 1232.0707478523254s
Availability | SPARQL endpoint availability check for Land use merced dataset took 5.7697296142578125e-05s
Availability | VoID file availability check for Land use merced dataset took 0.000732421875s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.7311069965362549s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.0517578125e-05s
Believability | Calculation of trust value for Land use merced dataset took 7.3909759521484375e-06s
INFO | --- Analysis for remote_Sensing took 15.549628734588623s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.7016165256500244s
Availability | VoID file availability check for Renewable Energy Generators took 0.00083160400390625s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.2680497169494629s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.021238088607788086s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.4345855712890625e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 6.198883056640625e-06s
INFO | --- Analysis for renewable_energy_generators took 11.447220087051392s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.05805182456970215s
Availability | VoID file availability check for research.data.gov.uk took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.2788350582122803s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007474422454833984s
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 5.4836273193359375e-06s
INFO | --- Analysis for research-data-gov-uk took 2.9388160705566406s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 8.463859558105469e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.2763817310333252s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 2.9087066650390625e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 6.9141387939453125e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 3.8920230865478516s
Availability | SPARQL endpoint availability check for Restaurantes took 4.029273986816406e-05s
Availability | VoID file availability check for Restaurantes took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.3404085636138916s
Reputation | Calculation of the PageRank for Restaurantes took 0.020885467529296875s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 3.0279159545898438e-05s
Believability | Calculation of trust value for Restaurantes took 7.3909759521484375e-06s
INFO | --- Analysis for restaurantes-zaragoza took 3.1542844772338867s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.172325134277344e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.2544376850128174s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.723403930664062e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 6.4373016357421875e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 3.779634952545166s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.047394514083862305s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.2845041751861572s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.02098703384399414s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.0994415283203125e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 5.9604644775390625e-06s
INFO | --- Analysis for revistas_turismo took 2.51583194732666s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.2737576961517334s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2814457416534424s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.021091699600219727s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011801719665527344s
Believability | Calculation of trust value for Revyu.com - Review Anything took 8.106231689453125e-06s
INFO | --- Analysis for revyu took 2.7742531299591064s
Availability | SPARQL endpoint availability check for sdafsadf took 0.34546589851379395s
Availability | VoID file availability check for sdafsadf took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.3126976490020752s
Reputation | Calculation of the PageRank for sdafsadf took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 2.956390380859375e-05s
Believability | Calculation of trust value for sdafsadf took 5.7220458984375e-06s
INFO | --- Analysis for rgsdfg took 3.3118693828582764s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.9591064453125e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.2701416015625s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.7206878662109375e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 6.198883056640625e-06s
INFO | --- Analysis for riese took 3.0669615268707275s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 5.316734313964844e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.2725040912628174s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.0517578125e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 6.67572021484375e-06s
INFO | --- Analysis for rijksmuseum took 3.005093812942505s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.6502482891082764s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.2704436779022217s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.649162292480469e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 6.4373016357421875e-06s
INFO | --- Analysis for rism took 3.7670607566833496s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.19211816787719727s
Availability | VoID file availability check for RISM Authority data took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.26047492027282715s
Reputation | Calculation of the PageRank for RISM Authority data took 0.02092432975769043s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.3392181396484375e-05s
Believability | Calculation of trust value for RISM Authority data took 6.4373016357421875e-06s
INFO | --- Analysis for rism-authorities took 3.1446988582611084s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 5.435943603515625e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2885863780975342s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020917654037475586s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.9087066650390625e-05s
Believability | Calculation of trust value for engineering equipment ontology took 5.7220458984375e-06s
INFO | --- Analysis for rk took 2.434967517852783s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.05964183807373047s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.2666738033294678s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.020999431610107422s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002307891845703125s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.5896048545837402s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.046283721923828125s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.2517852783203125s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.021255016326904297s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00013685226440429688s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.53847336769104s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.05010032653808594s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.27405476570129395s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.02097630500793457s
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.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.000194549560546875s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.5682623386383057s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.050641536712646484s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.3000812530517578s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020919322967529297s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0001552104949951172s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-cordis took 3.186464548110962s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.05033612251281738s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.27806520462036133s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020756959915161133s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00015401840209960938s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.5951411724090576s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.053667545318603516s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.2872035503387451s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 5.650520324707031e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.6355819702148438s
Availability | SPARQL endpoint availability check for crm took 8.96453857421875e-05s
Availability | VoID file availability check for crm took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for crm took 0.30390095710754395s
Reputation | Calculation of the PageRank for crm took 0.021175622940063477s
Interlinking | Calculation of Degree of Connection for crm took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for crm took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for crm took 5.0067901611328125e-05s
Believability | Calculation of trust value for crm took 5.745887756347656e-05s
INFO | --- Analysis for rkb-explorer-crm took 3.0404012203216553s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.05434918403625488s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.26804685592651367s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020969629287719727s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00011849403381347656s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.529804229736328s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.04944205284118652s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.2850511074066162s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.0207974910736084s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.1975250244140625e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.5911638736724854s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.05593991279602051s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.26488780975341797s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.0207674503326416s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00023221969604492188s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.5467493534088135s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.04770255088806152s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.27097272872924805s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020978450775146484s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.319450378417969e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.5495738983154297s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.043790578842163086s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2757987976074219s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020784854888916016s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.489059448242188e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.5339672565460205s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.05290627479553223s
Availability | VoID file availability check for digitaleconomy took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.26529860496520996s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020901203155517578s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.075599670410156e-05s
Believability | Calculation of trust value for digitaleconomy took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.5400936603546143s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.04749107360839844s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2844691276550293s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020781517028808594s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014781951904296875s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.5769383907318115s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.04816460609436035s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2806568145751953s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020961284637451172s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0008203983306884766s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.7206878662109375e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-ecs took 3.215378761291504s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.0531158447265625e-05s
Availability | VoID file availability check for enaktingpsi took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.26375508308410645s
Reputation | Calculation of the PageRank for enaktingpsi took 0.02043771743774414s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 3.0279159545898438e-05s
Believability | Calculation of trust value for enaktingpsi took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.9324541091918945s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.044556379318237305s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.30896592140197754s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020879268646240234s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0001819133758544922s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-eprints took 2.5242881774902344s
Availability | SPARQL endpoint availability check for epsrc took 0.05036568641662598s
Availability | VoID file availability check for epsrc took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for epsrc took 0.26986265182495117s
Reputation | Calculation of the PageRank for epsrc took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for epsrc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.793571472167969e-05s
Believability | Calculation of trust value for epsrc took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.57698655128479s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.037058115005493164s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0003731250762939453s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.2769186496734619s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0009663105010986328s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.703636169433594e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-era took 2.5482447147369385s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.05040693283081055s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.28322267532348633s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010275840759277344s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.654416799545288s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.00543212890625e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.28621435165405273s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 2.9325485229492188e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-foreign took 3.0026795864105225s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.04145479202270508s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.2720448970794678s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020793676376342773s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.869171142578125e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.573108196258545s
Availability | SPARQL endpoint availability check for fun took 0.04672837257385254s
Availability | VoID file availability check for fun took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for fun took 0.2763190269470215s
Reputation | Calculation of the PageRank for fun took 0.021047592163085938s
Interlinking | Calculation of Degree of Connection for fun took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for fun took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for fun took 7.414817810058594e-05s
Believability | Calculation of trust value for fun took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.5951788425445557s
Availability | SPARQL endpoint availability check for gdlc took 0.05226421356201172s
Availability | VoID file availability check for gdlc took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for gdlc took 0.26204562187194824s
Reputation | Calculation of the PageRank for gdlc took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.556510925292969e-05s
Believability | Calculation of trust value for gdlc took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.520643711090088s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.043050527572631836s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.29546499252319336s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02083444595336914s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011086463928222656s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.586620330810547s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.042525291442871094s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.30922508239746094s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020789623260498047s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001316070556640625s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.559966564178467s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.04268002510070801s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.26788783073425293s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020580530166625977s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0001347064971923828s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.5345120429992676s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.04270172119140625s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.2683899402618408s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.413459777832031e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.5737900733947754s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.05576920509338379s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.30050134658813477s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02093338966369629s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0008275508880615234s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.486343383789062e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.7427337169647217s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.04202079772949219s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2584834098815918s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.02089977264404297s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.5299530029296875e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.6026289463043213s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.04509782791137695s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2524383068084717s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016045570373535156s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.5540008544921875s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.04904031753540039s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0004277229309082031s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.2796444892883301s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00014543533325195312s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.626250743865967s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.042738914489746094s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.2656567096710205s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.29425048828125e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.5234501361846924s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.042464494705200195s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.30045080184936523s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015425682067871094s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.5679242610931396s
Availability | SPARQL endpoint availability check for notube took 0.04665946960449219s
Availability | VoID file availability check for notube took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for notube took 0.25768375396728516s
Reputation | Calculation of the PageRank for notube took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for notube took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for notube took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for notube took 4.172325134277344e-05s
Believability | Calculation of trust value for notube took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.556156635284424s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.03494000434875488s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.2658810615539551s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.0215299129486084s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0016429424285888672s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00028586387634277344s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.568289279937744s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.04587531089782715s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.2855570316314697s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020873069763183594s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015783309936523438s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.540581703186035s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 3.981590270996094e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.2883467674255371s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 3.008965015411377s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.05205941200256348s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.27438902854919434s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.319450378417969e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-os took 2.5622315406799316s
Availability | SPARQL endpoint availability check for photos took 0.04437446594238281s
Availability | VoID file availability check for photos took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for photos took 0.28651976585388184s
Reputation | Calculation of the PageRank for photos took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for photos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for photos took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for photos took 7.033348083496094e-05s
Believability | Calculation of trust value for photos took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.5727782249450684s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.04675483703613281s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.2580854892730713s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00010967254638671875s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.525257110595703s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.04762887954711914s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.2712686061859131s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.02075362205505371s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019550323486328125s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.5604684352874756s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.05318260192871094s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.2664327621459961s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.02064824104309082s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0001354217529296875s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.5195555686950684s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.047986507415771484s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.2702145576477051s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.560585021972656e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.5476174354553223s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.04648613929748535s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.25498080253601074s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020286083221435547s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012063980102539062s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.4666855335235596s
Availability | SPARQL endpoint availability check for roni took 0.0337522029876709s
Availability | VoID file availability check for roni took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for roni took 0.24556183815002441s
Reputation | Calculation of the PageRank for roni took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for roni took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for roni took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for roni took 2.7894973754882812e-05s
Believability | Calculation of trust value for roni took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.4535372257232666s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.05185532569885254s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.28713250160217285s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00021457672119140625s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.5472891330718994s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04622054100036621s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.27408671379089355s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010752677917480469s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.519113302230835s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.037481069564819336s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.2578697204589844s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.894371032714844e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.5122220516204834s
Availability | SPARQL endpoint availability check for webconf took 0.04604601860046387s
Availability | VoID file availability check for webconf took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for webconf took 0.2707099914550781s
Reputation | Calculation of the PageRank for webconf took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for webconf took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010228157043457031s
Believability | Calculation of trust value for webconf took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-webconf took 13.342671155929565s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.045297861099243164s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.27921056747436523s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.033348083496094e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-webscience took 3.010969400405884s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.04698920249938965s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2661936283111572s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.0002028942108154297s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.5489985942840576s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.03810882568359375s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.26047182083129883s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.799003601074219e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.522303342819214s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.076957702636719e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.2719731330871582s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.02191472053527832s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for RKB Explorer Data took 7.3909759521484375e-06s
INFO | --- Analysis for rkb_explorer_data took 2.942507743835449s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.4740147590637207s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.2656590938568115s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.020884037017822266s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0008563995361328125s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.344650268554688e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 6.67572021484375e-06s
INFO | --- Analysis for roceeh-road took 3.595003843307495s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.0531158447265625e-05s
Availability | VoID file availability check for The Rosetta Project took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.2562713623046875s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 2.7418136596679688e-05s
Believability | Calculation of trust value for The Rosetta Project took 6.9141387939453125e-06s
INFO | --- Analysis for rosetta-project took 2.9140207767486572s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.172325134277344e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.289872407913208s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.0517578125e-05s
Believability | Calculation of trust value for ontology terrorist attack took 7.152557373046875e-06s
INFO | --- Analysis for ROSHANI took 3.977829933166504s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.172325134277344e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.26334428787231445s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020869731903076172s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.0517578125e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 8.821487426757812e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.4391040802001953s
Availability | SPARQL endpoint availability check for x took 4.363059997558594e-05s
Availability | VoID file availability check for x took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for x took 0.26811933517456055s
Reputation | Calculation of the PageRank for x took 0.020778417587280273s
Interlinking | Calculation of Degree of Connection for x took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for x took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for x took 2.956390380859375e-05s
Believability | Calculation of trust value for x took 6.9141387939453125e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.5201761722564697s
Availability | SPARQL endpoint availability check for Rpm Find took 4.2438507080078125e-05s
Availability | VoID file availability check for Rpm Find took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.28844261169433594s
Reputation | Calculation of the PageRank for Rpm Find took 0.020647287368774414s
Interlinking | Calculation of Degree of Connection for Rpm Find took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 2.7179718017578125e-05s
Believability | Calculation of trust value for Rpm Find took 7.152557373046875e-06s
INFO | --- Analysis for rpm_find took 2.9581480026245117s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 5.030632019042969e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.2685105800628662s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.02061915397644043s
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.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.270408630371094e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 7.152557373046875e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.509012460708618s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.291534423828125e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.27617716789245605s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020488262176513672s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 6.866455078125e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 6.9141387939453125e-06s
INFO | --- Analysis for rubentaelman took 2.9656336307525635s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.267692565917969e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0010213851928710938s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.3357994556427002s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 9.036064147949219e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 7.867813110351562e-06s
INFO | --- Analysis for rubenverborgh took 3.4930808544158936s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 393.15232586860657s
Availability | VoID file availability check for Russian Universities Specialities took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.7429561614990234s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.020801782608032227s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 3.838539123535156e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 7.62939453125e-06s
INFO | --- Analysis for russian-universities-specialities took 680.397433757782s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.076957702636719e-05s
Availability | VoID file availability check for RuThes Cloud took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.73008131980896s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.020504236221313477s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 2.7894973754882812e-05s
Believability | Calculation of trust value for RuThes Cloud took 7.3909759521484375e-06s
INFO | --- Analysis for ruthes took 6.4996726512908936s
Availability | SPARQL endpoint availability check for RxNorm took 5.0067901611328125e-05s
Availability | VoID file availability check for RxNorm took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for RxNorm took 0.2581453323364258s
Reputation | Calculation of the PageRank for RxNorm took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for RxNorm took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RxNorm took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.170967102050781e-05s
Believability | Calculation of trust value for RxNorm took 9.298324584960938e-06s
INFO | --- Analysis for rxnorm took 3.7997632026672363s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.259359836578369s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.27684903144836426s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 2.9087066650390625e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 6.9141387939453125e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 9.702238082885742s
Availability | SPARQL endpoint availability check for SALDO took 4.100799560546875e-05s
Availability | VoID file availability check for SALDO took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for SALDO took 0.7021119594573975s
Reputation | Calculation of the PageRank for SALDO took 0.021117210388183594s
Interlinking | Calculation of Degree of Connection for SALDO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for SALDO took 2.7894973754882812e-05s
Believability | Calculation of trust value for SALDO took 7.867813110351562e-06s
INFO | --- Analysis for saldo took 4.685102701187134s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.2546887397766113s
Availability | VoID file availability check for SALDO-RDF took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.7118082046508789s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.457069396972656e-05s
Believability | Calculation of trust value for SALDO-RDF took 6.9141387939453125e-06s
INFO | --- Analysis for saldo-rdf took 6.197983980178833s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.5829572677612305s
Availability | VoID file availability check for SALDOM-RDF took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.27606844902038574s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020336151123046875s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.457069396972656e-05s
Believability | Calculation of trust value for SALDOM-RDF took 6.9141387939453125e-06s
INFO | --- Analysis for saldom-rdf took 4.950719594955444s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.172325134277344e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2700843811035156s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02030634880065918s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.0001010894775390625s
Believability | Calculation of trust value for Salzburgerland DE took 6.198883056640625e-06s
INFO | --- Analysis for salzburgerland-com-de took 3.0906240940093994s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.1484832763671875e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.30970096588134766s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.02071070671081543s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 9.965896606445312e-05s
Believability | Calculation of trust value for Salzburgerland EN took 7.3909759521484375e-06s
INFO | --- Analysis for salzburgerland-com-en took 3.1908295154571533s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.124641418457031e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.28740453720092773s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020680665969848633s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010609626770019531s
Believability | Calculation of trust value for Salzburgerland IT took 6.9141387939453125e-06s
INFO | --- Analysis for salzburgerland-com-it took 2.987619161605835s
Availability | SPARQL endpoint availability check for sameAs.org took 4.029273986816406e-05s
Availability | VoID file availability check for sameAs.org took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.26086997985839844s
Reputation | Calculation of the PageRank for sameAs.org took 0.020246267318725586s
Interlinking | Calculation of Degree of Connection for sameAs.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 2.86102294921875e-05s
Believability | Calculation of trust value for sameAs.org took 6.4373016357421875e-06s
INFO | --- Analysis for sameas-org took 2.928715467453003s
Availability | SPARQL endpoint availability check for sandrart.net took 4.673004150390625e-05s
Availability | VoID file availability check for sandrart.net took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.27094197273254395s
Reputation | Calculation of the PageRank for sandrart.net took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.628036499023438e-05s
Believability | Calculation of trust value for sandrart.net took 6.198883056640625e-06s
INFO | --- Analysis for sandrart-net took 3.6698856353759766s
Availability | SPARQL endpoint availability check for Taxons  took 0.589324951171875s
Availability | VoID file availability check for Taxons  took 0.0004470348358154297s
Extra | Recovery of all triples for Taxons  took 25.859795808792114s
Performance | Total latancy measurement for Taxons  took 0.4326915740966797s
Amount of data | Number of triples check for Taxons  took 2.3507704734802246s
Interoperability | New terms check for Taxons  took 1.7165508270263672s
Versatility | Languages check for Taxons  took 45.73772644996643s
Interpretability | Number of blank nodes check for Taxons  took 1.6191375255584717s
Security | Check HTTPS for Taxons  took 0.20734500885009766s
Interpretability | RDF structures check for Taxons  took 1.183237075805664s
Versatility | Serialization formats check for Taxons  took 0.5615921020507812s
Availability | RDF dump link check for Taxons  took 0.32701611518859863s
License | MR license check for Taxons  took 3.094189405441284s
License | HR license check for Taxons  took 2.3677196502685547s
Amount of data | Number of property check for Taxons  took 0.17077326774597168s
Understandability | Number of label check for Taxons  took 3.09806489944458s
Understandability | URI regex check for Taxons  took 0.7860968112945557s
Understandability | Vocabs check for Taxons  took 0.21669888496398926s
Verifiability | Authors check for Taxons  took 0.08672642707824707s
Verifiability | Publishers check for Taxons  took 0.08916449546813965s
Amount of data | Check the number of entities for Taxons  took 7.605552673339844e-05s
Verifiability | Contribs. check for Taxons  took 0.09330177307128906s
Interlinking | sameAs chians check for Taxons  took 0.15763282775878906s
Interlinking | skos check for Taxons  took 0.16313648223876953s
Interlinking | skos check for Taxons  took 0.09943938255310059s
Timeliness | dataset update frequency check for Taxons  took 0.44890928268432617s
Currency | Creation date check for Taxons  took 0.2116711139678955s
Currency | Modification date check for Taxons  took 0.2097628116607666s
Rep.Conc. | URIs length for Taxons  took 9.755662679672241s
Interoperability | New vocabularies check for Taxons  took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.12317371368408203s
Accuracy | Check Functional Property for Taxons  took 0.4307408332824707s
Accuracy | Check Inverse Functional Property for Taxons  took 0.500899076461792s
Accuracy | Check Empty annotation labels for Taxons  took 4.9790332317352295s
Accuracy | Check White space in annotation for Taxons  took 0.3050353527069092s
Accuracy | Check Datatype consistency for Taxons  took 0.27380871772766113s
Consistency | Disjoint class check for Taxons  took 0.1349475383758545s
Consistency | Check Misplaced properties for Taxons  took 4.723381519317627s
Consistency | Misplaced classes for Taxons  took 0.9733138084411621s
Consistency | Check Ontology hijacking for Taxons  took 5.626537322998047s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.1858701705932617s
Consistency | Check Invalid usage of undefined properties for Taxons  took 6.088260889053345s
Conciseness | Check Extensional conciseness for Taxons  took 0.2896120548248291s
Conciseness | Check Intensional conciseness for Taxons  took 0.19826674461364746s
Security | Sign check for Taxons  took 2.0335397720336914s
Availability | Check URIs Dereferenciability for Taxons  took 1732.3904163837433s
Completeness | Calculation of interlinking completeness for Taxons  took 1.0163114070892334s
Reputation | Calculation of the PageRank for Taxons  took 0.02240777015686035s
Interlinking | Calculation of Degree of Connection for Taxons  took 7.891654968261719e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0008544921875s
Interlinking | Calculation of Clustering coefficient for Taxons  took 9.131431579589844e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 2.86102294921875e-06s
Believability | Calculation of trust value for Taxons  took 8.821487426757812e-06s
INFO | --- Analysis for sandre took 1942.8046567440033s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.6938657760620117s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.7412152290344238s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020816326141357422s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.1948089599609375e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 7.867813110351562e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 9.443071842193604s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 270.6075644493103s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.7079260349273682s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.076957702636719e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 7.867813110351562e-06s
INFO | --- Analysis for santillana_guide_dataset took 717.9427967071533s
Availability | SPARQL endpoint availability check for SATAR test  took 4.553794860839844e-05s
Availability | VoID file availability check for SATAR test  took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.7566585540771484s
Reputation | Calculation of the PageRank for SATAR test  took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 2.8848648071289062e-05s
Believability | Calculation of trust value for SATAR test  took 6.4373016357421875e-06s
INFO | --- Analysis for SATAR_test took 6.504920244216919s
Availability | SPARQL endpoint availability check for SCBG Data took 22.579972982406616s
Availability | VoID file availability check for SCBG Data took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.2713005542755127s
Reputation | Calculation of the PageRank for SCBG Data took 0.020708560943603516s
Interlinking | Calculation of Degree of Connection for SCBG Data took 4.1484832763671875e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.225440979003906e-05s
Believability | Calculation of trust value for SCBG Data took 6.9141387939453125e-06s
INFO | --- Analysis for SCBG-Data took 55.435861587524414s
Availability | SPARQL endpoint availability check for schema.org took 5.125999450683594e-05s
Availability | VoID file availability check for schema.org took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for schema.org took 0.26763272285461426s
Reputation | Calculation of the PageRank for schema.org took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for schema.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.457069396972656e-05s
Believability | Calculation of trust value for schema.org took 7.3909759521484375e-06s
INFO | --- Analysis for schema-org took 3.9254658222198486s
Availability | SPARQL endpoint availability check for Schemantra took 4.1484832763671875e-05s
Availability | VoID file availability check for Schemantra took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Schemantra took 0.2768588066101074s
Reputation | Calculation of the PageRank for Schemantra took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Schemantra took 2.9802322387695312e-05s
Believability | Calculation of trust value for Schemantra took 7.152557373046875e-06s
INFO | --- Analysis for Schemantra took 3.280031681060791s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 0.9214105606079102s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.2924461364746094s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.361701965332031e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 7.62939453125e-06s
INFO | --- Analysis for schemapedia took 5.794938325881958s
Availability | SPARQL endpoint availability check for scholarlydata took 4.076957702636719e-05s
Availability | VoID file availability check for scholarlydata took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.2766754627227783s
Reputation | Calculation of the PageRank for scholarlydata took 0.02070021629333496s
Interlinking | Calculation of Degree of Connection for scholarlydata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 2.8133392333984375e-05s
Believability | Calculation of trust value for scholarlydata took 7.3909759521484375e-06s
INFO | --- Analysis for scholarlydata took 3.0249383449554443s
Availability | SPARQL endpoint availability check for Scholarometer took 4.2438507080078125e-05s
Availability | VoID file availability check for Scholarometer took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.2754974365234375s
Reputation | Calculation of the PageRank for Scholarometer took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 9.131431579589844e-05s
Believability | Calculation of trust value for Scholarometer took 7.867813110351562e-06s
INFO | --- Analysis for scholarometer took 7.21285343170166s
Availability | SPARQL endpoint availability check for Science Commons took 4.00543212890625e-05s
Availability | VoID file availability check for Science Commons took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Science Commons took 0.2724039554595947s
Reputation | Calculation of the PageRank for Science Commons took 0.020705461502075195s
Interlinking | Calculation of Degree of Connection for Science Commons took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Science Commons took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Science Commons took 3.4332275390625e-05s
Believability | Calculation of trust value for Science Commons took 7.3909759521484375e-06s
INFO | --- Analysis for science_commons took 2.9813528060913086s
Availability | SPARQL endpoint availability check for ScienceWise took 4.100799560546875e-05s
Availability | VoID file availability check for ScienceWise took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2696349620819092s
Reputation | Calculation of the PageRank for ScienceWise took 0.021433353424072266s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0008985996246337891s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.5762786865234375e-05s
Believability | Calculation of trust value for ScienceWise took 7.867813110351562e-06s
INFO | --- Analysis for sciencewise took 3.124300956726074s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.363059997558594e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.27309179306030273s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 2.7894973754882812e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 5.4836273193359375e-06s
INFO | --- Analysis for scoreboard took 3.4812562465667725s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.076957702636719e-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.0007073879241943359s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.29569458961486816s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020923376083374023s
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.0967254638671875e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 2.9802322387695312e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 7.62939453125e-06s
INFO | --- Analysis for SDDEC took 28.918049335479736s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.267692565917969e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.275714635848999s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 2.86102294921875e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 6.198883056640625e-06s
INFO | --- Analysis for SDG took 3.282067060470581s
Availability | SPARQL endpoint availability check for sears.com took 4.363059997558594e-05s
Availability | VoID file availability check for sears.com took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for sears.com took 0.28005194664001465s
Reputation | Calculation of the PageRank for sears.com took 0.020610809326171875s
Interlinking | Calculation of Degree of Connection for sears.com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.985664367675781e-05s
Believability | Calculation of trust value for sears.com took 5.4836273193359375e-06s
INFO | --- Analysis for sears took 4.3733978271484375s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 6.284811019897461s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.27048635482788086s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.726119995117188e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 5.0067901611328125e-06s
INFO | --- Analysis for sec-rdfabout took 18.678003549575806s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 32.23949956893921s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0008032321929931641s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.2654385566711426s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.177757263183594e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for secold took 168.60963916778564s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.506111145019531e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.2583146095275879s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.020927906036376953s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 3.147125244140625e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 8.58306884765625e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 3.568572998046875s
Availability | SPARQL endpoint availability check for semanlink took 4.076957702636719e-05s
Availability | VoID file availability check for semanlink took 0.0010409355163574219s
Completeness | Calculation of interlinking completeness for semanlink took 0.2711827754974365s
Reputation | Calculation of the PageRank for semanlink took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00014281272888183594s
Believability | Calculation of trust value for semanlink took 6.9141387939453125e-06s
INFO | --- Analysis for semanlink took 183.3887917995453s
Availability | SPARQL endpoint availability check for Semantic Library took 5.412101745605469e-05s
Availability | VoID file availability check for Semantic Library took 0.0003199577331542969s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.26857519149780273s
Reputation | Calculation of the PageRank for Semantic Library took 0.02035379409790039s
Interlinking | Calculation of Degree of Connection for Semantic Library took 4.76837158203125e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 2.6226043701171875e-05s
Believability | Calculation of trust value for Semantic Library took 7.62939453125e-06s
INFO | --- Analysis for semantic-library took 3.338615655899048s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.124641418457031e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.2850606441497803s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0009229183197021484s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.3855438232421875e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-profiling-network took 3.4721038341522217s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.08974838256835938s
Availability | VoID file availability check for Semantic Universe Data took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.2810781002044678s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Semantic Universe Data took 7.62939453125e-06s
INFO | --- Analysis for semantic-universe took 3.7521328926086426s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.323814153671265s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0007648468017578125s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2649502754211426s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00010991096496582031s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 6.4373016357421875e-06s
INFO | --- Analysis for semantic-web-dog-food took 83.5741491317749s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.1484832763671875e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.000362396240234375s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.2814619541168213s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.000812530517578125s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.2438507080078125e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 7.152557373046875e-06s
INFO | --- Analysis for semantic-web-grundlagen took 3.600100517272949s
Availability | SPARQL endpoint availability check for semantic-web-journal took 3.933906555175781e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.6939959526062012s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 2.8371810913085938e-05s
Believability | Calculation of trust value for semantic-web-journal took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-web-journal took 4.24017596244812s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.2438507080078125e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0013279914855957031s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.28179097175598145s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.535385131835938e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 6.198883056640625e-06s
INFO | --- Analysis for semantic-xbrl took 3.9220001697540283s
Availability | SPARQL endpoint availability check for Semantic Bible took 4.172325134277344e-05s
Availability | VoID file availability check for Semantic Bible took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.2903931140899658s
Reputation | Calculation of the PageRank for Semantic Bible took 0.020873069763183594s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 2.86102294921875e-05s
Believability | Calculation of trust value for Semantic Bible took 6.9141387939453125e-06s
INFO | --- Analysis for semantic_bible took 3.0518836975097656s
Availability | SPARQL endpoint availability check for SemanticQuran took 0.3428938388824463s
Availability | VoID file availability check for SemanticQuran took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.280059814453125s
Reputation | Calculation of the PageRank for SemanticQuran took 0.02026987075805664s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 6.818771362304688e-05s
Believability | Calculation of trust value for SemanticQuran took 6.9141387939453125e-06s
INFO | --- Analysis for semanticquran took 3.0626306533813477s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.076957702636719e-05s
Availability | VoID file availability check for SemanticTweet took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.25922179222106934s
Reputation | Calculation of the PageRank for SemanticTweet took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.221366882324219e-05s
Believability | Calculation of trust value for SemanticTweet took 1.1444091796875e-05s
INFO | --- Analysis for semantictweet took 4.450887441635132s
Availability | SPARQL endpoint availability check for semanticweb.org took 5.555152893066406e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.27298736572265625s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.295608520507812e-05s
Believability | Calculation of trust value for semanticweb.org took 6.4373016357421875e-06s
INFO | --- Analysis for semanticweb-org took 22.7868549823761s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.07036709785461426s
Availability | VoID file availability check for Semantic CrunchBase took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.29070568084716797s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.318092346191406e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 6.9141387939453125e-06s
INFO | --- Analysis for semsol-crunchbase took 2.572772264480591s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.100799560546875e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.3020191192626953s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 3.1948089599609375e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 3.2901763916015625e-05s
INFO | --- Analysis for sensores-de-intellidomo took 3.0280697345733643s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.2640995979309082s
Availability | VoID file availability check for SentimentWortschatz took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.30382204055786133s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.2438507080078125e-05s
Believability | Calculation of trust value for SentimentWortschatz took 8.106231689453125e-06s
INFO | --- Analysis for sentiws took 3.7076032161712646s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.01026201248169s
Availability | VoID file availability check for seoul-bike-data took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.28156471252441406s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.2901763916015625e-05s
Believability | Calculation of trust value for seoul-bike-data took 7.152557373046875e-06s
INFO | --- Analysis for seoul-bike-data took 73.0434103012085s
Availability | SPARQL endpoint availability check for Serendipity took 8.219070196151733s
Availability | VoID file availability check for Serendipity took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for Serendipity took 0.7185616493225098s
Reputation | Calculation of the PageRank for Serendipity took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Serendipity took 6.866455078125e-05s
Believability | Calculation of trust value for Serendipity took 6.67572021484375e-06s
INFO | --- Analysis for serendipity took 16.47489047050476s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.6253204345703125e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.6849024295806885s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.030007362365722656s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0013954639434814453s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 4.0531158447265625e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 5.0067901611328125e-06s
INFO | --- Analysis for Sherry_Wine took 3.1846277713775635s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.673004150390625e-05s
Availability | VoID file availability check for Sherry Wine took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.26126646995544434s
Reputation | Calculation of the PageRank for Sherry Wine took 0.021354198455810547s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.86102294921875e-05s
Believability | Calculation of trust value for Sherry Wine took 8.344650268554688e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.406203508377075s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.2288072109222412s
Availability | VoID file availability check for Shoah victims? names took 0.0005192756652832031s
Extra | Recovery of all triples for Shoah victims? names took 1.475264310836792s
Performance | Total latancy measurement for Shoah victims? names took 0.44608592987060547s
Amount of data | Number of triples check for Shoah victims? names took 1.4365103244781494s
Interoperability | New terms check for Shoah victims? names took 1.5857465267181396s
Versatility | Languages check for Shoah victims? names took 20.480048179626465s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.336826801300049s
Security | Check HTTPS for Shoah victims? names took 0.19787168502807617s
Interpretability | RDF structures check for Shoah victims? names took 0.456439733505249s
Versatility | Serialization formats check for Shoah victims? names took 0.2846512794494629s
Availability | RDF dump link check for Shoah victims? names took 0.171600341796875s
License | MR license check for Shoah victims? names took 0.3821744918823242s
License | HR license check for Shoah victims? names took 8.971218585968018s
Amount of data | Number of property check for Shoah victims? names took 0.13050246238708496s
Understandability | Number of label check for Shoah victims? names took 2.0026941299438477s
Understandability | URI regex check for Shoah victims? names took 0.5550565719604492s
Understandability | Vocabs check for Shoah victims? names took 0.09508013725280762s
Verifiability | Authors check for Shoah victims? names took 0.27615952491760254s
Verifiability | Publishers check for Shoah victims? names took 0.27163171768188477s
Performance | Throughput check for Shoah victims? names took 10.273505926132202s
Amount of data | Check the number of entities for Shoah victims? names took 8.463859558105469e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.07139182090759277s
Interlinking | sameAs chians check for Shoah victims? names took 0.1235206127166748s
Interlinking | skos check for Shoah victims? names took 0.29061365127563477s
Interlinking | skos check for Shoah victims? names took 0.07568550109863281s
Timeliness | dataset update frequency check for Shoah victims? names took 0.250180721282959s
Currency | Creation date check for Shoah victims? names took 0.1930229663848877s
Currency | Modification date check for Shoah victims? names took 0.19620609283447266s
Rep.Conc. | URIs length for Shoah victims? names took 3.1770107746124268s
Interoperability | New vocabularies check for Shoah victims? names took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.09270000457763672s
Accuracy | Check Functional Property for Shoah victims? names took 0.09740924835205078s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.12137198448181152s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.9125802516937256s
Accuracy | Check White space in annotation for Shoah victims? names took 0.029371023178100586s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.028254270553588867s
Consistency | Disjoint class check for Shoah victims? names took 0.2683446407318115s
Consistency | Check Misplaced properties for Shoah victims? names took 2.1052684783935547s
Consistency | Misplaced classes for Shoah victims? names took 0.2066490650177002s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.5893640518188477s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.1331291198730469s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.1808090209960938s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.029802322387695312s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.179365873336792s
Security | Sign check for Shoah victims? names took 1.0626704692840576s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1083.7780911922455s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.9365262985229492s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.02183818817138672s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 5.054473876953125e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.430511474609375e-06s
Believability | Calculation of trust value for Shoah victims? names took 8.58306884765625e-06s
INFO | --- Analysis for shoah-victims-names took 1221.7739124298096s
Availability | SPARQL endpoint availability check for Person took 4.2438507080078125e-05s
Availability | VoID file availability check for Person took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Person took 0.2687108516693115s
Reputation | Calculation of the PageRank for Person took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for Person took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Person took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Person took 3.0279159545898438e-05s
Believability | Calculation of trust value for Person took 7.152557373046875e-06s
INFO | --- Analysis for Shripriya_Dubey took 4.503404140472412s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.220008850097656e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.000244140625s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.7054083347320557s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 2.6226043701171875e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 8.58306884765625e-06s
INFO | --- Analysis for Shutterstock took 3.3077244758605957s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.76837158203125e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.2694234848022461s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 2.86102294921875e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 6.67572021484375e-06s
INFO | --- Analysis for simile_data_collection took 3.348072052001953s
Availability | SPARQL endpoint availability check for SIMPLE took 4.410743713378906e-05s
Availability | VoID file availability check for SIMPLE took 0.0008594989776611328s
Completeness | Calculation of interlinking completeness for SIMPLE took 2.0853219032287598s
Reputation | Calculation of the PageRank for SIMPLE took 0.021300077438354492s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.839897155761719e-05s
Believability | Calculation of trust value for SIMPLE took 9.298324584960938e-06s
INFO | --- Analysis for simple took 1809.2768795490265s
Availability | SPARQL endpoint availability check for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 4.7206878662109375e-05s
Availability | VoID file availability check for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.00036025047302246094s
Completeness | Calculation of interlinking completeness for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.2532026767730713s
Reputation | Calculation of the PageRank for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 1.2159347534179688e-05s
Believability | Calculation of trust value for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 7.3909759521484375e-06s
INFO | --- Analysis for sinh-CLSPIRData took 4.253643989562988s
Availability | SPARQL endpoint availability check for SITC-V4 took 26.974738359451294s
Availability | VoID file availability check for SITC-V4 took 0.0009076595306396484s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.693575382232666s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.790855407714844e-05s
Believability | Calculation of trust value for SITC-V4 took 5.9604644775390625e-06s
INFO | --- Analysis for sitc-v4 took 123.49591064453125s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 7.295608520507812e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.282604455947876s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 5.364418029785156e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 6.9141387939453125e-06s
INFO | --- Analysis for sli_galnet_rdf took 13.799222707748413s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.172325134277344e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.00031304359436035156s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.7026286125183105s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.170967102050781e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 6.4373016357421875e-06s
INFO | --- Analysis for slideshare2rdf took 3.7842392921447754s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.1484832763671875e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.2862420082092285s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 2.86102294921875e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 7.867813110351562e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 3.4752357006073s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.8351104259490967s
Availability | VoID file availability check for Linked Stage Graph took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.25626325607299805s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.020839929580688477s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 5.078315734863281e-05s
Believability | Calculation of trust value for Linked Stage Graph took 7.152557373046875e-06s
INFO | --- Analysis for slod took 3.7499423027038574s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 5.125999450683594e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.2401885986328125s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.020960092544555664s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.170967102050781e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 7.152557373046875e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 2.916750907897949s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.6180822849273682s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.00028824806213378906s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 112.42805290222168s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.942645788192749s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 8.094879865646362s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 15.621039152145386s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.2171607017517s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.839236259460449s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.2743363380432129s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 12.716296434402466s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.2881298065185547s
License | MR license check for Smart Points Of Interest @PSNC took 0.5991237163543701s
License | HR license check for Smart Points Of Interest @PSNC took 300.16218733787537s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.48381519317626953s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.718388557434082s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 0.8475627899169922s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.45815205574035645s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.18749618530273438s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.25655245780944824s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.545695066452026s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 9.369850158691406e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.18658447265625s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.20074009895324707s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.45563507080078125s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4447617530822754s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 7.718942642211914s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.49677133560180664s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.22475862503051758s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 175.86802983283997s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.19901823997497559s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.3384392261505127s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.33815646171569824s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 47.15448808670044s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.6841320991516113s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.6261558532714844s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.1946089267730713s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 106.6481945514679s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.439677238464355s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 38.283567905426025s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.2104270458221436s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 96.52958536148071s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7567105293273926s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.5895044803619385s
Security | Sign check for Smart Points Of Interest @PSNC took 0.9407706260681152s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 18.633312463760376s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 1.2778728008270264s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.02218794822692871s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.0001983642578125s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 6.67572021484375e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for Smart_POI_dataset took 2347.341489315033s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.923694849014282s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0008516311645507812s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.2745327949523926s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020964622497558594s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.600120544433594e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 8.106231689453125e-06s
INFO | --- Analysis for smartlink took 15.029517889022827s
Availability | SPARQL endpoint availability check for SNIK took 0.5167717933654785s
Availability | VoID file availability check for SNIK took 0.0013649463653564453s
Extra | Recovery of all triples for SNIK took 7.29805588722229s
Performance | Total latancy measurement for SNIK took 0.9652042388916016s
Amount of data | Number of triples check for SNIK took 0.19760465621948242s
Interoperability | New terms check for SNIK took 1.361510992050171s
Versatility | Languages check for SNIK took 0.2308647632598877s
Interpretability | Number of blank nodes check for SNIK took 0.20665645599365234s
Interpretability | RDF structures check for SNIK took 0.18653297424316406s
Versatility | Serialization formats check for SNIK took 0.19516658782958984s
Availability | RDF dump link check for SNIK took 0.19976496696472168s
License | MR license check for SNIK took 0.1873469352722168s
License | HR license check for SNIK took 0.23371005058288574s
Amount of data | Number of property check for SNIK took 0.18462061882019043s
Understandability | Number of label check for SNIK took 0.19727492332458496s
Understandability | URI regex check for SNIK took 0.4054861068725586s
Understandability | Vocabs check for SNIK took 0.2054884433746338s
Verifiability | Authors check for SNIK took 0.18410968780517578s
Verifiability | Publishers check for SNIK took 0.19679474830627441s
Performance | Throughput check for SNIK took 11.513622283935547s
Amount of data | Check the number of entities for SNIK took 3.2901763916015625e-05s
Verifiability | Contribs. check for SNIK took 0.19143176078796387s
Interlinking | sameAs chians check for SNIK took 0.1939220428466797s
Interlinking | skos check for SNIK took 0.19423937797546387s
Interlinking | skos check for SNIK took 0.2059462070465088s
Timeliness | dataset update frequency check for SNIK took 0.1838834285736084s
Currency | Creation date check for SNIK took 0.37549376487731934s
Currency | Modification date check for SNIK took 0.3856992721557617s
Rep.Conc. | URIs length for SNIK took 1.9948091506958008s
Interoperability | New vocabularies check for SNIK took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.19530272483825684s
Accuracy | Check Functional Property for SNIK took 0.19301700592041016s
Accuracy | Check Inverse Functional Property for SNIK took 0.20324087142944336s
Accuracy | Check Empty annotation labels for SNIK took 0.7693591117858887s
Accuracy | Check White space in annotation for SNIK took 0.027617931365966797s
Accuracy | Check Datatype consistency for SNIK took 0.22308683395385742s
Consistency | Disjoint class check for SNIK took 0.19436216354370117s
Consistency | Check Misplaced properties for SNIK took 0.6596026420593262s
Consistency | Misplaced classes for SNIK took 0.7073657512664795s
Consistency | Check Ontology hijacking for SNIK took 1.782029390335083s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.1819725036621094s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.461374044418335s
Conciseness | Check Extensional conciseness for SNIK took 0.158430814743042s
Conciseness | Check Intensional conciseness for SNIK took 0.3404662609100342s
Security | Sign check for SNIK took 0.19762015342712402s
Availability | Check URIs Dereferenciability for SNIK took 985.8688781261444s
Completeness | Calculation of interlinking completeness for SNIK took 0.9262845516204834s
Reputation | Calculation of the PageRank for SNIK took 0.02105998992919922s
Interlinking | Calculation of Degree of Connection for SNIK took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0008771419525146484s
Interlinking | Calculation of Clustering coefficient for SNIK took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 2.384185791015625e-06s
Believability | Calculation of trust value for SNIK took 8.106231689453125e-06s
INFO | --- Analysis for snik took 1046.5413174629211s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.172325134277344e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.4416673183441162s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.123283386230469e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 7.62939453125e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 4.963641881942749s
Availability | SPARQL endpoint availability check for SocialLink took 9.864710330963135s
Availability | VoID file availability check for SocialLink took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for SocialLink took 0.3068559169769287s
Reputation | Calculation of the PageRank for SocialLink took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.2479248046875e-05s
Believability | Calculation of trust value for SocialLink took 7.152557373046875e-06s
INFO | --- Analysis for SocialLink took 24.4110746383667s
Availability | SPARQL endpoint availability check for SocialLink took 4.0531158447265625e-05s
Availability | VoID file availability check for SocialLink took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for SocialLink took 0.7169146537780762s
Reputation | Calculation of the PageRank for SocialLink took 0.020761966705322266s
Interlinking | Calculation of Degree of Connection for SocialLink took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SocialLink took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for SocialLink took 2.8133392333984375e-05s
Believability | Calculation of trust value for SocialLink took 7.3909759521484375e-06s
INFO | --- Analysis for sociallink took 3.9272801876068115s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 4.291534423828125e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.26872706413269043s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 2.765655517578125e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 7.152557373046875e-06s
INFO | --- Analysis for SocialRoles took 10.622568845748901s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.23031210899353027s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0006299018859863281s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 22.74629044532776s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.5658788681030273s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.2519190311431885s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.3472659587860107s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.4269073009490967s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.1957862377166748s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.30729055404663086s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.15287184715270996s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.13328266143798828s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.8014671802520752s
License | MR license check for Social Semantic Web Thesaurus took 0.12633728981018066s
License | HR license check for Social Semantic Web Thesaurus took 0.10081648826599121s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.11962389945983887s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.12152266502380371s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.19701266288757324s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.11020803451538086s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.13724040985107422s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.12405657768249512s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.577725648880005s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 7.081031799316406e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.12090921401977539s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.12416887283325195s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.13943696022033691s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.0937957763671875s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.10140132904052734s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.18638968467712402s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.21974754333496094s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 2.166574239730835s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.18043041229248047s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.09303903579711914s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09561491012573242s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.5334339141845703s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012316703796386719s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.10997653007507324s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.3475301265716553s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.07745003700256348s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.117504358291626s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.4050371646881104s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00013637542724609375s
Security | Sign check for Social Semantic Web Thesaurus took 0.09307861328125s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 122.35464572906494s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 1.2675073146820068s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020917177200317383s
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.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 0.00010561943054199219s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 995.3229959011078s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.43522071838378906s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.00027489662170410156s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 116.41063499450684s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9469437599182129s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.47298812866211s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.755488395690918s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.24740052223206s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.0889623165130615s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.26832056045532227s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.798935413360596s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2811753749847412s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5701181888580322s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.21365761756897s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.34886860847473145s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.3278720378875732s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5244557857513428s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19337248802185059s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19362092018127441s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2793691158294678s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.538224458694458s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0001251697540283203s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20968365669250488s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1985476016998291s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4838123321533203s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4555974006652832s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.996539354324341s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4732372760772705s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.22484374046325684s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 174.77563571929932s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19510436058044434s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.34637951850891113s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3404116630554199s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 46.12558197975159s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.71144437789917s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6438796520233154s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19452404975891113s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 98.86122512817383s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.45425820350647s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 37.425122022628784s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.199789047241211s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 105.65040588378906s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.767057418823242s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5941345691680908s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.7870850563049316s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 12.372059106826782s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.3679563999176025s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.021597623825073242s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.58306884765625e-06s
INFO | --- Analysis for Soil_maps took 2341.1761095523834s
Availability | SPARQL endpoint availability check for terrorrist ontology took 7.82012939453125e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.2662923336029053s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.02109694480895996s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for terrorrist ontology took 7.62939453125e-06s
INFO | --- Analysis for somya_omer took 4.649155855178833s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.291534423828125e-05s
Availability | VoID file availability check for Sonclubcx took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.711820125579834s
Reputation | Calculation of the PageRank for Sonclubcx took 0.02027130126953125s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.1682510375976562e-05s
Believability | Calculation of trust value for Sonclubcx took 6.4373016357421875e-06s
INFO | --- Analysis for sonclubcx took 5.507985591888428s
Availability | SPARQL endpoint availability check for SORS took 4.2438507080078125e-05s
Availability | VoID file availability check for SORS took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for SORS took 0.2503974437713623s
Reputation | Calculation of the PageRank for SORS took 0.020294904708862305s
Interlinking | Calculation of Degree of Connection for SORS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for SORS took 4.792213439941406e-05s
Believability | Calculation of trust value for SORS took 5.4836273193359375e-06s
INFO | --- Analysis for sors took 3.6902577877044678s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.220008850097656e-05s
Availability | VoID file availability check for Soudy České republiky took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.2881758213043213s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 3.0994415283203125e-05s
Believability | Calculation of trust value for Soudy České republiky took 7.62939453125e-06s
INFO | --- Analysis for soudy--esk--republiky took 3.545381784439087s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.172325134277344e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.2917609214782715s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.059906005859375e-05s
Believability | Calculation of trust value for southampton-ac-uk took 6.9141387939453125e-06s
INFO | --- Analysis for southampton-ac-uk took 4.520275354385376s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 5.153123617172241s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.263836145401001s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020824909210205078s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 6.67572021484375e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 12.538482427597046s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.1961669921875e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.25334644317626953s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020839452743530273s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.059906005859375e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 8.821487426757812e-06s
INFO | --- Analysis for southampton-ecs-eprints took 5.72646951675415s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5800299644470215s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.000324249267578125s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 209.81602334976196s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.2418415546417236s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.128140687942505s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.000436782836914s
Versatility | Languages check for Spanish Linguistic Datasets took 45.964210510253906s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.0870025157928467s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.14668965339660645s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.30007243156433105s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.29340052604675293s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.2894744873046875s
License | MR license check for Spanish Linguistic Datasets took 0.30147457122802734s
License | HR license check for Spanish Linguistic Datasets took 0.38009071350097656s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.3014700412750244s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.31146788597106934s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.591916561126709s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.2897059917449951s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.29941511154174805s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.2987229824066162s
Performance | Throughput check for Spanish Linguistic Datasets took 11.279050588607788s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 0.000141143798828125s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.27796220779418945s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.2817037105560303s
Interlinking | skos check for Spanish Linguistic Datasets took 0.288161039352417s
Interlinking | skos check for Spanish Linguistic Datasets took 0.22913074493408203s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.29088854789733887s
Currency | Creation date check for Spanish Linguistic Datasets took 0.599168062210083s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5860543251037598s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 78.41645789146423s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.31136655807495117s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.29935288429260254s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.26935863494873047s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9569244384765625s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010608673095703125s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.700988531112671s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.2975609302520752s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.652137994766235s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.469051599502563s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 68.82187342643738s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.3927333354949951s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.639286756515503s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.9636170864105225s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.31491684913635254s
Security | Sign check for Spanish Linguistic Datasets took 0.2789032459259033s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 21.387707948684692s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.9360520839691162s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.170967102050781e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.384185791015625e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.7881393432617188e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 519.2254021167755s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.09081339836120605s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2762923240661621s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.315376281738281e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 7.152557373046875e-06s
INFO | --- Analysis for sparql-endpoint-status took 2.9656713008880615s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 4.076957702636719e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.2909564971923828s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.02050328254699707s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 2.8371810913085938e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 7.62939453125e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 3.0498344898223877s
Availability | SPARQL endpoint availability check for SPQR took 4.00543212890625e-05s
Availability | VoID file availability check for SPQR took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for SPQR took 0.2572915554046631s
Reputation | Calculation of the PageRank for SPQR took 0.02073383331298828s
Interlinking | Calculation of Degree of Connection for SPQR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for SPQR took 2.6941299438476562e-05s
Believability | Calculation of trust value for SPQR took 7.3909759521484375e-06s
INFO | --- Analysis for spqr took 3.3728458881378174s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.2438507080078125e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.275754451751709s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.559226989746094e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 7.867813110351562e-06s
INFO | --- Analysis for springernaturescigraph took 3.457242727279663s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.1961669921875e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.2768392562866211s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 7.3909759521484375e-06s
INFO | --- Analysis for srcmf took 6.797751426696777s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 30.22601056098938s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.26221418380737305s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0009038448333740234s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 4.982948303222656e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 8.106231689453125e-06s
INFO | --- Analysis for ssf took 83.69450402259827s
Availability | SPARQL endpoint availability check for SSF took 4.0531158447265625e-05s
Availability | VoID file availability check for SSF took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for SSF took 0.7222239971160889s
Reputation | Calculation of the PageRank for SSF took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for SSF took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for SSF took 0.0011167526245117188s
Interlinking | Calculation of Clustering coefficient for SSF took 3.647804260253906e-05s
Believability | Calculation of trust value for SSF took 7.3909759521484375e-06s
INFO | --- Analysis for ssf-lexicon took 5.231327772140503s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.124641418457031e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.29302048683166504s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.361701965332031e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 6.4373016357421875e-06s
INFO | --- Analysis for st-andrews-resource-lists took 3.28800106048584s
Availability | SPARQL endpoint availability check for STAC took 4.0531158447265625e-05s
Availability | VoID file availability check for STAC took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for STAC took 0.2646780014038086s
Reputation | Calculation of the PageRank for STAC took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for STAC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for STAC took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for STAC took 2.9087066650390625e-05s
Believability | Calculation of trust value for STAC took 7.3909759521484375e-06s
INFO | --- Analysis for stac took 3.45548939704895s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.0531158447265625e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.2630937099456787s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 3.4332275390625e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 6.67572021484375e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 3.0530576705932617s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.315376281738281e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.31099820137023926s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.0279159545898438e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 6.9141387939453125e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 4.31961727142334s
Availability | SPARQL endpoint availability check for Stammbuch took 5.4836273193359375e-05s
Availability | VoID file availability check for Stammbuch took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2618443965911865s
Reputation | Calculation of the PageRank for Stammbuch took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 2.7894973754882812e-05s
Believability | Calculation of trust value for Stammbuch took 6.67572021484375e-06s
INFO | --- Analysis for Stammbuch took 2.380265951156616s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.370758295059204s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.2526528835296631s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010085105895996094s
Believability | Calculation of trust value for statistics.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for statistics-data-gov-uk took 4.577639818191528s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 4.029273986816406e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.2921597957611084s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 2.9087066650390625e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 7.62939453125e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.993762493133545s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.29405856132507324s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010204315185546875s
Believability | Calculation of trust value for statusnet-1w6-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-1w6-org took 2.9883267879486084s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.2666616439819336s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.02023768424987793s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.031990051269531e-05s
Believability | Calculation of trust value for statusnet-20100-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-20100-org took 2.529473066329956s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2478642463684082s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020785093307495117s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.782472848892212s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.27754640579223633s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 8.368492126464844e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.643094062805176s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.272371768951416s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 8.749961853027344e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.5492985248565674s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.2663736343383789s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00010466575622558594s
Believability | Calculation of trust value for statusnet-bka-li took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-bka-li took 2.557847738265991s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.26117658615112305s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.6716461181640625e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.3884689807891846s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.2605001926422119s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.506111145019531e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-ced117-net took 3.886746406555176s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.27983832359313965s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.0067901611328125e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.5848729610443115s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.26821088790893555s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020748615264892578s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00010728836059570312s
Believability | Calculation of trust value for statusnet-chromic-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.6045949459075928s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2761547565460205s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.843971252441406e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 5.95636510848999s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 5.435943603515625e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2645144462585449s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.2928924560546875e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.5629525184631348s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2797572612762451s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.02028036117553711s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.532669067382812e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.3671655654907227s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.26388096809387207s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010275840759277344s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.9934043884277344s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.2791626453399658s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.021484851837158203s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.507704257965088s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2529909610748291s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 4.863739013671875e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.394335985183716s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2779843807220459s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.936622619628906e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-dtdns-net took 22.46980094909668s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 5.698204040527344e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.2802393436431885s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.02070021629333496s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.314018249511719e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.7642974853515625e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 2.4288296699523926s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.26607513427734375s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.2479248046875e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.486887693405151s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.27710819244384766s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 8.869171142578125e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-fcac-com took 22.874944925308228s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.25006580352783203s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.1975250244140625e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 2.55433988571167s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.27637267112731934s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0008230209350585938s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018334388732910156s
Believability | Calculation of trust value for statusnet-fragdev-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.7968835830688477s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.25669121742248535s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.021315813064575195s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0009322166442871094s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 8.726119995117188e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.9102284908294678s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.2684922218322754s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010466575622558594s
Believability | Calculation of trust value for statusnet-gegeweb-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.6466147899627686s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.2932412624359131s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.29425048828125e-05s
Believability | Calculation of trust value for statusnet-glou-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-glou-org took 2.924862861633301s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 5.7697296142578125e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.27839112281799316s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00011920928955078125s
Believability | Calculation of trust value for statusnet-gomertronic-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.5103750228881836s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2533280849456787s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020537853240966797s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.0001010894775390625s
Believability | Calculation of trust value for statusnet-hackerposse-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.918456554412842s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2678651809692383s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.315376281738281e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-hii-co-il took 2.9367432594299316s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.2661714553833008s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 8.749961853027344e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.4835102558135986s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.2794194221496582s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.6329541206359863s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2539844512939453s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 3.5762786865234375e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.627819776535034s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0007984638214111328s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.29032444953918457s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.48969006538391s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2606196403503418s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00014352798461914062s
Believability | Calculation of trust value for statusnet-jonkman-ca took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.5047342777252197s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2624247074127197s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.1552734375e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.4149105548858643s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.2738981246948242s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.020734548568725586s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.839897155761719e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.438595771789551s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.28685498237609863s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.743171691894531e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.2842981815338135s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 7.653236389160156e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.25753116607666016s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020956754684448242s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 6.937980651855469e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.409085273742676s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.2748453617095947s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.021622419357299805s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.76837158203125e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.5311191082000732s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.2559628486633301s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 5.984306335449219e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.5004920959472656s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.2739381790161133s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.0208590030670166s
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.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.036064147949219e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.6386685371398926s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.26934814453125s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011229515075683594s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.483912467956543s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0007312297821044922s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.31550168991088867s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.459785461425781e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ludost-net took 4.177727222442627s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.25948429107666016s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020575284957885742s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.799003601074219e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.4338953495025635s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2876088619232178s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.020586729049682617s
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.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.269050598144531e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.5225696563720703s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2563014030456543s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00014543533325195312s
Believability | Calculation of trust value for statusnet-macno-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-macno-org took 2.434910535812378s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.2595231533050537s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.0203554630279541s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.4975290298461914s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2675459384918213s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 7.486343383789062e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.059892892837524s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.27385950088500977s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020852327346801758s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00015687942504882812s
Believability | Calculation of trust value for statusnet-morphtown-de took 5.0067901611328125e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.570559501647949s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.2666890621185303s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.02077794075012207s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.512901306152344e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 2.603362798690796s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.27767324447631836s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020381689071655273s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.269050598144531e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.418654680252075s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 5.4836273193359375e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0012257099151611328s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.6444714069366455s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020359039306640625s
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.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.030632019042969e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-my-status-tk took 3.1314921379089355s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2807319164276123s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010323524475097656s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.495769739151001s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2786879539489746s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.020426511764526367s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.6248326301574707s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 5.054473876953125e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.28696370124816895s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 5.984306335449219e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.623833179473877s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.2781529426574707s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.0108642578125e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.5502538681030273s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 5.054473876953125e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2625386714935303s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.02035689353942871s
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.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.38690185546875e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-panda-id-au took 3.3448638916015625s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.27604198455810547s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.489059448242188e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 7.62939453125e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.4784812927246094s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.3046259880065918s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.462501525878906e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.4629099369049072s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.26152992248535156s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.02091526985168457s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00023031234741210938s
Believability | Calculation of trust value for statusnet-postblue-info took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.9104952812194824s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 0.0004322528839111328s
Availability | VoID file availability check for statusnet-progval-net took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.2804386615753174s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-progval-net took 2.596266508102417s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.2816922664642334s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011277198791503906s
Believability | Calculation of trust value for statusnet-qdnx-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.9730422496795654s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.24878454208374023s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.02036881446838379s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 5.888938903808594e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.2789816856384277s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.2735130786895752s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00021529197692871094s
Believability | Calculation of trust value for statusnet-quitter-se took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.6071112155914307s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.25825047492980957s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 9.822845458984375e-05s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.6115713119506836s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 5.555152893066406e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.2769782543182373s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.6743621826171875e-05s
Believability | Calculation of trust value for statusnet-recit-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-recit-org took 4.298479318618774s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.27775025367736816s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001423358917236328s
Believability | Calculation of trust value for statusnet-russwurm-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-russwurm-org took 3.211540699005127s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.2578308582305908s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 7.724761962890625e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 3.123283386230469e-05s
INFO | --- Analysis for statusnet-samnoble-org took 4.726957082748413s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.24876809120178223s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 7.748603820800781e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.470219850540161s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.26238465309143066s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020807504653930664s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.250640869140625e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 7.50428318977356s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.2731611728668213s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.5397775173187256s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.28125929832458496s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.05718994140625e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.435056686401367s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.2833404541015625s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00020313262939453125s
Believability | Calculation of trust value for statusnet-skilledtests-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 4.8600146770477295s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.26864075660705566s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020474910736083984s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010251998901367188s
Believability | Calculation of trust value for statusnet-somsants-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.478055477142334s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.25969529151916504s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.0001327991485595703s
Believability | Calculation of trust value for statusnet-soucy-cc took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.5187933444976807s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2746095657348633s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02098846435546875s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-spip-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-spip-org took 3.921379327774048s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2612640857696533s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.246566772460938e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.827714204788208s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 5.269050598144531e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.28161025047302246s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00011324882507324219s
Believability | Calculation of trust value for statusnet-ssweeny-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.342557430267334s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.935264587402344e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.29011034965515137s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020723819732666016s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.0002219676971435547s
Believability | Calculation of trust value for statusnet-status-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-status-net took 3.5094716548919678s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2588963508605957s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.14984130859375e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.444591999053955s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.25725650787353516s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.02056288719177246s
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.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 8.559226989746094e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.512902021408081s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.2449932098388672s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.0210568904876709s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012135505676269531s
Believability | Calculation of trust value for statusnet-thelovebug-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.5136847496032715s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.26218247413635254s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020654678344726562s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.748603820800781e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-thornton2-com took 5.001623868942261s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.25102782249450684s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.02105569839477539s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.0001087188720703125s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.6783552169799805s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2788121700286865s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.695487976074219e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.9190995693206787s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.26959800720214844s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.699562072753906e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.8104660511016846s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2570013999938965s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.600120544433594e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 3.389326810836792s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.220008850097656e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.2888967990875244s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020435571670532227s
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.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.075599670410156e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for steak took 2.722742795944214s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.172325134277344e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.26813197135925293s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.3882598876953125e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 8.106231689453125e-06s
INFO | --- Analysis for stitch-rameau took 4.071129322052002s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.6780304908752441s
Availability | VoID file availability check for Stone Tech Square took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.26647353172302246s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.2874603271484375e-05s
Believability | Calculation of trust value for Stone Tech Square took 7.62939453125e-06s
INFO | --- Analysis for stone-tech-square-data took 4.6043617725372314s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.1484832763671875e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.2686276435852051s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 3.1948089599609375e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 7.3909759521484375e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.996407985687256s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.5387492179870605s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.001552581787109375s
Extra | Recovery of all triples for STW Thesaurus for Economics took 44.12520956993103s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.2077314853668213s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6755483150482178s
Interoperability | New terms check for STW Thesaurus for Economics took 1.4271986484527588s
Versatility | Languages check for STW Thesaurus for Economics took 1.5060749053955078s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5772924423217773s
Security | Check HTTPS for STW Thesaurus for Economics took 0.14054417610168457s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.24791789054870605s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.27170705795288086s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.23802566528320312s
License | MR license check for STW Thesaurus for Economics took 0.26613593101501465s
License | HR license check for STW Thesaurus for Economics took 2.4386329650878906s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.2526872158050537s
Understandability | Number of label check for STW Thesaurus for Economics took 0.622382640838623s
Understandability | URI regex check for STW Thesaurus for Economics took 0.50765061378479s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.25442957878112793s
Verifiability | Authors check for STW Thesaurus for Economics took 0.24754548072814941s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.24684596061706543s
Performance | Throughput check for STW Thesaurus for Economics took 11.009878396987915s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7414565086364746s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2678546905517578s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.2429044246673584s
Interlinking | skos check for STW Thesaurus for Economics took 0.34686875343322754s
Interlinking | skos check for STW Thesaurus for Economics took 0.37717652320861816s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.25632405281066895s
Currency | Creation date check for STW Thesaurus for Economics took 0.48694825172424316s
Currency | Modification date check for STW Thesaurus for Economics took 0.4893982410430908s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 10.511590719223022s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2781686782836914s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2708017826080322s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.26128530502319336s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 12.008526086807251s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0622906684875488s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.392543077468872s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.27602195739746094s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2772502899169922s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 2.266887903213501s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.1902415752410889s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.194026231765747s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6757087707519531s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.26793766021728516s
Security | Sign check for STW Thesaurus for Economics took 0.2575545310974121s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 3258.547380208969s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 1.5500497817993164s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.02262568473815918s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00017380714416503906s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.0728836059570312e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 3476.8236906528473s
Availability | SPARQL endpoint availability check for SudershanTech took 4.2438507080078125e-05s
Availability | VoID file availability check for SudershanTech took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.26311588287353516s
Reputation | Calculation of the PageRank for SudershanTech took 0.020875930786132812s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.0040740966796875e-05s
Believability | Calculation of trust value for SudershanTech took 7.152557373046875e-06s
INFO | --- Analysis for SudershanTech took 3.832195520401001s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.5972499847412109s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0006737709045410156s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.26523494720458984s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.02083611488342285s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 5.841255187988281e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 7.867813110351562e-06s
INFO | --- Analysis for sudocfr took 8.718584299087524s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 0.9903154373168945s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006375312805175781s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 278.43850088119507s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.7102768421173096s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.5200440883636475s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.8016927242279053s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.026998281478882s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.1508190631866455s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5416646003723145s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5710439682006836s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5423929691314697s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5231738090515137s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 8.11254334449768s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.6040010452270508s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.7018535137176514s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.1010692119598389s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5358333587646484s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5470104217529297s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.552541971206665s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.644193649291992s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 7.2479248046875e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5531718730926514s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5636787414550781s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6312441825866699s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.579840898513794s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5118842124938965s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.0845844745635986s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.1229007244110107s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 55.99993968009949s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5393917560577393s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5291464328765869s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5573611259460449s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 13.686537742614746s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.3670206069946289s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5544557571411133s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 13.699974775314331s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 10.083637475967407s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.3981499671936s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 4.097007989883423s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.9858384132385254s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 3.136428117752075s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5641319751739502s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 1676.7868905067444s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 1.3996093273162842s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.02124786376953125s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 7.390975952148438e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 8.106231689453125e-06s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 5482.498051643372s
Availability | SPARQL endpoint availability check for Surge Radio took 6.794929504394531e-05s
Availability | VoID file availability check for Surge Radio took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.27792787551879883s
Reputation | Calculation of the PageRank for Surge Radio took 0.02064967155456543s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.487701416015625e-05s
Believability | Calculation of trust value for Surge Radio took 6.9141387939453125e-06s
INFO | --- Analysis for surge-radio took 5.726078271865845s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 0.0006127357482910156s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.29049229621887207s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 2.9087066650390625e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 7.62939453125e-06s
INFO | --- Analysis for SWAT took 24.889228582382202s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.124641418457031e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.3978304862976074s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.2700791358947754s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 7.557868957519531e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 7.867813110351562e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.433175802230835s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.0766336917877197s
Availability | VoID file availability check for SweFN-RDF took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.28221797943115234s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.314018249511719e-05s
Believability | Calculation of trust value for SweFN-RDF took 7.152557373046875e-06s
INFO | --- Analysis for swefn-rdf took 6.095693349838257s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.1484832763671875e-05s
Availability | VoID file availability check for SwetoDblp took 0.0006797313690185547s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.2957746982574463s
Reputation | Calculation of the PageRank for SwetoDblp took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.504753112792969e-05s
Believability | Calculation of trust value for SwetoDblp took 9.775161743164062e-06s
INFO | --- Analysis for sweto-dblp took 22.877730131149292s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 4.045109272003174s
Availability | VoID file availability check for Swift Vocabulary took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.2933948040008545s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 6.604194641113281e-05s
Believability | Calculation of trust value for Swift Vocabulary took 7.62939453125e-06s
INFO | --- Analysis for Swift took 8.615337371826172s
Availability | SPARQL endpoint availability check for SymbolicData took 3.910064697265625e-05s
Availability | VoID file availability check for SymbolicData took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.25435805320739746s
Reputation | Calculation of the PageRank for SymbolicData took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for SymbolicData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 3.0040740966796875e-05s
Believability | Calculation of trust value for SymbolicData took 8.344650268554688e-06s
INFO | --- Analysis for symbolicdata took 3.4253320693969727s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.076957702636719e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0012967586517333984s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.2719886302947998s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 2.8848648071289062e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 6.67572021484375e-06s
INFO | --- Analysis for symptoms-in-chinese took 53.06126832962036s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.5104000568389893s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0006351470947265625s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.5631396770477295s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 1.0438587665557861s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 51.87143588066101s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 18.597869873046875s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.2161550521850586s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 50.5846734046936s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.1521596908569336s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 64.43484711647034s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.4275546073913574s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.23115253448486328s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.31890392303466797s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.52774500846863s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5123951435089111s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 37.09121513366699s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.42286181449890137s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.20099496841430664s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.18585896492004395s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.21976685523986816s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 11.773106575012207s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.271766662597656e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.7165358066558838s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 2.0608150959014893s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.795562744140625s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.7953791618347168s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.8502590656280518s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.5699479579925537s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 3.267829656600952s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 73.39831829071045s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.19237065315246582s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.25986552238464355s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0011930465698242188s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0015358924865722656s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.2537055015563965s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 48.90910720825195s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.3058474063873291s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.474036455154419s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.1643924713134766s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 46.52431011199951s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.0019783973693847656s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.31907057762145996s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.20536184310913086s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 5.881532669067383s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 1.212491512298584s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.020825624465942383s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 9.179115295410156e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 7.3909759521484375e-06s
INFO | --- Analysis for sztaki-lod took 898.4533095359802s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.4345855712890625e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.2703268527984619s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 4.839897155761719e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 8.106231689453125e-06s
INFO | --- Analysis for t4gm-info took 6.638313055038452s
Availability | SPARQL endpoint availability check for tags2con delicious took 6.270408630371094e-05s
Availability | VoID file availability check for tags2con delicious took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for tags2con delicious took 1.4271202087402344s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020863771438598633s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 0.00010609626770019531s
Believability | Calculation of trust value for tags2con delicious took 7.3909759521484375e-06s
INFO | --- Analysis for tags2con-delicious took 847.3553657531738s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.05521750450134s
Availability | VoID file availability check for Taiwan geographic names took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.7325351238250732s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.021349430084228516s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.1975250244140625e-05s
Believability | Calculation of trust value for Taiwan geographic names took 7.3909759521484375e-06s
INFO | --- Analysis for taiwan-geographic-names took 670.0206816196442s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.410743713378906e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.7090611457824707s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.02082967758178711s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 8.58306884765625e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 7.867813110351562e-06s
INFO | --- Analysis for talis-openlibrary took 12.684631109237671s
Availability | SPARQL endpoint availability check for TalkBank took 4.0531158447265625e-05s
Availability | VoID file availability check for TalkBank took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for TalkBank took 0.25992918014526367s
Reputation | Calculation of the PageRank for TalkBank took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.7894973754882812e-05s
Believability | Calculation of trust value for TalkBank took 7.3909759521484375e-06s
INFO | --- Analysis for talkbank took 5.061103105545044s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.9556586742401123s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0007188320159912109s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.3037106990814209s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.021312475204467773s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00011849403381347656s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 6.4373016357421875e-06s
INFO | --- Analysis for taxonconcept took 14.633869409561157s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.482269287109375e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.2750215530395508s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020806074142456055s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.0108642578125e-05s
Believability | Calculation of trust value for taxonconcept-assets took 6.9141387939453125e-06s
INFO | --- Analysis for taxonconcept-assets took 3.7334682941436768s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.839897155761719e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.26299452781677246s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.221366882324219e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 7.62939453125e-06s
INFO | --- Analysis for taxonconcept-occurences took 2.8295328617095947s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.5243484973907471s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.2735166549682617s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 5.054473876953125e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 8.106231689453125e-06s
INFO | --- Analysis for taxref-ld took 5.286767244338989s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 0.7106618881225586s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.30115222930908203s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 2.9325485229492188e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 6.9141387939453125e-06s
INFO | --- Analysis for tcga took 7.8035430908203125s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.36438560485839844s
Availability | VoID file availability check for TCGA Roadmap took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.27955031394958496s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02035355567932129s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.009506225585938e-05s
Believability | Calculation of trust value for TCGA Roadmap took 7.3909759521484375e-06s
INFO | --- Analysis for tcga-roadmap took 5.95971417427063s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 2.229724645614624s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.28995585441589355s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010657310485839844s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for tcmgenedit_dataset took 140.10712957382202s
Availability | SPARQL endpoint availability check for TDS took 4.100799560546875e-05s
Availability | VoID file availability check for TDS took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for TDS took 0.6800994873046875s
Reputation | Calculation of the PageRank for TDS took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for TDS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TDS took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for TDS took 3.62396240234375e-05s
Believability | Calculation of trust value for TDS took 7.3909759521484375e-06s
INFO | --- Analysis for tds took 5.512656211853027s
Availability | SPARQL endpoint availability check for TED Talks took 4.124641418457031e-05s
Availability | VoID file availability check for TED Talks took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for TED Talks took 0.6833939552307129s
Reputation | Calculation of the PageRank for TED Talks took 0.02094721794128418s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for TED Talks took 2.8371810913085938e-05s
Believability | Calculation of trust value for TED Talks took 6.198883056640625e-06s
INFO | --- Analysis for ted-talks took 3.4717085361480713s
Availability | SPARQL endpoint availability check for TEKORD took 4.267692565917969e-05s
Availability | VoID file availability check for TEKORD took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2680342197418213s
Reputation | Calculation of the PageRank for TEKORD took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0008590221405029297s
Interlinking | Calculation of Clustering coefficient for TEKORD took 5.0067901611328125e-05s
Believability | Calculation of trust value for TEKORD took 7.867813110351562e-06s
INFO | --- Analysis for tekord took 5.979638576507568s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 1.8155083656311035s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.25985240936279297s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00010442733764648438s
Believability | Calculation of trust value for Telegraphis Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for telegraphis took 8.249463558197021s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.124641418457031e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.2864644527435303s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 6.818771362304688e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 7.867813110351562e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 14.030888319015503s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 3.9577484130859375e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.28376126289367676s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.02086782455444336s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 2.7894973754882812e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.983121395111084s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2815995216369629s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.027287721633911133s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.001322031021118164s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 3.552436828613281e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for terminesp took 2.9467785358428955s
Availability | SPARQL endpoint availability check for Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Ontology took 0.30080366134643555s
Reputation | Calculation of the PageRank for Ontology took 0.02023935317993164s
Interlinking | Calculation of Degree of Connection for Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Ontology took 2.7418136596679688e-05s
Believability | Calculation of trust value for Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for Terrorist_attack took 3.180849313735962s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 5.125999450683594e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.2727682590484619s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020615577697753906s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 2.7179718017578125e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 7.152557373046875e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 2.399214744567871s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.124641418457031e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.2875401973724365s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 2.8133392333984375e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.152557373046875e-06s
INFO | --- Analysis for tesauro-materias-bupm took 2.9446756839752197s
Availability | SPARQL endpoint availability check for Teseo took 4.100799560546875e-05s
Availability | VoID file availability check for Teseo took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Teseo took 0.27856969833374023s
Reputation | Calculation of the PageRank for Teseo took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for Teseo took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Teseo took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Teseo took 3.0994415283203125e-05s
Believability | Calculation of trust value for Teseo took 6.9141387939453125e-06s
INFO | --- Analysis for teseo took 3.0629661083221436s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.124641418457031e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.27507781982421875s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 2.8133392333984375e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 6.67572021484375e-06s
INFO | --- Analysis for Tesla_Deaths took 3.3541135787963867s
Availability | SPARQL endpoint availability check for test took 5.7697296142578125e-05s
Availability | VoID file availability check for test took 0.0003311634063720703s
Completeness | Calculation of interlinking completeness for test took 0.28215789794921875s
Reputation | Calculation of the PageRank for test took 0.020771026611328125s
Interlinking | Calculation of Degree of Connection for test took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for test took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for test took 2.8848648071289062e-05s
Believability | Calculation of trust value for test took 5.4836273193359375e-06s
INFO | --- Analysis for test took 2.4298107624053955s
Availability | SPARQL endpoint availability check for Test took 4.172325134277344e-05s
Availability | VoID file availability check for Test took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for Test took 0.2870967388153076s
Reputation | Calculation of the PageRank for Test took 0.020211458206176758s
Interlinking | Calculation of Degree of Connection for Test took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Test took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Test took 2.8848648071289062e-05s
Believability | Calculation of trust value for Test took 8.58306884765625e-06s
INFO | --- Analysis for Test took 2.4235970973968506s
Availability | SPARQL endpoint availability check for test-svu took 20.208685398101807s
Availability | VoID file availability check for test-svu took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for test-svu took 0.2922978401184082s
Reputation | Calculation of the PageRank for test-svu took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for test-svu took 2.8133392333984375e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for test-svu took 2.8371810913085938e-05s
Believability | Calculation of trust value for test-svu took 6.9141387939453125e-06s
INFO | --- Analysis for test-svu took 52.64940023422241s
Availability | SPARQL endpoint availability check for Test took 6.079673767089844e-05s
Availability | VoID file availability check for Test took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Test took 0.276104211807251s
Reputation | Calculation of the PageRank for Test took 0.021060705184936523s
Interlinking | Calculation of Degree of Connection for Test took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Test took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Test took 2.765655517578125e-05s
Believability | Calculation of trust value for Test took 5.7220458984375e-06s
INFO | --- Analysis for Test_ took 2.8818047046661377s
Availability | SPARQL endpoint availability check for xxxxx took 261.03622579574585s
Availability | VoID file availability check for xxxxx took 0.0010149478912353516s
Completeness | Calculation of interlinking completeness for xxxxx took 0.7887835502624512s
Reputation | Calculation of the PageRank for xxxxx took 0.021311283111572266s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for xxxxx took 4.6253204345703125e-05s
Believability | Calculation of trust value for xxxxx took 7.152557373046875e-06s
INFO | --- Analysis for testee took 798.1726784706116s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.3392181396484375e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.7190334796905518s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.02094554901123047s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.504753112792969e-05s
Believability | Calculation of trust value for Texai Lexicon took 6.4373016357421875e-06s
INFO | --- Analysis for texai_lexicon took 7.12355899810791s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.3392181396484375e-05s
Availability | VoID file availability check for tharawat magazine took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.4631521701812744s
Reputation | Calculation of the PageRank for tharawat magazine took 0.02064681053161621s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010371208190917969s
Believability | Calculation of trust value for tharawat magazine took 6.67572021484375e-06s
INFO | --- Analysis for tharawat-magazine-com took 4.590771913528442s
Availability | SPARQL endpoint availability check for The CIARD RING took 4.100799560546875e-05s
Availability | VoID file availability check for The CIARD RING took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.2546045780181885s
Reputation | Calculation of the PageRank for The CIARD RING took 0.02064681053161621s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 2.9087066650390625e-05s
Believability | Calculation of trust value for The CIARD RING took 6.4373016357421875e-06s
INFO | --- Analysis for the-ciard-ring took 3.4822936058044434s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.18161416053771973s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.27176594734191895s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.266334533691406e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 6.9141387939453125e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 3.112159490585327s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.9079492092132568s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007603168487548828s
Extra | Recovery of all triples for The European Library Open Dataset took 1.4660437107086182s
Performance | Total latancy measurement for The European Library Open Dataset took 1.3583109378814697s
Amount of data | Number of triples check for The European Library Open Dataset took 30.244210243225098s
Versatility | Languages check for The European Library Open Dataset took 0.27768492698669434s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.201799869537354s
Interpretability | RDF structures check for The European Library Open Dataset took 0.41480040550231934s
Versatility | Serialization formats check for The European Library Open Dataset took 0.2685732841491699s
Availability | RDF dump link check for The European Library Open Dataset took 0.2340679168701172s
License | MR license check for The European Library Open Dataset took 0.7896051406860352s
License | HR license check for The European Library Open Dataset took 0.4072079658508301s
Amount of data | Number of property check for The European Library Open Dataset took 0.2740154266357422s
Understandability | Number of label check for The European Library Open Dataset took 3.0322177410125732s
Understandability | URI regex check for The European Library Open Dataset took 0.4974679946899414s
Understandability | Vocabs check for The European Library Open Dataset took 0.2396712303161621s
Verifiability | Authors check for The European Library Open Dataset took 0.23573660850524902s
Verifiability | Publishers check for The European Library Open Dataset took 0.23084235191345215s
Performance | Throughput check for The European Library Open Dataset took 11.959717988967896s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.081031799316406e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.21811199188232422s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.41266942024230957s
Interlinking | skos check for The European Library Open Dataset took 1.1449592113494873s
Interlinking | skos check for The European Library Open Dataset took 1.1354241371154785s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.2721226215362549s
Currency | Creation date check for The European Library Open Dataset took 3.006272315979004s
Currency | Modification date check for The European Library Open Dataset took 1.7526624202728271s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.51361703872681s
Interoperability | New vocabularies check for The European Library Open Dataset took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.22966623306274414s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 1.842466115951538s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.03079533576965332s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02859807014465332s
Consistency | Disjoint class check for The European Library Open Dataset took 0.2946457862854004s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.43158507347107s
Consistency | Misplaced classes for The European Library Open Dataset took 0.34210753440856934s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.711879014968872s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.1702723503112793s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.42679214477539s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.035216331481933594s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.3566625118255615s
Security | Sign check for The European Library Open Dataset took 0.24831175804138184s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 4.999264240264893s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.7503743171691895s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 7.176399230957031e-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 7.62939453125e-06s
INFO | --- Analysis for the-european-library-open-dataset took 404.1585171222687s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.04559803009033s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0007457733154296875s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.26062607765197754s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010776519775390625s
Believability | Calculation of trust value for The Eurostat Linked Data took 4.5299530029296875e-06s
INFO | --- Analysis for the-eurostat-linked-data took 243.57102847099304s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.1484832763671875e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.694343090057373s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.337860107421875e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.3909759521484375e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 6.109131336212158s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.220008850097656e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.2935199737548828s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.021306991577148438s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 8.416175842285156e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 7.3909759521484375e-06s
INFO | --- Analysis for the-living-lod-cloud took 43.503862142562866s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 4.029273986816406e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.26769161224365234s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020519495010375977s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 2.8133392333984375e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 7.152557373046875e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 3.461395740509033s
Availability | SPARQL endpoint availability check for The View From took 0.0749354362487793s
Availability | VoID file availability check for The View From took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for The View From took 0.26433348655700684s
Reputation | Calculation of the PageRank for The View From took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for The View From took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The View From took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for The View From took 7.82012939453125e-05s
Believability | Calculation of trust value for The View From took 7.152557373046875e-06s
INFO | --- Analysis for the-view-from took 2.593301773071289s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.55248785018921s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.25626277923583984s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0008087158203125s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.4332275390625e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 7.152557373046875e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.07401633262634s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.14466643333435s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0007658004760742188s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.7129693031311035s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020901918411254883s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007569789886474609s
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 7.867813110351562e-06s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 104.56782293319702s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.3392181396484375e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.2795524597167969s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010466575622558594s
Believability | Calculation of trust value for The Content Wrangler took 5.9604644775390625e-06s
INFO | --- Analysis for thecontentwrangler-com took 2.9129624366760254s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 7.152557373046875e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.2878999710083008s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02105545997619629s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.0994415283203125e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 8.106231689453125e-06s
INFO | --- Analysis for thesaurus-bncf took 3.8725411891937256s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.220008850097656e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.26448750495910645s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.2901763916015625e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 5.4836273193359375e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.442432403564453s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.16854262351989746s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.6980347633361816s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.02103137969970703s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.915496826171875e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 6.198883056640625e-06s
INFO | --- Analysis for thesaurus-w took 3.5581135749816895s
Availability | SPARQL endpoint availability check for theses.fr took 4.267692565917969e-05s
Availability | VoID file availability check for theses.fr took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for theses.fr took 0.26207923889160156s
Reputation | Calculation of the PageRank for theses.fr took 0.020847797393798828s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.8160552978515625e-05s
Believability | Calculation of trust value for theses.fr took 6.67572021484375e-06s
INFO | --- Analysis for thesesfr took 4.788714647293091s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.0531158447265625e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0002257823944091797s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.28936171531677246s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.552436828613281e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 5.0067901611328125e-06s
INFO | --- Analysis for Thinkphile took 2.4634523391723633s
Availability | SPARQL endpoint availability check for ThIST took 264.8920283317566s
Availability | VoID file availability check for ThIST took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for ThIST took 0.7106587886810303s
Reputation | Calculation of the PageRank for ThIST took 0.02101755142211914s
Interlinking | Calculation of Degree of Connection for ThIST took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for ThIST took 8.749961853027344e-05s
Believability | Calculation of trust value for ThIST took 7.62939453125e-06s
INFO | --- Analysis for thist took 560.5385353565216s
Availability | SPARQL endpoint availability check for TIP took 40.03560996055603s
Availability | VoID file availability check for TIP took 0.0003216266632080078s
Completeness | Calculation of interlinking completeness for TIP took 0.2785053253173828s
Reputation | Calculation of the PageRank for TIP took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for TIP took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011086463928222656s
Believability | Calculation of trust value for TIP took 7.62939453125e-06s
INFO | --- Analysis for tip took 104.81429839134216s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.696846008300781e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.2750084400177002s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 2.9087066650390625e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 8.344650268554688e-06s
INFO | --- Analysis for TOPMODEL took 22.198097229003906s
Availability | SPARQL endpoint availability check for Tourpedia took 4.029273986816406e-05s
Availability | VoID file availability check for Tourpedia took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.27864766120910645s
Reputation | Calculation of the PageRank for Tourpedia took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for Tourpedia took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Tourpedia took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 2.9325485229492188e-05s
Believability | Calculation of trust value for Tourpedia took 7.3909759521484375e-06s
INFO | --- Analysis for tourpedia took 4.6280763149261475s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.425481081008911s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.2630956172943115s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.2901763916015625e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.1444091796875e-05s
INFO | --- Analysis for TP-data took 8.022811889648438s
Availability | SPARQL endpoint availability check for True Parents Legacy Teaching Archive took 4.172325134277344e-05s
Availability | VoID file availability check for True Parents Legacy Teaching Archive took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for True Parents Legacy Teaching Archive took 0.2647740840911865s
Reputation | Calculation of the PageRank for True Parents Legacy Teaching Archive took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for True Parents Legacy Teaching Archive took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for True Parents Legacy Teaching Archive took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for True Parents Legacy Teaching Archive took 1.1205673217773438e-05s
Believability | Calculation of trust value for True Parents Legacy Teaching Archive took 6.9141387939453125e-06s
INFO | --- Analysis for tplegacy took 3.787965774536133s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 0.35074448585510254s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.2755587100982666s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 1.2874603271484375e-05s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for trackloaded took 6.748698472976685s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.8862428665161133s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.2665581703186035s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.021076440811157227s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.458427429199219e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 6.67572021484375e-06s
INFO | --- Analysis for traditional-korean-medicine took 3.9526021480560303s
Availability | SPARQL endpoint availability check for Traffic Scotland took 10.202439308166504s
Availability | VoID file availability check for Traffic Scotland took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.30329275131225586s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.0207674503326416s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.457069396972656e-05s
Believability | Calculation of trust value for Traffic Scotland took 4.291534423828125e-06s
INFO | --- Analysis for traffic-scotland took 12.757049798965454s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.20084381103515625s
Availability | VoID file availability check for Transparency International Linked Data took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.2944159507751465s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.020934581756591797s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00011038780212402344s
Believability | Calculation of trust value for Transparency International Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for transparency-linked-data took 2.6749372482299805s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.8769586086273193s
Availability | VoID file availability check for transport.data.gov.uk took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.292996883392334s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 8.988380432128906e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 6.198883056640625e-06s
INFO | --- Analysis for transport-data-gov-uk took 5.281333684921265s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 3.933906555175781e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.25872015953063965s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.020782470703125s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 2.8848648071289062e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 6.9141387939453125e-06s
INFO | --- Analysis for transport-openuplabs took 2.971608877182007s
Availability | SPARQL endpoint availability check for Trelios took 4.1961669921875e-05s
Availability | VoID file availability check for Trelios took 0.00038552284240722656s
Completeness | Calculation of interlinking completeness for Trelios took 0.2617003917694092s
Reputation | Calculation of the PageRank for Trelios took 0.0209500789642334s
Interlinking | Calculation of Degree of Connection for Trelios took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.3828277587890625e-05s
Believability | Calculation of trust value for Trelios took 6.9141387939453125e-06s
INFO | --- Analysis for Trelios took 2.416872024536133s
Availability | SPARQL endpoint availability check for Twarql took 10.553325891494751s
Availability | VoID file availability check for Twarql took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Twarql took 0.24093365669250488s
Reputation | Calculation of the PageRank for Twarql took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for Twarql took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.4849853515625e-05s
Believability | Calculation of trust value for Twarql took 6.198883056640625e-06s
INFO | --- Analysis for twarql took 12.997169494628906s
Availability | SPARQL endpoint availability check for TWC Data-gov took 4.482269287109375e-05s
Availability | VoID file availability check for TWC Data-gov took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.3044166564941406s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.021758079528808594s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0010290145874023438s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 4.553794860839844e-05s
Believability | Calculation of trust value for TWC Data-gov took 4.76837158203125e-06s
INFO | --- Analysis for twc-data-gov took 2.577760934829712s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 3.9577484130859375e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.2484743595123291s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.020499229431152344s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 3.123283386230469e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 9.298324584960938e-06s
INFO | --- Analysis for twc-demos took 2.967472553253174s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.17520499229431152s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.00033974647521972656s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.25336146354675293s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 3.719329833984375e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 5.0067901611328125e-06s
INFO | --- Analysis for twc-healthdata took 13.250454425811768s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 3.3026957511901855s
Availability | VoID file availability check for Instance Hub (all) took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.282320499420166s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 6.723403930664062e-05s
Believability | Calculation of trust value for Instance Hub (all) took 9.059906005859375e-06s
INFO | --- Analysis for twc-hub took 69.53893899917603s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.14881467819213867s
Availability | VoID file availability check for IEEE VIS Source Data took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.5270609855651855s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00010919570922851562s
Believability | Calculation of trust value for IEEE VIS Source Data took 2.2649765014648438e-05s
INFO | --- Analysis for twc-ieeevis took 103.47339725494385s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.9591064453125e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.26218724250793457s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 8.893013000488281e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 5.9604644775390625e-06s
INFO | --- Analysis for twc-logd took 2.5783145427703857s
Availability | SPARQL endpoint availability check for twc-opendap took 0.14939475059509277s
Availability | VoID file availability check for twc-opendap took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.2817342281341553s
Reputation | Calculation of the PageRank for twc-opendap took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 7.224082946777344e-05s
Believability | Calculation of trust value for twc-opendap took 7.3909759521484375e-06s
INFO | --- Analysis for twc-opendap took 154.9272243976593s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 6.079673767089844e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.7093982696533203s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.022017478942871094s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 2.9325485229492188e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 7.62939453125e-06s
INFO | --- Analysis for tweetskb took 3.9100489616394043s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 5.1021575927734375e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.2757904529571533s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 2.6941299438476562e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 9.059906005859375e-06s
INFO | --- Analysis for twitter-lids took 2.9536256790161133s
Availability | SPARQL endpoint availability check for typepad took 4.100799560546875e-05s
Availability | VoID file availability check for typepad took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for typepad took 0.2733266353607178s
Reputation | Calculation of the PageRank for typepad took 0.020447731018066406s
Interlinking | Calculation of Degree of Connection for typepad took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for typepad took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for typepad took 4.7206878662109375e-05s
Believability | Calculation of trust value for typepad took 8.58306884765625e-06s
INFO | --- Analysis for typepad took 3.04856276512146s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.942924976348877s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0003731250762939453s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.27769947052001953s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 3.6716461181640625e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 6.4373016357421875e-06s
INFO | --- Analysis for ub-mannheim-linked-data took 4.86368203163147s
Availability | SPARQL endpoint availability check for Uberblic.org took 0.12009835243225098s
Availability | VoID file availability check for Uberblic.org took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.28876256942749023s
Reputation | Calculation of the PageRank for Uberblic.org took 0.020694255828857422s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010657310485839844s
Believability | Calculation of trust value for Uberblic.org took 7.152557373046875e-06s
INFO | --- Analysis for uberblic took 2.9006502628326416s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.48413538932800293s
Availability | VoID file availability check for UDante in LiLa took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.2589282989501953s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.457069396972656e-05s
Believability | Calculation of trust value for UDante in LiLa took 9.059906005859375e-06s
INFO | --- Analysis for UDante took 3.988192319869995s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 1.0552668571472168s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.2698404788970947s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for ufo took 4.367685556411743s
Availability | SPARQL endpoint availability check for Uganda Disasters took 4.38690185546875e-05s
Availability | VoID file availability check for Uganda Disasters took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.2888307571411133s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 6.580352783203125e-05s
Believability | Calculation of trust value for Uganda Disasters took 6.9141387939453125e-06s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.5063929557800293s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.15152788162231445s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.27858448028564453s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 9.942054748535156e-05s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for uis-linked-data took 2.5889198780059814s
Availability | SPARQL endpoint availability check for UK Legislation took 7.796287536621094e-05s
Availability | VoID file availability check for UK Legislation took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.2632436752319336s
Reputation | Calculation of the PageRank for UK Legislation took 0.020812273025512695s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.749961853027344e-05s
Believability | Calculation of trust value for UK Legislation took 6.4373016357421875e-06s
INFO | --- Analysis for uk-legislation-api took 3.431767702102661s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.2438507080078125e-05s
Availability | VoID file availability check for UK Postcodes took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.2741878032684326s
Reputation | Calculation of the PageRank for UK Postcodes took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.53131103515625e-05s
Believability | Calculation of trust value for UK Postcodes took 7.3909759521484375e-06s
INFO | --- Analysis for uk-postcodes took 2.8577704429626465s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.172325134277344e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.2824742794036865s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.020144939422607422s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.000835418701171875s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00013208389282226562s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 7.152557373046875e-06s
INFO | --- Analysis for umbel took 5.391580581665039s
Availability | SPARQL endpoint availability check for UMTHES took 4.1961669921875e-05s
Availability | VoID file availability check for UMTHES took 0.0003402233123779297s
Completeness | Calculation of interlinking completeness for UMTHES took 0.2749137878417969s
Reputation | Calculation of the PageRank for UMTHES took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for UMTHES took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UMTHES took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.029273986816406e-05s
Believability | Calculation of trust value for UMTHES took 5.0067901611328125e-06s
INFO | --- Analysis for umthes took 3.7844696044921875s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.7685561180114746s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0008437633514404297s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.2801656723022461s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.020842790603637695s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0009067058563232422s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.218650817871094e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 5.0067901611328125e-06s
INFO | --- Analysis for un-hazardous-numbers took 33.11353826522827s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 5.7220458984375e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.27784204483032227s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 2.6702880859375e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for unesco-thesaurus took 3.003366470336914s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.2617661952972412s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020261526107788086s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 2.8848648071289062e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for unescothes took 3.026717185974121s
Availability | SPARQL endpoint availability check for UniProt took 1.5550968647003174s
Availability | VoID file availability check for UniProt took 0.0008254051208496094s
Extra | Recovery of all triples for UniProt took 83.73803877830505s
Performance | Total latancy measurement for UniProt took 2.706165313720703s
Amount of data | Number of triples check for UniProt took 0.15794682502746582s
Interoperability | New terms check for UniProt took 1.3813395500183105s
Versatility | Languages check for UniProt took 300.07881355285645s
Interpretability | Number of blank nodes check for UniProt took 0.7527859210968018s
Interpretability | RDF structures check for UniProt took 0.15872597694396973s
Versatility | Serialization formats check for UniProt took 0.0975189208984375s
Availability | RDF dump link check for UniProt took 0.08270382881164551s
License | MR license check for UniProt took 0.11542868614196777s
License | HR license check for UniProt took 300.104332447052s
Amount of data | Number of property check for UniProt took 0.16819262504577637s
Understandability | Number of label check for UniProt took 41.000996589660645s
Understandability | URI regex check for UniProt took 0.1826157569885254s
Understandability | Vocabs check for UniProt took 0.0914452075958252s
Verifiability | Authors check for UniProt took 0.12990474700927734s
Verifiability | Publishers check for UniProt took 0.11713457107543945s
Performance | Throughput check for UniProt took 15.85711932182312s
Amount of data | Check the number of entities for UniProt took 7.605552673339844e-05s
Verifiability | Contribs. check for UniProt took 0.10172772407531738s
Interlinking | sameAs chians check for UniProt took 0.1523149013519287s
Interlinking | skos check for UniProt took 0.15906405448913574s
Interlinking | skos check for UniProt took 0.21498703956604004s
Timeliness | dataset update frequency check for UniProt took 0.09660911560058594s
Currency | Creation date check for UniProt took 0.2884366512298584s
Currency | Modification date check for UniProt took 0.20041370391845703s
Rep.Conc. | URIs length for UniProt took 176.07704186439514s
Interoperability | New vocabularies check for UniProt took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.09103775024414062s
Accuracy | Check Functional Property for UniProt took 0.09134936332702637s
Accuracy | Check Inverse Functional Property for UniProt took 0.09962129592895508s
Accuracy | Check Empty annotation labels for UniProt took 22.845826864242554s
Accuracy | Check White space in annotation for UniProt took 2.518662214279175s
Accuracy | Check Datatype consistency for UniProt took 7.40445613861084s
Consistency | Disjoint class check for UniProt took 0.09382224082946777s
Consistency | Check Misplaced properties for UniProt took 11.051777601242065s
Consistency | Check Ontology hijacking for UniProt took 25.170990705490112s
Consistency | Check Invalid usage of undefined classes for UniProt took 19431.941490888596s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.647681474685669s
Conciseness | Check Extensional conciseness for UniProt took 2.7129874229431152s
Conciseness | Check Intensional conciseness for UniProt took 0.122894287109375s
Security | Sign check for UniProt took 0.1734778881072998s
Availability | Check URIs Dereferenciability for UniProt took 5.06132173538208s
Completeness | Calculation of interlinking completeness for UniProt took 1.5931434631347656s
Reputation | Calculation of the PageRank for UniProt took 0.022131919860839844s
Interlinking | Calculation of Degree of Connection for UniProt took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 2.384185791015625e-06s
Believability | Calculation of trust value for UniProt took 8.106231689453125e-06s
INFO | --- Analysis for UniProt took 20892.439387083054s
Availability | SPARQL endpoint availability check for UniProt took 1.7107634544372559s
Availability | VoID file availability check for UniProt took 0.0006186962127685547s
Extra | Recovery of all triples for UniProt took 83.74661755561829s
Performance | Total latancy measurement for UniProt took 3.254998207092285s
Amount of data | Number of triples check for UniProt took 0.3448214530944824s
Versatility | Languages check for UniProt took 300.25381875038147s
Interpretability | Number of blank nodes check for UniProt took 0.7908034324645996s
Security | Check HTTPS for UniProt took 1.592665672302246s
Interpretability | RDF structures check for UniProt took 0.17811250686645508s
Versatility | Serialization formats check for UniProt took 0.18326783180236816s
Availability | RDF dump link check for UniProt took 0.1676180362701416s
License | MR license check for UniProt took 0.1810004711151123s
License | HR license check for UniProt took 0.1754930019378662s
Amount of data | Number of property check for UniProt took 0.18778204917907715s
Understandability | Number of label check for UniProt took 0.1859877109527588s
Understandability | URI regex check for UniProt took 0.3463473320007324s
Understandability | Vocabs check for UniProt took 0.1670546531677246s
Verifiability | Authors check for UniProt took 0.1691889762878418s
Verifiability | Publishers check for UniProt took 0.15586161613464355s
Performance | Throughput check for UniProt took 19.610206604003906s
Amount of data | Check the number of entities for UniProt took 0.00018668174743652344s
Verifiability | Contribs. check for UniProt took 0.18265128135681152s
Interlinking | sameAs chians check for UniProt took 0.1796736717224121s
Interlinking | skos check for UniProt took 0.19136428833007812s
Interlinking | skos check for UniProt took 0.1435542106628418s
Timeliness | dataset update frequency check for UniProt took 0.18543529510498047s
Currency | Creation date check for UniProt took 0.3648200035095215s
Currency | Modification date check for UniProt took 0.3511967658996582s
Rep.Conc. | URIs length for UniProt took 178.62713027000427s
Interoperability | New vocabularies check for UniProt took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.17336368560791016s
Accuracy | Check Datatype consistency for UniProt took 7.349614381790161s
Consistency | Disjoint class check for UniProt took 0.17179274559020996s
Consistency | Check Ontology hijacking for UniProt took 0.18014192581176758s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.6002614498138428s
Conciseness | Check Extensional conciseness for UniProt took 2.7193753719329834s
Security | Sign check for UniProt took 0.170762300491333s
Availability | Check URIs Dereferenciability for UniProt took 4.6124866008758545s
Completeness | Calculation of interlinking completeness for UniProt took 0.8309109210968018s
Reputation | Calculation of the PageRank for UniProt took 0.023401260375976562s
Interlinking | Calculation of Degree of Connection for UniProt took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for UniProt took 5.7220458984375e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 9.5367431640625e-07s
Believability | Calculation of trust value for UniProt took 7.62939453125e-06s
INFO | --- Analysis for uniprot took 1145.851796388626s
Availability | SPARQL endpoint availability check for UniProt citations took 4.315376281738281e-05s
Availability | VoID file availability check for UniProt citations took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.7085525989532471s
Reputation | Calculation of the PageRank for UniProt citations took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 2.9802322387695312e-05s
Believability | Calculation of trust value for UniProt citations took 7.3909759521484375e-06s
INFO | --- Analysis for uniprot-citations took 5.6105146408081055s
Availability | SPARQL endpoint availability check for UniProt databases took 4.076957702636719e-05s
Availability | VoID file availability check for UniProt databases took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.2635366916656494s
Reputation | Calculation of the PageRank for UniProt databases took 0.0208587646484375s
Interlinking | Calculation of Degree of Connection for UniProt databases took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 2.956390380859375e-05s
Believability | Calculation of trust value for UniProt databases took 5.9604644775390625e-06s
INFO | --- Analysis for uniprot-databases took 3.818573474884033s
Availability | SPARQL endpoint availability check for uniprot-metadata took 4.124641418457031e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.27745699882507324s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020696401596069336s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 5.91278076171875e-05s
Believability | Calculation of trust value for uniprot-metadata took 6.67572021484375e-06s
INFO | --- Analysis for uniprot-metadata took 3.836465835571289s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 5.2928924560546875e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.268383264541626s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 2.9802322387695312e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 5.7220458984375e-06s
INFO | --- Analysis for uniprot-taxonomy took 3.0090179443359375s
Availability | SPARQL endpoint availability check for UniProt UniParc took 5.221366882324219e-05s
Availability | VoID file availability check for UniProt UniParc took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.29004979133605957s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.0208437442779541s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 2.9802322387695312e-05s
Believability | Calculation of trust value for UniProt UniParc took 6.67572021484375e-06s
INFO | --- Analysis for uniprot-uniparc took 3.001251220703125s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 6.723403930664062e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.28723788261413574s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 3.0279159545898438e-05s
Believability | Calculation of trust value for UniProt UniPathway took 5.245208740234375e-06s
INFO | --- Analysis for uniprot-unipathway took 3.4072282314300537s
Availability | SPARQL endpoint availability check for UniProtKB took 1.3400397300720215s
Availability | VoID file availability check for UniProtKB took 0.0005364418029785156s
Extra | Recovery of all triples for UniProtKB took 74.98445320129395s
Performance | Total latancy measurement for UniProtKB took 3.409391403198242s
Amount of data | Number of triples check for UniProtKB took 0.19042658805847168s
Interoperability | New terms check for UniProtKB took 1.3677654266357422s
Versatility | Languages check for UniProtKB took 300.1576027870178s
Interpretability | Number of blank nodes check for UniProtKB took 0.4761531352996826s
Interpretability | RDF structures check for UniProtKB took 0.4435269832611084s
Versatility | Serialization formats check for UniProtKB took 0.16060185432434082s
Availability | RDF dump link check for UniProtKB took 0.2115464210510254s
License | MR license check for UniProtKB took 0.16620707511901855s
License | HR license check for UniProtKB took 300.076030254364s
Amount of data | Number of property check for UniProtKB took 0.17375659942626953s
Understandability | Number of label check for UniProtKB took 48.88390922546387s
Understandability | URI regex check for UniProtKB took 0.3175196647644043s
Understandability | Vocabs check for UniProtKB took 0.13932371139526367s
Verifiability | Authors check for UniProtKB took 0.13449907302856445s
Verifiability | Publishers check for UniProtKB took 0.10897278785705566s
Performance | Throughput check for UniProtKB took 17.876792192459106s
Amount of data | Check the number of entities for UniProtKB took 7.152557373046875e-05s
Verifiability | Contribs. check for UniProtKB took 0.1026759147644043s
Interlinking | sameAs chians check for UniProtKB took 0.1277306079864502s
Interlinking | skos check for UniProtKB took 0.19400238990783691s
Interlinking | skos check for UniProtKB took 0.07450985908508301s
Timeliness | dataset update frequency check for UniProtKB took 0.08324193954467773s
Currency | Creation date check for UniProtKB took 0.24616312980651855s
Currency | Modification date check for UniProtKB took 0.19012999534606934s
Rep.Conc. | URIs length for UniProtKB took 175.58624958992004s
Interoperability | New vocabularies check for UniProtKB took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.10610365867614746s
Accuracy | Check Functional Property for UniProtKB took 0.09215736389160156s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.1334223747253418s
Accuracy | Check Empty annotation labels for UniProtKB took 25.6164391040802s
Accuracy | Check White space in annotation for UniProtKB took 2.564622640609741s
Accuracy | Check Datatype consistency for UniProtKB took 7.331755638122559s
Consistency | Disjoint class check for UniProtKB took 0.09351706504821777s
Consistency | Check Misplaced properties for UniProtKB took 11.588580131530762s
Consistency | Check Ontology hijacking for UniProtKB took 27.494789123535156s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 19719.91610455513s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 2.189502716064453s
Conciseness | Check Extensional conciseness for UniProtKB took 2.694671154022217s
Conciseness | Check Intensional conciseness for UniProtKB took 0.4621000289916992s
Security | Sign check for UniProtKB took 0.5078959465026855s
Availability | Check URIs Dereferenciability for UniProtKB took 4.976003408432007s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.7181186676025391s
Reputation | Calculation of the PageRank for UniProtKB took 0.021371841430664062s
Interlinking | Calculation of Degree of Connection for UniProtKB took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 6.866455078125e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 1.9073486328125e-06s
Believability | Calculation of trust value for UniProtKB took 7.867813110351562e-06s
INFO | --- Analysis for uniprotkb took 21141.06109714508s
Availability | SPARQL endpoint availability check for UniProt UniRef took 7.653236389160156e-05s
Availability | VoID file availability check for UniProt UniRef took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.30144476890563965s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 2.9325485229492188e-05s
Believability | Calculation of trust value for UniProt UniRef took 1.5735626220703125e-05s
INFO | --- Analysis for uniref took 3.0108325481414795s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 4.0531158447265625e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0002961158752441406s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.2706003189086914s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 2.8371810913085938e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 7.3909759521484375e-06s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 3.0651676654815674s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 5.364418029785156e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.25977396965026855s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.020174264907836914s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 2.7418136596679688e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 7.3909759521484375e-06s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 3.004556655883789s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 0.00010418891906738281s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.2701706886291504s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.021218538284301758s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.423859596252441s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 5.340576171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.26779985427856445s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 3.852879047393799s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 4.076957702636719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.27649426460266113s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.415101528167725s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.26968884468078613s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.241214752197266s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.3168296813964844s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.21386981010437s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0007507801055908203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.28006696701049805s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.310825824737549s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.3066411018371582s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 3.9790682792663574s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 5.0067901611328125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.2761049270629883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.02091240882873535s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 4.839897155761719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.194621562957764s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 5.340576171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.278883695602417s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020485639572143555s
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.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.183638572692871s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.26878809928894043s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.124688625335693s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.2808094024658203s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.166752099990845s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.2727475166320801s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.02077651023864746s
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.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.604453802108765s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.2638695240020752s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.975400447845459s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.2808413505554199s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.021027326583862305s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.286635398864746s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 5.173683166503906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.27625012397766113s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.025775432586669922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.14367389678955s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 5.340576171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.3911130428314209s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0008814334869384766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.317843198776245s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.2901928424835205s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.092934846878052s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 5.2928924560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.2800281047821045s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.10855770111084s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.2789285182952881s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.021063804626464844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0008363723754882812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.31948733329773s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.27509093284606934s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020530223846435547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 3.881134510040283s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.2513253688812256s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 13.019627094268799s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0008542537689208984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.2617452144622803s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.222388982772827s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.29211926460266113s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.229438781738281s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.262514591217041s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 3.6794424057006836s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 6.937980651855469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.27446794509887695s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.02060246467590332s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 3.660659074783325s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0007319450378417969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.276386022567749s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.02057027816772461s
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.0007374286651611328s
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 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 3.776815176010132s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.27225518226623535s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-greek took 3.700608730316162s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.28262877464294434s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.268054962158203s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.2648310661315918s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.02027153968811035s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.250946283340454s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 5.1975250244140625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.28371477127075195s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 3.875284433364868s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.3378570079803467s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.310078382492065s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 7.200241088867188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.26430320739746094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-irish took 4.375553846359253s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.2573130130767822s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.244002103805542s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0008065700531005859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.27030086517333984s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.266305685043335s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.76837158203125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.00067138671875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.26859569549560547s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 3.763871431350708s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.26207900047302246s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020097970962524414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.328732967376709s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 5.340576171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.26850247383117676s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 4.0787506103515625s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.25362086296081543s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02057480812072754s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.147680044174194s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.27875328063964844s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.014549255371094s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0008177757263183594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.3084738254547119s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.02074432373046875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.291594743728638s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.2861135005950928s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.00074005126953125s
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 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 12.99546766281128s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.26455116271972656s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.232813835144043s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.7699432373046875s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-persian took 4.1873087882995605s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.30820608139038086s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.224331140518188s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 5.340576171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.2769920825958252s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0008370876312255859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 12.843985319137573s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0007441043853759766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.3441131114959717s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.696846008300781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.158108472824097s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0007677078247070312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.28513431549072266s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.36714482307434s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.26750946044921875s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.02030014991760254s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.269041776657104s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 5.555152893066406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.2584102153778076s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.02055954933166504s
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.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.251571893692017s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.25889134407043457s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 3.536130905151367s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0008482933044433594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.275409460067749s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.020967483520507812s
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.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.147044897079468s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.27642178535461426s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.670737028121948s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 6.0558319091796875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0008018016815185547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.28740501403808594s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.021836280822753906s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0009427070617675781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.863739013671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.7642974853515625e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.272431373596191s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.029273986816406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.26867151260375977s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020446062088012695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.276515245437622s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.2801854610443115s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.552436828613281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.665343523025513s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.27004265785217285s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.02036881446838379s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.122782707214355s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.27843785285949707s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 3.964975118637085s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.27776384353637695s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 3.5384929180145264s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.27040767669677734s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.290473937988281s
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.0006649494171142578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.2714381217956543s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.171664953231812s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.286175012588501s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.02045750617980957s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.234675407409668s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.24895906448364258s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.280861854553223s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.076957702636719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.2652769088745117s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.020605802536010742s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.217597484588623s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.2907092571258545s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.322763442993164s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.100799560546875e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.25830888748168945s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.437301635742188e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.1920928955078125e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.629655361175537s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 3.933906555175781e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.29755640029907227s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 2.6702880859375e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 6.4373016357421875e-06s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 3.0494158267974854s
Availability | SPARQL endpoint availability check for University of Bristol took 4.00543212890625e-05s
Availability | VoID file availability check for University of Bristol took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.2910459041595459s
Reputation | Calculation of the PageRank for University of Bristol took 0.020514249801635742s
Interlinking | Calculation of Degree of Connection for University of Bristol took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 2.5987625122070312e-05s
Believability | Calculation of trust value for University of Bristol took 7.152557373046875e-06s
INFO | --- Analysis for university-of-bristol took 3.005352020263672s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.124641418457031e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.2694056034088135s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 4.696846008300781e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 6.9141387939453125e-06s
INFO | --- Analysis for university-plymouth-reading-lists took 3.0563642978668213s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.100799560546875e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.28058648109436035s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.1948089599609375e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 6.67572021484375e-06s
INFO | --- Analysis for university-sussex-reading-lists took 2.826246976852417s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 4.725168466567993s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.2890639305114746s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.176399230957031e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 6.67572021484375e-06s
INFO | --- Analysis for unodc took 12.41685438156128s
Availability | SPARQL endpoint availability check for Super Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Super Ontology took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2828066349029541s
Reputation | Calculation of the PageRank for Super Ontology took 0.020374298095703125s
Interlinking | Calculation of Degree of Connection for Super Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 7.534027099609375e-05s
Believability | Calculation of trust value for Super Ontology took 7.152557373046875e-06s
INFO | --- Analysis for upper-ontology took 3.8211557865142822s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 1.522404670715332s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.27716994285583496s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.020128488540649414s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 2.9325485229492188e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for Upper_Ontology took 4.825908422470093s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 4.076957702636719e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.2785193920135498s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 2.7418136596679688e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 5.9604644775390625e-06s
INFO | --- Analysis for Urban_Atlas_ took 2.3995542526245117s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.5795655250549316s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0002410411834716797s
Extra | Recovery of all triples for Urban Atlas dataset @PSNC took 27.45966148376465s
Performance | Total latancy measurement for Urban Atlas dataset @PSNC took 0.9524722099304199s
Amount of data | Number of triples check for Urban Atlas dataset @PSNC took 9.550437211990356s
Interoperability | New terms check for Urban Atlas dataset @PSNC took 13.505497932434082s
Versatility | Languages check for Urban Atlas dataset @PSNC took 6.358419418334961s
Interpretability | Number of blank nodes check for Urban Atlas dataset @PSNC took 2.9590537548065186s
Interpretability | RDF structures check for Urban Atlas dataset @PSNC took 0.2604086399078369s
Versatility | Serialization formats check for Urban Atlas dataset @PSNC took 8.26242184638977s
Availability | RDF dump link check for Urban Atlas dataset @PSNC took 0.2776455879211426s
License | MR license check for Urban Atlas dataset @PSNC took 0.568129301071167s
License | HR license check for Urban Atlas dataset @PSNC took 11.628965377807617s
Amount of data | Number of property check for Urban Atlas dataset @PSNC took 0.20204663276672363s
Understandability | Number of label check for Urban Atlas dataset @PSNC took 2.78432559967041s
Understandability | URI regex check for Urban Atlas dataset @PSNC took 0.6698026657104492s
Understandability | Vocabs check for Urban Atlas dataset @PSNC took 0.3941795825958252s
Verifiability | Authors check for Urban Atlas dataset @PSNC took 0.2014763355255127s
Verifiability | Publishers check for Urban Atlas dataset @PSNC took 0.25888919830322266s
Performance | Throughput check for Urban Atlas dataset @PSNC took 11.508702039718628s
Amount of data | Check the number of entities for Urban Atlas dataset @PSNC took 0.00010180473327636719s
Verifiability | Contribs. check for Urban Atlas dataset @PSNC took 0.20220160484313965s
Interlinking | sameAs chians check for Urban Atlas dataset @PSNC took 0.22215557098388672s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.46507811546325684s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.4607555866241455s
Timeliness | dataset update frequency check for Urban Atlas dataset @PSNC took 5.530050992965698s
Currency | Creation date check for Urban Atlas dataset @PSNC took 0.5098068714141846s
Currency | Modification date check for Urban Atlas dataset @PSNC took 0.22211861610412598s
Rep.Conc. | URIs length for Urban Atlas dataset @PSNC took 105.5627965927124s
Interoperability | New vocabularies check for Urban Atlas dataset @PSNC took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Urban Atlas dataset @PSNC took 0.2131962776184082s
Accuracy | Check Functional Property for Urban Atlas dataset @PSNC took 0.32350611686706543s
Accuracy | Check Inverse Functional Property for Urban Atlas dataset @PSNC took 0.34076380729675293s
Accuracy | Check Empty annotation labels for Urban Atlas dataset @PSNC took 37.053016901016235s
Accuracy | Check White space in annotation for Urban Atlas dataset @PSNC took 2.679966688156128s
Consistency | Disjoint class check for Urban Atlas dataset @PSNC took 0.21056771278381348s
Consistency | Check Misplaced properties for Urban Atlas dataset @PSNC took 26.80766463279724s
Consistency | Misplaced classes for Urban Atlas dataset @PSNC took 0.36327409744262695s
Consistency | Check Ontology hijacking for Urban Atlas dataset @PSNC took 42.71557116508484s
Consistency | Check Invalid usage of undefined properties for Urban Atlas dataset @PSNC took 22.17091655731201s
Conciseness | Check Extensional conciseness for Urban Atlas dataset @PSNC took 0.00016570091247558594s
Conciseness | Check Intensional conciseness for Urban Atlas dataset @PSNC took 0.5885040760040283s
Security | Sign check for Urban Atlas dataset @PSNC took 0.7964296340942383s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.3074800968170166s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 3.361701965332031e-05s
Interoperability | Check the re-using of existing vocabs for Urban Atlas dataset @PSNC took 1.1920928955078125e-06s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Urban_Atlas_Dataset took 1162.7199459075928s
Availability | SPARQL endpoint availability check for URIBurner took 127.55702924728394s
Availability | VoID file availability check for URIBurner took 0.0006976127624511719s
Extra | Recovery of all triples for URIBurner took 201.16839838027954s
Amount of data | Number of triples check for URIBurner took 10.097211599349976s
Versatility | Languages check for URIBurner took 10.091517210006714s
Interpretability | Number of blank nodes check for URIBurner took 10.007209062576294s
Interpretability | RDF structures check for URIBurner took 9.998519897460938s
Versatility | Serialization formats check for URIBurner took 10.005527257919312s
Availability | RDF dump link check for URIBurner took 23.032899618148804s
License | MR license check for URIBurner took 10.070550680160522s
License | HR license check for URIBurner took 10.103158950805664s
Amount of data | Number of property check for URIBurner took 10.09337306022644s
Understandability | Number of label check for URIBurner took 10.003041744232178s
Understandability | URI regex check for URIBurner took 20.1972918510437s
Understandability | Vocabs check for URIBurner took 18.89555859565735s
Verifiability | Authors check for URIBurner took 10.01080846786499s
Verifiability | Publishers check for URIBurner took 22.56347942352295s
Amount of data | Check the number of entities for URIBurner took 8.58306884765625e-05s
Verifiability | Contribs. check for URIBurner took 10.099143028259277s
Interlinking | sameAs chians check for URIBurner took 10.098713874816895s
Interlinking | skos check for URIBurner took 29.28928565979004s
Interlinking | skos check for URIBurner took 10.009710788726807s
Timeliness | dataset update frequency check for URIBurner took 9.996501207351685s
Currency | Creation date check for URIBurner took 20.0098717212677s
Currency | Modification date check for URIBurner took 20.097222089767456s
Rep.Conc. | URIs length for URIBurner took 20.198994636535645s
Interoperability | New vocabularies check for URIBurner took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for URIBurner took 10.095165491104126s
Consistency | Disjoint class check for URIBurner took 10.093778848648071s
Consistency | Check Ontology hijacking for URIBurner took 10.100770950317383s
Consistency | Check Invalid usage of undefined properties for URIBurner took 11.246653079986572s
Conciseness | Check Extensional conciseness for URIBurner took 0.00014209747314453125s
Security | Sign check for URIBurner took 10.000713348388672s
Completeness | Calculation of interlinking completeness for URIBurner took 1.3198494911193848s
Reputation | Calculation of the PageRank for URIBurner took 0.021061182022094727s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00010895729064941406s
Interoperability | Check the re-using of existing vocabs for URIBurner took 7.152557373046875e-07s
Believability | Calculation of trust value for URIBurner took 7.152557373046875e-06s
INFO | --- Analysis for uriburner took 1176.9763083457947s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.982948303222656e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.26355409622192383s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02084970474243164s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.8133392333984375e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 6.9141387939453125e-06s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 4.587997674942017s
Availability | SPARQL endpoint availability check for Legija Stranaca took 4.100799560546875e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.26807332038879395s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.020534753799438477s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 2.9087066650390625e-05s
Believability | Calculation of trust value for Legija Stranaca took 7.152557373046875e-06s
INFO | --- Analysis for Uros_Legija_Susa took 4.5321080684661865s
Availability | SPARQL endpoint availability check for Legija took 4.220008850097656e-05s
Availability | VoID file availability check for Legija took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Legija took 0.27039361000061035s
Reputation | Calculation of the PageRank for Legija took 0.02093815803527832s
Interlinking | Calculation of Degree of Connection for Legija took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Legija took 3.123283386230469e-05s
Believability | Calculation of trust value for Legija took 6.67572021484375e-06s
INFO | --- Analysis for Uros_Susa took 2.4288783073425293s
Availability | SPARQL endpoint availability check for US Political Violence took 4.220008850097656e-05s
Availability | VoID file availability check for US Political Violence took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.6939582824707031s
Reputation | Calculation of the PageRank for US Political Violence took 0.020680904388427734s
Interlinking | Calculation of Degree of Connection for US Political Violence took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 3.0040740966796875e-05s
Believability | Calculation of trust value for US Political Violence took 7.867813110351562e-06s
INFO | --- Analysis for us-political-violence took 5.116164922714233s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.0585026741027832s
Availability | VoID file availability check for USAGE review corpus took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.2578239440917969s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.147125244140625e-05s
Believability | Calculation of trust value for USAGE review corpus took 6.198883056640625e-06s
INFO | --- Analysis for usage-review-corpus took 2.4440410137176514s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 3.4691884517669678s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.2689065933227539s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.020975351333618164s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.843971252441406e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.049041748046875e-05s
INFO | --- Analysis for utpl-lod took 8.944847822189331s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 4.2438507080078125e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.28603076934814453s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 2.9802322387695312e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 7.3909759521484375e-06s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 2.9808363914489746s
Availability | SPARQL endpoint availability check for terrorist attack took 4.291534423828125e-05s
Availability | VoID file availability check for terrorist attack took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.29105424880981445s
Reputation | Calculation of the PageRank for terrorist attack took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for terrorist attack took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 2.6702880859375e-05s
Believability | Calculation of trust value for terrorist attack took 7.152557373046875e-06s
INFO | --- Analysis for varsha took 4.082761526107788s
Availability | SPARQL endpoint availability check for VA took 4.124641418457031e-05s
Availability | VoID file availability check for VA took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for VA took 0.26074767112731934s
Reputation | Calculation of the PageRank for VA took 0.020307064056396484s
Interlinking | Calculation of Degree of Connection for VA took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for VA took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for VA took 2.9087066650390625e-05s
Believability | Calculation of trust value for VA took 1.049041748046875e-05s
INFO | --- Analysis for Vehicule_Autonome took 2.7087395191192627s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.3875577449798584s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.24727320671081543s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.020364046096801758s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 4.3392181396484375e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for VelezIndexTotiusArtis took 3.809422731399536s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 1.0031228065490723s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.2675309181213379s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.225440979003906e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 7.867813110351562e-06s
INFO | --- Analysis for verrijktkoninkrijk took 9.807861089706421s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 7.176399230957031e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.27768445014953613s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00016689300537109375s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 6.198883056640625e-06s
INFO | --- Analysis for viaf took 3.0978007316589355s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 4.029273986816406e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.27823734283447266s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 5.9604644775390625e-06s
INFO | --- Analysis for vias-publicas-zaragoza took 2.929291009902954s
Availability | SPARQL endpoint availability check for Vihar Exports took 4.124641418457031e-05s
Availability | VoID file availability check for Vihar Exports took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.27150559425354004s
Reputation | Calculation of the PageRank for Vihar Exports took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 2.7418136596679688e-05s
Believability | Calculation of trust value for Vihar Exports took 7.3909759521484375e-06s
INFO | --- Analysis for Vihar_Exports took 2.492265224456787s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 4.124641418457031e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.2744135856628418s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 2.86102294921875e-05s
Believability | Calculation of trust value for vimeo.videoobject took 6.9141387939453125e-06s
INFO | --- Analysis for vimeo_videoobject took 2.9821691513061523s
Availability | SPARQL endpoint availability check for VIVO took 4.9591064453125e-05s
Availability | VoID file availability check for VIVO took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for VIVO took 0.2675201892852783s
Reputation | Calculation of the PageRank for VIVO took 0.020247697830200195s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.4849853515625e-05s
Believability | Calculation of trust value for VIVO took 6.67572021484375e-06s
INFO | --- Analysis for vivo took 4.994290590286255s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.2438507080078125e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.26523351669311523s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.021190881729125977s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0011026859283447266s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 0.00010347366333007812s
Believability | Calculation of trust value for VIVO Cornell took 5.9604644775390625e-06s
INFO | --- Analysis for vivo-cornell-university took 5.905677795410156s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 4.124641418457031e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.2709531784057617s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 2.765655517578125e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 7.152557373046875e-06s
INFO | --- Analysis for vivo-cu-boulder took 3.0016353130340576s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.1961669921875e-05s
Availability | VoID file availability check for VIVO Indiana took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2704639434814453s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 7.724761962890625e-05s
Believability | Calculation of trust value for VIVO Indiana took 6.67572021484375e-06s
INFO | --- Analysis for vivo-indiana-university took 2.9724020957946777s
Availability | SPARQL endpoint availability check for VIVO Ponce took 4.1484832763671875e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.2638533115386963s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020352840423583984s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.0279159545898438e-05s
Believability | Calculation of trust value for VIVO Ponce took 6.9141387939453125e-06s
INFO | --- Analysis for vivo-ponce took 2.90240740776062s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 4.2438507080078125e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.24868297576904297s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.457069396972656e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 7.867813110351562e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 2.875149965286255s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0011296272277832031s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.27904605865478516s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.02092742919921875s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.393692016601562e-05s
Believability | Calculation of trust value for VIVO University of Florida took 8.821487426757812e-06s
INFO | --- Analysis for vivo-university-of-florida took 2.542013645172119s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 4.5299530029296875e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.29893970489501953s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.022062063217163086s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0010986328125s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 4.5299530029296875e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 1.9073486328125e-05s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.9942691326141357s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 7.128715515136719e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.28185439109802246s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.838539123535156e-05s
Believability | Calculation of trust value for VIVO WUSTL took 8.58306884765625e-06s
INFO | --- Analysis for vivo-wustl took 3.049290657043457s
Availability | SPARQL endpoint availability check for vivo2doi took 4.1961669921875e-05s
Availability | VoID file availability check for vivo2doi took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.3053627014160156s
Reputation | Calculation of the PageRank for vivo2doi took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.100799560546875e-05s
Believability | Calculation of trust value for vivo2doi took 5.7220458984375e-06s
INFO | --- Analysis for vivo2doi took 23.78817844390869s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 4.172325134277344e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.3853757381439209s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.651878356933594e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 6.4373016357421875e-06s
INFO | --- Analysis for vu-wordnet took 12.566964387893677s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.8822381496429443s
Availability | VoID file availability check for vulnerapedia took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.2854154109954834s
Reputation | Calculation of the PageRank for vulnerapedia took 0.020616531372070312s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 7.128715515136719e-05s
Believability | Calculation of trust value for vulnerapedia took 8.344650268554688e-06s
INFO | --- Analysis for vulnerapedia took 3.8113715648651123s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 4.363059997558594e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.287250280380249s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0008404254913330078s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1205673217773438e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 7.152557373046875e-06s
INFO | --- Analysis for VVASIAK took 2.4535398483276367s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 4.506111145019531e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.27770328521728516s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 2.6464462280273438e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 7.62939453125e-06s
INFO | --- Analysis for Vyvasta took 2.476649761199951s
Availability | SPARQL endpoint availability check for W3C took 4.172325134277344e-05s
Availability | VoID file availability check for W3C took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for W3C took 0.24742579460144043s
Reputation | Calculation of the PageRank for W3C took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for W3C took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for W3C took 0.00013399124145507812s
Believability | Calculation of trust value for W3C took 6.9141387939453125e-06s
INFO | --- Analysis for w3c took 2.672208786010742s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 3.886222839355469e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.2480936050415039s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 2.9802322387695312e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 5.9604644775390625e-06s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.989055871963501s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 4.220008850097656e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.2812662124633789s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.020629167556762695s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00010967254638671875s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 8.106231689453125e-06s
INFO | --- Analysis for w3c-wordnet took 3.2320334911346436s
Availability | SPARQL endpoint availability check for WarSampo took 0.39228248596191406s
Availability | VoID file availability check for WarSampo took 0.0006449222564697266s
Extra | Recovery of all triples for WarSampo took 149.38515949249268s
Performance | Total latancy measurement for WarSampo took 0.7894542217254639s
Amount of data | Number of triples check for WarSampo took 20.11741328239441s
Interoperability | New terms check for WarSampo took 3.808842420578003s
Versatility | Languages check for WarSampo took 55.27148938179016s
Interpretability | Number of blank nodes check for WarSampo took 20.108020305633545s
Security | Check HTTPS for WarSampo took 0.39385128021240234s
Interpretability | RDF structures check for WarSampo took 0.18477463722229004s
Versatility | Serialization formats check for WarSampo took 0.15343141555786133s
Availability | RDF dump link check for WarSampo took 0.8506598472595215s
License | MR license check for WarSampo took 0.1761472225189209s
License | HR license check for WarSampo took 48.438607931137085s
Amount of data | Number of property check for WarSampo took 0.18898653984069824s
Understandability | Number of label check for WarSampo took 10.710828065872192s
Understandability | URI regex check for WarSampo took 0.3441758155822754s
Understandability | Vocabs check for WarSampo took 0.1528153419494629s
Verifiability | Authors check for WarSampo took 0.17717528343200684s
Verifiability | Publishers check for WarSampo took 0.19256114959716797s
Performance | Throughput check for WarSampo took 10.589155912399292s
Amount of data | Check the number of entities for WarSampo took 15.1627938747406s
Verifiability | Contribs. check for WarSampo took 0.20305681228637695s
Interlinking | sameAs chians check for WarSampo took 0.20040225982666016s
Interlinking | skos check for WarSampo took 0.2033696174621582s
Interlinking | skos check for WarSampo took 0.15660953521728516s
Timeliness | dataset update frequency check for WarSampo took 0.1539630889892578s
Currency | Creation date check for WarSampo took 0.35627174377441406s
Currency | Modification date check for WarSampo took 0.3551008701324463s
Rep.Conc. | URIs length for WarSampo took 94.70811057090759s
Interoperability | New vocabularies check for WarSampo took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.15342211723327637s
Accuracy | Check Functional Property for WarSampo took 0.1842634677886963s
Accuracy | Check Inverse Functional Property for WarSampo took 0.15366029739379883s
Accuracy | Check Empty annotation labels for WarSampo took 51.937700033187866s
Accuracy | Check White space in annotation for WarSampo took 2.2585015296936035s
Accuracy | Check Datatype consistency for WarSampo took 5.422192573547363s
Consistency | Disjoint class check for WarSampo took 0.17926454544067383s
Consistency | Check Misplaced properties for WarSampo took 22.645734310150146s
Consistency | Check Ontology hijacking for WarSampo took 59.384610176086426s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.4083755016326904s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.5819439888000488s
Conciseness | Check Extensional conciseness for WarSampo took 2.9786689281463623s
Conciseness | Check Intensional conciseness for WarSampo took 0.259368896484375s
Security | Sign check for WarSampo took 0.16046905517578125s
Availability | Check URIs Dereferenciability for WarSampo took 2.6733286380767822s
Completeness | Calculation of interlinking completeness for WarSampo took 0.851264238357544s
Reputation | Calculation of the PageRank for WarSampo took 0.020343780517578125s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.463859558105469e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 5.245208740234375e-06s
Believability | Calculation of trust value for WarSampo took 6.9141387939453125e-06s
INFO | --- Analysis for warsampo took 1228.7740700244904s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.500473737716675s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.724480152130127s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.557868957519531e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for wasabi took 57.09808897972107s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.4810192584991455s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0002486705780029297s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 20.023670196533203s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 1.035710096359253s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 9.624382257461548s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 17.74867844581604s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 65.46141004562378s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 3.065474271774292s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.2599644660949707s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 10.504994869232178s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.2893519401550293s
License | MR license check for FAO water areas classification as linked data @PSNC took 0.507117509841919s
License | HR license check for FAO water areas classification as linked data @PSNC took 23.421817302703857s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.2030658721923828s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 2.6363282203674316s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 0.7503931522369385s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.3431971073150635s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.2047567367553711s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.26169705390930176s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 11.400036334991455s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 8.416175842285156e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.17896032333374023s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.2064495086669922s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.5157768726348877s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.4254329204559326s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 4.524713039398193s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.49592041969299316s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.24367451667785645s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 34.35509443283081s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.17903566360473633s
Accuracy | Check Functional Property for FAO water areas classification as linked data @PSNC took 0.30599021911621094s
Accuracy | Check Inverse Functional Property for FAO water areas classification as linked data @PSNC took 0.3034248352050781s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.17357373237609863s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 17.168999671936035s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 0.3740849494934082s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 14.324619770050049s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 59.691462993621826s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 0.0001761913299560547s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.45856690406799316s
Security | Sign check for FAO water areas classification as linked data @PSNC took 0.608534574508667s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 1.2437961101531982s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.020982980728149414s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for FAO water areas classification as linked data @PSNC took 1.1920928955078125e-06s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 6.198883056640625e-06s
INFO | --- Analysis for Water_Areas_Classification took 1096.5653431415558s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.20563173294067383s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.00026297569274902344s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 42.589269161224365s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 0.9488945007324219s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 8.548822402954102s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 20.72125506401062s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 78.86957097053528s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 2.7855358123779297s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.24730277061462402s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 9.192265272140503s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.27683472633361816s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.4883699417114258s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 116.14603304862976s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.20502662658691406s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 2.5450878143310547s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 0.7793364524841309s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.3968231678009033s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.19694995880126953s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.24554157257080078s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 11.435739040374756s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 7.128715515136719e-05s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.17988371849060059s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.1930983066558838s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.475386381149292s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.4433279037475586s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 6.735398292541504s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.47402024269104004s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.22884654998779297s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 118.60758376121521s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.19580626487731934s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.3590199947357178s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.38845229148864746s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.18987679481506348s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 68.80692672729492s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 0.3409388065338135s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 3.1596662998199463s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 90.1045708656311s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.00021386146545410156s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.5303449630737305s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 0.831305742263794s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.3385200500488281s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.1837916374206543s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 3.337860107421875e-05s
Interoperability | Check the re-using of existing vocabs for Water buffer dataset from Czech Republic @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.8835067749023438e-05s
INFO | --- Analysis for Water_Buffer took 1346.8714616298676s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.2234210968017578s
Availability | VoID file availability check for WebIsALOD took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.26394128799438477s
Reputation | Calculation of the PageRank for WebIsALOD took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0010094642639160156s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 9.822845458984375e-05s
Believability | Calculation of trust value for WebIsALOD took 8.344650268554688e-06s
INFO | --- Analysis for webisalod took 7.6416990756988525s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 4.220008850097656e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0007860660552978516s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.27485060691833496s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.020531892776489258s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.3855438232421875e-05s
Believability | Calculation of trust value for webnmasunotraveler took 7.3909759521484375e-06s
INFO | --- Analysis for webnmasunotraveler took 12.830408334732056s
Availability | SPARQL endpoint availability check for Whisky Circle took 5.14984130859375e-05s
Availability | VoID file availability check for Whisky Circle took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.276904821395874s
Reputation | Calculation of the PageRank for Whisky Circle took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010395050048828125s
Believability | Calculation of trust value for Whisky Circle took 8.344650268554688e-06s
INFO | --- Analysis for whisky-circle-info took 3.0185983180999756s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 20.237452745437622s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.2826383113861084s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.02025771141052246s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.4332275390625e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for WHOnto took 36.292283058166504s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.2667994499206543s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.0204317569732666s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 4.5299530029296875e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 7.62939453125e-06s
INFO | --- Analysis for whonto took 8.868546485900879s
Availability | SPARQL endpoint availability check for Wikidata took 0.6439449787139893s
Availability | VoID file availability check for Wikidata took 0.0006432533264160156s
Extra | Recovery of all triples for Wikidata took 0.09479689598083496s
Amount of data | Number of triples check for Wikidata took 0.08411240577697754s
Versatility | Languages check for Wikidata took 0.08382725715637207s
Interpretability | Number of blank nodes check for Wikidata took 0.09516286849975586s
Interpretability | RDF structures check for Wikidata took 0.09352707862854004s
Versatility | Serialization formats check for Wikidata took 0.08321237564086914s
Availability | RDF dump link check for Wikidata took 0.08362102508544922s
License | MR license check for Wikidata took 0.08424496650695801s
License | HR license check for Wikidata took 0.09738397598266602s
Amount of data | Number of property check for Wikidata took 0.08643817901611328s
Understandability | Number of label check for Wikidata took 0.09416842460632324s
Understandability | URI regex check for Wikidata took 0.15381288528442383s
Understandability | Vocabs check for Wikidata took 0.08473682403564453s
Verifiability | Authors check for Wikidata took 0.0959022045135498s
Verifiability | Publishers check for Wikidata took 0.08430981636047363s
Amount of data | Check the number of entities for Wikidata took 0.00018024444580078125s
Verifiability | Contribs. check for Wikidata took 0.09386587142944336s
Interlinking | sameAs chians check for Wikidata took 0.08608150482177734s
Interlinking | skos check for Wikidata took 0.07349658012390137s
Interlinking | skos check for Wikidata took 0.09345722198486328s
Timeliness | dataset update frequency check for Wikidata took 0.08602452278137207s
Currency | Creation date check for Wikidata took 0.15826082229614258s
Currency | Modification date check for Wikidata took 0.16866254806518555s
Rep.Conc. | URIs length for Wikidata took 0.17600321769714355s
Interoperability | New vocabularies check for Wikidata took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Wikidata took 0.08316206932067871s
Consistency | Disjoint class check for Wikidata took 0.07263445854187012s
Consistency | Check Ontology hijacking for Wikidata took 0.08434677124023438s
Consistency | Check Invalid usage of undefined properties for Wikidata took 1.268162488937378s
Conciseness | Check Extensional conciseness for Wikidata took 0.00016641616821289062s
Security | Sign check for Wikidata took 0.0678260326385498s
Completeness | Calculation of interlinking completeness for Wikidata took 0.34091687202453613s
Reputation | Calculation of the PageRank for Wikidata took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0002777576446533203s
Interoperability | Check the re-using of existing vocabs for Wikidata took 4.76837158203125e-07s
Believability | Calculation of trust value for Wikidata took 5.4836273193359375e-06s
INFO | --- Analysis for wikidata took 25.51891541481018s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 4.100799560546875e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.2568972110748291s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.02031540870666504s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 6.723403930664062e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 8.821487426757812e-06s
INFO | --- Analysis for wikilinks-rdf-nif took 2.5459048748016357s
Availability | SPARQL endpoint availability check for WikiPathways took 3.981590270996094e-05s
Availability | VoID file availability check for WikiPathways took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.26981186866760254s
Reputation | Calculation of the PageRank for WikiPathways took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for WikiPathways took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.7179718017578125e-05s
Believability | Calculation of trust value for WikiPathways took 9.059906005859375e-06s
INFO | --- Analysis for wikipathways took 2.956364154815674s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 4.0531158447265625e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.2730286121368408s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 8.106231689453125e-06s
INFO | --- Analysis for wikiword_thesaurus took 3.025836944580078s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2677326202392578s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.26376819610595703s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.368492126464844e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 9.059906005859375e-06s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.4604527950286865s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 4.076957702636719e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.0002982616424560547s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.2549870014190674s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for Wings workflow provenance dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Wings workflow provenance dataset took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Wings workflow provenance dataset took 2.8133392333984375e-05s
Believability | Calculation of trust value for Wings workflow provenance dataset took 8.106231689453125e-06s
INFO | --- Analysis for wings-workflow-provenance-dataset took 2.923125743865967s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.242828607559204s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.27977490425109863s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 2.765655517578125e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 8.821487426757812e-06s
INFO | --- Analysis for wl-kg took 3.9822261333465576s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 4.363059997558594e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.2920827865600586s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 9.226799011230469e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 8.106231689453125e-06s
INFO | --- Analysis for wn-wiki-instances took 3.161975383758545s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.11941742897033691s
Availability | VoID file availability check for World Loanword Database took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.25424861907958984s
Reputation | Calculation of the PageRank for World Loanword Database took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.390975952148438e-05s
Believability | Calculation of trust value for World Loanword Database took 7.62939453125e-06s
INFO | --- Analysis for wold took 2.60174560546875s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 4.220008850097656e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.25469112396240234s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.020253896713256836s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 2.765655517578125e-05s
Believability | Calculation of trust value for Wood Trick LLC took 8.106231689453125e-06s
INFO | --- Analysis for woodtrick took 3.0945920944213867s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.372450590133667s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.2892599105834961s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 5.745887756347656e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for WordFormationLatin took 3.678934335708618s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 4.3392181396484375e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.2523047924041748s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010442733764648438s
Believability | Calculation of trust value for WordLift Blog EN took 7.867813110351562e-06s
INFO | --- Analysis for wordlift-io-blog-en took 3.432460308074951s
Availability | SPARQL endpoint availability check for WordLift IT took 4.267692565917969e-05s
Availability | VoID file availability check for WordLift IT took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.26613640785217285s
Reputation | Calculation of the PageRank for WordLift IT took 0.020817995071411133s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00010657310485839844s
Believability | Calculation of trust value for WordLift IT took 8.106231689453125e-06s
INFO | --- Analysis for wordlift-io-blog-it took 2.884028911590576s
Availability | SPARQL endpoint availability check for Wordnet took 4.076957702636719e-05s
Availability | VoID file availability check for Wordnet took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Wordnet took 0.2389523983001709s
Reputation | Calculation of the PageRank for Wordnet took 0.02076435089111328s
Interlinking | Calculation of Degree of Connection for Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wordnet took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Wordnet took 3.910064697265625e-05s
Believability | Calculation of trust value for Wordnet took 7.867813110351562e-06s
INFO | --- Analysis for wordnet took 3.1394755840301514s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.1961669921875e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.2752194404602051s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.021033287048339844s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 8.96453857421875e-05s
Believability | Calculation of trust value for WordNet-RDF took 6.9141387939453125e-06s
INFO | --- Analysis for wordnet-rdf took 2.4713950157165527s
Availability | SPARQL endpoint availability check for wordpress took 4.1484832763671875e-05s
Availability | VoID file availability check for wordpress took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for wordpress took 0.252183198928833s
Reputation | Calculation of the PageRank for wordpress took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for wordpress took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for wordpress took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.034706115722656e-05s
Believability | Calculation of trust value for wordpress took 6.4373016357421875e-06s
INFO | --- Analysis for wordpress took 2.949533462524414s
Availability | SPARQL endpoint availability check for wordpress.post took 4.00543212890625e-05s
Availability | VoID file availability check for wordpress.post took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.26256871223449707s
Reputation | Calculation of the PageRank for wordpress.post took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for wordpress.post took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for wordpress.post took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 2.9325485229492188e-05s
Believability | Calculation of trust value for wordpress.post took 7.62939453125e-06s
INFO | --- Analysis for wordpress_post took 2.972108840942383s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.1951439380645752s
Availability | VoID file availability check for World Bank Linked Data took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.2890050411224365s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012350082397460938s
Believability | Calculation of trust value for World Bank Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for world-bank-linked-data took 2.770670175552368s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 0.8806116580963135s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.27501535415649414s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.020747661590576172s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.463859558105469e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 6.198883056640625e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 5.1796252727508545s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.267692565917969e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.2811093330383301s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.893013000488281e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 5.0067901611328125e-06s
INFO | --- Analysis for world-wide-web-foundation took 5.677020072937012s
Availability | SPARQL endpoint availability check for WikiPathways took 3.981590270996094e-05s
Availability | VoID file availability check for WikiPathways took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2495572566986084s
Reputation | Calculation of the PageRank for WikiPathways took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.8371810913085938e-05s
Believability | Calculation of trust value for WikiPathways took 7.3909759521484375e-06s
INFO | --- Analysis for wp took 2.953594207763672s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 4.124641418457031e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.29361724853515625s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.020181894302368164s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 2.7894973754882812e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 7.867813110351562e-06s
INFO | --- Analysis for wunderground_weatherreport took 3.0202207565307617s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.32468366622924805s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0005526542663574219s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 15.548844337463379s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.796018123626709s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.23182058334350586s
Interoperability | New terms check for World War 1 as Linked Open Data took 2.364077568054199s
Versatility | Languages check for World War 1 as Linked Open Data took 0.4442610740661621s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.23022985458374023s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.3758103847503662s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.17704319953918457s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.18299174308776855s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.8275017738342285s
License | MR license check for World War 1 as Linked Open Data took 0.19063186645507812s
License | HR license check for World War 1 as Linked Open Data took 1.7976157665252686s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.19048404693603516s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.3829636573791504s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.32895541191101074s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.2593226432800293s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.18775701522827148s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.18284130096435547s
Performance | Throughput check for World War 1 as Linked Open Data took 10.428302526473999s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.0719609260559082s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.18203020095825195s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.4538605213165283s
Interlinking | skos check for World War 1 as Linked Open Data took 0.19217658042907715s
Interlinking | skos check for World War 1 as Linked Open Data took 0.15671300888061523s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.14497685432434082s
Currency | Creation date check for World War 1 as Linked Open Data took 0.36041879653930664s
Currency | Modification date check for World War 1 as Linked Open Data took 0.1854391098022461s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 3.4106335639953613s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.19025635719299316s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.17642593383789062s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.1435079574584961s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.6748387813568115s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.0496525764465332s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.31803393363952637s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.17676877975463867s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.5714108943939209s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.0850658416748047s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.196908712387085s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.4458951950073242s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.19301748275756836s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.5986506938934326s
Security | Sign check for World War 1 as Linked Open Data took 0.14318490028381348s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1643.9668202400208s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.29470062255859375s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.021442174911499023s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 6.985664367675781e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0009706020355224609s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 0.00010752677917480469s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for ww1lod took 1745.3027801513672s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 4.100799560546875e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.2874603271484375s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.02076125144958496s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 2.9802322387695312e-05s
Believability | Calculation of trust value for XlendiAmphorae took 6.67572021484375e-06s
INFO | --- Analysis for xlendiamphorae took 3.443817377090454s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.3428363800048828s
Availability | VoID file availability check for xLiD-Lexica took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.26691246032714844s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 6.961822509765625e-05s
Believability | Calculation of trust value for xLiD-Lexica took 7.62939453125e-06s
INFO | --- Analysis for xlid-lexica took 3.913966417312622s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.291534423828125e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.25663232803344727s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.910064697265625e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 7.3909759521484375e-06s
INFO | --- Analysis for xwn took 2.8318259716033936s
Availability | SPARQL endpoint availability check for xxx took 7.2479248046875e-05s
Availability | VoID file availability check for xxx took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for xxx took 0.2701277732849121s
Reputation | Calculation of the PageRank for xxx took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for xxx took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for xxx took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for xxx took 3.147125244140625e-05s
Believability | Calculation of trust value for xxx took 8.106231689453125e-06s
INFO | --- Analysis for xx took 2.4505951404571533s
Availability | SPARQL endpoint availability check for YAGO took 4.4345855712890625e-05s
Availability | VoID file availability check for YAGO took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for YAGO took 0.2688462734222412s
Reputation | Calculation of the PageRank for YAGO took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for YAGO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for YAGO took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00013065338134765625s
Believability | Calculation of trust value for YAGO took 7.3909759521484375e-06s
INFO | --- Analysis for yago took 6.995697021484375s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 1.7628295421600342s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.3210923671722412s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.020171403884887695s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 9.393692016601562e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 7.62939453125e-06s
INFO | --- Analysis for yahoo_geoplanet took 11.604835271835327s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.14524054527282715s
Availability | VoID file availability check for Yale Senselab took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.27387285232543945s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 2.765655517578125e-05s
Believability | Calculation of trust value for Yale Senselab took 6.4373016357421875e-06s
INFO | --- Analysis for yale_senselab took 9.285818815231323s
Availability | SPARQL endpoint availability check for test-dapp-2 took 4.100799560546875e-05s
Availability | VoID file availability check for test-dapp-2 took 0.000244140625s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.28005123138427734s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 2.8371810913085938e-05s
Believability | Calculation of trust value for test-dapp-2 took 6.4373016357421875e-06s
INFO | --- Analysis for yordhis took 2.5147364139556885s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 1.068429946899414s
Availability | VoID file availability check for Yovisto - academic video search took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.2729611396789551s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020392656326293945s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.389617919921875e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 5.9604644775390625e-06s
INFO | --- Analysis for yovisto took 24.641640186309814s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 4.1484832763671875e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.00042748451232910156s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.2621631622314453s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.020676136016845703s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.2901763916015625e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 8.344650268554688e-06s
INFO | --- Analysis for ysa took 4.3165223598480225s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0004019737243652344s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.2742619514465332s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.173683166503906e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for yso took 4.2658350467681885s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.267692565917969e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.26160216331481934s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.4332275390625e-05s
Believability | Calculation of trust value for yso-fi-allars took 8.821487426757812e-06s
INFO | --- Analysis for yso-fi-allars took 3.532275915145874s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.291534423828125e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.2701563835144043s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.3855438232421875e-05s
Believability | Calculation of trust value for yso-fi-ysa took 6.198883056640625e-06s
INFO | --- Analysis for yso-fi-ysa took 3.0179283618927s
Availability | SPARQL endpoint availability check for YSO places took 0.6117923259735107s
Availability | VoID file availability check for YSO places took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for YSO places took 0.26859045028686523s
Reputation | Calculation of the PageRank for YSO places took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for YSO places took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.1948089599609375e-05s
Believability | Calculation of trust value for YSO places took 8.106231689453125e-06s
INFO | --- Analysis for yso-paikat took 4.168736457824707s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.506111145019531e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.2939109802246094s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.4809112548828125e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 5.245208740234375e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 6.6553051471710205s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 4.1961669921875e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.28681135177612305s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.020848512649536133s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.3855438232421875e-05s
Believability | Calculation of trust value for zaragoza_turruta took 8.58306884765625e-06s
INFO | --- Analysis for zaragoza_turruta took 2.607248544692993s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.458427429199219e-05s
Availability | VoID file availability check for ZBW Labs took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.28682374954223633s
Reputation | Calculation of the PageRank for ZBW Labs took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 6.651878356933594e-05s
Believability | Calculation of trust value for ZBW Labs took 7.152557373046875e-06s
INFO | --- Analysis for zbw-labs took 3.4645583629608154s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.16030287742614746s
Availability | VoID file availability check for 20th Century Press Archives took 0.0005857944488525391s
Extra | Recovery of all triples for 20th Century Press Archives took 64.5554666519165s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7446444034576416s
Amount of data | Number of triples check for 20th Century Press Archives took 1.1050760746002197s
Interoperability | New terms check for 20th Century Press Archives took 1.485804557800293s
Versatility | Languages check for 20th Century Press Archives took 3.0296170711517334s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.9048252105712891s
Interpretability | RDF structures check for 20th Century Press Archives took 0.16076922416687012s
Versatility | Serialization formats check for 20th Century Press Archives took 0.1557919979095459s
Availability | RDF dump link check for 20th Century Press Archives took 0.15781044960021973s
License | MR license check for 20th Century Press Archives took 0.1367039680480957s
License | HR license check for 20th Century Press Archives took 4.870018005371094s
Amount of data | Number of property check for 20th Century Press Archives took 0.13540935516357422s
Understandability | Number of label check for 20th Century Press Archives took 0.5047550201416016s
Understandability | URI regex check for 20th Century Press Archives took 0.2894582748413086s
Understandability | Vocabs check for 20th Century Press Archives took 0.16510748863220215s
Verifiability | Authors check for 20th Century Press Archives took 0.1594395637512207s
Verifiability | Publishers check for 20th Century Press Archives took 0.13813066482543945s
Performance | Throughput check for 20th Century Press Archives took 10.997737884521484s
Amount of data | Check the number of entities for 20th Century Press Archives took 0.00010538101196289062s
Verifiability | Contribs. check for 20th Century Press Archives took 0.1835644245147705s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.1397416591644287s
Interlinking | skos check for 20th Century Press Archives took 0.27060651779174805s
Interlinking | skos check for 20th Century Press Archives took 0.20630812644958496s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.14133620262145996s
Currency | Creation date check for 20th Century Press Archives took 0.2797536849975586s
Currency | Modification date check for 20th Century Press Archives took 0.2691218852996826s
Rep.Conc. | URIs length for 20th Century Press Archives took 21.190683364868164s
Interoperability | New vocabularies check for 20th Century Press Archives took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.1425485610961914s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.14057612419128418s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.1525402069091797s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 9.443068742752075s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8809547424316406s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.0906195640563965s
Consistency | Disjoint class check for 20th Century Press Archives took 0.15001463890075684s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.163588523864746s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 3.5007200241088867s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.556327819824219s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.141685962677002s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.7843213081359863s
Security | Sign check for 20th Century Press Archives took 0.16064190864562988s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1049.7347066402435s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.2668139934539795s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021397829055786133s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00010347366333007812s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 2.384185791015625e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 8.58306884765625e-06s
INFO | --- Analysis for zbw-pressemappe20 took 1218.0308001041412s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.649162292480469e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0007696151733398438s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.29135751724243164s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.021299362182617188s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 5.125999450683594e-05s
Believability | Calculation of trust value for zhishi.lemon took 8.58306884765625e-06s
INFO | --- Analysis for zhishi-lemon took 24.029232501983643s
Availability | SPARQL endpoint availability check for Zhishi.me took 3.044586420059204s
Availability | VoID file availability check for Zhishi.me took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.28775477409362793s
Reputation | Calculation of the PageRank for Zhishi.me took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.176399230957031e-05s
Believability | Calculation of trust value for Zhishi.me took 7.62939453125e-06s
INFO | --- Analysis for zhishi-me took 7.467441082000732s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.7206878662109375e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.28331661224365234s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.020779132843017578s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 5.793571472167969e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 7.3909759521484375e-06s
INFO | --- Analysis for zitgist-musicbrainz took 3.2141151428222656s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 4.291534423828125e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.26651859283447266s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.020680665969848633s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 3.123283386230469e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 9.059906005859375e-06s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.979367256164551s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.2691473960876465s
Availability | VoID file availability check for performing-arts.ch took 0.00029659271240234375s
Extra | Recovery of all triples for performing-arts.ch took 89.55467581748962s
Performance | Total latancy measurement for performing-arts.ch took 0.5975246429443359s
Amount of data | Number of triples check for performing-arts.ch took 24.132620573043823s
Interoperability | New terms check for performing-arts.ch took 1.3075988292694092s
Versatility | Languages check for performing-arts.ch took 60.11470365524292s
Interpretability | Number of blank nodes check for performing-arts.ch took 0.11521649360656738s
Interpretability | RDF structures check for performing-arts.ch took 0.09334492683410645s
Versatility | Serialization formats check for performing-arts.ch took 0.10473203659057617s
Availability | RDF dump link check for performing-arts.ch took 0.09296131134033203s
License | MR license check for performing-arts.ch took 0.10724520683288574s
License | HR license check for performing-arts.ch took 0.10370826721191406s
Amount of data | Number of property check for performing-arts.ch took 0.11331605911254883s
Understandability | Number of label check for performing-arts.ch took 0.1174321174621582s
Understandability | URI regex check for performing-arts.ch took 0.19408750534057617s
Understandability | Vocabs check for performing-arts.ch took 0.11657357215881348s
Verifiability | Authors check for performing-arts.ch took 0.1038367748260498s
Verifiability | Publishers check for performing-arts.ch took 0.11460089683532715s
Amount of data | Check the number of entities for performing-arts.ch took 0.000125885009765625s
Verifiability | Contribs. check for performing-arts.ch took 0.1027064323425293s
Interlinking | sameAs chians check for performing-arts.ch took 0.0915522575378418s
Interlinking | skos check for performing-arts.ch took 0.11240649223327637s
Interlinking | skos check for performing-arts.ch took 0.09188079833984375s
Timeliness | dataset update frequency check for performing-arts.ch took 0.10229229927062988s
Currency | Creation date check for performing-arts.ch took 0.18492746353149414s
Currency | Modification date check for performing-arts.ch took 0.20852923393249512s
Rep.Conc. | URIs length for performing-arts.ch took 3.7077722549438477s
Interoperability | New vocabularies check for performing-arts.ch took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.10312724113464355s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.854310750961304s
Consistency | Disjoint class check for performing-arts.ch took 0.1404426097869873s
Consistency | Check Misplaced properties for performing-arts.ch took 0.45317530632019043s
Consistency | Misplaced classes for performing-arts.ch took 8.551503896713257s
Consistency | Check Ontology hijacking for performing-arts.ch took 53.063133001327515s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 16329.133553981781s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 3.7064626216888428s
Conciseness | Check Extensional conciseness for performing-arts.ch took 22.49289035797119s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.41602134704589844s
Security | Sign check for performing-arts.ch took 0.21732854843139648s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.853003978729248s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 1.2049944400787354s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.5035343170166016s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 0.0007233619689941406s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.01674818992614746s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 0.02182316780090332s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 1.1920928955078125e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.2159347534179688e-05s
INFO | --- Analysis for performing-arts.ch took 16688.398710489273s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.0163702964782715s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0003666877746582031s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.25232744216918945s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.2874603271484375e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for The-AA-Thesaurus took 7.741245985031128s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.599984884262085s
Availability | VoID file availability check for MiMoTextBase took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.281996488571167s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.024105548858642578s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.2874603271484375e-05s
Believability | Calculation of trust value for MiMoTextBase took 8.58306884765625e-06s
INFO | --- Analysis for MiMoTextBase took 6.067750453948975s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.47725939750671387s
Availability | VoID file availability check for National Library of Sweden took 0.0006623268127441406s
Extra | Recovery of all triples for National Library of Sweden took 14.116527080535889s
Performance | Total latancy measurement for National Library of Sweden took 1.0358374118804932s
Amount of data | Number of triples check for National Library of Sweden took 22.030714750289917s
Interoperability | New terms check for National Library of Sweden took 15.664371252059937s
Versatility | Languages check for National Library of Sweden took 0.19746780395507812s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.17692470550537s
Interpretability | RDF structures check for National Library of Sweden took 3.09895920753479s
Versatility | Serialization formats check for National Library of Sweden took 0.2424623966217041s
Availability | RDF dump link check for National Library of Sweden took 0.19819259643554688s
License | MR license check for National Library of Sweden took 0.3169677257537842s
License | HR license check for National Library of Sweden took 0.29844117164611816s
Amount of data | Number of property check for National Library of Sweden took 0.1893463134765625s
Understandability | Number of label check for National Library of Sweden took 0.4691452980041504s
Understandability | URI regex check for National Library of Sweden took 0.4445383548736572s
Understandability | Vocabs check for National Library of Sweden took 0.21000337600708008s
Verifiability | Authors check for National Library of Sweden took 0.23684215545654297s
Verifiability | Publishers check for National Library of Sweden took 0.23518061637878418s
Performance | Throughput check for National Library of Sweden took 11.30127239227295s
Amount of data | Check the number of entities for National Library of Sweden took 7.033348083496094e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.24405503273010254s
Interlinking | sameAs chians check for National Library of Sweden took 0.22153997421264648s
Interlinking | skos check for National Library of Sweden took 0.3052647113800049s
Interlinking | skos check for National Library of Sweden took 0.18712282180786133s
Timeliness | dataset update frequency check for National Library of Sweden took 0.23267674446105957s
Currency | Creation date check for National Library of Sweden took 0.45917177200317383s
Currency | Modification date check for National Library of Sweden took 0.43466949462890625s
Rep.Conc. | URIs length for National Library of Sweden took 83.33451247215271s
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.21904444694519043s
Accuracy | Check Functional Property for National Library of Sweden took 0.22381281852722168s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.2128458023071289s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.2740132808685303s
Consistency | Disjoint class check for National Library of Sweden took 0.24666523933410645s
Consistency | Check Misplaced properties for National Library of Sweden took 63.16330432891846s
Consistency | Misplaced classes for National Library of Sweden took 1.1156816482543945s
Consistency | Check Ontology hijacking for National Library of Sweden took 5.127125978469849s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.1542842388153076s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 64.43336343765259s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.278458833694458s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.33727073669433594s
Security | Sign check for National Library of Sweden took 0.34392404556274414s
Availability | Check URIs Dereferenciability for National Library of Sweden took 18.660808801651s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.8986964225769043s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.1920928955078125e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.1682510375976562e-05s
INFO | --- Analysis for NLS took 1386.2469644546509s
Availability | SPARQL endpoint availability check for Japan Search took 1.7676069736480713s
Availability | VoID file availability check for Japan Search took 0.00025725364685058594s
Extra | Recovery of all triples for Japan Search took 3.3151094913482666s
Performance | Total latancy measurement for Japan Search took 1.612607479095459s
Amount of data | Number of triples check for Japan Search took 7.875823497772217s
Interoperability | New terms check for Japan Search took 3.3329625129699707s
Versatility | Languages check for Japan Search took 91.75624251365662s
Interpretability | Number of blank nodes check for Japan Search took 91.54492712020874s
Interpretability | RDF structures check for Japan Search took 1.1626906394958496s
Versatility | Serialization formats check for Japan Search took 0.9133076667785645s
Availability | RDF dump link check for Japan Search took 0.4600045680999756s
License | MR license check for Japan Search took 1.280972957611084s
License | HR license check for Japan Search took 90.98882746696472s
Amount of data | Number of property check for Japan Search took 0.8091323375701904s
Understandability | Number of label check for Japan Search took 4.644683837890625s
Understandability | URI regex check for Japan Search took 0.6085531711578369s
Understandability | Vocabs check for Japan Search took 0.31319189071655273s
Verifiability | Authors check for Japan Search took 0.41791558265686035s
Verifiability | Publishers check for Japan Search took 0.3066115379333496s
Performance | Throughput check for Japan Search took 11.196496963500977s
Amount of data | Check the number of entities for Japan Search took 8.726119995117188e-05s
Verifiability | Contribs. check for Japan Search took 0.2863936424255371s
Interlinking | sameAs chians check for Japan Search took 0.3216845989227295s
Interlinking | skos check for Japan Search took 0.32701778411865234s
Interlinking | skos check for Japan Search took 0.30754733085632324s
Timeliness | dataset update frequency check for Japan Search took 0.5985214710235596s
Currency | Creation date check for Japan Search took 0.5749170780181885s
Currency | Modification date check for Japan Search took 0.5932745933532715s
Rep.Conc. | URIs length for Japan Search took 31.352609395980835s
Interoperability | New vocabularies check for Japan Search took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.26108527183532715s
Accuracy | Check Functional Property for Japan Search took 0.45226383209228516s
Accuracy | Check Inverse Functional Property for Japan Search took 0.4087221622467041s
Accuracy | Check Empty annotation labels for Japan Search took 0.5473034381866455s
Accuracy | Check White space in annotation for Japan Search took 0.0314939022064209s
Accuracy | Check Datatype consistency for Japan Search took 0.029152393341064453s
Consistency | Disjoint class check for Japan Search took 0.3476448059082031s
Consistency | Check Misplaced properties for Japan Search took 28.544007778167725s
Consistency | Misplaced classes for Japan Search took 0.3871457576751709s
Consistency | Check Ontology hijacking for Japan Search took 5.059671640396118s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.184175968170166s
Consistency | Check Invalid usage of undefined properties for Japan Search took 29.651392698287964s
Conciseness | Check Extensional conciseness for Japan Search took 0.038324594497680664s
Conciseness | Check Intensional conciseness for Japan Search took 1.1212549209594727s
Security | Sign check for Japan Search took 0.3159060478210449s
Availability | Check URIs Dereferenciability for Japan Search took 5.290904760360718s
Completeness | Calculation of interlinking completeness for Japan Search took 0.5543415546417236s
Reputation | Calculation of the PageRank for Japan Search took 0.02241992950439453s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Japan Search took 2.193450927734375e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 2.1457672119140625e-06s
Believability | Calculation of trust value for Japan Search took 8.58306884765625e-06s
INFO | --- Analysis for Japan-Search took 808.1905310153961s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 0.9314687252044678s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.28814053535461426s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.022197484970092773s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.1920928955078125e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 7.62939453125e-06s
INFO | --- Analysis for Rijksmuseum took 4.339766979217529s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.6794660091400146s
Availability | VoID file availability check for Finnish Public Libraries took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.27310919761657715s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.1205673217773438e-05s
Believability | Calculation of trust value for Finnish Public Libraries took 8.106231689453125e-06s
INFO | --- Analysis for FI-Library took 3.9981441497802734s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 3.802380084991455s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.3381381034851074s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.4543533325195312e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 7.3909759521484375e-06s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 9.06798005104065s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.456779956817627s
Availability | VoID file availability check for National Library Netherlands took 0.0005595684051513672s
Extra | Recovery of all triples for National Library Netherlands took 1.090627670288086s
Performance | Total latancy measurement for National Library Netherlands took 0.8007123470306396s
Amount of data | Number of triples check for National Library Netherlands took 0.1525278091430664s
Interoperability | New terms check for National Library Netherlands took 1.290647029876709s
Versatility | Languages check for National Library Netherlands took 58.12201118469238s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.13761234283447266s
Interpretability | RDF structures check for National Library Netherlands took 0.13640284538269043s
Versatility | Serialization formats check for National Library Netherlands took 0.1354682445526123s
Availability | RDF dump link check for National Library Netherlands took 0.13919281959533691s
License | MR license check for National Library Netherlands took 0.17337250709533691s
License | HR license check for National Library Netherlands took 58.163718938827515s
Amount of data | Number of property check for National Library Netherlands took 0.16344404220581055s
Understandability | Number of label check for National Library Netherlands took 0.187103271484375s
Understandability | URI regex check for National Library Netherlands took 0.3166661262512207s
Understandability | Vocabs check for National Library Netherlands took 0.15656542778015137s
Verifiability | Authors check for National Library Netherlands took 0.12960147857666016s
Verifiability | Publishers check for National Library Netherlands took 0.18761634826660156s
Performance | Throughput check for National Library Netherlands took 10.745537996292114s
Amount of data | Check the number of entities for National Library Netherlands took 7.271766662597656e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.15358877182006836s
Interlinking | sameAs chians check for National Library Netherlands took 0.1300039291381836s
Interlinking | skos check for National Library Netherlands took 0.14584112167358398s
Interlinking | skos check for National Library Netherlands took 0.16396260261535645s
Timeliness | dataset update frequency check for National Library Netherlands took 0.15896129608154297s
Currency | Creation date check for National Library Netherlands took 0.2944023609161377s
Currency | Modification date check for National Library Netherlands took 0.14255857467651367s
Rep.Conc. | URIs length for National Library Netherlands took 0.7192544937133789s
Interoperability | New vocabularies check for National Library Netherlands took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.16596627235412598s
Accuracy | Check Functional Property for National Library Netherlands took 0.16867399215698242s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.15874528884887695s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.5121400356292725s
Accuracy | Check White space in annotation for National Library Netherlands took 0.021745920181274414s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.02817368507385254s
Consistency | Disjoint class check for National Library Netherlands took 0.1611340045928955s
Consistency | Check Misplaced properties for National Library Netherlands took 0.39758872985839844s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.6870923042297363s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.9343829154968262s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.3572206497192383s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.03789544105529785s
Security | Sign check for National Library Netherlands took 0.142592191696167s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1709.3018114566803s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.6728100776672363s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 1.6927719116210938e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for National Library Netherlands took 7.867813110351562e-06s
INFO | --- Analysis for National-Library-Netherlands took 1876.0091536045074s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.2972145080566406s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.273212194442749s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.239776611328125e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 6.9141387939453125e-06s
INFO | --- Analysis for Antique-Renaissance took 5.347767353057861s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 7.038739204406738s
Availability | VoID file availability check for ARTSDATA.CA took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.2729361057281494s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.020914077758789062s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.049041748046875e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 6.67572021484375e-06s
INFO | --- Analysis for ARTSDATA-CA took 12.868754863739014s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.10688948631286621s
Availability | VoID file availability check for Architecture of Knowledge took 0.0006077289581298828s
Extra | Recovery of all triples for Architecture of Knowledge took 60.27123141288757s
Performance | Total latancy measurement for Architecture of Knowledge took 0.22679948806762695s
Amount of data | Number of triples check for Architecture of Knowledge took 6.4961817264556885s
Interoperability | New terms check for Architecture of Knowledge took 5.136094570159912s
Versatility | Languages check for Architecture of Knowledge took 60.16557240486145s
Interpretability | Number of blank nodes check for Architecture of Knowledge took 0.07095742225646973s
Interpretability | RDF structures check for Architecture of Knowledge took 0.1362907886505127s
Versatility | Serialization formats check for Architecture of Knowledge took 0.07493209838867188s
Availability | RDF dump link check for Architecture of Knowledge took 0.036669254302978516s
License | MR license check for Architecture of Knowledge took 0.13393044471740723s
License | HR license check for Architecture of Knowledge took 60.165380239486694s
Amount of data | Number of property check for Architecture of Knowledge took 0.07231545448303223s
Understandability | Number of label check for Architecture of Knowledge took 1.960636854171753s
Understandability | URI regex check for Architecture of Knowledge took 0.07556796073913574s
Understandability | Vocabs check for Architecture of Knowledge took 0.03943514823913574s
Verifiability | Authors check for Architecture of Knowledge took 0.08049273490905762s
Verifiability | Publishers check for Architecture of Knowledge took 0.036380767822265625s
Performance | Throughput check for Architecture of Knowledge took 10.24260687828064s
Amount of data | Check the number of entities for Architecture of Knowledge took 4.839897155761719e-05s
Verifiability | Contribs. check for Architecture of Knowledge took 0.0619196891784668s
Interlinking | sameAs chians check for Architecture of Knowledge took 0.06831979751586914s
Interlinking | skos check for Architecture of Knowledge took 0.16244101524353027s
Interlinking | skos check for Architecture of Knowledge took 0.0434565544128418s
Timeliness | dataset update frequency check for Architecture of Knowledge took 0.0376889705657959s
Currency | Creation date check for Architecture of Knowledge took 0.19918513298034668s
Currency | Modification date check for Architecture of Knowledge took 0.18469738960266113s
Rep.Conc. | URIs length for Architecture of Knowledge took 83.2278425693512s
Interoperability | New vocabularies check for Architecture of Knowledge took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Architecture of Knowledge took 0.06532478332519531s
Accuracy | Check Functional Property for Architecture of Knowledge took 0.11191344261169434s
Accuracy | Check Inverse Functional Property for Architecture of Knowledge took 0.07855892181396484s
Accuracy | Check Empty annotation labels for Architecture of Knowledge took 46.931755781173706s
Accuracy | Check White space in annotation for Architecture of Knowledge took 3.1182055473327637s
Consistency | Disjoint class check for Architecture of Knowledge took 0.21220779418945312s
Consistency | Check Misplaced properties for Architecture of Knowledge took 27.711162090301514s
Consistency | Misplaced classes for Architecture of Knowledge took 0.1109464168548584s
Consistency | Check Ontology hijacking for Architecture of Knowledge took 40.0438129901886s
Consistency | Check Invalid usage of undefined properties for Architecture of Knowledge took 29.149152517318726s
Conciseness | Check Extensional conciseness for Architecture of Knowledge took 0.0001544952392578125s
Conciseness | Check Intensional conciseness for Architecture of Knowledge took 0.11609220504760742s
Security | Sign check for Architecture of Knowledge took 0.642427921295166s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.37386345863342285s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.021870136260986328s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Architecture of Knowledge took 2.86102294921875e-06s
Believability | Calculation of trust value for Architecture of Knowledge took 8.821487426757812e-06s
INFO | --- Analysis for ArCo took 706.1059191226959s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.3535327911376953s
Availability | VoID file availability check for ConfermentSampo took 0.0002551078796386719s
Extra | Recovery of all triples for ConfermentSampo took 146.09348678588867s
Performance | Total latancy measurement for ConfermentSampo took 0.8533785343170166s
Amount of data | Number of triples check for ConfermentSampo took 16.29046654701233s
Interoperability | New terms check for ConfermentSampo took 2.47719669342041s
Versatility | Languages check for ConfermentSampo took 31.01932430267334s
Interpretability | Number of blank nodes check for ConfermentSampo took 7.573620557785034s
Security | Check HTTPS for ConfermentSampo took 0.3718993663787842s
Interpretability | RDF structures check for ConfermentSampo took 0.20135211944580078s
Versatility | Serialization formats check for ConfermentSampo took 0.2062675952911377s
Availability | RDF dump link check for ConfermentSampo took 2.91508412361145s
License | MR license check for ConfermentSampo took 0.199202299118042s
License | HR license check for ConfermentSampo took 0.321120023727417s
Amount of data | Number of property check for ConfermentSampo took 0.19621658325195312s
Understandability | Number of label check for ConfermentSampo took 14.110880851745605s
Understandability | URI regex check for ConfermentSampo took 0.3434123992919922s
Understandability | Vocabs check for ConfermentSampo took 0.16142630577087402s
Verifiability | Authors check for ConfermentSampo took 0.1984703540802002s
Verifiability | Publishers check for ConfermentSampo took 0.1901226043701172s
Performance | Throughput check for ConfermentSampo took 10.629372835159302s
Amount of data | Check the number of entities for ConfermentSampo took 3.925766706466675s
Verifiability | Contribs. check for ConfermentSampo took 0.18187880516052246s
Interlinking | sameAs chians check for ConfermentSampo took 0.5009827613830566s
Interlinking | skos check for ConfermentSampo took 0.1629478931427002s
Interlinking | skos check for ConfermentSampo took 0.14776897430419922s
Timeliness | dataset update frequency check for ConfermentSampo took 0.18741750717163086s
Currency | Creation date check for ConfermentSampo took 0.41864991188049316s
Currency | Modification date check for ConfermentSampo took 0.40222764015197754s
Rep.Conc. | URIs length for ConfermentSampo took 85.14616894721985s
Interoperability | New vocabularies check for ConfermentSampo took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.1846003532409668s
Accuracy | Check Functional Property for ConfermentSampo took 0.1870594024658203s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.1565084457397461s
Accuracy | Check Empty annotation labels for ConfermentSampo took 50.47961735725403s
Accuracy | Check White space in annotation for ConfermentSampo took 3.017582654953003s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.261029243469238s
Consistency | Disjoint class check for ConfermentSampo took 0.16521286964416504s
Consistency | Check Misplaced properties for ConfermentSampo took 6.195409059524536s
Consistency | Check Ontology hijacking for ConfermentSampo took 53.404866218566895s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.3139584064483643s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.4241225719451904s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.849945068359375s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.1952202320098877s
Security | Sign check for ConfermentSampo took 0.1486663818359375s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1365.9737031459808s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.5471546649932861s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 2.1696090698242188e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 1.6689300537109375e-06s
Believability | Calculation of trust value for ConfermentSampo took 1.0967254638671875e-05s
INFO | --- Analysis for ConfermentSampo took 1929.641372203827s
Availability | SPARQL endpoint availability check for Museum Finland took 0.19913148880004883s
Availability | VoID file availability check for Museum Finland took 0.0002703666687011719s
Extra | Recovery of all triples for Museum Finland took 42.01087951660156s
Performance | Total latancy measurement for Museum Finland took 0.7817740440368652s
Amount of data | Number of triples check for Museum Finland took 0.3340294361114502s
Interoperability | New terms check for Museum Finland took 1.8434114456176758s
Versatility | Languages check for Museum Finland took 0.7135672569274902s
Interpretability | Number of blank nodes check for Museum Finland took 0.3253602981567383s
Security | Check HTTPS for Museum Finland took 0.22831201553344727s
Interpretability | RDF structures check for Museum Finland took 0.9286329746246338s
Versatility | Serialization formats check for Museum Finland took 0.19334697723388672s
Availability | RDF dump link check for Museum Finland took 0.15815043449401855s
License | MR license check for Museum Finland took 0.1505134105682373s
License | HR license check for Museum Finland took 0.45657968521118164s
Amount of data | Number of property check for Museum Finland took 0.1893913745880127s
Understandability | Number of label check for Museum Finland took 0.46364903450012207s
Understandability | URI regex check for Museum Finland took 0.31563711166381836s
Understandability | Vocabs check for Museum Finland took 0.1441333293914795s
Verifiability | Authors check for Museum Finland took 0.1592879295349121s
Verifiability | Publishers check for Museum Finland took 0.1448671817779541s
Performance | Throughput check for Museum Finland took 10.487237691879272s
Amount of data | Check the number of entities for Museum Finland took 7.104873657226562e-05s
Verifiability | Contribs. check for Museum Finland took 0.14448833465576172s
Interlinking | sameAs chians check for Museum Finland took 0.1676192283630371s
Interlinking | skos check for Museum Finland took 0.15300488471984863s
Interlinking | skos check for Museum Finland took 0.15613818168640137s
Timeliness | dataset update frequency check for Museum Finland took 0.15431571006774902s
Currency | Creation date check for Museum Finland took 0.3411836624145508s
Currency | Modification date check for Museum Finland took 0.33864545822143555s
Rep.Conc. | URIs length for Museum Finland took 6.913750410079956s
Interoperability | New vocabularies check for Museum Finland took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.1741178035736084s
Accuracy | Check Functional Property for Museum Finland took 0.15164518356323242s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.18225407600402832s
Accuracy | Check Empty annotation labels for Museum Finland took 1.8426520824432373s
Accuracy | Check White space in annotation for Museum Finland took 0.061995744705200195s
Accuracy | Check Datatype consistency for Museum Finland took 1.0107746124267578s
Consistency | Disjoint class check for Museum Finland took 0.1576836109161377s
Consistency | Check Misplaced properties for Museum Finland took 0.6203906536102295s
Consistency | Check Ontology hijacking for Museum Finland took 3.2426140308380127s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.5154786109924316s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.7300434112548828s
Conciseness | Check Extensional conciseness for Museum Finland took 0.699230432510376s
Conciseness | Check Intensional conciseness for Museum Finland took 0.2553074359893799s
Security | Sign check for Museum Finland took 0.14303159713745117s
Availability | Check URIs Dereferenciability for Museum Finland took 8.446850538253784s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.2668750286102295s
Reputation | Calculation of the PageRank for Museum Finland took 0.021221160888671875s
Interlinking | Calculation of Degree of Connection for Museum Finland took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 2.384185791015625e-06s
Believability | Calculation of trust value for Museum Finland took 7.62939453125e-06s
INFO | --- Analysis for FI-Museum took 105.56276655197144s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.17717576026916504s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0006058216094970703s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 145.82931065559387s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.7940723896026611s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 31.66936421394348s
Interoperability | New terms check for Mapping Manuscript Migrations took 4.659762144088745s
Versatility | Languages check for Mapping Manuscript Migrations took 79.43824124336243s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.934129238128662s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.3746359348297119s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.1849679946899414s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.17829155921936035s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.15891766548156738s
License | MR license check for Mapping Manuscript Migrations took 0.208282470703125s
License | HR license check for Mapping Manuscript Migrations took 1.8769853115081787s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.1979529857635498s
Understandability | Number of label check for Mapping Manuscript Migrations took 29.284064769744873s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3367493152618408s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.15973186492919922s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.1758427619934082s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.17605924606323242s
Performance | Throughput check for Mapping Manuscript Migrations took 10.526798248291016s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0908432006835938s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.16024160385131836s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 2.008221387863159s
Interlinking | skos check for Mapping Manuscript Migrations took 0.15274786949157715s
Interlinking | skos check for Mapping Manuscript Migrations took 0.15558981895446777s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.16730237007141113s
Currency | Creation date check for Mapping Manuscript Migrations took 0.35558056831359863s
Currency | Modification date check for Mapping Manuscript Migrations took 0.1824343204498291s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 82.04350113868713s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.1772165298461914s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.15946674346923828s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.15285873413085938s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 50.20375370979309s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.4393036365509033s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.74575662612915s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.19376564025878906s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 22.524471521377563s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 56.50686550140381s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.4116320610046387s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.4182672500610352s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.8375003337860107s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.18870210647583008s
Security | Sign check for Mapping Manuscript Migrations took 0.18990635871887207s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1555.2893314361572s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.7707343101501465s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.02117466926574707s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.049041748046875e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 1.6689300537109375e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.4781951904296875e-05s
INFO | --- Analysis for MMM took 2226.7773303985596s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.18407297134399414s
Availability | VoID file availability check for Semantic Kalevala took 0.00025081634521484375s
Extra | Recovery of all triples for Semantic Kalevala took 51.218788623809814s
Performance | Total latancy measurement for Semantic Kalevala took 0.7573440074920654s
Amount of data | Number of triples check for Semantic Kalevala took 0.4367389678955078s
Interoperability | New terms check for Semantic Kalevala took 1.979196310043335s
Versatility | Languages check for Semantic Kalevala took 1.0266079902648926s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.37312746047973633s
Security | Check HTTPS for Semantic Kalevala took 0.3849170207977295s
Interpretability | RDF structures check for Semantic Kalevala took 0.1830737590789795s
Versatility | Serialization formats check for Semantic Kalevala took 0.18343234062194824s
Availability | RDF dump link check for Semantic Kalevala took 0.18614673614501953s
License | MR license check for Semantic Kalevala took 0.181532621383667s
License | HR license check for Semantic Kalevala took 0.9961647987365723s
Amount of data | Number of property check for Semantic Kalevala took 0.182145357131958s
Understandability | Number of label check for Semantic Kalevala took 0.3629477024078369s
Understandability | URI regex check for Semantic Kalevala took 0.295133113861084s
Understandability | Vocabs check for Semantic Kalevala took 0.15968942642211914s
Verifiability | Authors check for Semantic Kalevala took 0.17206096649169922s
Verifiability | Publishers check for Semantic Kalevala took 0.15046310424804688s
Performance | Throughput check for Semantic Kalevala took 10.591752529144287s
Amount of data | Check the number of entities for Semantic Kalevala took 0.00013589859008789062s
Verifiability | Contribs. check for Semantic Kalevala took 0.14578580856323242s
Interlinking | sameAs chians check for Semantic Kalevala took 0.18245720863342285s
Interlinking | skos check for Semantic Kalevala took 0.2635023593902588s
Interlinking | skos check for Semantic Kalevala took 0.14899802207946777s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.15201950073242188s
Currency | Creation date check for Semantic Kalevala took 0.3408529758453369s
Currency | Modification date check for Semantic Kalevala took 0.32869434356689453s
Rep.Conc. | URIs length for Semantic Kalevala took 11.522088289260864s
Interoperability | New vocabularies check for Semantic Kalevala took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.20836472511291504s
Accuracy | Check Functional Property for Semantic Kalevala took 0.18120932579040527s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.15131688117980957s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 5.627905607223511s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.2962043285369873s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.3918662071228027s
Consistency | Disjoint class check for Semantic Kalevala took 0.14548492431640625s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7496576309204102s
Consistency | Check Ontology hijacking for Semantic Kalevala took 3.5922861099243164s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.2527837753295898s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.431185007095337s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.8872735500335693s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.1825714111328125s
Security | Sign check for Semantic Kalevala took 0.16034579277038574s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 3.3844001293182373s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.264509916305542s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.9073486328125e-06s
Believability | Calculation of trust value for Semantic Kalevala took 7.867813110351562e-06s
INFO | --- Analysis for Semantic-Kalevala took 119.46949243545532s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.9271621704101562s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0004413127899169922s
Extra | Recovery of all triples for Smithsonian American Art Museum took 287.9562129974365s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.2239012718200684s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.6038901805877686s
Interoperability | New terms check for Smithsonian American Art Museum took 4.011799573898315s
Versatility | Languages check for Smithsonian American Art Museum took 30.721927881240845s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.6016089916229248s
Security | Check HTTPS for Smithsonian American Art Museum took 0.35248780250549316s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.6820361614227295s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6612327098846436s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.6073861122131348s
License | MR license check for Smithsonian American Art Museum took 0.6609630584716797s
License | HR license check for Smithsonian American Art Museum took 19.753316164016724s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5752031803131104s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5955777168273926s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1838359832763672s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.604733943939209s
Verifiability | Authors check for Smithsonian American Art Museum took 0.608630895614624s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.5981168746948242s
Performance | Throughput check for Smithsonian American Art Museum took 11.868339538574219s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 9.202957153320312e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.5973596572875977s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5700511932373047s
Interlinking | skos check for Smithsonian American Art Museum took 0.6108593940734863s
Interlinking | skos check for Smithsonian American Art Museum took 0.6048703193664551s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5922715663909912s
Currency | Creation date check for Smithsonian American Art Museum took 1.3317968845367432s
Currency | Modification date check for Smithsonian American Art Museum took 1.2301361560821533s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 106.2562050819397s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.6323721408843994s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 25.717963933944702s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.5015952587127686s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.36189603805542s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5887207984924316s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 4.195537567138672s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 102.89123749732971s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.4797372817993164s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 4.7855751514434814s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.892396926879883s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.5984995365142822s
Security | Sign check for Smithsonian American Art Museum took 0.5745139122009277s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.3540565967559814s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.5093843936920166s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.2636184692382812e-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 8.344650268554688e-06s
INFO | --- Analysis for Smithsonian took 725.4137053489685s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.22635722160339355s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.28037333488464355s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.021025657653808594s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.2874603271484375e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 8.821487426757812e-06s
INFO | --- Analysis for Zeri-Photo-Archive took 8.096659660339355s
Availability | SPARQL endpoint availability check for Archives Hub took 20.73420000076294s
Availability | VoID file availability check for Archives Hub took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.27817344665527344s
Reputation | Calculation of the PageRank for Archives Hub took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.1682510375976562e-05s
Believability | Calculation of trust value for Archives Hub took 7.62939453125e-06s
INFO | --- Analysis for Archives-Hub took 53.88195753097534s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.2509644031524658s
Availability | VoID file availability check for Yale centre of British Art took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.26713061332702637s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.02102351188659668s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007350444793701172s
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 7.867813110351562e-06s
INFO | --- Analysis for Yale took 4.241371393203735s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 262.55716943740845s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.2722620964050293s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.021186351776123047s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 2.193450927734375e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 8.106231689453125e-06s
INFO | --- Analysis for ADL took 537.5341565608978s
Availability | SPARQL endpoint availability check for MusicKG took 0.6863365173339844s
Availability | VoID file availability check for MusicKG took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for MusicKG took 0.29213690757751465s
Reputation | Calculation of the PageRank for MusicKG took 0.020855188369750977s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.2159347534179688e-05s
Believability | Calculation of trust value for MusicKG took 6.9141387939453125e-06s
INFO | --- Analysis for MusicKG took 4.204655408859253s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.7354443073272705s
Availability | VoID file availability check for CIDOC-CRM took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.29891538619995117s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.1682510375976562e-05s
Believability | Calculation of trust value for CIDOC-CRM took 7.152557373046875e-06s
INFO | --- Analysis for CIDOC-CRM took 4.022621393203735s
Availability | SPARQL endpoint availability check for Mondis took 10.398826122283936s
Availability | VoID file availability check for Mondis took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Mondis took 0.2667417526245117s
Reputation | Calculation of the PageRank for Mondis took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for Mondis took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.3113021850585938e-05s
Believability | Calculation of trust value for Mondis took 7.867813110351562e-06s
INFO | --- Analysis for Mondis took 13.3654305934906s
Availability | SPARQL endpoint availability check for DigitalNZ took 0.18349766731262207s
Availability | VoID file availability check for DigitalNZ took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.28508663177490234s
Reputation | Calculation of the PageRank for DigitalNZ took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.239776611328125e-05s
Believability | Calculation of trust value for DigitalNZ took 7.867813110351562e-06s
INFO | --- Analysis for DigitalNZ took 4.170490980148315s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.18718647956848145s
Availability | VoID file availability check for Fondazione Zeri took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.26839113235473633s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020987272262573242s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0008611679077148438s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.4066696166992188e-05s
Believability | Calculation of trust value for Fondazione Zeri took 7.867813110351562e-06s
INFO | --- Analysis for Fondazione-Zeri took 3.2881124019622803s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 1.0874240398406982s
Availability | VoID file availability check for Digital Public Library of America took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.26979589462280273s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.1444091796875e-05s
Believability | Calculation of trust value for Digital Public Library of America took 6.67572021484375e-06s
INFO | --- Analysis for Library-of-America took 4.9775214195251465s
Availability | SPARQL endpoint availability check for Auckland Museum took 0.6793358325958252s
Availability | VoID file availability check for Auckland Museum took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.28595614433288574s
Reputation | Calculation of the PageRank for Auckland Museum took 0.020556211471557617s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0008940696716308594s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.239776611328125e-05s
Believability | Calculation of trust value for Auckland Museum took 7.867813110351562e-06s
INFO | --- Analysis for Auckland-Museum took 5.2782862186431885s
Availability | SPARQL endpoint availability check for National Library of Spain took 2.299240827560425s
Availability | VoID file availability check for National Library of Spain took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.30793118476867676s
Reputation | Calculation of the PageRank for National Library of Spain took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.2636184692382812e-05s
Believability | Calculation of trust value for National Library of Spain took 7.3909759521484375e-06s
INFO | --- Analysis for BNE took 5.395886182785034s
Availability | SPARQL endpoint availability check for National Library of Korea took 2.563406467437744s
Availability | VoID file availability check for National Library of Korea took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.2967545986175537s
Reputation | Calculation of the PageRank for National Library of Korea took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.0967254638671875e-05s
Believability | Calculation of trust value for National Library of Korea took 9.298324584960938e-06s
INFO | --- Analysis for Korea-Library took 5.50596022605896s
Availability | SPARQL endpoint availability check for The State Russian Museum took 2.853524684906006s
Availability | VoID file availability check for The State Russian Museum took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.3009645938873291s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.2874603271484375e-05s
Believability | Calculation of trust value for The State Russian Museum took 7.867813110351562e-06s
INFO | --- Analysis for Russian-Museum took 5.841951608657837s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.8895440101623535s
Availability | VoID file availability check for National Library of Scotland took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.26242971420288086s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.02079010009765625s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007581710815429688s
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 8.106231689453125e-06s
INFO | --- Analysis for National-Library-of-Scotland took 7.345394849777222s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.3979337215423584s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.2567424774169922s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.239776611328125e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 8.106231689453125e-06s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.4336512088775635s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.21105074882507324s
Availability | VoID file availability check for OntoComedySources took 0.0003724098205566406s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.27176785469055176s
Reputation | Calculation of the PageRank for OntoComedySources took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.239776611328125e-05s
Believability | Calculation of trust value for OntoComedySources took 8.106231689453125e-06s
INFO | --- Analysis for OntoComedySources took 3.983060836791992s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.21578192710876465s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.28319764137268066s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.02094864845275879s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.2874603271484375e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 8.821487426757812e-06s
INFO | --- Analysis for OntoCeramic-2.0 took 4.647528886795044s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.9747505187988281s
Availability | VoID file availability check for SaintGall Ontology took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.28389430046081543s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.021422386169433594s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0009284019470214844s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.3113021850585938e-05s
Believability | Calculation of trust value for SaintGall Ontology took 8.58306884765625e-06s
INFO | --- Analysis for SaintGall-Ontology took 3.960547685623169s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.8157508373260498s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.28166866302490234s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.3828277587890625e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 7.62939453125e-06s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 3.954071283340454s
Availability | SPARQL endpoint availability check for ICON took 0.26778697967529297s
Availability | VoID file availability check for ICON took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for ICON took 0.2795727252960205s
Reputation | Calculation of the PageRank for ICON took 0.02112579345703125s
Interlinking | Calculation of Degree of Connection for ICON took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for ICON took 1.2874603271484375e-05s
Believability | Calculation of trust value for ICON took 6.67572021484375e-06s
INFO | --- Analysis for ICON took 4.0093512535095215s
Availability | SPARQL endpoint availability check for Polifonia took 0.285381555557251s
Availability | VoID file availability check for Polifonia took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for Polifonia took 0.3035910129547119s
Reputation | Calculation of the PageRank for Polifonia took 0.02143263816833496s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.33514404296875e-05s
Believability | Calculation of trust value for Polifonia took 7.152557373046875e-06s
INFO | --- Analysis for Polifonia took 4.643102169036865s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.2542545795440674s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.3056905269622803s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.021286725997924805s
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.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.3589859008789062e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 7.152557373046875e-06s
INFO | --- Analysis for Atlas-of-Paths took 3.944979667663574s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.20056438446044922s
Availability | VoID file availability check for Music Note Ontology took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.28376102447509766s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.020750045776367188s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.1920928955078125e-05s
Believability | Calculation of trust value for Music Note Ontology took 7.152557373046875e-06s
INFO | --- Analysis for Music-Note-Ontology took 8.04809856414795s
Availability | SPARQL endpoint availability check for HaMSE took 0.2269885540008545s
Availability | VoID file availability check for HaMSE took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for HaMSE took 0.24988079071044922s
Reputation | Calculation of the PageRank for HaMSE took 0.02074599266052246s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.1444091796875e-05s
Believability | Calculation of trust value for HaMSE took 7.152557373046875e-06s
INFO | --- Analysis for HaMSE took 4.685831785202026s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.11090302467346191s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.2788417339324951s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.02084493637084961s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.1444091796875e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for FOod took 3.3519229888916016s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 1.1252667903900146s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.26894497871398926s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.3113021850585938e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 7.152557373046875e-06s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.47735857963562s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.5910413265228271s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.2648482322692871s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.020646333694458008s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.0967254638671875e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for ARIADNE took 5.692584276199341s
Availability | SPARQL endpoint availability check for MappingChange took 20.467029571533203s
Availability | VoID file availability check for MappingChange took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for MappingChange took 0.2805051803588867s
Reputation | Calculation of the PageRank for MappingChange took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for MappingChange took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for MappingChange took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for MappingChange took 1.1205673217773438e-05s
Believability | Calculation of trust value for MappingChange took 7.867813110351562e-06s
INFO | --- Analysis for mappingch took 53.64275860786438s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.39073920249938965s
Availability | VoID file availability check for Odeuropa Ontology took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.2526252269744873s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.02154088020324707s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.2636184692382812e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 7.152557373046875e-06s
INFO | --- Analysis for Odeuropa took 3.42592453956604s
Availability | SPARQL endpoint availability check for Continental European Books in Early Modern England, 1500-1640 took 0.5014152526855469s
Availability | VoID file availability check for Continental European Books in Early Modern England, 1500-1640 took 0.0002536773681640625s
Extra | Recovery of all triples for Continental European Books in Early Modern England, 1500-1640 took 91.24624133110046s
Performance | Total latancy measurement for Continental European Books in Early Modern England, 1500-1640 took 0.7898952960968018s
Amount of data | Number of triples check for Continental European Books in Early Modern England, 1500-1640 took 8.872303009033203s
Interoperability | New terms check for Continental European Books in Early Modern England, 1500-1640 took 9.090553045272827s
Versatility | Languages check for Continental European Books in Early Modern England, 1500-1640 took 10.885058164596558s
Interpretability | Number of blank nodes check for Continental European Books in Early Modern England, 1500-1640 took 6.354667663574219s
Interpretability | RDF structures check for Continental European Books in Early Modern England, 1500-1640 took 0.22775650024414062s
Versatility | Serialization formats check for Continental European Books in Early Modern England, 1500-1640 took 0.18492960929870605s
Availability | RDF dump link check for Continental European Books in Early Modern England, 1500-1640 took 1.6533219814300537s
License | MR license check for Continental European Books in Early Modern England, 1500-1640 took 0.15990757942199707s
License | HR license check for Continental European Books in Early Modern England, 1500-1640 took 0.33678436279296875s
Amount of data | Number of property check for Continental European Books in Early Modern England, 1500-1640 took 0.17586851119995117s
Understandability | Number of label check for Continental European Books in Early Modern England, 1500-1640 took 0.20570898056030273s
Understandability | URI regex check for Continental European Books in Early Modern England, 1500-1640 took 0.33426570892333984s
Understandability | Vocabs check for Continental European Books in Early Modern England, 1500-1640 took 0.15989279747009277s
Verifiability | Authors check for Continental European Books in Early Modern England, 1500-1640 took 0.17082715034484863s
Verifiability | Publishers check for Continental European Books in Early Modern England, 1500-1640 took 0.14948534965515137s
Performance | Throughput check for Continental European Books in Early Modern England, 1500-1640 took 11.274710416793823s
Amount of data | Check the number of entities for Continental European Books in Early Modern England, 1500-1640 took 1.0422053337097168s
Verifiability | Contribs. check for Continental European Books in Early Modern England, 1500-1640 took 0.1468822956085205s
Interlinking | sameAs chians check for Continental European Books in Early Modern England, 1500-1640 took 0.15688753128051758s
Interlinking | skos check for Continental European Books in Early Modern England, 1500-1640 took 0.1763753890991211s
Interlinking | skos check for Continental European Books in Early Modern England, 1500-1640 took 0.16231369972229004s
Timeliness | dataset update frequency check for Continental European Books in Early Modern England, 1500-1640 took 0.16646718978881836s
Currency | Creation date check for Continental European Books in Early Modern England, 1500-1640 took 0.32401251792907715s
Currency | Modification date check for Continental European Books in Early Modern England, 1500-1640 took 0.18523120880126953s
Rep.Conc. | URIs length for Continental European Books in Early Modern England, 1500-1640 took 41.59903645515442s
Consistency | Deprecated classes/propertiers check for Continental European Books in Early Modern England, 1500-1640 took 0.14818024635314941s
Accuracy | Check Functional Property for Continental European Books in Early Modern England, 1500-1640 took 0.17004966735839844s
Accuracy | Check Inverse Functional Property for Continental European Books in Early Modern England, 1500-1640 took 0.17053842544555664s
Accuracy | Check Empty annotation labels for Continental European Books in Early Modern England, 1500-1640 took 1.2014524936676025s
Accuracy | Check White space in annotation for Continental European Books in Early Modern England, 1500-1640 took 0.03582906723022461s
Accuracy | Check Datatype consistency for Continental European Books in Early Modern England, 1500-1640 took 4.584459543228149s
Consistency | Disjoint class check for Continental European Books in Early Modern England, 1500-1640 took 0.16163849830627441s
Consistency | Check Misplaced properties for Continental European Books in Early Modern England, 1500-1640 took 8.370905637741089s
Consistency | Check Ontology hijacking for Continental European Books in Early Modern England, 1500-1640 took 26.718559741973877s
Consistency | Check Invalid usage of undefined classes for Continental European Books in Early Modern England, 1500-1640 took 1.214052438735962s
Consistency | Check Invalid usage of undefined properties for Continental European Books in Early Modern England, 1500-1640 took 9.026218175888062s
Conciseness | Check Extensional conciseness for Continental European Books in Early Modern England, 1500-1640 took 2.8187191486358643s
Security | Sign check for Continental European Books in Early Modern England, 1500-1640 took 0.15042448043823242s
Availability | Check URIs Dereferenciability for Continental European Books in Early Modern England, 1500-1640 took 1497.6626138687134s
Completeness | Calculation of interlinking completeness for Continental European Books in Early Modern England, 1500-1640 took 0.5332133769989014s
Reputation | Calculation of the PageRank for Continental European Books in Early Modern England, 1500-1640 took 0.02147221565246582s
Interlinking | Calculation of Degree of Connection for Continental European Books in Early Modern England, 1500-1640 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Continental European Books in Early Modern England, 1500-1640 took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Continental European Books in Early Modern England, 1500-1640 took 1.1205673217773438e-05s
Believability | Calculation of trust value for Continental European Books in Early Modern England, 1500-1640 took 7.62939453125e-06s
INFO | --- Analysis for CEBEME took 1806.7537627220154s

--- Total time for analysis:676262.0188951492s ---
--- Total time for analysis:187.85056080420813 hours ---