Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.792213439941406e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0007395744323730469s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 1.5747342109680176s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.05374860763549805s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0008282661437988281s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0003826618194580078s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.1444091796875e-05s
INFO | --- Analysis for 0080-3626 took 12.901988506317139s
Availability | SPARQL endpoint availability check for 土地利用图 took 9.179115295410156e-05s
Availability | VoID file availability check for 土地利用图 took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for 土地利用图 took 1.8863072395324707s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020973682403564453s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0008776187896728516s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.4332275390625e-05s
Believability | Calculation of trust value for 土地利用图 took 1.1682510375976562e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 10.688583374023438s
Availability | SPARQL endpoint availability check for 113322 took 0.0001251697540283203s
Availability | VoID file availability check for 113322 took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for 113322 took 0.33811068534851074s
Reputation | Calculation of the PageRank for 113322 took 0.022239208221435547s
Interlinking | Calculation of Degree of Connection for 113322 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.765655517578125e-05s
Believability | Calculation of trust value for 113322 took 1.3113021850585938e-05s
INFO | --- Analysis for 11 took 5.232550859451294s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 9.107589721679688e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.00035190582275390625s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 3.330169439315796s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.021494626998901367s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.123283386230469e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.1920928955078125e-05s
INFO | --- Analysis for 12323 took 9.389394760131836s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.06632304191589355s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0003428459167480469s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.37460875511169434s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.749961853027344e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.0967254638671875e-05s
INFO | --- Analysis for 2000-us-census-rdf took 4.084418058395386s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.846412181854248s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 2.7014408111572266s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.02105879783630371s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0009565353393554688s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.9114227294921875e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 8.58306884765625e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 11.8995680809021s
Availability | SPARQL endpoint availability check for Open Data Web took 12.465930223464966s
Availability | VoID file availability check for Open Data Web took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.30613112449645996s
Reputation | Calculation of the PageRank for Open Data Web took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.24249267578125e-05s
Believability | Calculation of trust value for Open Data Web took 1.1205673217773438e-05s
INFO | --- Analysis for _data.odw.tw took 15.153508186340332s
Availability | SPARQL endpoint availability check for 土地利用 took 9.250640869140625e-05s
Availability | VoID file availability check for 土地利用 took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.3281223773956299s
Reputation | Calculation of the PageRank for 土地利用 took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for 土地利用 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 2.8848648071289062e-05s
Believability | Calculation of trust value for 土地利用 took 1.1444091796875e-05s
INFO | --- Analysis for _data1.odw.tw took 3.264258861541748s
Availability | SPARQL endpoint availability check for 土地利用模型 took 0.0001266002655029297s
Availability | VoID file availability check for 土地利用模型 took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 1.9771661758422852s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.0201718807220459s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.956390380859375e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.2159347534179688e-05s
INFO | --- Analysis for _data2.odw.tw took 10.539032936096191s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00010657310485839844s
Availability | VoID file availability check for Indian Biodiversity took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.583540678024292s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020195484161376953s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7179718017578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1444091796875e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 6.886895179748535s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 0.00010848045349121094s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.5805308818817139s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.6702880859375e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.0967254638671875e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 6.233237981796265s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 8.821487426757812e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.46908140182495117s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.123283386230469e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 1.1920928955078125e-05s
INFO | --- Analysis for A1 took 6.674308776855469s
Availability | SPARQL endpoint availability check for SummerOlympics took 2.65972638130188s
Availability | VoID file availability check for SummerOlympics took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for SummerOlympics took 2.036046266555786s
Reputation | Calculation of the PageRank for SummerOlympics took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.365776062011719e-05s
Believability | Calculation of trust value for SummerOlympics took 1.239776611328125e-05s
INFO | --- Analysis for abc took 13.582715272903442s
Availability | SPARQL endpoint availability check for Test_m took 9.012222290039062e-05s
Availability | VoID file availability check for Test_m took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Test_m took 0.32454776763916016s
Reputation | Calculation of the PageRank for Test_m took 0.022955656051635742s
Interlinking | Calculation of Degree of Connection for Test_m took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0010790824890136719s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.409385681152344e-05s
Believability | Calculation of trust value for Test_m took 1.2636184692382812e-05s
INFO | --- Analysis for ABC took 6.618637561798096s
Availability | SPARQL endpoint availability check for my intro took 8.845329284667969e-05s
Availability | VoID file availability check for my intro took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for my intro took 0.8369035720825195s
Reputation | Calculation of the PageRank for my intro took 0.021445274353027344s
Interlinking | Calculation of Degree of Connection for my intro took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for my intro took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for my intro took 2.765655517578125e-05s
Believability | Calculation of trust value for my intro took 1.1920928955078125e-05s
INFO | --- Analysis for abhay_intro took 5.249483346939087s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.10355305671691895s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.3231852054595947s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.022206544876098633s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010323524475097656s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for abs-linked-data took 3.2376046180725098s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 391.33285903930664s
Availability | VoID file availability check for Academic Offer of UNL took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 1.2868943214416504s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.5762786865234375e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.2636184692382812e-05s
INFO | --- Analysis for academic-offer-of-unl took 526.8045799732208s
Availability | SPARQL endpoint availability check for AcadOnto took 8.797645568847656e-05s
Availability | VoID file availability check for AcadOnto took 0.0007724761962890625s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.5115809440612793s
Reputation | Calculation of the PageRank for AcadOnto took 0.025819778442382812s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.266334533691406e-05s
Believability | Calculation of trust value for AcadOnto took 1.1205673217773438e-05s
INFO | --- Analysis for acadonto took 5.307428598403931s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.206868886947632s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.5934629440307617s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.3548102378845215s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.02120351791381836s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.315376281738281e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for acorn-sat took 36.016480922698975s
Availability | SPARQL endpoint availability check for Addgene took 8.678436279296875e-05s
Availability | VoID file availability check for Addgene took 0.0008060932159423828s
Completeness | Calculation of interlinking completeness for Addgene took 0.6273891925811768s
Reputation | Calculation of the PageRank for Addgene took 0.021290302276611328s
Interlinking | Calculation of Degree of Connection for Addgene took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0009694099426269531s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.220008850097656e-05s
Believability | Calculation of trust value for Addgene took 1.1920928955078125e-05s
INFO | --- Analysis for addgene took 19.254913806915283s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 8.7738037109375e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.8724470138549805s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.3811066150665283s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.021317005157470703s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.489059448242188e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.2159347534179688e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 8.190432786941528s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.4029722213745117s
Availability | VoID file availability check for AEMET metereological dataset took 0.23930859565734863s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.3113570213317871s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020144224166870117s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.4809112548828125e-05s
Interoperability | Check the re-using of existing vocabs for AEMET metereological dataset took 2.384185791015625e-06s
Believability | Calculation of trust value for AEMET metereological dataset took 1.5735626220703125e-05s
INFO | --- Analysis for aemet took 5.357422351837158s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 9.083747863769531e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 1.6477510929107666s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 2.7894973754882812e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 1.1920928955078125e-05s
INFO | --- Analysis for agenda-de-zaragoza took 7.56414270401001s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.039072275161743164s
Availability | VoID file availability check for AgriNepalData took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.4675276279449463s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020836830139160156s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.271766662597656e-05s
Believability | Calculation of trust value for AgriNepalData took 1.1682510375976562e-05s
INFO | --- Analysis for agrinepaldata took 2.7750680446624756s
Availability | SPARQL endpoint availability check for AGRIS took 262.854243516922s
Availability | VoID file availability check for AGRIS took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for AGRIS took 0.6782317161560059s
Reputation | Calculation of the PageRank for AGRIS took 0.02618551254272461s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0013165473937988281s
Interlinking | Calculation of Clustering coefficient for AGRIS took 0.00010156631469726562s
Believability | Calculation of trust value for AGRIS took 1.2874603271484375e-05s
INFO | --- Analysis for agris took 434.9240577220917s
Availability | SPARQL endpoint availability check for AGROVOC took 0.1429288387298584s
Availability | VoID file availability check for AGROVOC took 0.0005471706390380859s
Extra | Recovery of all triples for AGROVOC took 28.184093952178955s
Performance | Total latancy measurement for AGROVOC took 0.4219799041748047s
Amount of data | Number of triples check for AGROVOC took 18.311718225479126s
Interoperability | New terms check for AGROVOC took 2.8953609466552734s
Versatility | Languages check for AGROVOC took 77.76648664474487s
Interpretability | Number of blank nodes check for AGROVOC took 20.505142211914062s
Interpretability | RDF structures check for AGROVOC took 0.09996318817138672s
Versatility | Serialization formats check for AGROVOC took 0.1370394229888916s
Availability | RDF dump link check for AGROVOC took 0.0872201919555664s
License | MR license check for AGROVOC took 0.08738422393798828s
License | HR license check for AGROVOC took 0.645050048828125s
Amount of data | Number of property check for AGROVOC took 0.0902559757232666s
Understandability | Number of label check for AGROVOC took 53.50935244560242s
Understandability | URI regex check for AGROVOC took 0.165252685546875s
Understandability | Vocabs check for AGROVOC took 0.0881342887878418s
Verifiability | Authors check for AGROVOC took 0.08731412887573242s
Verifiability | Publishers check for AGROVOC took 0.08781123161315918s
Performance | Throughput check for AGROVOC took 10.361539602279663s
Amount of data | Check the number of entities for AGROVOC took 0.0001621246337890625s
Verifiability | Contribs. check for AGROVOC took 0.08542656898498535s
Interlinking | sameAs chians check for AGROVOC took 0.07468080520629883s
Interlinking | skos check for AGROVOC took 0.927720308303833s
Interlinking | skos check for AGROVOC took 0.20722126960754395s
Timeliness | dataset update frequency check for AGROVOC took 0.08945941925048828s
Currency | Creation date check for AGROVOC took 0.17516613006591797s
Currency | Modification date check for AGROVOC took 0.163482666015625s
Rep.Conc. | URIs length for AGROVOC took 53.26382374763489s
Interoperability | New vocabularies check for AGROVOC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.07566452026367188s
Accuracy | Check Functional Property for AGROVOC took 0.08779501914978027s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.08743619918823242s
Accuracy | Check Empty annotation labels for AGROVOC took 26.173304557800293s
Accuracy | Check White space in annotation for AGROVOC took 2.9891409873962402s
Accuracy | Check Datatype consistency for AGROVOC took 4.60439920425415s
Consistency | Disjoint class check for AGROVOC took 0.11265254020690918s
Consistency | Check Misplaced properties for AGROVOC took 17.457780599594116s
Consistency | Check Ontology hijacking for AGROVOC took 29.127864837646484s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.5337004661560059s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 18.944746017456055s
Conciseness | Check Extensional conciseness for AGROVOC took 2.6085546016693115s
Conciseness | Check Intensional conciseness for AGROVOC took 0.08541107177734375s
Security | Sign check for AGROVOC took 0.09862565994262695s
Availability | Check URIs Dereferenciability for AGROVOC took 18.373785257339478s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.34000134468078613s
Reputation | Calculation of the PageRank for AGROVOC took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.000118255615234375s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.9073486328125e-06s
Believability | Calculation of trust value for AGROVOC took 1.1920928955078125e-05s
INFO | --- Analysis for agrovoc took 725.1456317901611s
Availability | SPARQL endpoint availability check for AGROVOC took 8.606910705566406e-05s
Availability | VoID file availability check for AGROVOC took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for AGROVOC took 1.5120728015899658s
Reputation | Calculation of the PageRank for AGROVOC took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.817413330078125e-05s
Believability | Calculation of trust value for AGROVOC took 5.7220458984375e-05s
INFO | --- Analysis for agrovoc-skos took 12.000202178955078s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 0.9703238010406494s
Availability | VoID file availability check for Analytics India Magazine took 0.0006315708160400391s
Extra | Recovery of all triples for Analytics India Magazine took 2.1825361251831055s
Performance | Total latancy measurement for Analytics India Magazine took 2.5867233276367188s
Amount of data | Number of triples check for Analytics India Magazine took 1.1955478191375732s
Versatility | Languages check for Analytics India Magazine took 1.428396224975586s
Interpretability | Number of blank nodes check for Analytics India Magazine took 0.8956413269042969s
Interpretability | RDF structures check for Analytics India Magazine took 1.0043573379516602s
Versatility | Serialization formats check for Analytics India Magazine took 1.1573903560638428s
Availability | RDF dump link check for Analytics India Magazine took 1.08099365234375s
License | MR license check for Analytics India Magazine took 1.0124714374542236s
License | HR license check for Analytics India Magazine took 0.8532810211181641s
Amount of data | Number of property check for Analytics India Magazine took 1.3265676498413086s
Understandability | Number of label check for Analytics India Magazine took 1.5518383979797363s
Understandability | URI regex check for Analytics India Magazine took 2.067277193069458s
Understandability | Vocabs check for Analytics India Magazine took 1.016890048980713s
Verifiability | Authors check for Analytics India Magazine took 1.4956920146942139s
Verifiability | Publishers check for Analytics India Magazine took 1.119093656539917s
Performance | Throughput check for Analytics India Magazine took 15.66731071472168s
Amount of data | Check the number of entities for Analytics India Magazine took 0.0001220703125s
Verifiability | Contribs. check for Analytics India Magazine took 0.987025260925293s
Interlinking | sameAs chians check for Analytics India Magazine took 0.984882116317749s
Interlinking | skos check for Analytics India Magazine took 0.9198493957519531s
Interlinking | skos check for Analytics India Magazine took 1.063598394393921s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.031487226486206s
Currency | Creation date check for Analytics India Magazine took 2.014261245727539s
Currency | Modification date check for Analytics India Magazine took 2.1384530067443848s
Rep.Conc. | URIs length for Analytics India Magazine took 1.8115949630737305s
Interoperability | New vocabularies check for Analytics India Magazine took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 0.8410813808441162s
Consistency | Disjoint class check for Analytics India Magazine took 1.0307247638702393s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.2357890605926514s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.8261966705322266s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.00015854835510253906s
Security | Sign check for Analytics India Magazine took 1.0488507747650146s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 1.3070642948150635s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020025014877319336s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 2.8371810913085938e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 4.76837158203125e-07s
Believability | Calculation of trust value for Analytics India Magazine took 1.239776611328125e-05s
INFO | --- Analysis for AIM took 104.27188658714294s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 261.1142065525055s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.3632035255432129s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.021118879318237305s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.4809112548828125e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.0251998901367188e-05s
INFO | --- Analysis for AISHE took 275.14339232444763s
Availability | SPARQL endpoint availability check for  equipment ontology took 0.00013136863708496094s
Availability | VoID file availability check for  equipment ontology took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for  equipment ontology took 1.022688388824463s
Reputation | Calculation of the PageRank for  equipment ontology took 0.021396875381469727s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for  equipment ontology took 1.1205673217773438e-05s
INFO | --- Analysis for akash took 6.2019031047821045s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 1.4810993671417236s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.0007593631744384766s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.4302403926849365s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.02740335464477539s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0014345645904541016s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 5.3882598876953125e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 1.1682510375976562e-05s
INFO | --- Analysis for aksworg took 12.380505084991455s
Availability | SPARQL endpoint availability check for AlchemyAPI took 0.00043892860412597656s
Availability | VoID file availability check for AlchemyAPI took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.299152135848999s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.03519463539123535s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 2.288818359375e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.001596689224243164s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 6.29425048828125e-05s
Believability | Calculation of trust value for AlchemyAPI took 1.2874603271484375e-05s
INFO | --- Analysis for alchemyapi took 4.149213790893555s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 392.4121997356415s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0007770061492919922s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.38777613639831543s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.021035432815551758s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.933906555175781e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 1.1444091796875e-05s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 528.111387014389s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 262.38402032852173s
Availability | VoID file availability check for aliada-scanbit-net took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 2.1773059368133545s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.023012399673461914s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00011944770812988281s
Believability | Calculation of trust value for aliada-scanbit-net took 1.2159347534179688e-05s
INFO | --- Analysis for aliada-scanbit-net took 1314.4101164340973s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.4345855712890625e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 1.4300167560577393s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.021232128143310547s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.7894973754882812e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 1.049041748046875e-05s
INFO | --- Analysis for allen-brain-atlas took 16.527545928955078s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.8539886474609375s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006525516510009766s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 109.97404217720032s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.704430341720581s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.6091783046722412s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.4989144802093506s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.04643988609314s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.1662514209747314s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8631994724273682s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.5818560123443604s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6351490020751953s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5746862888336182s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5739181041717529s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 30.528403520584106s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5769927501678467s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7706139087677002s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1486375331878662s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5684843063354492s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.5727548599243164s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5736503601074219s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.773961067199707s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 7.534027099609375e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5709304809570312s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5686604976654053s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5830528736114502s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5525424480438232s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5834522247314453s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.1473972797393799s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1470947265625s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 42.37182354927063s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5594072341918945s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6356697082519531s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6733894348144531s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 34.549660205841064s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.069091558456421s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.6494734287261963s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6202044486999512s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.148078203201294s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.743293046951294s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 31.058125972747803s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3963873386383057s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.011295080184937s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.841216802597046s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8430907726287842s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5553321838378906s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 13341.701761245728s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.4926011562347412s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.022046566009521484s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.153915405273438e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 5.7220458984375e-06s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.1444091796875e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 14041.217145681381s
Availability | SPARQL endpoint availability check for Alojamientos took 8.845329284667969e-05s
Availability | VoID file availability check for Alojamientos took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Alojamientos took 1.2839534282684326s
Reputation | Calculation of the PageRank for Alojamientos took 0.023340463638305664s
Interlinking | Calculation of Degree of Connection for Alojamientos took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 2.9325485229492188e-05s
Believability | Calculation of trust value for Alojamientos took 1.3589859008789062e-05s
INFO | --- Analysis for alojamientos-zaragoza took 6.521904945373535s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.28032708168029785s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.41356492042541504s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.02041769027709961s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.981590270996094e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.1920928955078125e-05s
INFO | --- Analysis for alpino-rdf took 4.144426107406616s
Availability | SPARQL endpoint availability check for AAT-atawil took 0.000102996826171875s
Availability | VoID file availability check for AAT-atawil took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.899376392364502s
Reputation | Calculation of the PageRank for AAT-atawil took 0.021111249923706055s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 2.9325485229492188e-05s
Believability | Calculation of trust value for AAT-atawil took 1.239776611328125e-05s
INFO | --- Analysis for Altawil took 7.992465496063232s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 5.989594459533691s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 2.3455960750579834s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 2.9087066650390625e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 1.1920928955078125e-05s
INFO | --- Analysis for am-collections-online took 15.532167673110962s
Availability | SPARQL endpoint availability check for Amer Nejma took 8.821487426757812e-05s
Availability | VoID file availability check for Amer Nejma took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.3519477844238281s
Reputation | Calculation of the PageRank for Amer Nejma took 0.021214723587036133s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 2.8371810913085938e-05s
Believability | Calculation of trust value for Amer Nejma took 1.1444091796875e-05s
INFO | --- Analysis for Amer_Nejma took 4.592875957489014s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.001336812973022461s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.707836389541626s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.02136540412902832s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.218650817871094e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for amon took 11.067616939544678s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7307209968566895s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.6476452350616455s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 8.797645568847656e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.1444091796875e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 6.415078163146973s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00040984153747558594s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.35912108421325684s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 2.8133392333984375e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 1.1682510375976562e-05s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 4.880175590515137s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 8.988380432128906e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 1.706038475036621s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.03005051612854004s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.00211334228515625s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 4.6253204345703125e-05s
Believability | Calculation of trust value for Animal Diversity Web took 1.0967254638671875e-05s
INFO | --- Analysis for animal-diversity-web took 18.958329916000366s
Availability | SPARQL endpoint availability check for Anime Dataset took 8.845329284667969e-05s
Availability | VoID file availability check for Anime Dataset took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Anime Dataset took 4.109732627868652s
Reputation | Calculation of the PageRank for Anime Dataset took 0.02092456817626953s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0008559226989746094s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for Anime Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Anime took 14.42644190788269s
Availability | SPARQL endpoint availability check for ANNO took 8.869171142578125e-05s
Availability | VoID file availability check for ANNO took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for ANNO took 0.5824754238128662s
Reputation | Calculation of the PageRank for ANNO took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for ANNO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ANNO took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.528594970703125e-05s
Believability | Calculation of trust value for ANNO took 1.1444091796875e-05s
INFO | --- Analysis for anno took 9.526800155639648s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 9.059906005859375e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.5315706729888916s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.796287536621094e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.2636184692382812e-05s
INFO | --- Analysis for AntiqueCarsCollection took 4.503783702850342s
Availability | SPARQL endpoint availability check for apache took 9.131431579589844e-05s
Availability | VoID file availability check for apache took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for apache took 0.3391423225402832s
Reputation | Calculation of the PageRank for apache took 0.02361440658569336s
Interlinking | Calculation of Degree of Connection for apache took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for apache took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for apache took 6.198883056640625e-05s
Believability | Calculation of trust value for apache took 1.1682510375976562e-05s
INFO | --- Analysis for apache took 3.083620071411133s
Availability | SPARQL endpoint availability check for Apertium RDF took 1.2694342136383057s
Availability | VoID file availability check for Apertium RDF took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.7653951644897461s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0008563995361328125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 5.0067901611328125e-05s
Believability | Calculation of trust value for Apertium RDF took 1.1444091796875e-05s
INFO | --- Analysis for apertium-rdf took 19.265292644500732s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 0.39073657989501953s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006890296936035156s
Extra | Recovery of all triples for Apertium RDF CA-IT took 263.6281461715698s
Performance | Total latancy measurement for Apertium RDF CA-IT took 1.2372214794158936s
Amount of data | Number of triples check for Apertium RDF CA-IT took 2.1287035942077637s
Interoperability | New terms check for Apertium RDF CA-IT took 3.178509473800659s
Versatility | Languages check for Apertium RDF CA-IT took 44.2562894821167s
Interpretability | Number of blank nodes check for Apertium RDF CA-IT took 1.091848611831665s
Security | Check HTTPS for Apertium RDF CA-IT took 0.13679027557373047s
Interpretability | RDF structures check for Apertium RDF CA-IT took 0.2958221435546875s
Versatility | Serialization formats check for Apertium RDF CA-IT took 0.30619192123413086s
Availability | RDF dump link check for Apertium RDF CA-IT took 0.28833866119384766s
License | MR license check for Apertium RDF CA-IT took 0.28931522369384766s
License | HR license check for Apertium RDF CA-IT took 0.4074232578277588s
Amount of data | Number of property check for Apertium RDF CA-IT took 0.29881858825683594s
Understandability | Number of label check for Apertium RDF CA-IT took 0.323336124420166s
Understandability | URI regex check for Apertium RDF CA-IT took 0.5725195407867432s
Understandability | Vocabs check for Apertium RDF CA-IT took 0.27701330184936523s
Verifiability | Authors check for Apertium RDF CA-IT took 0.30087733268737793s
Verifiability | Publishers check for Apertium RDF CA-IT took 0.2945234775543213s
Performance | Throughput check for Apertium RDF CA-IT took 11.414533138275146s
Amount of data | Check the number of entities for Apertium RDF CA-IT took 7.2479248046875e-05s
Verifiability | Contribs. check for Apertium RDF CA-IT took 0.2881443500518799s
Interlinking | sameAs chians check for Apertium RDF CA-IT took 0.28653931617736816s
Interlinking | skos check for Apertium RDF CA-IT took 0.3202641010284424s
Interlinking | skos check for Apertium RDF CA-IT took 0.2061614990234375s
Timeliness | dataset update frequency check for Apertium RDF CA-IT took 0.3021833896636963s
Currency | Creation date check for Apertium RDF CA-IT took 0.5884320735931396s
Currency | Modification date check for Apertium RDF CA-IT took 0.6089978218078613s
Rep.Conc. | URIs length for Apertium RDF CA-IT took 89.29072761535645s
Interoperability | New vocabularies check for Apertium RDF CA-IT took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF CA-IT took 0.3245973587036133s
Accuracy | Check Functional Property for Apertium RDF CA-IT took 0.27812743186950684s
Accuracy | Check Inverse Functional Property for Apertium RDF CA-IT took 0.3015170097351074s
Accuracy | Check Empty annotation labels for Apertium RDF CA-IT took 0.787628173828125s
Accuracy | Check White space in annotation for Apertium RDF CA-IT took 0.01001739501953125s
Accuracy | Check Datatype consistency for Apertium RDF CA-IT took 2.603424310684204s
Consistency | Disjoint class check for Apertium RDF CA-IT took 0.2851893901824951s
Consistency | Check Misplaced properties for Apertium RDF CA-IT took 4.617088317871094s
Consistency | Misplaced classes for Apertium RDF CA-IT took 8.413787841796875s
Consistency | Check Ontology hijacking for Apertium RDF CA-IT took 90.26782608032227s
Consistency | Check Invalid usage of undefined classes for Apertium RDF CA-IT took 1.488685131072998s
Consistency | Check Invalid usage of undefined properties for Apertium RDF CA-IT took 5.6588897705078125s
Conciseness | Check Extensional conciseness for Apertium RDF CA-IT took 2.8762423992156982s
Conciseness | Check Intensional conciseness for Apertium RDF CA-IT took 0.3190641403198242s
Security | Sign check for Apertium RDF CA-IT took 0.29243946075439453s
Availability | Check URIs Dereferenciability for Apertium RDF CA-IT took 10.25871992111206s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.6815009117126465s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020931243896484375s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF CA-IT took 1.1920928955078125e-06s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 636.82856798172s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 0.22812461853027344s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006568431854248047s
Extra | Recovery of all triples for Apertium RDF EN-CA took 265.4109077453613s
Performance | Total latancy measurement for Apertium RDF EN-CA took 1.248157262802124s
Amount of data | Number of triples check for Apertium RDF EN-CA took 2.220977306365967s
Interoperability | New terms check for Apertium RDF EN-CA took 2.894162893295288s
Versatility | Languages check for Apertium RDF EN-CA took 44.23626446723938s
Interpretability | Number of blank nodes check for Apertium RDF EN-CA took 1.2392566204071045s
Security | Check HTTPS for Apertium RDF EN-CA took 0.1251225471496582s
Interpretability | RDF structures check for Apertium RDF EN-CA took 0.30307936668395996s
Versatility | Serialization formats check for Apertium RDF EN-CA took 0.2926521301269531s
Availability | RDF dump link check for Apertium RDF EN-CA took 0.30205368995666504s
License | MR license check for Apertium RDF EN-CA took 0.302933931350708s
License | HR license check for Apertium RDF EN-CA took 0.3756701946258545s
Amount of data | Number of property check for Apertium RDF EN-CA took 0.2914848327636719s
Understandability | Number of label check for Apertium RDF EN-CA took 0.3254389762878418s
Understandability | URI regex check for Apertium RDF EN-CA took 0.5935497283935547s
Understandability | Vocabs check for Apertium RDF EN-CA took 0.2946774959564209s
Verifiability | Authors check for Apertium RDF EN-CA took 0.29148292541503906s
Verifiability | Publishers check for Apertium RDF EN-CA took 0.28615617752075195s
Performance | Throughput check for Apertium RDF EN-CA took 11.180920362472534s
Amount of data | Check the number of entities for Apertium RDF EN-CA took 6.341934204101562e-05s
Verifiability | Contribs. check for Apertium RDF EN-CA took 0.2899811267852783s
Interlinking | sameAs chians check for Apertium RDF EN-CA took 0.30416369438171387s
Interlinking | skos check for Apertium RDF EN-CA took 0.28877997398376465s
Interlinking | skos check for Apertium RDF EN-CA took 0.2236647605895996s
Timeliness | dataset update frequency check for Apertium RDF EN-CA took 0.2962653636932373s
Currency | Creation date check for Apertium RDF EN-CA took 0.6020209789276123s
Currency | Modification date check for Apertium RDF EN-CA took 0.5927894115447998s
Rep.Conc. | URIs length for Apertium RDF EN-CA took 86.35098767280579s
Interoperability | New vocabularies check for Apertium RDF EN-CA took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-CA took 0.3318791389465332s
Accuracy | Check Functional Property for Apertium RDF EN-CA took 0.2905538082122803s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-CA took 0.28856825828552246s
Accuracy | Check Empty annotation labels for Apertium RDF EN-CA took 0.85433030128479s
Accuracy | Check White space in annotation for Apertium RDF EN-CA took 0.010046720504760742s
Accuracy | Check Datatype consistency for Apertium RDF EN-CA took 2.6776437759399414s
Consistency | Disjoint class check for Apertium RDF EN-CA took 0.29955196380615234s
Consistency | Check Misplaced properties for Apertium RDF EN-CA took 4.706600189208984s
Consistency | Misplaced classes for Apertium RDF EN-CA took 8.435390710830688s
Consistency | Check Ontology hijacking for Apertium RDF EN-CA took 91.50314736366272s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-CA took 1.530013084411621s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-CA took 5.634869337081909s
Conciseness | Check Extensional conciseness for Apertium RDF EN-CA took 2.9697790145874023s
Conciseness | Check Intensional conciseness for Apertium RDF EN-CA took 0.33254170417785645s
Security | Sign check for Apertium RDF EN-CA took 0.2902047634124756s
Availability | Check URIs Dereferenciability for Apertium RDF EN-CA took 9.846752166748047s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.3534858226776123s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.02097940444946289s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 630.0700356960297s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 0.23183441162109375s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0005223751068115234s
Extra | Recovery of all triples for Apertium RDF EN-ES took 264.90843200683594s
Performance | Total latancy measurement for Apertium RDF EN-ES took 1.2764406204223633s
Amount of data | Number of triples check for Apertium RDF EN-ES took 2.256645679473877s
Interoperability | New terms check for Apertium RDF EN-ES took 2.8926851749420166s
Versatility | Languages check for Apertium RDF EN-ES took 44.05761957168579s
Interpretability | Number of blank nodes check for Apertium RDF EN-ES took 1.0701045989990234s
Security | Check HTTPS for Apertium RDF EN-ES took 0.12251996994018555s
Interpretability | RDF structures check for Apertium RDF EN-ES took 0.30828142166137695s
Versatility | Serialization formats check for Apertium RDF EN-ES took 0.2991204261779785s
Availability | RDF dump link check for Apertium RDF EN-ES took 0.2849106788635254s
License | MR license check for Apertium RDF EN-ES took 0.29206395149230957s
License | HR license check for Apertium RDF EN-ES took 0.3791978359222412s
Amount of data | Number of property check for Apertium RDF EN-ES took 0.316605806350708s
Understandability | Number of label check for Apertium RDF EN-ES took 0.32063889503479004s
Understandability | URI regex check for Apertium RDF EN-ES took 0.578495979309082s
Understandability | Vocabs check for Apertium RDF EN-ES took 0.294497013092041s
Verifiability | Authors check for Apertium RDF EN-ES took 0.2949182987213135s
Verifiability | Publishers check for Apertium RDF EN-ES took 0.2817213535308838s
Performance | Throughput check for Apertium RDF EN-ES took 11.22569727897644s
Amount of data | Check the number of entities for Apertium RDF EN-ES took 7.128715515136719e-05s
Verifiability | Contribs. check for Apertium RDF EN-ES took 0.2818937301635742s
Interlinking | sameAs chians check for Apertium RDF EN-ES took 0.2979722023010254s
Interlinking | skos check for Apertium RDF EN-ES took 0.29442548751831055s
Interlinking | skos check for Apertium RDF EN-ES took 0.23901796340942383s
Timeliness | dataset update frequency check for Apertium RDF EN-ES took 0.3005235195159912s
Currency | Creation date check for Apertium RDF EN-ES took 0.5627548694610596s
Currency | Modification date check for Apertium RDF EN-ES took 0.6088972091674805s
Rep.Conc. | URIs length for Apertium RDF EN-ES took 89.63183403015137s
Interoperability | New vocabularies check for Apertium RDF EN-ES took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-ES took 0.307389497756958s
Accuracy | Check Functional Property for Apertium RDF EN-ES took 0.2819857597351074s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-ES took 0.2974245548248291s
Accuracy | Check Empty annotation labels for Apertium RDF EN-ES took 0.8578479290008545s
Accuracy | Check White space in annotation for Apertium RDF EN-ES took 0.010241985321044922s
Accuracy | Check Datatype consistency for Apertium RDF EN-ES took 2.674039840698242s
Consistency | Disjoint class check for Apertium RDF EN-ES took 0.3116140365600586s
Consistency | Check Misplaced properties for Apertium RDF EN-ES took 4.700394630432129s
Consistency | Misplaced classes for Apertium RDF EN-ES took 8.475648164749146s
Consistency | Check Ontology hijacking for Apertium RDF EN-ES took 90.92001938819885s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-ES took 1.5195116996765137s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-ES took 5.965438365936279s
Conciseness | Check Extensional conciseness for Apertium RDF EN-ES took 3.0108697414398193s
Conciseness | Check Intensional conciseness for Apertium RDF EN-ES took 0.3527841567993164s
Security | Sign check for Apertium RDF EN-ES took 0.281170129776001s
Availability | Check URIs Dereferenciability for Apertium RDF EN-ES took 10.215987205505371s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.5410656929016113s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.021724462509155273s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0010495185852050781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 6.389617919921875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-ES took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-en-es took 630.3060686588287s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 0.22216439247131348s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0007181167602539062s
Extra | Recovery of all triples for Apertium RDF EN-GL took 262.3765478134155s
Performance | Total latancy measurement for Apertium RDF EN-GL took 1.276545763015747s
Amount of data | Number of triples check for Apertium RDF EN-GL took 2.252748727798462s
Interoperability | New terms check for Apertium RDF EN-GL took 2.982264518737793s
Versatility | Languages check for Apertium RDF EN-GL took 43.98879146575928s
Interpretability | Number of blank nodes check for Apertium RDF EN-GL took 1.1735870838165283s
Security | Check HTTPS for Apertium RDF EN-GL took 0.14705371856689453s
Interpretability | RDF structures check for Apertium RDF EN-GL took 0.29533815383911133s
Versatility | Serialization formats check for Apertium RDF EN-GL took 0.30214595794677734s
Availability | RDF dump link check for Apertium RDF EN-GL took 0.2884199619293213s
License | MR license check for Apertium RDF EN-GL took 0.28317761421203613s
License | HR license check for Apertium RDF EN-GL took 0.36029505729675293s
Amount of data | Number of property check for Apertium RDF EN-GL took 0.2940361499786377s
Understandability | Number of label check for Apertium RDF EN-GL took 0.33080172538757324s
Understandability | URI regex check for Apertium RDF EN-GL took 0.5620541572570801s
Understandability | Vocabs check for Apertium RDF EN-GL took 0.2843778133392334s
Verifiability | Authors check for Apertium RDF EN-GL took 0.2895228862762451s
Verifiability | Publishers check for Apertium RDF EN-GL took 0.28949570655822754s
Performance | Throughput check for Apertium RDF EN-GL took 11.342350244522095s
Amount of data | Check the number of entities for Apertium RDF EN-GL took 3.361701965332031e-05s
Verifiability | Contribs. check for Apertium RDF EN-GL took 0.30529141426086426s
Interlinking | sameAs chians check for Apertium RDF EN-GL took 0.28873682022094727s
Interlinking | skos check for Apertium RDF EN-GL took 0.27069616317749023s
Interlinking | skos check for Apertium RDF EN-GL took 0.21406316757202148s
Timeliness | dataset update frequency check for Apertium RDF EN-GL took 0.2824137210845947s
Currency | Creation date check for Apertium RDF EN-GL took 0.6045382022857666s
Currency | Modification date check for Apertium RDF EN-GL took 0.5801725387573242s
Rep.Conc. | URIs length for Apertium RDF EN-GL took 93.9988420009613s
Interoperability | New vocabularies check for Apertium RDF EN-GL took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-GL took 0.3453226089477539s
Accuracy | Check Functional Property for Apertium RDF EN-GL took 0.3008687496185303s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-GL took 0.3061177730560303s
Accuracy | Check Empty annotation labels for Apertium RDF EN-GL took 0.8408455848693848s
Accuracy | Check White space in annotation for Apertium RDF EN-GL took 0.010048151016235352s
Accuracy | Check Datatype consistency for Apertium RDF EN-GL took 2.6887471675872803s
Consistency | Disjoint class check for Apertium RDF EN-GL took 0.26887059211730957s
Consistency | Check Misplaced properties for Apertium RDF EN-GL took 6.732646703720093s
Consistency | Misplaced classes for Apertium RDF EN-GL took 8.538161754608154s
Consistency | Check Ontology hijacking for Apertium RDF EN-GL took 92.07264161109924s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-GL took 1.5290820598602295s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-GL took 5.831133127212524s
Conciseness | Check Extensional conciseness for Apertium RDF EN-GL took 3.076320171356201s
Conciseness | Check Intensional conciseness for Apertium RDF EN-GL took 0.3282053470611572s
Security | Sign check for Apertium RDF EN-GL took 0.295198917388916s
Availability | Check URIs Dereferenciability for Apertium RDF EN-GL took 10.485451698303223s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.4655792713165283s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020892620086669922s
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.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 5.2928924560546875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-GL took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.1444091796875e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 644.6156222820282s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 0.21259784698486328s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0007534027099609375s
Extra | Recovery of all triples for Apertium RDF EO-CA took 276.85239601135254s
Performance | Total latancy measurement for Apertium RDF EO-CA took 1.2674763202667236s
Amount of data | Number of triples check for Apertium RDF EO-CA took 2.227098226547241s
Interoperability | New terms check for Apertium RDF EO-CA took 2.882021188735962s
Versatility | Languages check for Apertium RDF EO-CA took 45.05593967437744s
Interpretability | Number of blank nodes check for Apertium RDF EO-CA took 1.0939347743988037s
Security | Check HTTPS for Apertium RDF EO-CA took 0.13337993621826172s
Interpretability | RDF structures check for Apertium RDF EO-CA took 0.28177332878112793s
Versatility | Serialization formats check for Apertium RDF EO-CA took 0.28967905044555664s
Availability | RDF dump link check for Apertium RDF EO-CA took 0.2918236255645752s
License | MR license check for Apertium RDF EO-CA took 0.3066720962524414s
License | HR license check for Apertium RDF EO-CA took 0.3497328758239746s
Amount of data | Number of property check for Apertium RDF EO-CA took 0.2681746482849121s
Understandability | Number of label check for Apertium RDF EO-CA took 0.3186373710632324s
Understandability | URI regex check for Apertium RDF EO-CA took 0.5916152000427246s
Understandability | Vocabs check for Apertium RDF EO-CA took 0.28897738456726074s
Verifiability | Authors check for Apertium RDF EO-CA took 0.2819991111755371s
Verifiability | Publishers check for Apertium RDF EO-CA took 0.2732889652252197s
Performance | Throughput check for Apertium RDF EO-CA took 12.139413356781006s
Amount of data | Check the number of entities for Apertium RDF EO-CA took 7.724761962890625e-05s
Verifiability | Contribs. check for Apertium RDF EO-CA took 0.28392815589904785s
Interlinking | sameAs chians check for Apertium RDF EO-CA took 0.273883581161499s
Interlinking | skos check for Apertium RDF EO-CA took 0.2869722843170166s
Interlinking | skos check for Apertium RDF EO-CA took 0.22653818130493164s
Timeliness | dataset update frequency check for Apertium RDF EO-CA took 0.28360605239868164s
Currency | Creation date check for Apertium RDF EO-CA took 0.569990873336792s
Currency | Modification date check for Apertium RDF EO-CA took 0.6080138683319092s
Rep.Conc. | URIs length for Apertium RDF EO-CA took 87.10217046737671s
Interoperability | New vocabularies check for Apertium RDF EO-CA took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-CA took 0.33469629287719727s
Accuracy | Check Functional Property for Apertium RDF EO-CA took 0.3018946647644043s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-CA took 0.2902560234069824s
Accuracy | Check Empty annotation labels for Apertium RDF EO-CA took 0.8006882667541504s
Accuracy | Check White space in annotation for Apertium RDF EO-CA took 0.010056018829345703s
Accuracy | Check Datatype consistency for Apertium RDF EO-CA took 2.6703665256500244s
Consistency | Disjoint class check for Apertium RDF EO-CA took 0.28368091583251953s
Consistency | Check Misplaced properties for Apertium RDF EO-CA took 4.615904331207275s
Consistency | Misplaced classes for Apertium RDF EO-CA took 8.547404766082764s
Consistency | Check Ontology hijacking for Apertium RDF EO-CA took 85.55194640159607s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-CA took 1.5038418769836426s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-CA took 5.761847496032715s
Conciseness | Check Extensional conciseness for Apertium RDF EO-CA took 3.0515620708465576s
Conciseness | Check Intensional conciseness for Apertium RDF EO-CA took 0.31442856788635254s
Security | Sign check for Apertium RDF EO-CA took 0.30345916748046875s
Availability | Check URIs Dereferenciability for Apertium RDF EO-CA took 10.142051696777344s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.7310516834259033s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020954370498657227s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EO-CA took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 628.4654397964478s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 0.22666096687316895s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0005009174346923828s
Extra | Recovery of all triples for Apertium RDF EO-EN took 276.68261551856995s
Performance | Total latancy measurement for Apertium RDF EO-EN took 1.3124396800994873s
Amount of data | Number of triples check for Apertium RDF EO-EN took 2.1687517166137695s
Interoperability | New terms check for Apertium RDF EO-EN took 2.923980236053467s
Versatility | Languages check for Apertium RDF EO-EN took 43.91123342514038s
Interpretability | Number of blank nodes check for Apertium RDF EO-EN took 1.175168514251709s
Security | Check HTTPS for Apertium RDF EO-EN took 0.12303757667541504s
Interpretability | RDF structures check for Apertium RDF EO-EN took 0.31223464012145996s
Versatility | Serialization formats check for Apertium RDF EO-EN took 0.2982182502746582s
Availability | RDF dump link check for Apertium RDF EO-EN took 0.2742185592651367s
License | MR license check for Apertium RDF EO-EN took 0.30433034896850586s
License | HR license check for Apertium RDF EO-EN took 0.37827539443969727s
Amount of data | Number of property check for Apertium RDF EO-EN took 0.34732580184936523s
Understandability | Number of label check for Apertium RDF EO-EN took 0.33896923065185547s
Understandability | URI regex check for Apertium RDF EO-EN took 0.5440516471862793s
Understandability | Vocabs check for Apertium RDF EO-EN took 0.281980037689209s
Verifiability | Authors check for Apertium RDF EO-EN took 0.2957596778869629s
Verifiability | Publishers check for Apertium RDF EO-EN took 0.2864410877227783s
Performance | Throughput check for Apertium RDF EO-EN took 11.209959030151367s
Amount of data | Check the number of entities for Apertium RDF EO-EN took 7.557868957519531e-05s
Verifiability | Contribs. check for Apertium RDF EO-EN took 0.3272109031677246s
Interlinking | sameAs chians check for Apertium RDF EO-EN took 0.27555108070373535s
Interlinking | skos check for Apertium RDF EO-EN took 0.2843945026397705s
Interlinking | skos check for Apertium RDF EO-EN took 0.20730352401733398s
Timeliness | dataset update frequency check for Apertium RDF EO-EN took 0.29508256912231445s
Currency | Creation date check for Apertium RDF EO-EN took 0.5900239944458008s
Currency | Modification date check for Apertium RDF EO-EN took 0.7539210319519043s
Rep.Conc. | URIs length for Apertium RDF EO-EN took 89.71167778968811s
Interoperability | New vocabularies check for Apertium RDF EO-EN took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-EN took 0.30936551094055176s
Accuracy | Check Functional Property for Apertium RDF EO-EN took 0.31294846534729004s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-EN took 0.2836446762084961s
Accuracy | Check Empty annotation labels for Apertium RDF EO-EN took 0.794060230255127s
Accuracy | Check White space in annotation for Apertium RDF EO-EN took 0.010043621063232422s
Accuracy | Check Datatype consistency for Apertium RDF EO-EN took 2.6945037841796875s
Consistency | Disjoint class check for Apertium RDF EO-EN took 0.2823355197906494s
Consistency | Check Misplaced properties for Apertium RDF EO-EN took 4.630452871322632s
Consistency | Misplaced classes for Apertium RDF EO-EN took 8.501471281051636s
Consistency | Check Ontology hijacking for Apertium RDF EO-EN took 90.9316840171814s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-EN took 1.5086877346038818s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-EN took 5.801349878311157s
Conciseness | Check Extensional conciseness for Apertium RDF EO-EN took 3.0619592666625977s
Conciseness | Check Intensional conciseness for Apertium RDF EO-EN took 0.3176431655883789s
Security | Sign check for Apertium RDF EO-EN took 0.3248162269592285s
Availability | Check URIs Dereferenciability for Apertium RDF EO-EN took 10.748257160186768s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.9063475131988525s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-EN took 1.1920928955078125e-06s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 655.1941413879395s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 0.23561358451843262s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006341934204101562s
Extra | Recovery of all triples for Apertium RDF EO-ES took 253.05406856536865s
Performance | Total latancy measurement for Apertium RDF EO-ES took 1.2602097988128662s
Amount of data | Number of triples check for Apertium RDF EO-ES took 2.2315056324005127s
Interoperability | New terms check for Apertium RDF EO-ES took 3.042379140853882s
Versatility | Languages check for Apertium RDF EO-ES took 43.98896670341492s
Interpretability | Number of blank nodes check for Apertium RDF EO-ES took 1.080648422241211s
Security | Check HTTPS for Apertium RDF EO-ES took 0.14396071434020996s
Interpretability | RDF structures check for Apertium RDF EO-ES took 0.2826263904571533s
Versatility | Serialization formats check for Apertium RDF EO-ES took 0.2945892810821533s
Availability | RDF dump link check for Apertium RDF EO-ES took 0.2811696529388428s
License | MR license check for Apertium RDF EO-ES took 0.2957181930541992s
License | HR license check for Apertium RDF EO-ES took 0.3800039291381836s
Amount of data | Number of property check for Apertium RDF EO-ES took 0.28098464012145996s
Understandability | Number of label check for Apertium RDF EO-ES took 0.3273158073425293s
Understandability | URI regex check for Apertium RDF EO-ES took 0.5715513229370117s
Understandability | Vocabs check for Apertium RDF EO-ES took 0.2971920967102051s
Verifiability | Authors check for Apertium RDF EO-ES took 0.3110065460205078s
Verifiability | Publishers check for Apertium RDF EO-ES took 0.29305219650268555s
Performance | Throughput check for Apertium RDF EO-ES took 11.305047988891602s
Amount of data | Check the number of entities for Apertium RDF EO-ES took 9.107589721679688e-05s
Verifiability | Contribs. check for Apertium RDF EO-ES took 0.27719736099243164s
Interlinking | sameAs chians check for Apertium RDF EO-ES took 0.43630146980285645s
Interlinking | skos check for Apertium RDF EO-ES took 0.28923940658569336s
Interlinking | skos check for Apertium RDF EO-ES took 0.2119431495666504s
Timeliness | dataset update frequency check for Apertium RDF EO-ES took 0.5492870807647705s
Currency | Creation date check for Apertium RDF EO-ES took 0.5794339179992676s
Currency | Modification date check for Apertium RDF EO-ES took 0.5579304695129395s
Rep.Conc. | URIs length for Apertium RDF EO-ES took 90.07847785949707s
Interoperability | New vocabularies check for Apertium RDF EO-ES took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-ES took 0.32451319694519043s
Accuracy | Check Functional Property for Apertium RDF EO-ES took 0.28624534606933594s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-ES took 0.2758901119232178s
Accuracy | Check Empty annotation labels for Apertium RDF EO-ES took 0.8574233055114746s
Accuracy | Check White space in annotation for Apertium RDF EO-ES took 0.01002359390258789s
Accuracy | Check Datatype consistency for Apertium RDF EO-ES took 2.656798839569092s
Consistency | Disjoint class check for Apertium RDF EO-ES took 0.29079675674438477s
Consistency | Check Misplaced properties for Apertium RDF EO-ES took 4.6993567943573s
Consistency | Misplaced classes for Apertium RDF EO-ES took 8.481821298599243s
Consistency | Check Ontology hijacking for Apertium RDF EO-ES took 90.5900628566742s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-ES took 1.5261659622192383s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-ES took 5.897104978561401s
Conciseness | Check Extensional conciseness for Apertium RDF EO-ES took 3.061668634414673s
Conciseness | Check Intensional conciseness for Apertium RDF EO-ES took 0.36685800552368164s
Security | Sign check for Apertium RDF EO-ES took 0.28485751152038574s
Availability | Check URIs Dereferenciability for Apertium RDF EO-ES took 10.282183408737183s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 3.0850908756256104s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.02092266082763672s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-ES took 1.1920928955078125e-06s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 621.2650401592255s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 0.21574783325195312s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0009377002716064453s
Extra | Recovery of all triples for Apertium RDF EO-FR took 275.2799849510193s
Performance | Total latancy measurement for Apertium RDF EO-FR took 1.3742763996124268s
Amount of data | Number of triples check for Apertium RDF EO-FR took 2.281639814376831s
Interoperability | New terms check for Apertium RDF EO-FR took 2.8912014961242676s
Versatility | Languages check for Apertium RDF EO-FR took 44.94727849960327s
Interpretability | Number of blank nodes check for Apertium RDF EO-FR took 1.21519136428833s
Security | Check HTTPS for Apertium RDF EO-FR took 0.1337296962738037s
Interpretability | RDF structures check for Apertium RDF EO-FR took 0.29942941665649414s
Versatility | Serialization formats check for Apertium RDF EO-FR took 0.3099520206451416s
Availability | RDF dump link check for Apertium RDF EO-FR took 0.28746604919433594s
License | MR license check for Apertium RDF EO-FR took 0.2917177677154541s
License | HR license check for Apertium RDF EO-FR took 0.37817811965942383s
Amount of data | Number of property check for Apertium RDF EO-FR took 0.2943272590637207s
Understandability | Number of label check for Apertium RDF EO-FR took 0.3225421905517578s
Understandability | URI regex check for Apertium RDF EO-FR took 0.5835998058319092s
Understandability | Vocabs check for Apertium RDF EO-FR took 0.2707386016845703s
Verifiability | Authors check for Apertium RDF EO-FR took 0.30007362365722656s
Verifiability | Publishers check for Apertium RDF EO-FR took 0.2794313430786133s
Performance | Throughput check for Apertium RDF EO-FR took 11.291246891021729s
Amount of data | Check the number of entities for Apertium RDF EO-FR took 0.0001342296600341797s
Verifiability | Contribs. check for Apertium RDF EO-FR took 0.30982542037963867s
Interlinking | sameAs chians check for Apertium RDF EO-FR took 0.2989513874053955s
Interlinking | skos check for Apertium RDF EO-FR took 0.31366968154907227s
Interlinking | skos check for Apertium RDF EO-FR took 0.24421977996826172s
Timeliness | dataset update frequency check for Apertium RDF EO-FR took 0.29935789108276367s
Currency | Creation date check for Apertium RDF EO-FR took 0.5947067737579346s
Currency | Modification date check for Apertium RDF EO-FR took 0.5787951946258545s
Rep.Conc. | URIs length for Apertium RDF EO-FR took 93.99919319152832s
Interoperability | New vocabularies check for Apertium RDF EO-FR took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-FR took 0.30464744567871094s
Accuracy | Check Functional Property for Apertium RDF EO-FR took 0.3046684265136719s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-FR took 0.27459287643432617s
Accuracy | Check Empty annotation labels for Apertium RDF EO-FR took 0.8472371101379395s
Accuracy | Check White space in annotation for Apertium RDF EO-FR took 0.014470815658569336s
Accuracy | Check Datatype consistency for Apertium RDF EO-FR took 2.698268175125122s
Consistency | Disjoint class check for Apertium RDF EO-FR took 0.29611730575561523s
Consistency | Check Misplaced properties for Apertium RDF EO-FR took 4.715635061264038s
Consistency | Misplaced classes for Apertium RDF EO-FR took 8.455599069595337s
Consistency | Check Ontology hijacking for Apertium RDF EO-FR took 85.79816913604736s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-FR took 1.5013644695281982s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-FR took 5.752392768859863s
Conciseness | Check Extensional conciseness for Apertium RDF EO-FR took 3.056335210800171s
Conciseness | Check Intensional conciseness for Apertium RDF EO-FR took 0.3273735046386719s
Security | Sign check for Apertium RDF EO-FR took 0.28981971740722656s
Availability | Check URIs Dereferenciability for Apertium RDF EO-FR took 24.40138840675354s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.3439443111419678s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-FR took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 655.4401769638062s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 0.24121546745300293s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0006287097930908203s
Extra | Recovery of all triples for Apertium RDF ES-AN took 251.72393417358398s
Performance | Total latancy measurement for Apertium RDF ES-AN took 1.2653450965881348s
Amount of data | Number of triples check for Apertium RDF ES-AN took 2.2547807693481445s
Interoperability | New terms check for Apertium RDF ES-AN took 2.9164767265319824s
Versatility | Languages check for Apertium RDF ES-AN took 44.058775186538696s
Interpretability | Number of blank nodes check for Apertium RDF ES-AN took 1.0957844257354736s
Security | Check HTTPS for Apertium RDF ES-AN took 0.13761544227600098s
Interpretability | RDF structures check for Apertium RDF ES-AN took 0.28488779067993164s
Versatility | Serialization formats check for Apertium RDF ES-AN took 0.29119348526000977s
Availability | RDF dump link check for Apertium RDF ES-AN took 0.28136420249938965s
License | MR license check for Apertium RDF ES-AN took 0.28669261932373047s
License | HR license check for Apertium RDF ES-AN took 0.379014253616333s
Amount of data | Number of property check for Apertium RDF ES-AN took 0.27515411376953125s
Understandability | Number of label check for Apertium RDF ES-AN took 0.39029693603515625s
Understandability | URI regex check for Apertium RDF ES-AN took 0.587867259979248s
Understandability | Vocabs check for Apertium RDF ES-AN took 0.2796616554260254s
Verifiability | Authors check for Apertium RDF ES-AN took 0.3025367259979248s
Verifiability | Publishers check for Apertium RDF ES-AN took 0.28492164611816406s
Performance | Throughput check for Apertium RDF ES-AN took 11.385512113571167s
Amount of data | Check the number of entities for Apertium RDF ES-AN took 7.557868957519531e-05s
Verifiability | Contribs. check for Apertium RDF ES-AN took 0.30637025833129883s
Interlinking | sameAs chians check for Apertium RDF ES-AN took 0.30835604667663574s
Interlinking | skos check for Apertium RDF ES-AN took 0.2995777130126953s
Interlinking | skos check for Apertium RDF ES-AN took 0.23357582092285156s
Timeliness | dataset update frequency check for Apertium RDF ES-AN took 0.3365976810455322s
Currency | Creation date check for Apertium RDF ES-AN took 0.6152081489562988s
Currency | Modification date check for Apertium RDF ES-AN took 0.5728728771209717s
Rep.Conc. | URIs length for Apertium RDF ES-AN took 90.38246893882751s
Interoperability | New vocabularies check for Apertium RDF ES-AN took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AN took 0.30660533905029297s
Accuracy | Check Functional Property for Apertium RDF ES-AN took 0.2972073554992676s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AN took 0.27816104888916016s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AN took 0.8072736263275146s
Accuracy | Check White space in annotation for Apertium RDF ES-AN took 0.010006904602050781s
Accuracy | Check Datatype consistency for Apertium RDF ES-AN took 2.668107748031616s
Consistency | Disjoint class check for Apertium RDF ES-AN took 0.28556370735168457s
Consistency | Check Misplaced properties for Apertium RDF ES-AN took 4.6581385135650635s
Consistency | Misplaced classes for Apertium RDF ES-AN took 8.518824338912964s
Consistency | Check Ontology hijacking for Apertium RDF ES-AN took 86.03863668441772s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AN took 1.499340534210205s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AN took 5.774286270141602s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AN took 3.056354284286499s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AN took 0.3459630012512207s
Security | Sign check for Apertium RDF ES-AN took 0.2983858585357666s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AN took 9.82044005393982s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 1.0486164093017578s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 5.412101745605469e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AN took 1.1920928955078125e-06s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.430511474609375e-05s
INFO | --- Analysis for apertium-rdf-es-an took 610.7991080284119s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 0.22781682014465332s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006656646728515625s
Extra | Recovery of all triples for Apertium RDF ES-AST took 264.0676169395447s
Performance | Total latancy measurement for Apertium RDF ES-AST took 1.275376796722412s
Amount of data | Number of triples check for Apertium RDF ES-AST took 2.2570741176605225s
Interoperability | New terms check for Apertium RDF ES-AST took 2.914019823074341s
Versatility | Languages check for Apertium RDF ES-AST took 44.92030167579651s
Interpretability | Number of blank nodes check for Apertium RDF ES-AST took 1.2627215385437012s
Security | Check HTTPS for Apertium RDF ES-AST took 0.1347672939300537s
Interpretability | RDF structures check for Apertium RDF ES-AST took 0.2900972366333008s
Versatility | Serialization formats check for Apertium RDF ES-AST took 0.2875356674194336s
Availability | RDF dump link check for Apertium RDF ES-AST took 0.29430603981018066s
License | MR license check for Apertium RDF ES-AST took 0.2781083583831787s
License | HR license check for Apertium RDF ES-AST took 0.38644957542419434s
Amount of data | Number of property check for Apertium RDF ES-AST took 0.27971386909484863s
Understandability | Number of label check for Apertium RDF ES-AST took 0.3222084045410156s
Understandability | URI regex check for Apertium RDF ES-AST took 0.5417196750640869s
Understandability | Vocabs check for Apertium RDF ES-AST took 0.2764246463775635s
Verifiability | Authors check for Apertium RDF ES-AST took 0.2845783233642578s
Verifiability | Publishers check for Apertium RDF ES-AST took 0.3010246753692627s
Performance | Throughput check for Apertium RDF ES-AST took 11.302639245986938s
Amount of data | Check the number of entities for Apertium RDF ES-AST took 7.200241088867188e-05s
Verifiability | Contribs. check for Apertium RDF ES-AST took 0.2775745391845703s
Interlinking | sameAs chians check for Apertium RDF ES-AST took 0.2921159267425537s
Interlinking | skos check for Apertium RDF ES-AST took 0.2918989658355713s
Interlinking | skos check for Apertium RDF ES-AST took 0.22078227996826172s
Timeliness | dataset update frequency check for Apertium RDF ES-AST took 0.2879199981689453s
Currency | Creation date check for Apertium RDF ES-AST took 0.586850643157959s
Currency | Modification date check for Apertium RDF ES-AST took 0.5671942234039307s
Rep.Conc. | URIs length for Apertium RDF ES-AST took 90.81354188919067s
Interoperability | New vocabularies check for Apertium RDF ES-AST took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AST took 0.31472301483154297s
Accuracy | Check Functional Property for Apertium RDF ES-AST took 0.2883005142211914s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AST took 0.2943446636199951s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AST took 0.8453004360198975s
Accuracy | Check White space in annotation for Apertium RDF ES-AST took 0.010101079940795898s
Accuracy | Check Datatype consistency for Apertium RDF ES-AST took 2.6915218830108643s
Consistency | Disjoint class check for Apertium RDF ES-AST took 0.27117061614990234s
Consistency | Check Misplaced properties for Apertium RDF ES-AST took 4.6928184032440186s
Consistency | Misplaced classes for Apertium RDF ES-AST took 8.545818567276001s
Consistency | Check Ontology hijacking for Apertium RDF ES-AST took 92.9554340839386s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AST took 1.5204966068267822s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AST took 5.837876558303833s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AST took 3.052934408187866s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AST took 0.3407893180847168s
Security | Sign check for Apertium RDF ES-AST took 0.2959573268890381s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AST took 11.9548499584198s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.3612644672393799s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AST took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 635.5986995697021s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 0.21366214752197266s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0006601810455322266s
Extra | Recovery of all triples for Apertium RDF ES-CA took 264.4163956642151s
Performance | Total latancy measurement for Apertium RDF ES-CA took 1.4068818092346191s
Amount of data | Number of triples check for Apertium RDF ES-CA took 2.3048031330108643s
Interoperability | New terms check for Apertium RDF ES-CA took 3.122501850128174s
Versatility | Languages check for Apertium RDF ES-CA took 44.708839416503906s
Interpretability | Number of blank nodes check for Apertium RDF ES-CA took 1.0615735054016113s
Security | Check HTTPS for Apertium RDF ES-CA took 0.1714468002319336s
Interpretability | RDF structures check for Apertium RDF ES-CA took 0.27822089195251465s
Versatility | Serialization formats check for Apertium RDF ES-CA took 0.2828328609466553s
Availability | RDF dump link check for Apertium RDF ES-CA took 0.28276824951171875s
License | MR license check for Apertium RDF ES-CA took 0.2840707302093506s
License | HR license check for Apertium RDF ES-CA took 0.3935718536376953s
Amount of data | Number of property check for Apertium RDF ES-CA took 0.2849314212799072s
Understandability | Number of label check for Apertium RDF ES-CA took 0.3359501361846924s
Understandability | URI regex check for Apertium RDF ES-CA took 0.5493900775909424s
Understandability | Vocabs check for Apertium RDF ES-CA took 0.2758903503417969s
Verifiability | Authors check for Apertium RDF ES-CA took 0.299910306930542s
Verifiability | Publishers check for Apertium RDF ES-CA took 0.29085445404052734s
Performance | Throughput check for Apertium RDF ES-CA took 11.378247499465942s
Amount of data | Check the number of entities for Apertium RDF ES-CA took 0.00010704994201660156s
Verifiability | Contribs. check for Apertium RDF ES-CA took 0.2868478298187256s
Interlinking | sameAs chians check for Apertium RDF ES-CA took 0.2956509590148926s
Interlinking | skos check for Apertium RDF ES-CA took 0.2965128421783447s
Interlinking | skos check for Apertium RDF ES-CA took 0.2787184715270996s
Timeliness | dataset update frequency check for Apertium RDF ES-CA took 0.28856897354125977s
Currency | Creation date check for Apertium RDF ES-CA took 0.5876810550689697s
Currency | Modification date check for Apertium RDF ES-CA took 0.5980925559997559s
Rep.Conc. | URIs length for Apertium RDF ES-CA took 89.59834337234497s
Interoperability | New vocabularies check for Apertium RDF ES-CA took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-CA took 0.32149338722229004s
Accuracy | Check Functional Property for Apertium RDF ES-CA took 0.2806835174560547s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-CA took 0.3362386226654053s
Accuracy | Check Empty annotation labels for Apertium RDF ES-CA took 0.8888161182403564s
Accuracy | Check White space in annotation for Apertium RDF ES-CA took 0.010087013244628906s
Accuracy | Check Datatype consistency for Apertium RDF ES-CA took 2.6614158153533936s
Consistency | Disjoint class check for Apertium RDF ES-CA took 0.3058927059173584s
Consistency | Check Misplaced properties for Apertium RDF ES-CA took 4.649972915649414s
Consistency | Misplaced classes for Apertium RDF ES-CA took 8.586840152740479s
Consistency | Check Ontology hijacking for Apertium RDF ES-CA took 85.26817607879639s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-CA took 1.4879064559936523s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-CA took 5.842630624771118s
Conciseness | Check Extensional conciseness for Apertium RDF ES-CA took 3.046643018722534s
Conciseness | Check Intensional conciseness for Apertium RDF ES-CA took 0.32808732986450195s
Security | Sign check for Apertium RDF ES-CA took 0.33039426803588867s
Availability | Check URIs Dereferenciability for Apertium RDF ES-CA took 9.843907356262207s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 1.0329170227050781s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-CA took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 641.8729135990143s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 0.2190995216369629s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006632804870605469s
Extra | Recovery of all triples for Apertium RDF ES-GL took 263.42026376724243s
Performance | Total latancy measurement for Apertium RDF ES-GL took 1.449035406112671s
Amount of data | Number of triples check for Apertium RDF ES-GL took 2.161254644393921s
Interoperability | New terms check for Apertium RDF ES-GL took 2.944485664367676s
Versatility | Languages check for Apertium RDF ES-GL took 44.08829402923584s
Interpretability | Number of blank nodes check for Apertium RDF ES-GL took 1.219040870666504s
Security | Check HTTPS for Apertium RDF ES-GL took 0.12337613105773926s
Interpretability | RDF structures check for Apertium RDF ES-GL took 0.2862052917480469s
Versatility | Serialization formats check for Apertium RDF ES-GL took 0.29486584663391113s
Availability | RDF dump link check for Apertium RDF ES-GL took 0.2767977714538574s
License | MR license check for Apertium RDF ES-GL took 0.26500415802001953s
License | HR license check for Apertium RDF ES-GL took 0.38521552085876465s
Amount of data | Number of property check for Apertium RDF ES-GL took 0.2872474193572998s
Understandability | Number of label check for Apertium RDF ES-GL took 0.3472628593444824s
Understandability | URI regex check for Apertium RDF ES-GL took 0.5989506244659424s
Understandability | Vocabs check for Apertium RDF ES-GL took 0.2985804080963135s
Verifiability | Authors check for Apertium RDF ES-GL took 0.35908007621765137s
Verifiability | Publishers check for Apertium RDF ES-GL took 0.28781628608703613s
Performance | Throughput check for Apertium RDF ES-GL took 11.479950189590454s
Amount of data | Check the number of entities for Apertium RDF ES-GL took 7.462501525878906e-05s
Verifiability | Contribs. check for Apertium RDF ES-GL took 0.2922065258026123s
Interlinking | sameAs chians check for Apertium RDF ES-GL took 0.29672670364379883s
Interlinking | skos check for Apertium RDF ES-GL took 0.30317115783691406s
Interlinking | skos check for Apertium RDF ES-GL took 0.2339627742767334s
Timeliness | dataset update frequency check for Apertium RDF ES-GL took 0.35786986351013184s
Currency | Creation date check for Apertium RDF ES-GL took 0.5581302642822266s
Currency | Modification date check for Apertium RDF ES-GL took 0.592766284942627s
Rep.Conc. | URIs length for Apertium RDF ES-GL took 86.48908257484436s
Interoperability | New vocabularies check for Apertium RDF ES-GL took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-GL took 0.3229982852935791s
Accuracy | Check Functional Property for Apertium RDF ES-GL took 0.31563830375671387s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-GL took 0.2836322784423828s
Accuracy | Check Empty annotation labels for Apertium RDF ES-GL took 0.8619625568389893s
Accuracy | Check White space in annotation for Apertium RDF ES-GL took 0.010245323181152344s
Accuracy | Check Datatype consistency for Apertium RDF ES-GL took 2.6671786308288574s
Consistency | Disjoint class check for Apertium RDF ES-GL took 0.2792794704437256s
Consistency | Check Misplaced properties for Apertium RDF ES-GL took 4.8052263259887695s
Consistency | Misplaced classes for Apertium RDF ES-GL took 8.545931816101074s
Consistency | Check Ontology hijacking for Apertium RDF ES-GL took 90.93651461601257s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-GL took 1.5078861713409424s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-GL took 6.738977670669556s
Conciseness | Check Extensional conciseness for Apertium RDF ES-GL took 3.0806758403778076s
Conciseness | Check Intensional conciseness for Apertium RDF ES-GL took 0.36760425567626953s
Security | Sign check for Apertium RDF ES-GL took 0.29594874382019043s
Availability | Check URIs Dereferenciability for Apertium RDF ES-GL took 10.881986856460571s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.8204114437103271s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-GL took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 630.184282541275s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 0.22423315048217773s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006515979766845703s
Extra | Recovery of all triples for Apertium RDF ES-PT took 275.57178807258606s
Performance | Total latancy measurement for Apertium RDF ES-PT took 1.4203836917877197s
Amount of data | Number of triples check for Apertium RDF ES-PT took 2.1338205337524414s
Interoperability | New terms check for Apertium RDF ES-PT took 3.089233636856079s
Versatility | Languages check for Apertium RDF ES-PT took 44.556984186172485s
Interpretability | Number of blank nodes check for Apertium RDF ES-PT took 1.155463695526123s
Security | Check HTTPS for Apertium RDF ES-PT took 0.14525747299194336s
Interpretability | RDF structures check for Apertium RDF ES-PT took 0.31157612800598145s
Versatility | Serialization formats check for Apertium RDF ES-PT took 0.29746365547180176s
Availability | RDF dump link check for Apertium RDF ES-PT took 0.2732822895050049s
License | MR license check for Apertium RDF ES-PT took 0.2850217819213867s
License | HR license check for Apertium RDF ES-PT took 0.38288450241088867s
Amount of data | Number of property check for Apertium RDF ES-PT took 0.28455233573913574s
Understandability | Number of label check for Apertium RDF ES-PT took 0.30835413932800293s
Understandability | URI regex check for Apertium RDF ES-PT took 0.5835847854614258s
Understandability | Vocabs check for Apertium RDF ES-PT took 0.2851741313934326s
Verifiability | Authors check for Apertium RDF ES-PT took 0.29366111755371094s
Verifiability | Publishers check for Apertium RDF ES-PT took 0.27333664894104004s
Performance | Throughput check for Apertium RDF ES-PT took 11.551833152770996s
Amount of data | Check the number of entities for Apertium RDF ES-PT took 7.510185241699219e-05s
Verifiability | Contribs. check for Apertium RDF ES-PT took 0.31252312660217285s
Interlinking | sameAs chians check for Apertium RDF ES-PT took 0.29370570182800293s
Interlinking | skos check for Apertium RDF ES-PT took 0.3008251190185547s
Interlinking | skos check for Apertium RDF ES-PT took 0.2170121669769287s
Timeliness | dataset update frequency check for Apertium RDF ES-PT took 0.29662585258483887s
Currency | Creation date check for Apertium RDF ES-PT took 0.5931210517883301s
Currency | Modification date check for Apertium RDF ES-PT took 0.5720884799957275s
Rep.Conc. | URIs length for Apertium RDF ES-PT took 89.70248198509216s
Interoperability | New vocabularies check for Apertium RDF ES-PT took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-PT took 0.30035948753356934s
Accuracy | Check Functional Property for Apertium RDF ES-PT took 0.2923927307128906s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-PT took 0.2927718162536621s
Accuracy | Check Empty annotation labels for Apertium RDF ES-PT took 0.8488812446594238s
Accuracy | Check White space in annotation for Apertium RDF ES-PT took 0.009990930557250977s
Accuracy | Check Datatype consistency for Apertium RDF ES-PT took 2.6589832305908203s
Consistency | Disjoint class check for Apertium RDF ES-PT took 0.2726738452911377s
Consistency | Check Misplaced properties for Apertium RDF ES-PT took 4.671030044555664s
Consistency | Misplaced classes for Apertium RDF ES-PT took 8.559355020523071s
Consistency | Check Ontology hijacking for Apertium RDF ES-PT took 91.48343825340271s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-PT took 1.5079765319824219s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-PT took 5.863896131515503s
Conciseness | Check Extensional conciseness for Apertium RDF ES-PT took 3.0815839767456055s
Conciseness | Check Intensional conciseness for Apertium RDF ES-PT took 0.35990405082702637s
Security | Sign check for Apertium RDF ES-PT took 0.2850911617279053s
Availability | Check URIs Dereferenciability for Apertium RDF ES-PT took 10.193161249160767s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.5420408248901367s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-PT took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 644.50599360466s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 0.21909594535827637s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006427764892578125s
Extra | Recovery of all triples for Apertium RDF ES-RO took 262.89165806770325s
Performance | Total latancy measurement for Apertium RDF ES-RO took 1.2269244194030762s
Amount of data | Number of triples check for Apertium RDF ES-RO took 2.1668648719787598s
Interoperability | New terms check for Apertium RDF ES-RO took 2.901787757873535s
Versatility | Languages check for Apertium RDF ES-RO took 43.99076271057129s
Interpretability | Number of blank nodes check for Apertium RDF ES-RO took 1.114365577697754s
Security | Check HTTPS for Apertium RDF ES-RO took 0.13629889488220215s
Interpretability | RDF structures check for Apertium RDF ES-RO took 0.3035428524017334s
Versatility | Serialization formats check for Apertium RDF ES-RO took 0.28307533264160156s
Availability | RDF dump link check for Apertium RDF ES-RO took 0.27887654304504395s
License | MR license check for Apertium RDF ES-RO took 0.2986636161804199s
License | HR license check for Apertium RDF ES-RO took 0.3610093593597412s
Amount of data | Number of property check for Apertium RDF ES-RO took 0.29326629638671875s
Understandability | Number of label check for Apertium RDF ES-RO took 0.3230605125427246s
Understandability | URI regex check for Apertium RDF ES-RO took 0.6333990097045898s
Understandability | Vocabs check for Apertium RDF ES-RO took 0.282163143157959s
Verifiability | Authors check for Apertium RDF ES-RO took 0.29585814476013184s
Verifiability | Publishers check for Apertium RDF ES-RO took 0.28295207023620605s
Performance | Throughput check for Apertium RDF ES-RO took 11.350078821182251s
Amount of data | Check the number of entities for Apertium RDF ES-RO took 3.4332275390625e-05s
Verifiability | Contribs. check for Apertium RDF ES-RO took 0.30107855796813965s
Interlinking | sameAs chians check for Apertium RDF ES-RO took 0.29746007919311523s
Interlinking | skos check for Apertium RDF ES-RO took 0.30644941329956055s
Interlinking | skos check for Apertium RDF ES-RO took 0.22908782958984375s
Timeliness | dataset update frequency check for Apertium RDF ES-RO took 0.29631567001342773s
Currency | Creation date check for Apertium RDF ES-RO took 0.6550648212432861s
Currency | Modification date check for Apertium RDF ES-RO took 0.5815329551696777s
Rep.Conc. | URIs length for Apertium RDF ES-RO took 94.57453298568726s
Interoperability | New vocabularies check for Apertium RDF ES-RO took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-RO took 0.34819936752319336s
Accuracy | Check Functional Property for Apertium RDF ES-RO took 0.29238176345825195s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-RO took 0.28886890411376953s
Accuracy | Check Empty annotation labels for Apertium RDF ES-RO took 0.8477656841278076s
Accuracy | Check White space in annotation for Apertium RDF ES-RO took 0.010278701782226562s
Accuracy | Check Datatype consistency for Apertium RDF ES-RO took 2.686232566833496s
Consistency | Disjoint class check for Apertium RDF ES-RO took 0.27676916122436523s
Consistency | Check Misplaced properties for Apertium RDF ES-RO took 4.8149449825286865s
Consistency | Misplaced classes for Apertium RDF ES-RO took 8.824350118637085s
Consistency | Check Ontology hijacking for Apertium RDF ES-RO took 85.36067533493042s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-RO took 1.6415934562683105s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-RO took 5.717920303344727s
Conciseness | Check Extensional conciseness for Apertium RDF ES-RO took 3.083836078643799s
Conciseness | Check Intensional conciseness for Apertium RDF ES-RO took 0.3168206214904785s
Security | Sign check for Apertium RDF ES-RO took 0.3008713722229004s
Availability | Check URIs Dereferenciability for Apertium RDF ES-RO took 10.151325225830078s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.7372374534606934s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.76837158203125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-RO took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 633.3157160282135s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 0.22380590438842773s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006382465362548828s
Extra | Recovery of all triples for Apertium RDF EU-EN took 263.6359419822693s
Performance | Total latancy measurement for Apertium RDF EU-EN took 1.3225789070129395s
Amount of data | Number of triples check for Apertium RDF EU-EN took 2.266364574432373s
Interoperability | New terms check for Apertium RDF EU-EN took 2.9772541522979736s
Versatility | Languages check for Apertium RDF EU-EN took 44.06393098831177s
Interpretability | Number of blank nodes check for Apertium RDF EU-EN took 1.0943844318389893s
Security | Check HTTPS for Apertium RDF EU-EN took 0.1438438892364502s
Interpretability | RDF structures check for Apertium RDF EU-EN took 0.3052821159362793s
Versatility | Serialization formats check for Apertium RDF EU-EN took 0.2831909656524658s
Availability | RDF dump link check for Apertium RDF EU-EN took 0.2836432456970215s
License | MR license check for Apertium RDF EU-EN took 0.2884368896484375s
License | HR license check for Apertium RDF EU-EN took 0.3729689121246338s
Amount of data | Number of property check for Apertium RDF EU-EN took 0.28600382804870605s
Understandability | Number of label check for Apertium RDF EU-EN took 0.31583070755004883s
Understandability | URI regex check for Apertium RDF EU-EN took 0.5686130523681641s
Understandability | Vocabs check for Apertium RDF EU-EN took 0.2889714241027832s
Verifiability | Authors check for Apertium RDF EU-EN took 0.28873467445373535s
Verifiability | Publishers check for Apertium RDF EU-EN took 0.280010461807251s
Performance | Throughput check for Apertium RDF EU-EN took 11.370846033096313s
Amount of data | Check the number of entities for Apertium RDF EU-EN took 7.605552673339844e-05s
Verifiability | Contribs. check for Apertium RDF EU-EN took 0.29103636741638184s
Interlinking | sameAs chians check for Apertium RDF EU-EN took 0.3124072551727295s
Interlinking | skos check for Apertium RDF EU-EN took 0.2995586395263672s
Interlinking | skos check for Apertium RDF EU-EN took 0.22502803802490234s
Timeliness | dataset update frequency check for Apertium RDF EU-EN took 0.28351330757141113s
Currency | Creation date check for Apertium RDF EU-EN took 0.5717921257019043s
Currency | Modification date check for Apertium RDF EU-EN took 0.5751705169677734s
Rep.Conc. | URIs length for Apertium RDF EU-EN took 90.97001552581787s
Interoperability | New vocabularies check for Apertium RDF EU-EN took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-EN took 0.31163835525512695s
Accuracy | Check Functional Property for Apertium RDF EU-EN took 0.3034176826477051s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-EN took 0.38219499588012695s
Accuracy | Check Empty annotation labels for Apertium RDF EU-EN took 1.5794851779937744s
Accuracy | Check White space in annotation for Apertium RDF EU-EN took 0.010089874267578125s
Accuracy | Check Datatype consistency for Apertium RDF EU-EN took 2.683497190475464s
Consistency | Disjoint class check for Apertium RDF EU-EN took 0.29947876930236816s
Consistency | Check Misplaced properties for Apertium RDF EU-EN took 4.629422664642334s
Consistency | Misplaced classes for Apertium RDF EU-EN took 8.6338791847229s
Consistency | Check Ontology hijacking for Apertium RDF EU-EN took 91.0105230808258s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-EN took 1.5087623596191406s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-EN took 5.7218403816223145s
Conciseness | Check Extensional conciseness for Apertium RDF EU-EN took 3.1024887561798096s
Conciseness | Check Intensional conciseness for Apertium RDF EU-EN took 0.3001668453216553s
Security | Sign check for Apertium RDF EU-EN took 0.2949354648590088s
Availability | Check URIs Dereferenciability for Apertium RDF EU-EN took 10.66874098777771s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.5329024791717529s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-EN took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 629.4878330230713s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 0.21138405799865723s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006971359252929688s
Extra | Recovery of all triples for Apertium RDF EU-ES took 263.3492240905762s
Performance | Total latancy measurement for Apertium RDF EU-ES took 1.2880823612213135s
Amount of data | Number of triples check for Apertium RDF EU-ES took 2.2054216861724854s
Interoperability | New terms check for Apertium RDF EU-ES took 2.9105162620544434s
Versatility | Languages check for Apertium RDF EU-ES took 44.057504415512085s
Interpretability | Number of blank nodes check for Apertium RDF EU-ES took 1.103020191192627s
Security | Check HTTPS for Apertium RDF EU-ES took 0.13377618789672852s
Interpretability | RDF structures check for Apertium RDF EU-ES took 0.2966132164001465s
Versatility | Serialization formats check for Apertium RDF EU-ES took 0.2897040843963623s
Availability | RDF dump link check for Apertium RDF EU-ES took 0.28856635093688965s
License | MR license check for Apertium RDF EU-ES took 0.281780481338501s
License | HR license check for Apertium RDF EU-ES took 0.37808704376220703s
Amount of data | Number of property check for Apertium RDF EU-ES took 0.2957570552825928s
Understandability | Number of label check for Apertium RDF EU-ES took 0.32581353187561035s
Understandability | URI regex check for Apertium RDF EU-ES took 0.586982250213623s
Understandability | Vocabs check for Apertium RDF EU-ES took 0.2808053493499756s
Verifiability | Authors check for Apertium RDF EU-ES took 0.2783370018005371s
Verifiability | Publishers check for Apertium RDF EU-ES took 0.3624460697174072s
Performance | Throughput check for Apertium RDF EU-ES took 11.15486216545105s
Amount of data | Check the number of entities for Apertium RDF EU-ES took 0.00011372566223144531s
Verifiability | Contribs. check for Apertium RDF EU-ES took 0.3016810417175293s
Interlinking | sameAs chians check for Apertium RDF EU-ES took 0.27076125144958496s
Interlinking | skos check for Apertium RDF EU-ES took 0.2721250057220459s
Interlinking | skos check for Apertium RDF EU-ES took 0.2178058624267578s
Timeliness | dataset update frequency check for Apertium RDF EU-ES took 0.31352829933166504s
Currency | Creation date check for Apertium RDF EU-ES took 0.5991439819335938s
Currency | Modification date check for Apertium RDF EU-ES took 0.5944468975067139s
Rep.Conc. | URIs length for Apertium RDF EU-ES took 90.84568977355957s
Interoperability | New vocabularies check for Apertium RDF EU-ES took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-ES took 0.30711865425109863s
Accuracy | Check Functional Property for Apertium RDF EU-ES took 0.29026007652282715s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-ES took 0.2824361324310303s
Accuracy | Check Empty annotation labels for Apertium RDF EU-ES took 0.8471822738647461s
Accuracy | Check White space in annotation for Apertium RDF EU-ES took 0.010118961334228516s
Accuracy | Check Datatype consistency for Apertium RDF EU-ES took 2.7650277614593506s
Consistency | Disjoint class check for Apertium RDF EU-ES took 0.30217766761779785s
Consistency | Check Misplaced properties for Apertium RDF EU-ES took 4.6488893032073975s
Consistency | Misplaced classes for Apertium RDF EU-ES took 8.548542976379395s
Consistency | Check Ontology hijacking for Apertium RDF EU-ES took 96.46216702461243s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-ES took 1.568718671798706s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-ES took 5.803333282470703s
Conciseness | Check Extensional conciseness for Apertium RDF EU-ES took 3.0958826541900635s
Conciseness | Check Intensional conciseness for Apertium RDF EU-ES took 0.4897937774658203s
Security | Sign check for Apertium RDF EU-ES took 0.32270193099975586s
Availability | Check URIs Dereferenciability for Apertium RDF EU-ES took 10.434690475463867s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.4113306999206543s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-ES took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 640.0836839675903s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 0.24344682693481445s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0006959438323974609s
Extra | Recovery of all triples for Apertium RDF FR-CA took 262.8019645214081s
Performance | Total latancy measurement for Apertium RDF FR-CA took 1.2984764575958252s
Amount of data | Number of triples check for Apertium RDF FR-CA took 2.2319529056549072s
Interoperability | New terms check for Apertium RDF FR-CA took 2.9060916900634766s
Versatility | Languages check for Apertium RDF FR-CA took 44.038333892822266s
Interpretability | Number of blank nodes check for Apertium RDF FR-CA took 1.070876121520996s
Security | Check HTTPS for Apertium RDF FR-CA took 0.12392139434814453s
Interpretability | RDF structures check for Apertium RDF FR-CA took 0.29064226150512695s
Versatility | Serialization formats check for Apertium RDF FR-CA took 0.2741243839263916s
Availability | RDF dump link check for Apertium RDF FR-CA took 0.2789759635925293s
License | MR license check for Apertium RDF FR-CA took 0.2790358066558838s
License | HR license check for Apertium RDF FR-CA took 0.37629246711730957s
Amount of data | Number of property check for Apertium RDF FR-CA took 0.2947556972503662s
Understandability | Number of label check for Apertium RDF FR-CA took 0.31258440017700195s
Understandability | URI regex check for Apertium RDF FR-CA took 0.5560824871063232s
Understandability | Vocabs check for Apertium RDF FR-CA took 0.300243616104126s
Verifiability | Authors check for Apertium RDF FR-CA took 0.30484771728515625s
Verifiability | Publishers check for Apertium RDF FR-CA took 0.29188036918640137s
Performance | Throughput check for Apertium RDF FR-CA took 11.246360063552856s
Amount of data | Check the number of entities for Apertium RDF FR-CA took 0.00011205673217773438s
Verifiability | Contribs. check for Apertium RDF FR-CA took 0.304063081741333s
Interlinking | sameAs chians check for Apertium RDF FR-CA took 0.2764170169830322s
Interlinking | skos check for Apertium RDF FR-CA took 0.29010009765625s
Interlinking | skos check for Apertium RDF FR-CA took 0.21781039237976074s
Timeliness | dataset update frequency check for Apertium RDF FR-CA took 0.27814579010009766s
Currency | Creation date check for Apertium RDF FR-CA took 0.58917236328125s
Currency | Modification date check for Apertium RDF FR-CA took 0.6211655139923096s
Rep.Conc. | URIs length for Apertium RDF FR-CA took 90.20996308326721s
Interoperability | New vocabularies check for Apertium RDF FR-CA took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-CA took 0.3432481288909912s
Accuracy | Check Functional Property for Apertium RDF FR-CA took 0.3060731887817383s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-CA took 0.4728989601135254s
Accuracy | Check Empty annotation labels for Apertium RDF FR-CA took 0.9398448467254639s
Accuracy | Check White space in annotation for Apertium RDF FR-CA took 0.010389328002929688s
Accuracy | Check Datatype consistency for Apertium RDF FR-CA took 2.6862330436706543s
Consistency | Disjoint class check for Apertium RDF FR-CA took 0.2807128429412842s
Consistency | Check Misplaced properties for Apertium RDF FR-CA took 4.795372247695923s
Consistency | Misplaced classes for Apertium RDF FR-CA took 8.506033658981323s
Consistency | Check Ontology hijacking for Apertium RDF FR-CA took 97.3691143989563s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-CA took 1.536008358001709s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-CA took 5.835419178009033s
Conciseness | Check Extensional conciseness for Apertium RDF FR-CA took 3.0688133239746094s
Conciseness | Check Intensional conciseness for Apertium RDF FR-CA took 0.3353734016418457s
Security | Sign check for Apertium RDF FR-CA took 0.29904747009277344s
Availability | Check URIs Dereferenciability for Apertium RDF FR-CA took 9.973699569702148s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.4806177616119385s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02086639404296875s
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.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-CA took 1.1920928955078125e-06s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 640.2643277645111s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 0.22126007080078125s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0007851123809814453s
Extra | Recovery of all triples for Apertium RDF FR-ES took 266.01479148864746s
Performance | Total latancy measurement for Apertium RDF FR-ES took 1.406484842300415s
Amount of data | Number of triples check for Apertium RDF FR-ES took 2.1750171184539795s
Interoperability | New terms check for Apertium RDF FR-ES took 3.1106231212615967s
Versatility | Languages check for Apertium RDF FR-ES took 44.084845781326294s
Interpretability | Number of blank nodes check for Apertium RDF FR-ES took 1.2804417610168457s
Security | Check HTTPS for Apertium RDF FR-ES took 0.12614846229553223s
Interpretability | RDF structures check for Apertium RDF FR-ES took 0.2774984836578369s
Versatility | Serialization formats check for Apertium RDF FR-ES took 0.3252251148223877s
Availability | RDF dump link check for Apertium RDF FR-ES took 0.2875640392303467s
License | MR license check for Apertium RDF FR-ES took 0.28063464164733887s
License | HR license check for Apertium RDF FR-ES took 0.5552175045013428s
Amount of data | Number of property check for Apertium RDF FR-ES took 0.28606677055358887s
Understandability | Number of label check for Apertium RDF FR-ES took 0.3178846836090088s
Understandability | URI regex check for Apertium RDF FR-ES took 0.5934665203094482s
Understandability | Vocabs check for Apertium RDF FR-ES took 0.2745370864868164s
Verifiability | Authors check for Apertium RDF FR-ES took 0.27843427658081055s
Verifiability | Publishers check for Apertium RDF FR-ES took 0.27533602714538574s
Performance | Throughput check for Apertium RDF FR-ES took 11.34222936630249s
Amount of data | Check the number of entities for Apertium RDF FR-ES took 7.05718994140625e-05s
Verifiability | Contribs. check for Apertium RDF FR-ES took 0.3005032539367676s
Interlinking | sameAs chians check for Apertium RDF FR-ES took 0.2798614501953125s
Interlinking | skos check for Apertium RDF FR-ES took 0.28035712242126465s
Interlinking | skos check for Apertium RDF FR-ES took 0.22359824180603027s
Timeliness | dataset update frequency check for Apertium RDF FR-ES took 0.2926323413848877s
Currency | Creation date check for Apertium RDF FR-ES took 0.5463953018188477s
Currency | Modification date check for Apertium RDF FR-ES took 0.5864019393920898s
Rep.Conc. | URIs length for Apertium RDF FR-ES took 86.81988406181335s
Interoperability | New vocabularies check for Apertium RDF FR-ES took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-ES took 0.294954776763916s
Accuracy | Check Functional Property for Apertium RDF FR-ES took 0.31056714057922363s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-ES took 0.2855033874511719s
Accuracy | Check Empty annotation labels for Apertium RDF FR-ES took 0.9631237983703613s
Accuracy | Check White space in annotation for Apertium RDF FR-ES took 0.010195255279541016s
Accuracy | Check Datatype consistency for Apertium RDF FR-ES took 2.699134588241577s
Consistency | Disjoint class check for Apertium RDF FR-ES took 0.29238367080688477s
Consistency | Check Misplaced properties for Apertium RDF FR-ES took 4.911623954772949s
Consistency | Misplaced classes for Apertium RDF FR-ES took 8.571467876434326s
Consistency | Check Ontology hijacking for Apertium RDF FR-ES took 95.85395312309265s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-ES took 1.5795042514801025s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-ES took 5.827581405639648s
Conciseness | Check Extensional conciseness for Apertium RDF FR-ES took 3.1728134155273438s
Conciseness | Check Intensional conciseness for Apertium RDF FR-ES took 0.3284149169921875s
Security | Sign check for Apertium RDF FR-ES took 0.2673332691192627s
Availability | Check URIs Dereferenciability for Apertium RDF FR-ES took 10.73986029624939s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.9796833992004395s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.02212238311767578s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0011315345764160156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 6.818771362304688e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-ES took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF FR-ES took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 648.3265340328217s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 0.2272167205810547s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0006489753723144531s
Extra | Recovery of all triples for Apertium RDF OC-CA took 262.880113363266s
Performance | Total latancy measurement for Apertium RDF OC-CA took 1.2510912418365479s
Amount of data | Number of triples check for Apertium RDF OC-CA took 2.243473768234253s
Interoperability | New terms check for Apertium RDF OC-CA took 2.932868480682373s
Versatility | Languages check for Apertium RDF OC-CA took 44.2786602973938s
Interpretability | Number of blank nodes check for Apertium RDF OC-CA took 1.2539036273956299s
Security | Check HTTPS for Apertium RDF OC-CA took 0.13342618942260742s
Interpretability | RDF structures check for Apertium RDF OC-CA took 0.2958521842956543s
Versatility | Serialization formats check for Apertium RDF OC-CA took 0.3130366802215576s
Availability | RDF dump link check for Apertium RDF OC-CA took 0.2744407653808594s
License | MR license check for Apertium RDF OC-CA took 0.29857730865478516s
License | HR license check for Apertium RDF OC-CA took 0.38530683517456055s
Amount of data | Number of property check for Apertium RDF OC-CA took 0.285358190536499s
Understandability | Number of label check for Apertium RDF OC-CA took 0.31463027000427246s
Understandability | URI regex check for Apertium RDF OC-CA took 0.5476853847503662s
Understandability | Vocabs check for Apertium RDF OC-CA took 0.2828493118286133s
Verifiability | Authors check for Apertium RDF OC-CA took 0.2939643859863281s
Verifiability | Publishers check for Apertium RDF OC-CA took 0.3338301181793213s
Performance | Throughput check for Apertium RDF OC-CA took 11.379696369171143s
Amount of data | Check the number of entities for Apertium RDF OC-CA took 7.176399230957031e-05s
Verifiability | Contribs. check for Apertium RDF OC-CA took 0.28685832023620605s
Interlinking | sameAs chians check for Apertium RDF OC-CA took 0.28339147567749023s
Interlinking | skos check for Apertium RDF OC-CA took 0.28653669357299805s
Interlinking | skos check for Apertium RDF OC-CA took 0.21215415000915527s
Timeliness | dataset update frequency check for Apertium RDF OC-CA took 0.28032779693603516s
Currency | Creation date check for Apertium RDF OC-CA took 0.5755839347839355s
Currency | Modification date check for Apertium RDF OC-CA took 0.5766324996948242s
Rep.Conc. | URIs length for Apertium RDF OC-CA took 94.13771176338196s
Interoperability | New vocabularies check for Apertium RDF OC-CA took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-CA took 0.3184659481048584s
Accuracy | Check Functional Property for Apertium RDF OC-CA took 0.3080098628997803s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-CA took 0.2875373363494873s
Accuracy | Check Empty annotation labels for Apertium RDF OC-CA took 0.8174290657043457s
Accuracy | Check White space in annotation for Apertium RDF OC-CA took 0.010178327560424805s
Accuracy | Check Datatype consistency for Apertium RDF OC-CA took 2.728227138519287s
Consistency | Disjoint class check for Apertium RDF OC-CA took 0.3091847896575928s
Consistency | Check Misplaced properties for Apertium RDF OC-CA took 4.64359450340271s
Consistency | Misplaced classes for Apertium RDF OC-CA took 8.581218004226685s
Consistency | Check Ontology hijacking for Apertium RDF OC-CA took 90.70662426948547s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-CA took 1.5190861225128174s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-CA took 5.726907014846802s
Conciseness | Check Extensional conciseness for Apertium RDF OC-CA took 3.096637725830078s
Conciseness | Check Intensional conciseness for Apertium RDF OC-CA took 0.33204007148742676s
Security | Sign check for Apertium RDF OC-CA took 0.2790713310241699s
Availability | Check URIs Dereferenciability for Apertium RDF OC-CA took 10.088541269302368s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 1.1306018829345703s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-CA took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 629.3378098011017s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 0.21938633918762207s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.00118255615234375s
Extra | Recovery of all triples for Apertium RDF OC-ES took 275.8493797779083s
Performance | Total latancy measurement for Apertium RDF OC-ES took 1.3009259700775146s
Amount of data | Number of triples check for Apertium RDF OC-ES took 2.1838343143463135s
Interoperability | New terms check for Apertium RDF OC-ES took 3.44642972946167s
Versatility | Languages check for Apertium RDF OC-ES took 43.94848966598511s
Interpretability | Number of blank nodes check for Apertium RDF OC-ES took 1.1096315383911133s
Security | Check HTTPS for Apertium RDF OC-ES took 0.14309978485107422s
Interpretability | RDF structures check for Apertium RDF OC-ES took 0.30425596237182617s
Versatility | Serialization formats check for Apertium RDF OC-ES took 0.3223388195037842s
Availability | RDF dump link check for Apertium RDF OC-ES took 0.3269920349121094s
License | MR license check for Apertium RDF OC-ES took 0.3101468086242676s
License | HR license check for Apertium RDF OC-ES took 0.4035511016845703s
Amount of data | Number of property check for Apertium RDF OC-ES took 0.3100876808166504s
Understandability | Number of label check for Apertium RDF OC-ES took 0.33896446228027344s
Understandability | URI regex check for Apertium RDF OC-ES took 0.5923967361450195s
Understandability | Vocabs check for Apertium RDF OC-ES took 0.295943021774292s
Verifiability | Authors check for Apertium RDF OC-ES took 0.3051722049713135s
Verifiability | Publishers check for Apertium RDF OC-ES took 0.3200809955596924s
Performance | Throughput check for Apertium RDF OC-ES took 11.541443586349487s
Amount of data | Check the number of entities for Apertium RDF OC-ES took 7.104873657226562e-05s
Verifiability | Contribs. check for Apertium RDF OC-ES took 0.29392457008361816s
Interlinking | sameAs chians check for Apertium RDF OC-ES took 0.6011865139007568s
Interlinking | skos check for Apertium RDF OC-ES took 0.2994420528411865s
Interlinking | skos check for Apertium RDF OC-ES took 0.23523640632629395s
Timeliness | dataset update frequency check for Apertium RDF OC-ES took 0.3110637664794922s
Currency | Creation date check for Apertium RDF OC-ES took 0.5585541725158691s
Currency | Modification date check for Apertium RDF OC-ES took 0.5978865623474121s
Rep.Conc. | URIs length for Apertium RDF OC-ES took 89.77441501617432s
Interoperability | New vocabularies check for Apertium RDF OC-ES took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-ES took 0.32285165786743164s
Accuracy | Check Functional Property for Apertium RDF OC-ES took 0.297029972076416s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-ES took 0.30723142623901367s
Accuracy | Check Empty annotation labels for Apertium RDF OC-ES took 1.0089173316955566s
Accuracy | Check White space in annotation for Apertium RDF OC-ES took 0.010280847549438477s
Accuracy | Check Datatype consistency for Apertium RDF OC-ES took 2.6930463314056396s
Consistency | Disjoint class check for Apertium RDF OC-ES took 0.283510684967041s
Consistency | Check Misplaced properties for Apertium RDF OC-ES took 4.58019495010376s
Consistency | Misplaced classes for Apertium RDF OC-ES took 8.59192180633545s
Consistency | Check Ontology hijacking for Apertium RDF OC-ES took 89.68995952606201s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-ES took 1.5014636516571045s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-ES took 5.65627121925354s
Conciseness | Check Extensional conciseness for Apertium RDF OC-ES took 3.0683045387268066s
Conciseness | Check Intensional conciseness for Apertium RDF OC-ES took 0.3329145908355713s
Security | Sign check for Apertium RDF OC-ES took 0.3174288272857666s
Availability | Check URIs Dereferenciability for Apertium RDF OC-ES took 9.772538185119629s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 21.211491107940674s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-ES took 1.1920928955078125e-06s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 686.5323987007141s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 0.3087582588195801s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006363391876220703s
Extra | Recovery of all triples for Apertium RDF PT-CA took 250.23515701293945s
Performance | Total latancy measurement for Apertium RDF PT-CA took 1.3450746536254883s
Amount of data | Number of triples check for Apertium RDF PT-CA took 2.2082841396331787s
Interoperability | New terms check for Apertium RDF PT-CA took 2.9565653800964355s
Versatility | Languages check for Apertium RDF PT-CA took 44.59282636642456s
Interpretability | Number of blank nodes check for Apertium RDF PT-CA took 1.0911879539489746s
Security | Check HTTPS for Apertium RDF PT-CA took 0.1356487274169922s
Interpretability | RDF structures check for Apertium RDF PT-CA took 0.2784698009490967s
Versatility | Serialization formats check for Apertium RDF PT-CA took 0.2985191345214844s
Availability | RDF dump link check for Apertium RDF PT-CA took 0.27675318717956543s
License | MR license check for Apertium RDF PT-CA took 0.2755467891693115s
License | HR license check for Apertium RDF PT-CA took 0.3839750289916992s
Amount of data | Number of property check for Apertium RDF PT-CA took 0.3179166316986084s
Understandability | Number of label check for Apertium RDF PT-CA took 0.32196497917175293s
Understandability | URI regex check for Apertium RDF PT-CA took 0.6096422672271729s
Understandability | Vocabs check for Apertium RDF PT-CA took 0.31902050971984863s
Verifiability | Authors check for Apertium RDF PT-CA took 0.2876462936401367s
Verifiability | Publishers check for Apertium RDF PT-CA took 0.4097120761871338s
Performance | Throughput check for Apertium RDF PT-CA took 11.349843978881836s
Amount of data | Check the number of entities for Apertium RDF PT-CA took 3.24249267578125e-05s
Verifiability | Contribs. check for Apertium RDF PT-CA took 0.2925558090209961s
Interlinking | sameAs chians check for Apertium RDF PT-CA took 0.31126856803894043s
Interlinking | skos check for Apertium RDF PT-CA took 0.28278183937072754s
Interlinking | skos check for Apertium RDF PT-CA took 0.22601675987243652s
Timeliness | dataset update frequency check for Apertium RDF PT-CA took 0.285524845123291s
Currency | Creation date check for Apertium RDF PT-CA took 0.5457284450531006s
Currency | Modification date check for Apertium RDF PT-CA took 0.6050503253936768s
Rep.Conc. | URIs length for Apertium RDF PT-CA took 90.75196552276611s
Interoperability | New vocabularies check for Apertium RDF PT-CA took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-CA took 0.33149051666259766s
Accuracy | Check Functional Property for Apertium RDF PT-CA took 0.3032243251800537s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-CA took 0.2944355010986328s
Accuracy | Check Empty annotation labels for Apertium RDF PT-CA took 0.8539068698883057s
Accuracy | Check White space in annotation for Apertium RDF PT-CA took 0.010058403015136719s
Accuracy | Check Datatype consistency for Apertium RDF PT-CA took 2.6899561882019043s
Consistency | Disjoint class check for Apertium RDF PT-CA took 0.29448390007019043s
Consistency | Check Misplaced properties for Apertium RDF PT-CA took 4.713125944137573s
Consistency | Misplaced classes for Apertium RDF PT-CA took 8.643142223358154s
Consistency | Check Ontology hijacking for Apertium RDF PT-CA took 86.15243601799011s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-CA took 1.652831792831421s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-CA took 5.876797676086426s
Conciseness | Check Extensional conciseness for Apertium RDF PT-CA took 3.0893850326538086s
Conciseness | Check Intensional conciseness for Apertium RDF PT-CA took 0.3110833168029785s
Security | Sign check for Apertium RDF PT-CA took 0.27475786209106445s
Availability | Check URIs Dereferenciability for Apertium RDF PT-CA took 10.0375075340271s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 4.095372438430786s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.021134376525878906s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 630.4628095626831s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 0.23092103004455566s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0004801750183105469s
Extra | Recovery of all triples for Apertium RDF PT-GL took 276.27101039886475s
Performance | Total latancy measurement for Apertium RDF PT-GL took 1.3139920234680176s
Amount of data | Number of triples check for Apertium RDF PT-GL took 2.166776657104492s
Interoperability | New terms check for Apertium RDF PT-GL took 2.935634136199951s
Versatility | Languages check for Apertium RDF PT-GL took 43.95578169822693s
Interpretability | Number of blank nodes check for Apertium RDF PT-GL took 1.1141443252563477s
Security | Check HTTPS for Apertium RDF PT-GL took 0.1342611312866211s
Interpretability | RDF structures check for Apertium RDF PT-GL took 0.3316764831542969s
Versatility | Serialization formats check for Apertium RDF PT-GL took 0.28487396240234375s
Availability | RDF dump link check for Apertium RDF PT-GL took 0.28851962089538574s
License | MR license check for Apertium RDF PT-GL took 0.28913021087646484s
License | HR license check for Apertium RDF PT-GL took 0.3732469081878662s
Amount of data | Number of property check for Apertium RDF PT-GL took 0.29097485542297363s
Understandability | Number of label check for Apertium RDF PT-GL took 0.32194972038269043s
Understandability | URI regex check for Apertium RDF PT-GL took 0.5791196823120117s
Understandability | Vocabs check for Apertium RDF PT-GL took 0.440838098526001s
Verifiability | Authors check for Apertium RDF PT-GL took 0.35639452934265137s
Verifiability | Publishers check for Apertium RDF PT-GL took 0.2883641719818115s
Performance | Throughput check for Apertium RDF PT-GL took 11.304330110549927s
Amount of data | Check the number of entities for Apertium RDF PT-GL took 7.510185241699219e-05s
Verifiability | Contribs. check for Apertium RDF PT-GL took 0.2910339832305908s
Interlinking | sameAs chians check for Apertium RDF PT-GL took 0.29117608070373535s
Interlinking | skos check for Apertium RDF PT-GL took 0.28752803802490234s
Interlinking | skos check for Apertium RDF PT-GL took 0.22848296165466309s
Timeliness | dataset update frequency check for Apertium RDF PT-GL took 0.27089929580688477s
Currency | Creation date check for Apertium RDF PT-GL took 0.5647246837615967s
Currency | Modification date check for Apertium RDF PT-GL took 0.6294190883636475s
Rep.Conc. | URIs length for Apertium RDF PT-GL took 90.11592507362366s
Interoperability | New vocabularies check for Apertium RDF PT-GL took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-GL took 0.33727192878723145s
Accuracy | Check Functional Property for Apertium RDF PT-GL took 0.3007206916809082s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-GL took 0.29876708984375s
Accuracy | Check Empty annotation labels for Apertium RDF PT-GL took 0.8472769260406494s
Accuracy | Check White space in annotation for Apertium RDF PT-GL took 0.010081052780151367s
Accuracy | Check Datatype consistency for Apertium RDF PT-GL took 2.7159104347229004s
Consistency | Disjoint class check for Apertium RDF PT-GL took 0.2882041931152344s
Consistency | Check Misplaced properties for Apertium RDF PT-GL took 4.732868432998657s
Consistency | Misplaced classes for Apertium RDF PT-GL took 8.510396957397461s
Consistency | Check Ontology hijacking for Apertium RDF PT-GL took 96.4406487941742s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-GL took 1.5272552967071533s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-GL took 5.710726976394653s
Conciseness | Check Extensional conciseness for Apertium RDF PT-GL took 3.07755970954895s
Conciseness | Check Intensional conciseness for Apertium RDF PT-GL took 0.3052635192871094s
Security | Sign check for Apertium RDF PT-GL took 0.3468794822692871s
Availability | Check URIs Dereferenciability for Apertium RDF PT-GL took 10.28732967376709s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.36829423904418945s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020992755889892578s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-GL took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 649.893625497818s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.5313682556152344s
Availability | VoID file availability check for AragoDBPedia took 0.0008761882781982422s
Extra | Recovery of all triples for AragoDBPedia took 2.616037130355835s
Performance | Total latancy measurement for AragoDBPedia took 1.5488953590393066s
Amount of data | Number of triples check for AragoDBPedia took 0.9689257144927979s
Interoperability | New terms check for AragoDBPedia took 2.1540234088897705s
Versatility | Languages check for AragoDBPedia took 60.401282787323s
Interpretability | Number of blank nodes check for AragoDBPedia took 4.127145051956177s
Security | Check HTTPS for AragoDBPedia took 0.1896355152130127s
Interpretability | RDF structures check for AragoDBPedia took 0.7794170379638672s
Versatility | Serialization formats check for AragoDBPedia took 0.8591384887695312s
Availability | RDF dump link check for AragoDBPedia took 0.3406558036804199s
License | MR license check for AragoDBPedia took 0.6104874610900879s
License | HR license check for AragoDBPedia took 6.858896017074585s
Amount of data | Number of property check for AragoDBPedia took 0.3559117317199707s
Understandability | Number of label check for AragoDBPedia took 0.5192828178405762s
Understandability | URI regex check for AragoDBPedia took 0.8231472969055176s
Understandability | Vocabs check for AragoDBPedia took 0.46024417877197266s
Verifiability | Authors check for AragoDBPedia took 0.4802086353302002s
Verifiability | Publishers check for AragoDBPedia took 0.34401869773864746s
Performance | Throughput check for AragoDBPedia took 12.36087965965271s
Amount of data | Check the number of entities for AragoDBPedia took 8.678436279296875e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.46835994720458984s
Interlinking | sameAs chians check for AragoDBPedia took 0.33611035346984863s
Interlinking | skos check for AragoDBPedia took 0.6093802452087402s
Interlinking | skos check for AragoDBPedia took 0.3264040946960449s
Timeliness | dataset update frequency check for AragoDBPedia took 0.41829943656921387s
Currency | Creation date check for AragoDBPedia took 1.1383771896362305s
Currency | Modification date check for AragoDBPedia took 0.4302525520324707s
Rep.Conc. | URIs length for AragoDBPedia took 6.157888889312744s
Interoperability | New vocabularies check for AragoDBPedia took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.326812744140625s
Accuracy | Check Functional Property for AragoDBPedia took 0.41829776763916016s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.41675782203674316s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.0212767124176025s
Accuracy | Check White space in annotation for AragoDBPedia took 0.0299072265625s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.029859066009521484s
Consistency | Disjoint class check for AragoDBPedia took 0.34883904457092285s
Consistency | Check Misplaced properties for AragoDBPedia took 4.6227569580078125s
Consistency | Misplaced classes for AragoDBPedia took 0.5405895709991455s
Consistency | Check Ontology hijacking for AragoDBPedia took 3.38388729095459s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.5405426025390625s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 6.1732213497161865s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.034152984619140625s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.45961618423461914s
Security | Sign check for AragoDBPedia took 0.6106665134429932s
Availability | Check URIs Dereferenciability for AragoDBPedia took 2814.174231529236s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 0.6987526416778564s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.023968935012817383s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0011048316955566406s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 6.151199340820312e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for AragoDBPedia took 8.58306884765625e-06s
INFO | --- Analysis for aragodbpedia took 3002.4378051757812s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.332122087478638s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0007829666137695312s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.4570801258087158s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.02124929428100586s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0009076595306396484s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.5789947509765625e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for archiveshub-linkeddata took 65.10634779930115s
Availability | SPARQL endpoint availability check for Archivi ISMA took 30.136404514312744s
Availability | VoID file availability check for Archivi ISMA took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 1.1370913982391357s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.02152395248413086s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0010230541229248047s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 4.9114227294921875e-05s
Believability | Calculation of trust value for Archivi ISMA took 1.6689300537109375e-05s
INFO | --- Analysis for archivio-isma took 72.95984244346619s
Availability | SPARQL endpoint availability check for ARIADNE took 0.4484975337982178s
Availability | VoID file availability check for ARIADNE took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.4192018508911133s
Reputation | Calculation of the PageRank for ARIADNE took 0.02145981788635254s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 4.38690185546875e-05s
Believability | Calculation of trust value for ARIADNE took 1.1682510375976562e-05s
INFO | --- Analysis for ariadne took 132.5950391292572s
Availability | SPARQL endpoint availability check for Aristotle University took 1.8999667167663574s
Availability | VoID file availability check for Aristotle University took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.3173849582672119s
Reputation | Calculation of the PageRank for Aristotle University took 0.02195119857788086s
Interlinking | Calculation of Degree of Connection for Aristotle University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.075599670410156e-05s
Believability | Calculation of trust value for Aristotle University took 1.430511474609375e-05s
INFO | --- Analysis for aristotle-university took 5.8247034549713135s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.006236791610718s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.31602025032043457s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.021041154861450195s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0009565353393554688s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 4.0531158447265625e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.2874603271484375e-05s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 21.484731197357178s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 8.940696716308594e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.33254170417785645s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.022823333740234375s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.2901763916015625e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.239776611328125e-05s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.0953972339630127s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.8625433444976807s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.2891554832458496s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020615577697753906s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.910064697265625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.2159347534179688e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 13.594699144363403s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 8.821487426757812e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.4089477062225342s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.021050691604614258s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0001049041748046875s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.2636184692382812e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 10.939474821090698s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.57763671875e-05s
Availability | VoID file availability check for Arthroscopy community took 0.00036716461181640625s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 2.6959493160247803s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02115774154663086s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.0001201629638671875s
Believability | Calculation of trust value for Arthroscopy community took 1.1444091796875e-05s
INFO | --- Analysis for arthroscopy took 46.73686194419861s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.3578388690948486s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.3274550437927246s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0009322166442871094s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.059906005859375e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 13.294108390808105s
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.402125597000122s
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.0003898143768310547s
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.3856182098388672s
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.024590730667114258s
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.430511474609375e-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.000990152359008789s
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 0.00010442733764648438s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 10.78126072883606s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.403592824935913s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.5465896129608154s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.441375732421875e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 14.414912700653076s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.4136409759521484s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0007543563842773438s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.34060025215148926s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.021347522735595703s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.935264587402344e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-CRB took 15.208911895751953s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.3977532386779785s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.3250575065612793s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.021593570709228516s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.00010132789611816406s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0251998901367188e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 14.386443376541138s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.379669427871704s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 1.2431433200836182s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.0967254638671875e-05s
INFO | --- Analysis for ASCDC-DQOT took 13.668405294418335s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.3943588733673096s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0003705024719238281s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.5059986114501953s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.021600961685180664s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0008728504180908203s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.606910705566406e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0251998901367188e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.948658227920532s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.164506673812866s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.00038695335388183594s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.5420446395874023s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.02144026756286621s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.869171142578125e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 16.596774578094482s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.417678117752075s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0003769397735595703s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.45337510108947754s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.03123331069946289s
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.5735626220703125e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0014243125915527344s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 8.320808410644531e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.049041748046875e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 13.698338747024536s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.428809642791748s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0003998279571533203s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.4200623035430908s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.025989055633544922s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0013778209686279297s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 7.891654968261719e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 12.746671676635742s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.8587958812713623s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.40056419372558594s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.023440122604370117s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0013353824615478516s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.556510925292969e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 16.3445246219635s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.403395414352417s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0003650188446044922s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.33743834495544434s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0209352970123291s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 8.20159912109375e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 13.319169521331787s
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.3788790702819824s
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.00044155120849609375s
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.3213925361633301s
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.020615100860595703s
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 9.5367431640625e-06s
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.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 8.20159912109375e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.971298217773438s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.3718314170837402s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.8465869426727295s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.021239042282104492s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 5.340576171875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC_-_DNB took 12.273269653320312s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 9.703636169433594e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.6178970336914062s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.0207974910736084s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.794929504394531e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.0728836059570312e-05s
INFO | --- Analysis for asit took 13.873607635498047s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 0.00014638900756835938s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.33077383041381836s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.02202439308166504s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0008492469787597656s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.458427429199219e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 8.58306884765625e-06s
INFO | --- Analysis for asjp took 6.917234897613525s
Availability | SPARQL endpoint availability check for ASN:US took 267.21466040611267s
Availability | VoID file availability check for ASN:US took 0.0007951259613037109s
Completeness | Calculation of interlinking completeness for ASN:US took 0.8761477470397949s
Reputation | Calculation of the PageRank for ASN:US took 0.02224135398864746s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.43865966796875e-05s
Believability | Calculation of trust value for ASN:US took 1.1205673217773438e-05s
INFO | --- Analysis for asn-us took 424.17082929611206s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 8.7738037109375e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.30907750129699707s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.022975683212280273s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.2901763916015625e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 8.821487426757812e-06s
INFO | --- Analysis for aspire-mmu took 16.909983158111572s
Availability | SPARQL endpoint availability check for associations took 4.458427429199219e-05s
Availability | VoID file availability check for associations took 1.0962855815887451s
Completeness | Calculation of interlinking completeness for associations took 1.7942016124725342s
Reputation | Calculation of the PageRank for associations took 0.020362377166748047s
Interlinking | Calculation of Degree of Connection for associations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for associations took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for associations took 6.842613220214844e-05s
Interoperability | Check the re-using of existing vocabs for associations took 0.6590609550476074s
Believability | Calculation of trust value for associations took 8.344650268554688e-06s
INFO | --- Analysis for associations took 10.742713451385498s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 0.25356459617614746s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2867465019226074s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.0211489200592041s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.337860107421875e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 1.0251998901367188e-05s
INFO | --- Analysis for atc-publikovan--s-kl took 5.724303483963013s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 9.918212890625e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.3438405990600586s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.021570920944213867s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.179115295410156e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 7.152557373046875e-06s
INFO | --- Analysis for athelia-rfid took 10.917344808578491s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.47648286819458s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.3114657402038574s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.021991252899169922s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.266334533691406e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for aueb-linked-open-data took 13.309270858764648s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5646202564239502s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.5659685134887695s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.02086043357849121s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007288455963134766s
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 7.62939453125e-06s
INFO | --- Analysis for AugustiniConfessiones took 11.088058233261108s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.4694676399230957s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.39598798751831055s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.560585021972656e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.239776611328125e-05s
INFO | --- Analysis for austrian_ski_racers took 4.931698799133301s
Availability | SPARQL endpoint availability check for AVsOnto took 0.00012445449829101562s
Availability | VoID file availability check for AVsOnto took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.4380195140838623s
Reputation | Calculation of the PageRank for AVsOnto took 0.02096390724182129s
Interlinking | Calculation of Degree of Connection for AVsOnto took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.0517578125e-05s
Believability | Calculation of trust value for AVsOnto took 1.1682510375976562e-05s
INFO | --- Analysis for AVsOnto took 5.1597864627838135s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17186570167541504s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005257129669189453s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 27.391681671142578s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.665503978729248s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0923297405243s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0074677467346s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0159876346588s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1115126609802246s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.25298404693603516s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18317508697509766s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11860442161560059s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 202.46818161010742s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1025912761688s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12471985816955566s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0247540473938s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24464106559753418s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12117481231689453s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17012238502502441s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11470174789428711s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.011597156524658s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.486343383789062e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13052940368652344s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1038315296173s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.25414443016052246s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13092494010925293s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13550853729248047s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2495424747467041s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24636101722717285s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 473.51785016059875s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15103363990783691s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 30.916715621948242s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.4827451705932617s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.926556348800659s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12450695037841797s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.2112102508545s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 110.29536366462708s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.5336506366729736s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.47772765159607s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.929211139678955s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16408276557922363s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1662306785583496s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.674917459487915s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021266460418701172s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.319450378417969e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.8835067749023438e-05s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.059906005859375e-06s
INFO | --- Analysis for b3kat took 4190.101443767548s
Availability | SPARQL endpoint availability check for BabelNet took 0.5928871631622314s
Availability | VoID file availability check for BabelNet took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for BabelNet took 1.6855645179748535s
Reputation | Calculation of the PageRank for BabelNet took 0.021651506423950195s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0011119842529296875s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001938343048095703s
Believability | Calculation of trust value for BabelNet took 9.775161743164062e-06s
INFO | --- Analysis for babelnet took 8.064159393310547s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 8.654594421386719e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0008211135864257812s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 1.2284443378448486s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.1920928955078125e-05s
INFO | --- Analysis for Bacevicius.lt took 3.358705520629883s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.6103813648223877s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.31453514099121094s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.021045207977294922s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 5.650520324707031e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.239776611328125e-05s
INFO | --- Analysis for bag took 5.0954389572143555s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.35747313499450684s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 2.579864501953125s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020969390869140625s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.9802322387695312e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.33514404296875e-05s
INFO | --- Analysis for baixue took 5.635389566421509s
Availability | SPARQL endpoint availability check for baixue composer took 8.702278137207031e-05s
Availability | VoID file availability check for baixue composer took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for baixue composer took 1.7971012592315674s
Reputation | Calculation of the PageRank for baixue composer took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for baixue composer took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for baixue composer took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for baixue composer took 2.9087066650390625e-05s
Believability | Calculation of trust value for baixue composer took 1.2636184692382812e-05s
INFO | --- Analysis for baixue_composer took 5.560348749160767s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.393692016601562e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.619671106338501s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02104783058166504s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.2901763916015625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.2159347534179688e-05s
INFO | --- Analysis for baixue_imagery took 5.666522979736328s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.107589721679688e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0012555122375488281s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.5729320049285889s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.0220639705657959s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.9087066650390625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1444091796875e-05s
INFO | --- Analysis for baixue_imagery1 took 5.560549020767212s
Availability | SPARQL endpoint availability check for BAMS took 8.630752563476562e-05s
Availability | VoID file availability check for BAMS took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for BAMS took 0.7993173599243164s
Reputation | Calculation of the PageRank for BAMS took 0.02257513999938965s
Interlinking | Calculation of Degree of Connection for BAMS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BAMS took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.123283386230469e-05s
Believability | Calculation of trust value for BAMS took 1.2874603271484375e-05s
INFO | --- Analysis for bams took 11.087370157241821s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 8.821487426757812e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.3577558994293213s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.02127242088317871s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.315376281738281e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.3589859008789062e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 4.959970712661743s
Availability | SPARQL endpoint availability check for BBC Music took 0.8931059837341309s
Availability | VoID file availability check for BBC Music took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for BBC Music took 0.3242614269256592s
Reputation | Calculation of the PageRank for BBC Music took 0.0208895206451416s
Interlinking | Calculation of Degree of Connection for BBC Music took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBC Music took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001266002655029297s
Believability | Calculation of trust value for BBC Music took 1.1444091796875e-05s
INFO | --- Analysis for bbc-music took 4.696435451507568s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.39545655250549316s
Availability | VoID file availability check for BBC Programmes took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.44254255294799805s
Reputation | Calculation of the PageRank for BBC Programmes took 0.024268627166748047s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0011539459228515625s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00012826919555664062s
Believability | Calculation of trust value for BBC Programmes took 1.1920928955078125e-05s
INFO | --- Analysis for bbc-programmes took 13.431418180465698s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.3352656364440918s
Availability | VoID file availability check for BBC Wildlife Finder took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.4433400630950928s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020282983779907227s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 9.965896606445312e-05s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.1682510375976562e-05s
INFO | --- Analysis for bbc-wildlife-finder took 11.682773351669312s
Availability | SPARQL endpoint availability check for BBOP took 8.726119995117188e-05s
Availability | VoID file availability check for BBOP took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for BBOP took 0.35083937644958496s
Reputation | Calculation of the PageRank for BBOP took 0.02115345001220703s
Interlinking | Calculation of Degree of Connection for BBOP took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0010023117065429688s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.600120544433594e-05s
Believability | Calculation of trust value for BBOP took 1.0728836059570312e-05s
INFO | --- Analysis for bbop took 20.424013137817383s
Availability | SPARQL endpoint availability check for BBOP took 8.749961853027344e-05s
Availability | VoID file availability check for BBOP took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for BBOP took 0.3368079662322998s
Reputation | Calculation of the PageRank for BBOP took 0.02038121223449707s
Interlinking | Calculation of Degree of Connection for BBOP took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.7418136596679688e-05s
Believability | Calculation of trust value for BBOP took 1.2636184692382812e-05s
INFO | --- Analysis for bbop-selected took 26.24558925628662s
Availability | SPARQL endpoint availability check for Bdgp took 1.145277976989746s
Availability | VoID file availability check for Bdgp took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Bdgp took 2.12697696685791s
Reputation | Calculation of the PageRank for Bdgp took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.075599670410156e-05s
Believability | Calculation of trust value for Bdgp took 1.1920928955078125e-05s
INFO | --- Analysis for bdgp took 10.17285680770874s
Availability | SPARQL endpoint availability check for Bendev Junior took 8.916854858398438e-05s
Availability | VoID file availability check for Bendev Junior took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.5076403617858887s
Reputation | Calculation of the PageRank for Bendev Junior took 0.022563695907592773s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.001007080078125s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.6716461181640625e-05s
Believability | Calculation of trust value for Bendev Junior took 1.1920928955078125e-05s
INFO | --- Analysis for bendevoficial took 7.283974885940552s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 8.260623931884766s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0007491111755371094s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.3981194496154785s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.02201390266418457s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.510185241699219e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 9.298324584960938e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 19.01292395591736s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 0.00010323524475097656s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.42908668518066406s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.021943330764770508s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0010082721710205078s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.886222839355469e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 1.1682510375976562e-05s
INFO | --- Analysis for berlin-offener-haushalt took 2.1256356239318848s
Availability | SPARQL endpoint availability check for berlios took 9.870529174804688e-05s
Availability | VoID file availability check for berlios took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for berlios took 2.412437677383423s
Reputation | Calculation of the PageRank for berlios took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for berlios took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for berlios took 9.393692016601562e-05s
Believability | Calculation of trust value for berlios took 1.4781951904296875e-05s
INFO | --- Analysis for berlios took 5.884192943572998s
Availability | SPARQL endpoint availability check for Between Our Worlds took 8.726119995117188e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.3972795009613037s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.02179884910583496s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.914138793945312e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.2874603271484375e-05s
INFO | --- Analysis for betweenourworlds took 12.413039207458496s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.09675216674804688s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.3860790729522705s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.024090051651000977s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0014090538024902344s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00013685226440429688s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for bfs-linked-data took 3.3818514347076416s
Availability | SPARQL endpoint availability check for BibBase took 0.07346701622009277s
Availability | VoID file availability check for BibBase took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for BibBase took 0.30005407333374023s
Reputation | Calculation of the PageRank for BibBase took 0.02076268196105957s
Interlinking | Calculation of Degree of Connection for BibBase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.822845458984375e-05s
Believability | Calculation of trust value for BibBase took 1.3113021850585938e-05s
INFO | --- Analysis for bibbase took 3.8522019386291504s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 0.00010895729064941406s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0008053779602050781s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.5615484714508057s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.021441221237182617s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00010085105895996094s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.239776611328125e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 12.88512921333313s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.749961853027344e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 1.5512027740478516s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.021144866943359375s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.870529174804688e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.3113021850585938e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 9.473523378372192s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.00044417381286621094s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.5128588676452637s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.021561384201049805s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.504753112792969e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 5.41312050819397s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 8.749961853027344e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.9612681865692139s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020972013473510742s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.5762786865234375e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.1205673217773438e-05s
INFO | --- Analysis for BibSonomy took 13.562214136123657s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 8.7738037109375e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.3183455467224121s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.170967102050781e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.3589859008789062e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 8.212947845458984s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 8.726119995117188e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.3993866443634033s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020952224731445312s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.2636184692382812e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.7186009883880615s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 1.7809083461761475s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.321260929107666s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.021187782287597656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0008356571197509766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.409385681152344e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-acfsid took 19.09821581840515s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 0.2588052749633789s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006816387176513672s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 20.003867387771606s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5147991180419922s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 45.663198709487915s
Interoperability | New terms check for Bio2RDF::Affymetrix took 42.032533407211304s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.11955261230469s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.1390237808227539s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.2866637706756592s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.19032526016235352s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.2638139724731445s
License | MR license check for Bio2RDF::Affymetrix took 0.36414337158203125s
License | HR license check for Bio2RDF::Affymetrix took 60.10010290145874s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.12959527969360352s
Understandability | Number of label check for Bio2RDF::Affymetrix took 10.752824068069458s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.34647607803344727s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.12671375274658203s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.12230086326599121s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.13042521476745605s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.618117332458496s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.46297430992126465s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.14320945739746094s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.6588916778564453s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.23178744316101074s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.13336920738220215s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2608826160430908s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.2655010223388672s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 110.75680828094482s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.3088207244873047s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15023303031921387s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12184262275695801s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.27912163734436s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8822393417358398s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6643331050872803s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.3678874969482422s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 64.79782938957214s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.2505390644073486s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.697967052459717s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3878247737884521s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.44198703765869s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7136991024017334s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3263270854949951s
Security | Sign check for Bio2RDF::Affymetrix took 0.10940909385681152s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 11.091912269592285s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 2.6373212337493896s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.02054905891418457s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010347366333007812s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 1.1920928955078125e-06s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1014.5387449264526s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5281021595001221s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0007345676422119141s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 19.142162084579468s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2706477642059326s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 45.28111028671265s
Interoperability | New terms check for Bio2RDF::Biomodels took 40.402403116226196s
Versatility | Languages check for Bio2RDF::Biomodels took 60.26551294326782s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.26987195014953613s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.1458125114440918s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.5364322662353516s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.3045196533203125s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.357109546661377s
License | MR license check for Bio2RDF::Biomodels took 0.47910118103027344s
License | HR license check for Bio2RDF::Biomodels took 60.23712730407715s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.2574756145477295s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.346433162689209s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5610301494598389s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.23211097717285156s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.27802371978759766s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.2526876926422119s
Performance | Throughput check for Bio2RDF::Biomodels took 11.040771961212158s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 2.307943820953369s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.27167463302612305s
Interlinking | skos check for Bio2RDF::Biomodels took 0.7973544597625732s
Interlinking | skos check for Bio2RDF::Biomodels took 0.34487032890319824s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.26404905319213867s
Currency | Creation date check for Bio2RDF::Biomodels took 0.4900856018066406s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5058073997497559s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 107.93164420127869s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.46596765518188477s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.28677797317504883s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2833726406097412s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 6.585980415344238s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8860650062561035s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6590867042541504s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.28359293937683105s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.20883560180664s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.40163516998291s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.041280269622803s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.33198881149292s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.545955181121826s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.6973276138305664s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.4288370609283447s
Security | Sign check for Bio2RDF::Biomodels took 0.24553346633911133s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 9.811460256576538s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.5439317226409912s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011801719665527344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 1.430511474609375e-06s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1004.3631510734558s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 0.13361048698425293s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.3256826400756836s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.022446632385253906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 3.600120544433594e-05s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 2.8521642684936523s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.46948957443237305s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006461143493652344s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 18.799450635910034s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2596135139465332s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 45.2546865940094s
Interoperability | New terms check for Bio2RDF::Bioportal took 41.53735685348511s
Versatility | Languages check for Bio2RDF::Bioportal took 60.26831650733948s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.28008246421813965s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.14523673057556152s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.47913050651550293s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.32999205589294434s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.224313497543335s
License | MR license check for Bio2RDF::Bioportal took 0.27262282371520996s
License | HR license check for Bio2RDF::Bioportal took 60.26732635498047s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2565476894378662s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.013771295547485s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.6263580322265625s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2696413993835449s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.24767470359802246s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.2530391216278076s
Performance | Throughput check for Bio2RDF::Bioportal took 10.873579978942871s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.5884830951690674s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.2599217891693115s
Interlinking | skos check for Bio2RDF::Bioportal took 0.6201136112213135s
Interlinking | skos check for Bio2RDF::Bioportal took 0.34508180618286133s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.24273180961608887s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5170636177062988s
Currency | Modification date check for Bio2RDF::Bioportal took 0.4969604015350342s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 107.07277965545654s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4519326686859131s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.2675185203552246s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2415165901184082s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.74681830406189s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8916027545928955s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6614296436309814s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.31426501274108887s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 64.91456818580627s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.395223617553711s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.750058650970459s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3102853298187256s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.603960275650024s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7033662796020508s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.42351508140563965s
Security | Sign check for Bio2RDF::Bioportal took 0.2688770294189453s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 9.945295810699463s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 3.066791296005249s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02181720733642578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00044226646423339844s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 1.430511474609375e-06s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1021.841141462326s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.1435384750366211s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 2.1917476654052734s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.125999450683594e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-chembl took 25.752095699310303s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.48856282234191895s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0005908012390136719s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 19.115792989730835s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.234830617904663s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 45.926169872283936s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 41.757291316986084s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.26838755607605s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.26821041107177734s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.16682696342468262s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.3875129222869873s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.32683396339416504s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.211827516555786s
License | MR license check for Bio2RDF::Clinicaltrials took 0.38387537002563477s
License | HR license check for Bio2RDF::Clinicaltrials took 60.2387433052063s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.25359106063842773s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 9.632171392440796s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.6173474788665771s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.27448201179504395s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2676563262939453s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.2569766044616699s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.040385007858276s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.6274054050445557s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.274029016494751s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.7551512718200684s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3552384376525879s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.2597017288208008s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5125143527984619s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5064375400543213s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 108.26029562950134s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.43683290481567383s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2996234893798828s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.2849924564361572s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.8460774421691895s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.9011735916137695s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6686611175537109s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.30314183235168457s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.04711651802063s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.372128486633301s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.237212896347046s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3145651817321777s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.55806374549866s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7107574939727783s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.4345529079437256s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.25960230827331543s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 9.768287897109985s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 1.435753583908081s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 2.384185791015625e-06s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.0251998901367188e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1006.2590072154999s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 1.2756319046020508s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005972385406494141s
Extra | Recovery of all triples for Bio2RDF::Ctd took 19.309630155563354s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.267103910446167s
Amount of data | Number of triples check for Bio2RDF::Ctd took 45.65448045730591s
Interoperability | New terms check for Bio2RDF::Ctd took 40.80066227912903s
Versatility | Languages check for Bio2RDF::Ctd took 60.24062204360962s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2537994384765625s
Security | Check HTTPS for Bio2RDF::Ctd took 0.14436125755310059s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.2390139102935791s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.31465935707092285s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.47098445892334s
License | MR license check for Bio2RDF::Ctd took 0.3761606216430664s
License | HR license check for Bio2RDF::Ctd took 60.26029944419861s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.30742406845092773s
Understandability | Number of label check for Bio2RDF::Ctd took 10.157515287399292s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5979015827178955s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.25170373916625977s
Verifiability | Authors check for Bio2RDF::Ctd took 0.24147939682006836s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.27263569831848145s
Performance | Throughput check for Bio2RDF::Ctd took 11.23046088218689s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.6059820652008057s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.26348209381103516s
Interlinking | skos check for Bio2RDF::Ctd took 0.4451770782470703s
Interlinking | skos check for Bio2RDF::Ctd took 0.33829188346862793s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2487032413482666s
Currency | Creation date check for Bio2RDF::Ctd took 0.48479533195495605s
Currency | Modification date check for Bio2RDF::Ctd took 0.507958173751831s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 113.33769202232361s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4204416275024414s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2741820812225342s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.25330519676208496s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.336783409118652s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8781473636627197s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6543207168579102s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.44559383392333984s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.18466854095459s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.392521619796753s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.167784690856934s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.305802822113037s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.54698348045349s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.6967289447784424s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.4192476272583008s
Security | Sign check for Bio2RDF::Ctd took 0.2611863613128662s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 11.592305898666382s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 1.1347177028656006s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 1.430511474609375e-06s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-ctd took 1023.6093649864197s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 5.364418029785156e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0003714561462402344s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.32872796058654785s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.021544218063354492s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.14984130859375e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-dataset took 2.225895643234253s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.4978964328765869s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.000396728515625s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 18.695457220077515s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2586288452148438s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 46.014052867889404s
Interoperability | New terms check for Bio2RDF::Dbsnp took 40.7691650390625s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.25144076347351s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.269212007522583s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.15492630004882812s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.4469001293182373s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.32361340522766113s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.5376453399658203s
License | MR license check for Bio2RDF::Dbsnp took 0.47067785263061523s
License | HR license check for Bio2RDF::Dbsnp took 60.2754282951355s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2559976577758789s
Understandability | Number of label check for Bio2RDF::Dbsnp took 9.43334150314331s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5932328701019287s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.24320459365844727s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2733149528503418s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.25638246536254883s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.883845090866089s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.625342607498169s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.24614572525024414s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.8587515354156494s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.35186767578125s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2784404754638672s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5207304954528809s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5191113948822021s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 108.33911466598511s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4300715923309326s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.23937201499938965s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.26387929916381836s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.85081934928894s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8898286819458008s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6833169460296631s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.43410253524780273s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 64.96900248527527s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.426546335220337s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.083690881729126s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3227269649505615s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.553560972213745s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7169301509857178s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.4145388603210449s
Security | Sign check for Bio2RDF::Dbsnp took 0.2763497829437256s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 10.048025369644165s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 1.1985015869140625s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.025630712509155273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 5.2928924560546875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0011565685272216797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 0.00010442733764648438s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 2.6226043701171875e-06s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1009.640641450882s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.4721989631652832s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006101131439208984s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 18.19320297241211s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.589892864227295s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 45.3577299118042s
Interoperability | New terms check for Bio2RDF::Drugbank took 42.265127420425415s
Versatility | Languages check for Bio2RDF::Drugbank took 60.26908087730408s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2632322311401367s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.16817641258239746s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.4533810615539551s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3210482597351074s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.310377597808838s
License | MR license check for Bio2RDF::Drugbank took 0.5877935886383057s
License | HR license check for Bio2RDF::Drugbank took 60.25013208389282s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.27152037620544434s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.849430799484253s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.6126499176025391s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.261394739151001s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2713761329650879s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2646782398223877s
Performance | Throughput check for Bio2RDF::Drugbank took 10.533434629440308s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.5992496013641357s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.26511430740356445s
Interlinking | skos check for Bio2RDF::Drugbank took 0.5821826457977295s
Interlinking | skos check for Bio2RDF::Drugbank took 0.4003016948699951s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2774789333343506s
Currency | Creation date check for Bio2RDF::Drugbank took 0.4775669574737549s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5151562690734863s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 110.55652070045471s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4518141746520996s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.2693004608154297s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.23057055473327637s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 6.280463218688965s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8884263038635254s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6636784076690674s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.4616575241088867s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.48271322250366s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.461711883544922s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.185397386550903s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.2783763408660889s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.51746988296509s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7003195285797119s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.40696024894714355s
Security | Sign check for Bio2RDF::Drugbank took 0.24826312065124512s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 10.17222261428833s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 2.195279359817505s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011110305786132812s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 9.5367431640625e-07s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1018.6822991371155s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.47838473320007324s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006840229034423828s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.235989809036255s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2778992652893066s
Amount of data | Number of triples check for Bio2RDF::Genage took 45.48845386505127s
Interoperability | New terms check for Bio2RDF::Genage took 42.761354207992554s
Versatility | Languages check for Bio2RDF::Genage took 60.241687059402466s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2715489864349365s
Security | Check HTTPS for Bio2RDF::Genage took 0.15694785118103027s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.27741432189941406s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.29807424545288086s
Availability | RDF dump link check for Bio2RDF::Genage took 2.2439091205596924s
License | MR license check for Bio2RDF::Genage took 0.37172508239746094s
License | HR license check for Bio2RDF::Genage took 60.24870157241821s
Amount of data | Number of property check for Bio2RDF::Genage took 0.26755666732788086s
Understandability | Number of label check for Bio2RDF::Genage took 9.4886953830719s
Understandability | URI regex check for Bio2RDF::Genage took 0.6127777099609375s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2575855255126953s
Verifiability | Authors check for Bio2RDF::Genage took 0.25456833839416504s
Verifiability | Publishers check for Bio2RDF::Genage took 0.26023340225219727s
Performance | Throughput check for Bio2RDF::Genage took 10.862593173980713s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.623199462890625s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.2743234634399414s
Interlinking | skos check for Bio2RDF::Genage took 0.6290011405944824s
Interlinking | skos check for Bio2RDF::Genage took 0.341172456741333s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.24451231956481934s
Currency | Creation date check for Bio2RDF::Genage took 0.4838840961456299s
Currency | Modification date check for Bio2RDF::Genage took 0.509437084197998s
Rep.Conc. | URIs length for Bio2RDF::Genage took 107.40606570243835s
Interoperability | New vocabularies check for Bio2RDF::Genage took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4254150390625s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.27453064918518066s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.25650930404663086s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 6.473965883255005s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8867354393005371s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6617729663848877s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.25050806999206543s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.60059642791748s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.419131278991699s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 5.982186794281006s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3175132274627686s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.582470655441284s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7252688407897949s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.4160783290863037s
Security | Sign check for Bio2RDF::Genage took 0.28196144104003906s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 9.778222799301147s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.9193339347839355s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.021019458770751953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 7.009506225585938e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 1.6689300537109375e-06s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-genage took 1005.4420337677002s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 0.14071059226989746s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.31384921073913574s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.021195411682128906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.389617919921875e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-genbank took 6.413100481033325s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.46748948097229004s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006577968597412109s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.260916709899902s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2091798782348633s
Amount of data | Number of triples check for Bio2RDF::Gendr took 45.31513452529907s
Interoperability | New terms check for Bio2RDF::Gendr took 39.91792058944702s
Versatility | Languages check for Bio2RDF::Gendr took 60.25646233558655s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.25533199310302734s
Security | Check HTTPS for Bio2RDF::Gendr took 0.15477323532104492s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.2463521957397461s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.3014085292816162s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.2908935546875s
License | MR license check for Bio2RDF::Gendr took 0.5214369297027588s
License | HR license check for Bio2RDF::Gendr took 60.2618305683136s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.2555732727050781s
Understandability | Number of label check for Bio2RDF::Gendr took 9.746338129043579s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5744731426239014s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.23465943336486816s
Verifiability | Authors check for Bio2RDF::Gendr took 0.27118802070617676s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2542860507965088s
Performance | Throughput check for Bio2RDF::Gendr took 10.637882232666016s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.6245653629302979s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.29209160804748535s
Interlinking | skos check for Bio2RDF::Gendr took 0.5225965976715088s
Interlinking | skos check for Bio2RDF::Gendr took 0.3511490821838379s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2627542018890381s
Currency | Creation date check for Bio2RDF::Gendr took 0.49747729301452637s
Currency | Modification date check for Bio2RDF::Gendr took 0.5166957378387451s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 108.52834606170654s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.4528038501739502s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2775571346282959s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.29114246368408203s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.0863189697265625s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8842873573303223s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6583511829376221s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.4288206100463867s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.20076179504395s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.4006187915802s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.373082160949707s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.31955885887146s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.538410663604736s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.718897819519043s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.44266223907470703s
Security | Sign check for Bio2RDF::Gendr took 0.26526689529418945s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 11.725932121276855s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.5881967544555664s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020294666290283203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 9.5367431640625e-07s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-gendr took 1011.0076916217804s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.4851257801055908s
Availability | VoID file availability check for Bio2RDF::Goa took 0.00054168701171875s
Extra | Recovery of all triples for Bio2RDF::Goa took 18.94361639022827s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.232924222946167s
Amount of data | Number of triples check for Bio2RDF::Goa took 45.462910652160645s
Interoperability | New terms check for Bio2RDF::Goa took 42.25483441352844s
Versatility | Languages check for Bio2RDF::Goa took 60.2401340007782s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.26079463958740234s
Security | Check HTTPS for Bio2RDF::Goa took 0.16762566566467285s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.38315248489379883s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.2909419536590576s
Availability | RDF dump link check for Bio2RDF::Goa took 2.37068772315979s
License | MR license check for Bio2RDF::Goa took 0.5259265899658203s
License | HR license check for Bio2RDF::Goa took 60.24925446510315s
Amount of data | Number of property check for Bio2RDF::Goa took 0.268524169921875s
Understandability | Number of label check for Bio2RDF::Goa took 9.54607105255127s
Understandability | URI regex check for Bio2RDF::Goa took 0.6048238277435303s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2672407627105713s
Verifiability | Authors check for Bio2RDF::Goa took 0.24159789085388184s
Verifiability | Publishers check for Bio2RDF::Goa took 0.2668905258178711s
Performance | Throughput check for Bio2RDF::Goa took 10.620186567306519s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.7486636638641357s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.27179646492004395s
Interlinking | skos check for Bio2RDF::Goa took 0.8290972709655762s
Interlinking | skos check for Bio2RDF::Goa took 0.35060906410217285s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2565937042236328s
Currency | Creation date check for Bio2RDF::Goa took 0.5268118381500244s
Currency | Modification date check for Bio2RDF::Goa took 0.5051908493041992s
Rep.Conc. | URIs length for Bio2RDF::Goa took 109.83349013328552s
Interoperability | New vocabularies check for Bio2RDF::Goa took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.4643838405609131s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2665984630584717s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.28215527534484863s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.535095453262329s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8802835941314697s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6563713550567627s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4672050476074219s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 64.94019985198975s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.3899595737457275s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.138217449188232s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.2746191024780273s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.49594211578369s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.6986327171325684s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.45111703872680664s
Security | Sign check for Bio2RDF::Goa took 0.28125429153442383s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 10.159667491912842s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.9627597332000732s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020636320114135742s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 7.176399230957031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 1.430511474609375e-06s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-goa took 1019.0235514640808s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.4752976894378662s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006601810455322266s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 19.018462419509888s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2680251598358154s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 45.77049803733826s
Interoperability | New terms check for Bio2RDF::Hgnc took 42.71062159538269s
Versatility | Languages check for Bio2RDF::Hgnc took 60.259419202804565s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2567176818847656s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.16452240943908691s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.35100388526916504s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.31591081619262695s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.282672166824341s
License | MR license check for Bio2RDF::Hgnc took 0.572091817855835s
License | HR license check for Bio2RDF::Hgnc took 60.23304533958435s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.23541688919067383s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.624029159545898s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5906310081481934s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.26103806495666504s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.2438066005706787s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.26061153411865234s
Performance | Throughput check for Bio2RDF::Hgnc took 11.064691066741943s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.608924150466919s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.2518634796142578s
Interlinking | skos check for Bio2RDF::Hgnc took 0.9253251552581787s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3554651737213135s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.23990106582641602s
Currency | Creation date check for Bio2RDF::Hgnc took 0.4886338710784912s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5179483890533447s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 109.30191421508789s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.44701337814331055s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.29755473136901855s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.24915695190429688s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.238571643829346s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8890392780303955s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6667616367340088s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4205482006072998s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.18093991279602s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.3699300289154053s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.7399938106536865s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.300882339477539s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.53686547279358s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7158348560333252s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.43433332443237305s
Security | Sign check for Bio2RDF::Hgnc took 0.24698257446289062s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 11.6022310256958s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 1.0434818267822266s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.021165847778320312s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0009639263153076172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00012755393981933594s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 1.430511474609375e-06s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1013.6856281757355s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.4839344024658203s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006878376007080078s
Extra | Recovery of all triples for Bio2RDF::Homologene took 19.098674058914185s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2507071495056152s
Amount of data | Number of triples check for Bio2RDF::Homologene took 45.39893984794617s
Interoperability | New terms check for Bio2RDF::Homologene took 40.71895670890808s
Versatility | Languages check for Bio2RDF::Homologene took 60.24105381965637s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.27146244049072266s
Security | Check HTTPS for Bio2RDF::Homologene took 0.15581321716308594s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.24797630310058594s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.33086705207824707s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.448814868927002s
License | MR license check for Bio2RDF::Homologene took 0.6270081996917725s
License | HR license check for Bio2RDF::Homologene took 60.266043186187744s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.26116347312927246s
Understandability | Number of label check for Bio2RDF::Homologene took 9.991876363754272s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5926878452301025s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.25679683685302734s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2544827461242676s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.25798654556274414s
Performance | Throughput check for Bio2RDF::Homologene took 11.279919147491455s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.6278181076049805s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.2646141052246094s
Interlinking | skos check for Bio2RDF::Homologene took 0.38692545890808105s
Interlinking | skos check for Bio2RDF::Homologene took 0.3635735511779785s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.25315093994140625s
Currency | Creation date check for Bio2RDF::Homologene took 0.49161267280578613s
Currency | Modification date check for Bio2RDF::Homologene took 0.530991792678833s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 108.81516289710999s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4403855800628662s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.27582454681396484s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.2515382766723633s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 8.807729482650757s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8894331455230713s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.7184336185455322s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.4069406986236572s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.36171460151672s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.4358654022216797s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.786527395248413s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3088815212249756s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.554115295410156s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.711641788482666s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.41744494438171387s
Security | Sign check for Bio2RDF::Homologene took 0.25298261642456055s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 9.768008470535278s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.528843879699707s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.023169517517089844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.001172780990600586s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 6.794929504394531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 2.6226043701171875e-06s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-homologene took 1010.554354429245s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 0.14189434051513672s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.3476276397705078s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.022562503814697266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0009610652923583984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 4.2438507080078125e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-inoh took 2.742363452911377s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.4599301815032959s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0005688667297363281s
Extra | Recovery of all triples for Bio2RDF::Interpro took 19.61654043197632s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.319262981414795s
Amount of data | Number of triples check for Bio2RDF::Interpro took 46.075791120529175s
Interoperability | New terms check for Bio2RDF::Interpro took 41.132962226867676s
Versatility | Languages check for Bio2RDF::Interpro took 60.260868549346924s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2689847946166992s
Security | Check HTTPS for Bio2RDF::Interpro took 0.14435935020446777s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.24157404899597168s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.32140016555786133s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.4334466457366943s
License | MR license check for Bio2RDF::Interpro took 0.43447065353393555s
License | HR license check for Bio2RDF::Interpro took 60.24195599555969s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2481377124786377s
Understandability | Number of label check for Bio2RDF::Interpro took 9.763362884521484s
Understandability | URI regex check for Bio2RDF::Interpro took 0.6162395477294922s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2585325241088867s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2809031009674072s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.25531435012817383s
Performance | Throughput check for Bio2RDF::Interpro took 11.24758529663086s
Verifiability | Contribs. check for Bio2RDF::Interpro took 2.063962697982788s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.24524593353271484s
Interlinking | skos check for Bio2RDF::Interpro took 0.4310872554779053s
Interlinking | skos check for Bio2RDF::Interpro took 0.36051297187805176s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.24580073356628418s
Currency | Creation date check for Bio2RDF::Interpro took 0.5363466739654541s
Currency | Modification date check for Bio2RDF::Interpro took 0.5171794891357422s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 110.38824701309204s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.43545103073120117s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.28825998306274414s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.25960659980773926s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.113649845123291s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8851408958435059s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6621232032775879s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.4071080684661865s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.56368446350098s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.41182279586792s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.945767879486084s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.4272325038909912s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.55035185813904s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7077183723449707s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.41596531867980957s
Security | Sign check for Bio2RDF::Interpro took 0.2616994380950928s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 11.224278926849365s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 2.426366090774536s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.021233797073364258s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0009512901306152344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.0001163482666015625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 1.9073486328125e-06s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-interpro took 1020.7621245384216s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.14221549034118652s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 1.1730952262878418s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.653236389160156e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-iproclass took 26.096179246902466s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.4875514507293701s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006287097930908203s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 19.14002561569214s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2331552505493164s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 45.84315466880798s
Interoperability | New terms check for Bio2RDF::Irefindex took 41.771337032318115s
Versatility | Languages check for Bio2RDF::Irefindex took 60.252020597457886s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.26808714866638184s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.14299798011779785s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.2569465637207031s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.29719972610473633s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.4027278423309326s
License | MR license check for Bio2RDF::Irefindex took 0.46459031105041504s
License | HR license check for Bio2RDF::Irefindex took 60.25235962867737s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.27883338928222656s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.620198726654053s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5686590671539307s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.25768423080444336s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.24876117706298828s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.25310325622558594s
Performance | Throughput check for Bio2RDF::Irefindex took 11.458353996276855s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6144769191741943s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.252669095993042s
Interlinking | skos check for Bio2RDF::Irefindex took 0.6676278114318848s
Interlinking | skos check for Bio2RDF::Irefindex took 0.35448265075683594s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2679142951965332s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5052144527435303s
Currency | Modification date check for Bio2RDF::Irefindex took 0.521634578704834s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 111.03996968269348s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.44805073738098145s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.278033971786499s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.23807048797607422s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.60556697845459s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8970024585723877s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6865341663360596s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.41072607040405273s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.17022609710693s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.444246530532837s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.3599464893341064s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3038928508758545s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.59372854232788s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7083711624145508s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.4314429759979248s
Security | Sign check for Bio2RDF::Irefindex took 0.24101781845092773s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 10.509602785110474s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.5762929916381836s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.296966552734375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 1.1920928955078125e-06s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1015.3558688163757s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 0.47899651527404785s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0007152557373046875s
Extra | Recovery of all triples for Bio2RDF::KEGG took 18.683394193649292s
Performance | Total latancy measurement for Bio2RDF::KEGG took 1.2588331699371338s
Amount of data | Number of triples check for Bio2RDF::KEGG took 45.1317412853241s
Interoperability | New terms check for Bio2RDF::KEGG took 41.51863980293274s
Versatility | Languages check for Bio2RDF::KEGG took 60.25579357147217s
Interpretability | Number of blank nodes check for Bio2RDF::KEGG took 0.2601284980773926s
Security | Check HTTPS for Bio2RDF::KEGG took 0.15399909019470215s
Interpretability | RDF structures check for Bio2RDF::KEGG took 0.24881792068481445s
Versatility | Serialization formats check for Bio2RDF::KEGG took 0.2941138744354248s
Availability | RDF dump link check for Bio2RDF::KEGG took 2.650275945663452s
License | MR license check for Bio2RDF::KEGG took 0.39040040969848633s
License | HR license check for Bio2RDF::KEGG took 60.27936577796936s
Amount of data | Number of property check for Bio2RDF::KEGG took 0.25847601890563965s
Understandability | Number of label check for Bio2RDF::KEGG took 9.80919337272644s
Understandability | URI regex check for Bio2RDF::KEGG took 0.5721683502197266s
Understandability | Vocabs check for Bio2RDF::KEGG took 0.24869251251220703s
Verifiability | Authors check for Bio2RDF::KEGG took 0.27318429946899414s
Verifiability | Publishers check for Bio2RDF::KEGG took 0.2729921340942383s
Performance | Throughput check for Bio2RDF::KEGG took 10.632409572601318s
Verifiability | Contribs. check for Bio2RDF::KEGG took 0.626776933670044s
Interlinking | sameAs chians check for Bio2RDF::KEGG took 0.28430819511413574s
Interlinking | skos check for Bio2RDF::KEGG took 0.3893766403198242s
Interlinking | skos check for Bio2RDF::KEGG took 0.34527134895324707s
Timeliness | dataset update frequency check for Bio2RDF::KEGG took 0.24799847602844238s
Currency | Creation date check for Bio2RDF::KEGG took 0.5273053646087646s
Currency | Modification date check for Bio2RDF::KEGG took 0.5128893852233887s
Rep.Conc. | URIs length for Bio2RDF::KEGG took 112.07602024078369s
Interoperability | New vocabularies check for Bio2RDF::KEGG took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::KEGG took 0.4071929454803467s
Accuracy | Check Functional Property for Bio2RDF::KEGG took 0.27100038528442383s
Accuracy | Check Inverse Functional Property for Bio2RDF::KEGG took 0.2902991771697998s
Accuracy | Check Empty annotation labels for Bio2RDF::KEGG took 7.144021511077881s
Accuracy | Check White space in annotation for Bio2RDF::KEGG took 0.8836019039154053s
Accuracy | Check Datatype consistency for Bio2RDF::KEGG took 0.6528077125549316s
Consistency | Disjoint class check for Bio2RDF::KEGG took 0.4208536148071289s
Consistency | Check Misplaced properties for Bio2RDF::KEGG took 65.38340950012207s
Consistency | Misplaced classes for Bio2RDF::KEGG took 2.3773889541625977s
Consistency | Check Ontology hijacking for Bio2RDF::KEGG took 6.391053199768066s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::KEGG took 1.2934081554412842s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::KEGG took 61.562623262405396s
Conciseness | Check Extensional conciseness for Bio2RDF::KEGG took 0.7096490859985352s
Conciseness | Check Intensional conciseness for Bio2RDF::KEGG took 0.4593181610107422s
Security | Sign check for Bio2RDF::KEGG took 0.2726156711578369s
Availability | Check URIs Dereferenciability for Bio2RDF::KEGG took 10.712529182434082s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.7185344696044922s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020750999450683594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::KEGG took 1.6689300537109375e-06s
Believability | Calculation of trust value for Bio2RDF::KEGG took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-kegg took 1004.3146572113037s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 0.14059138298034668s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.982987642288208s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.02477097511291504s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0011730194091796875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 4.1484832763671875e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-kegg-biopax took 7.39438796043396s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.9429099559783936s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.5474274158477783s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020615100860595703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 9.951147079467773s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.4701354503631592s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0007262229919433594s
Extra | Recovery of all triples for Bio2RDF::Lsr took 18.679776430130005s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.273545742034912s
Amount of data | Number of triples check for Bio2RDF::Lsr took 45.555123805999756s
Interoperability | New terms check for Bio2RDF::Lsr took 42.408823013305664s
Versatility | Languages check for Bio2RDF::Lsr took 60.251442432403564s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.26799917221069336s
Security | Check HTTPS for Bio2RDF::Lsr took 0.15719342231750488s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.3671536445617676s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3304750919342041s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.2218499183654785s
License | MR license check for Bio2RDF::Lsr took 0.37618327140808105s
License | HR license check for Bio2RDF::Lsr took 60.24346923828125s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.24480485916137695s
Understandability | Number of label check for Bio2RDF::Lsr took 9.945564985275269s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5553350448608398s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.2593660354614258s
Verifiability | Authors check for Bio2RDF::Lsr took 0.25695109367370605s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.2646913528442383s
Performance | Throughput check for Bio2RDF::Lsr took 11.696291446685791s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.5799016952514648s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.2685861587524414s
Interlinking | skos check for Bio2RDF::Lsr took 0.859882116317749s
Interlinking | skos check for Bio2RDF::Lsr took 0.3550093173980713s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.24643421173095703s
Currency | Creation date check for Bio2RDF::Lsr took 0.503333330154419s
Currency | Modification date check for Bio2RDF::Lsr took 0.48952174186706543s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 108.33253312110901s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4048187732696533s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.2631499767303467s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.27268123626708984s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 6.960310220718384s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8896167278289795s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6662812232971191s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.30655694007873535s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.03248906135559s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.3914337158203125s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.3883280754089355s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3594884872436523s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.602285385131836s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7140796184539795s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.46907472610473633s
Security | Sign check for Bio2RDF::Lsr took 0.25859713554382324s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 10.269421815872192s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 106.36579775810242s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02192234992980957s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0018169879913330078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 9.012222290039062e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 3.814697265625e-06s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-lsr took 1142.6638407707214s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.48419737815856934s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0003333091735839844s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.257800817489624s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2454190254211426s
Amount of data | Number of triples check for Bio2RDF::Mesh took 45.25041079521179s
Interoperability | New terms check for Bio2RDF::Mesh took 40.06181812286377s
Versatility | Languages check for Bio2RDF::Mesh took 60.25748252868652s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.30429720878601074s
Security | Check HTTPS for Bio2RDF::Mesh took 0.15568256378173828s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.37631988525390625s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.3344149589538574s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.248183488845825s
License | MR license check for Bio2RDF::Mesh took 0.4846656322479248s
License | HR license check for Bio2RDF::Mesh took 60.276214599609375s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.26663684844970703s
Understandability | Number of label check for Bio2RDF::Mesh took 10.196461200714111s
Understandability | URI regex check for Bio2RDF::Mesh took 0.6060340404510498s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.25537729263305664s
Verifiability | Authors check for Bio2RDF::Mesh took 0.25799560546875s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2564253807067871s
Performance | Throughput check for Bio2RDF::Mesh took 11.159555435180664s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.5897216796875s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.2756195068359375s
Interlinking | skos check for Bio2RDF::Mesh took 0.7572891712188721s
Interlinking | skos check for Bio2RDF::Mesh took 0.38616514205932617s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.2671089172363281s
Currency | Creation date check for Bio2RDF::Mesh took 0.4985849857330322s
Currency | Modification date check for Bio2RDF::Mesh took 0.5089895725250244s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 109.66897058486938s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.5000331401824951s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2887594699859619s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2759089469909668s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 6.762912034988403s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8840415477752686s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6550967693328857s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.26711344718933105s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.0823118686676s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.3691697120666504s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.2176513671875s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.288456916809082s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.55250597000122s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7252371311187744s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.43445754051208496s
Security | Sign check for Bio2RDF::Mesh took 0.26021838188171387s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 11.909837007522583s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.6187350749969482s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020667314529418945s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.62939453125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 1.1920928955078125e-06s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-mesh took 1016.8749077320099s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.46700382232666016s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006439685821533203s
Extra | Recovery of all triples for Bio2RDF::Mgi took 19.729120016098022s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2312450408935547s
Amount of data | Number of triples check for Bio2RDF::Mgi took 45.756417989730835s
Interoperability | New terms check for Bio2RDF::Mgi took 42.16673707962036s
Versatility | Languages check for Bio2RDF::Mgi took 60.27696943283081s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.2946596145629883s
Security | Check HTTPS for Bio2RDF::Mgi took 0.15761995315551758s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.3471810817718506s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.3162729740142822s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.3389081954956055s
License | MR license check for Bio2RDF::Mgi took 0.4006228446960449s
License | HR license check for Bio2RDF::Mgi took 60.24420094490051s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.24495339393615723s
Understandability | Number of label check for Bio2RDF::Mgi took 9.759808540344238s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5579361915588379s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.24748516082763672s
Verifiability | Authors check for Bio2RDF::Mgi took 0.24005460739135742s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2686336040496826s
Performance | Throughput check for Bio2RDF::Mgi took 11.761887073516846s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.7171025276184082s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.25386953353881836s
Interlinking | skos check for Bio2RDF::Mgi took 0.4593544006347656s
Interlinking | skos check for Bio2RDF::Mgi took 0.3450813293457031s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2754838466644287s
Currency | Creation date check for Bio2RDF::Mgi took 0.5078837871551514s
Currency | Modification date check for Bio2RDF::Mgi took 0.531141996383667s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 109.62724256515503s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.44887781143188477s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.24422168731689453s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.25171685218811035s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 6.539335250854492s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8796682357788086s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6679725646972656s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.41809940338134766s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.22900772094727s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4294614791870117s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.509328842163086s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3598136901855469s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.52993845939636s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7223055362701416s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.42860889434814453s
Security | Sign check for Bio2RDF::Mgi took 0.27180981636047363s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 9.924449682235718s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.7794222831726074s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020819425582885742s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 0.0001049041748046875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 1.6689300537109375e-06s
Believability | Calculation of trust value for Bio2RDF::Mgi took 2.7894973754882812e-05s
INFO | --- Analysis for bio2rdf-mgi took 1020.2213110923767s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.4679982662200928s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0005927085876464844s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 18.942003965377808s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2226097583770752s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 45.98334622383118s
Interoperability | New terms check for Bio2RDF::Ncbigene took 40.65491318702698s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.255532026290894s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.31681299209594727s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.14843368530273438s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.2654898166656494s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.32814645767211914s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.3627262115478516s
License | MR license check for Bio2RDF::Ncbigene took 0.3471095561981201s
License | HR license check for Bio2RDF::Ncbigene took 60.25668716430664s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.25171518325805664s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.41203498840332s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5967409610748291s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.24481725692749023s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.24888086318969727s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.23511743545532227s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.452224016189575s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.583277702331543s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.26636767387390137s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.4264822006225586s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3356442451477051s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.24493098258972168s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5024776458740234s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5044121742248535s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 110.59386897087097s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4543437957763672s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2742040157318115s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.2377912998199463s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 6.579663515090942s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.884091854095459s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6627600193023682s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.29689979553222656s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.56764078140259s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.407792091369629s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.230517387390137s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3208575248718262s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.52237868309021s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.728374719619751s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.4557826519012451s
Security | Sign check for Bio2RDF::Ncbigene took 0.2664506435394287s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 14.931357860565186s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.9630811214447021s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.0210573673248291s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012612342834472656s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 1.9073486328125e-06s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1028.1978709697723s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.4871082305908203s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006151199340820312s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.70057201385498s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.253711462020874s
Amount of data | Number of triples check for Bio2RDF::Ndc took 45.326324224472046s
Interoperability | New terms check for Bio2RDF::Ndc took 41.849164962768555s
Versatility | Languages check for Bio2RDF::Ndc took 60.24213981628418s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.3050827980041504s
Security | Check HTTPS for Bio2RDF::Ndc took 0.15582847595214844s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.2501552104949951s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.3034694194793701s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.1754353046417236s
License | MR license check for Bio2RDF::Ndc took 0.4563312530517578s
License | HR license check for Bio2RDF::Ndc took 60.24328327178955s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2732839584350586s
Understandability | Number of label check for Bio2RDF::Ndc took 9.657044649124146s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5691757202148438s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2616086006164551s
Verifiability | Authors check for Bio2RDF::Ndc took 0.27358436584472656s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.27567076683044434s
Performance | Throughput check for Bio2RDF::Ndc took 11.888456344604492s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.5841140747070312s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.26807451248168945s
Interlinking | skos check for Bio2RDF::Ndc took 0.8680322170257568s
Interlinking | skos check for Bio2RDF::Ndc took 0.37587809562683105s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.24674129486083984s
Currency | Creation date check for Bio2RDF::Ndc took 0.5139718055725098s
Currency | Modification date check for Bio2RDF::Ndc took 0.4980041980743408s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 109.81329250335693s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.4137232303619385s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.272036075592041s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2690424919128418s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 6.60218620300293s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8863875865936279s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6751217842102051s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.24419903755187988s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.78629398345947s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.4378650188446045s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.324013948440552s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.278247356414795s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.54502987861633s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7283380031585693s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.4726097583770752s
Security | Sign check for Bio2RDF::Ndc took 0.2574775218963623s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 12.879342794418335s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.8528804779052734s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.021445035934448242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0009140968322753906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 6.389617919921875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 1.9073486328125e-06s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-ndc took 1012.8458530902863s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 0.13970041275024414s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.0004131793975830078s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.5871164798736572s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.02116560935974121s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.528594970703125e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-netpath took 129.11001873016357s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.1815352439880371s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.2993183135986328s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-nextprot took 2.798037052154541s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.5206754207611084s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006062984466552734s
Extra | Recovery of all triples for Bio2RDF::Omim took 18.723900318145752s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2591772079467773s
Amount of data | Number of triples check for Bio2RDF::Omim took 45.25882840156555s
Interoperability | New terms check for Bio2RDF::Omim took 39.95773649215698s
Versatility | Languages check for Bio2RDF::Omim took 60.25108051300049s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2801835536956787s
Security | Check HTTPS for Bio2RDF::Omim took 0.1565556526184082s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.2505054473876953s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.31725311279296875s
Availability | RDF dump link check for Bio2RDF::Omim took 2.375366687774658s
License | MR license check for Bio2RDF::Omim took 0.36901426315307617s
License | HR license check for Bio2RDF::Omim took 60.254220962524414s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2636141777038574s
Understandability | Number of label check for Bio2RDF::Omim took 9.865758657455444s
Understandability | URI regex check for Bio2RDF::Omim took 0.5857241153717041s
Understandability | Vocabs check for Bio2RDF::Omim took 0.24817562103271484s
Verifiability | Authors check for Bio2RDF::Omim took 0.25189900398254395s
Verifiability | Publishers check for Bio2RDF::Omim took 0.2436058521270752s
Performance | Throughput check for Bio2RDF::Omim took 10.833913803100586s
Verifiability | Contribs. check for Bio2RDF::Omim took 1.4085748195648193s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.2488563060760498s
Interlinking | skos check for Bio2RDF::Omim took 0.5388333797454834s
Interlinking | skos check for Bio2RDF::Omim took 0.35741209983825684s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.2717111110687256s
Currency | Creation date check for Bio2RDF::Omim took 0.5205750465393066s
Currency | Modification date check for Bio2RDF::Omim took 0.5023198127746582s
Rep.Conc. | URIs length for Bio2RDF::Omim took 111.40561008453369s
Interoperability | New vocabularies check for Bio2RDF::Omim took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4454030990600586s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.24874520301818848s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2648916244506836s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.357170343399048s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8835647106170654s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6790018081665039s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.28433895111083984s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 64.98793816566467s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.407538890838623s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.330796480178833s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.308948278427124s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.60973048210144s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7522268295288086s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.4300708770751953s
Security | Sign check for Bio2RDF::Omim took 0.24971485137939453s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 14.522329568862915s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.4031543731689453s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.0001354217529296875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 1.430511474609375e-06s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-omim took 1016.8717997074127s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 9.441375732421875e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.32125234603881836s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.022707223892211914s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.790855407714844e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 3.7297158241271973s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.4753899574279785s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0003151893615722656s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.89486527442932s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2909698486328125s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 45.686943769454956s
Interoperability | New terms check for Bio2RDF::Orphanet took 39.578720808029175s
Versatility | Languages check for Bio2RDF::Orphanet took 60.270219802856445s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.26257991790771484s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.1541764736175537s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.49439072608947754s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.32135558128356934s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.3558292388916016s
License | MR license check for Bio2RDF::Orphanet took 0.45168542861938477s
License | HR license check for Bio2RDF::Orphanet took 60.27267098426819s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.24879956245422363s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.603210210800171s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5797677040100098s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.24332094192504883s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.24375176429748535s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2363879680633545s
Performance | Throughput check for Bio2RDF::Orphanet took 11.107387065887451s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.60369873046875s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.2749135494232178s
Interlinking | skos check for Bio2RDF::Orphanet took 0.7746579647064209s
Interlinking | skos check for Bio2RDF::Orphanet took 0.3555636405944824s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.27588558197021484s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5277655124664307s
Currency | Modification date check for Bio2RDF::Orphanet took 0.47603893280029297s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 109.28346228599548s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.41051816940307617s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2871127128601074s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2747046947479248s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.263302326202393s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8846313953399658s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6714954376220703s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.5481066703796387s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.17977023124695s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.3845016956329346s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.630404710769653s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3343708515167236s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.608275413513184s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7738790512084961s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.4337465763092041s
Security | Sign check for Bio2RDF::Orphanet took 0.2512977123260498s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 28.461666584014893s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.815446138381958s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02234792709350586s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 5.888938903808594e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.001089334487915039s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 0.00012159347534179688s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 3.5762786865234375e-06s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1034.8666336536407s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.1418294906616211s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.4158751964569092s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020381689071655273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.249783754348755s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.4742124080657959s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0006699562072753906s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 19.135379552841187s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2322406768798828s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 44.72908902168274s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 39.90237736701965s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.24793481826782s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2516448497772217s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.16801810264587402s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.2531273365020752s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.30915379524230957s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.2611443996429443s
License | MR license check for Bio2RDF::Pharmgkb took 0.3919801712036133s
License | HR license check for Bio2RDF::Pharmgkb took 60.251404762268066s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.26001739501953125s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.289237976074219s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5581183433532715s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.2458655834197998s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.24415016174316406s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.23693156242370605s
Performance | Throughput check for Bio2RDF::Pharmgkb took 10.884778261184692s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.6219048500061035s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.26427745819091797s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.35295581817626953s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.3925044536590576s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2680675983428955s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5285160541534424s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5133943557739258s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 108.00483012199402s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4401514530181885s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2727782726287842s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.2678496837615967s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.777334213256836s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8774638175964355s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6606481075286865s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.3292572498321533s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.04512596130371s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.402081251144409s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.328169584274292s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3236594200134277s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.58876299858093s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7394773960113525s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.399660587310791s
Security | Sign check for Bio2RDF::Pharmgkb took 0.2487168312072754s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 13.216663122177124s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 5.139926433563232s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 1.1920928955078125e-06s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1026.0077860355377s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 0.13778376579284668s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.32443928718566895s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.025220155715942383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0010383129119873047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 4.172325134277344e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 5.088506698608398s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 0.9353783130645752s
Availability | VoID file availability check for Bio2RDF::PID took 0.00039315223693847656s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.9896085262298584s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.021258115768432617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-pid took 6.936473369598389s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 0.1385364532470703s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.46180105209350586s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020941734313964844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.8131375312805176s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.4994676113128662s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0006737709045410156s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 20.379255533218384s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2333998680114746s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 45.08271837234497s
Interoperability | New terms check for Bio2RDF::Pubmed took 40.43813109397888s
Versatility | Languages check for Bio2RDF::Pubmed took 60.253700733184814s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2841165065765381s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.14537811279296875s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.40418338775634766s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.31912755966186523s
Availability | RDF dump link check for Bio2RDF::Pubmed took 2.2923288345336914s
License | MR license check for Bio2RDF::Pubmed took 0.4661080837249756s
License | HR license check for Bio2RDF::Pubmed took 60.26903581619263s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2665865421295166s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.708912134170532s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6013209819793701s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.26134347915649414s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2636103630065918s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.25969958305358887s
Performance | Throughput check for Bio2RDF::Pubmed took 11.763816118240356s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.5926001071929932s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.2503783702850342s
Interlinking | skos check for Bio2RDF::Pubmed took 0.5821566581726074s
Interlinking | skos check for Bio2RDF::Pubmed took 0.3587155342102051s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.24941039085388184s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5079967975616455s
Currency | Modification date check for Bio2RDF::Pubmed took 0.48708486557006836s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 108.5104558467865s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.43203020095825195s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.24978208541870117s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.23090839385986328s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 6.520195484161377s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8863539695739746s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6663482189178467s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.3106052875518799s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.59740138053894s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.3758621215820312s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.22260856628418s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.370347499847412s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.60014343261719s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.712944746017456s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.46057629585266113s
Security | Sign check for Bio2RDF::Pubmed took 0.25633883476257324s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 12.609503030776978s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.5916969776153564s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.022517919540405273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0009710788726806641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00016188621520996094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 2.6226043701171875e-06s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1010.0197594165802s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 0.14570212364196777s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.35077595710754395s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.02155900001525879s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 8.273124694824219e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-reactome took 10.032840251922607s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 0.14862895011901855s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.3198204040527344s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.021677255630493164s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0008573532104492188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 6.413459777832031e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-rhea took 3.1159558296203613s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.1440110206604004s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 4.2012999057769775s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.486343383789062e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-sabiork took 14.65275764465332s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.4661221504211426s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0006260871887207031s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.738865852355957s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2140429019927979s
Amount of data | Number of triples check for Bio2RDF::Sgd took 45.730406284332275s
Interoperability | New terms check for Bio2RDF::Sgd took 42.79808592796326s
Versatility | Languages check for Bio2RDF::Sgd took 60.240721702575684s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.27401089668273926s
Security | Check HTTPS for Bio2RDF::Sgd took 0.16605567932128906s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.3670346736907959s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.33696746826171875s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.1749958992004395s
License | MR license check for Bio2RDF::Sgd took 0.3585653305053711s
License | HR license check for Bio2RDF::Sgd took 60.266780376434326s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.24683499336242676s
Understandability | Number of label check for Bio2RDF::Sgd took 10.269542694091797s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5893864631652832s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2515277862548828s
Verifiability | Authors check for Bio2RDF::Sgd took 0.2513120174407959s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.2665104866027832s
Performance | Throughput check for Bio2RDF::Sgd took 11.308324813842773s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.596811056137085s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.2547953128814697s
Interlinking | skos check for Bio2RDF::Sgd took 0.47809362411499023s
Interlinking | skos check for Bio2RDF::Sgd took 0.3382833003997803s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.24916458129882812s
Currency | Creation date check for Bio2RDF::Sgd took 0.5513722896575928s
Currency | Modification date check for Bio2RDF::Sgd took 0.4832766056060791s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 110.28298449516296s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.42023181915283203s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2731966972351074s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.24245429039001465s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.897424936294556s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8880107402801514s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6725049018859863s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.4526798725128174s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.05893921852112s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.378352642059326s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.4661924839019775s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3095941543579102s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.58302021026611s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7058281898498535s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.4261910915374756s
Security | Sign check for Bio2RDF::Sgd took 0.25209903717041016s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 14.250895023345947s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.6424639225006104s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010418891906738281s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 1.1920928955078125e-06s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-sgd took 1019.7688047885895s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 8.96453857421875e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.00034236907958984375s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.3210761547088623s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 4.0531158447265625e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 3.018726110458374s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.48118114471435547s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006346702575683594s
Extra | Recovery of all triples for Bio2RDF::Sider took 19.87999701499939s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.3127129077911377s
Amount of data | Number of triples check for Bio2RDF::Sider took 46.230621099472046s
Interoperability | New terms check for Bio2RDF::Sider took 40.53554081916809s
Versatility | Languages check for Bio2RDF::Sider took 60.24462962150574s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.272752046585083s
Security | Check HTTPS for Bio2RDF::Sider took 0.16637468338012695s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.3615899085998535s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.33206653594970703s
Availability | RDF dump link check for Bio2RDF::Sider took 2.2130074501037598s
License | MR license check for Bio2RDF::Sider took 0.35938143730163574s
License | HR license check for Bio2RDF::Sider took 60.248608350753784s
Amount of data | Number of property check for Bio2RDF::Sider took 0.24518918991088867s
Understandability | Number of label check for Bio2RDF::Sider took 9.388614416122437s
Understandability | URI regex check for Bio2RDF::Sider took 0.5743207931518555s
Understandability | Vocabs check for Bio2RDF::Sider took 0.24727821350097656s
Verifiability | Authors check for Bio2RDF::Sider took 0.256664514541626s
Verifiability | Publishers check for Bio2RDF::Sider took 0.26604652404785156s
Performance | Throughput check for Bio2RDF::Sider took 10.711140632629395s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.6401503086090088s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.25534987449645996s
Interlinking | skos check for Bio2RDF::Sider took 0.78220534324646s
Interlinking | skos check for Bio2RDF::Sider took 0.34465837478637695s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.25107336044311523s
Currency | Creation date check for Bio2RDF::Sider took 0.5428164005279541s
Currency | Modification date check for Bio2RDF::Sider took 0.5243964195251465s
Rep.Conc. | URIs length for Bio2RDF::Sider took 110.57171678543091s
Interoperability | New vocabularies check for Bio2RDF::Sider took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.40883731842041016s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.26381587982177734s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.25237369537353516s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 6.469455242156982s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.899808406829834s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.7053978443145752s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.28824472427368164s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.39315390586853s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.5004260540008545s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.676955223083496s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3160486221313477s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.60161209106445s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7130603790283203s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.4353046417236328s
Security | Sign check for Bio2RDF::Sider took 0.2595820426940918s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 12.459763526916504s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 1.3250670433044434s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020254135131835938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 1.1920928955078125e-06s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-sider took 1022.0348134040833s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 0.1354513168334961s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.45414280891418457s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.02404618263244629s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 4.935264587402344e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0011320114135742188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 6.318092346191406e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-spike took 14.443227291107178s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 8.630752563476562e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.6329352855682373s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.021103620529174805s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.267692565917969e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-taxon took 3.4221620559692383s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.4803657531738281s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006213188171386719s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 18.7798855304718s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2333686351776123s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 45.651607513427734s
Interoperability | New terms check for Bio2RDF::Taxonomy took 42.19104814529419s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.26457166671753s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2541794776916504s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.15249395370483398s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.27226734161376953s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.32935500144958496s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.556509017944336s
License | MR license check for Bio2RDF::Taxonomy took 0.5597696304321289s
License | HR license check for Bio2RDF::Taxonomy took 60.25615334510803s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.24556970596313477s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.7937593460083s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5775156021118164s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2528998851776123s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.2388286590576172s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.25664615631103516s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.279495000839233s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.6118559837341309s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.2640690803527832s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.6760094165802002s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.3563835620880127s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.26607632637023926s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5170142650604248s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.510096549987793s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 108.19921064376831s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4257385730743408s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.27099013328552246s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.24253392219543457s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.3953163623809814s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8891212940216064s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6709184646606445s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.422504186630249s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.36061477661133s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.3944203853607178s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.374193906784058s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3363323211669922s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.59193444252014s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7150499820709229s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.44024085998535156s
Security | Sign check for Bio2RDF::Taxonomy took 0.24801898002624512s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 13.352101802825928s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 1.0795509815216064s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010776519775390625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 1.6689300537109375e-06s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1027.1979892253876s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.1443626880645752s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.8551275730133057s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.02033400535583496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 20.087969541549683s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.4621090888977051s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006756782531738281s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 18.909902811050415s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2870464324951172s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.89956188201904s
Interoperability | New terms check for Bio2RDF::Wormbase took 41.819947957992554s
Versatility | Languages check for Bio2RDF::Wormbase took 60.24481701850891s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.2565906047821045s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15294289588928223s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.417194128036499s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.2971789836883545s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.4196600914001465s
License | MR license check for Bio2RDF::Wormbase took 0.4925856590270996s
License | HR license check for Bio2RDF::Wormbase took 60.25569772720337s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.2567126750946045s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.417101860046387s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5876610279083252s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2573556900024414s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.25623631477355957s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.26970362663269043s
Performance | Throughput check for Bio2RDF::Wormbase took 10.89607858657837s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.8623902797698975s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.24487805366516113s
Interlinking | skos check for Bio2RDF::Wormbase took 0.5279700756072998s
Interlinking | skos check for Bio2RDF::Wormbase took 0.3621084690093994s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.23449325561523438s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5079073905944824s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5285143852233887s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 109.22439932823181s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.4459419250488281s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2829580307006836s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2767367362976074s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.494896650314331s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8844375610351562s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6657717227935791s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.31598353385925293s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.63339138031006s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.37715482711792s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.669130086898804s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.334388017654419s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.559539794921875s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7199342250823975s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.450761079788208s
Security | Sign check for Bio2RDF::Wormbase took 0.2592349052429199s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 12.716416358947754s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 2.743079900741577s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020883798599243164s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.845329284667969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 1.1920928955078125e-06s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1024.6006944179535s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.5995042324066162s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 1.4022252559661865s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.225440979003906e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 8.58306884765625e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 6.26955509185791s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0339045524597168s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.3934860229492188s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.0994415283203125e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for biolit took 5.237469911575317s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 9.274482727050781e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.32605624198913574s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.553794860839844e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 6.198883056640625e-06s
INFO | --- Analysis for biolod-pdb took 8.472410917282104s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.5407075881958008s
Availability | VoID file availability check for BioModels RDF took 0.0864109992980957s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2892618179321289s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020927906036376953s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.2438507080078125e-05s
Believability | Calculation of trust value for BioModels RDF took 1.3828277587890625e-05s
INFO | --- Analysis for biomodels-rdf took 5.85297966003418s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.5704641342163086s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0003764629364013672s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.5169057846069336s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0212404727935791s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.3855438232421875e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1920928955078125e-05s
INFO | --- Analysis for Biop took 7.330097198486328s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.7738037109375e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.6906511783599854s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021163463592529297s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.695487976074219e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.430511474609375e-05s
INFO | --- Analysis for Bioportal took 10.054274320602417s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 8.845329284667969e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.33382248878479004s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.02100849151611328s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006437301635742188s
Believability | Calculation of trust value for Amphibian gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-aao took 13.675205707550049s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 8.893013000488281e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 1.194901466369629s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020830631256103516s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0003330707550048828s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-aba took 14.891359567642212s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.000408172607421875s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.41827392578125s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020443201065063477s
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.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0014922618865966797s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-acgt took 16.562945127487183s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 8.678436279296875e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.3133561611175537s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020789146423339844s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003571510314941406s
Believability | Calculation of trust value for Animal natural history and life history took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-adw took 6.972037076950073s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 9.322166442871094e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 2.744826316833496s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.021065235137939453s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0009233951568603516s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00048732757568359375s
Believability | Calculation of trust value for Anatomical Entity Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-aeo took 35.551175355911255s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 10.180118560791016s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009744167327880859s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-aero took 38.85295343399048s
Availability | SPARQL endpoint availability check for AI/RHEUM took 0.0002422332763671875s
Availability | VoID file availability check for AI/RHEUM took 0.0007634162902832031s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 3.2540979385375977s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.021793127059936523s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004086494445800781s
Believability | Calculation of trust value for AI/RHEUM took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-air took 32.96819710731506s
Availability | SPARQL endpoint availability check for Amino Acid took 4.410743713378906e-05s
Availability | VoID file availability check for Amino Acid took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.32083797454833984s
Reputation | Calculation of the PageRank for Amino Acid took 0.02118206024169922s
Interlinking | Calculation of Degree of Connection for Amino Acid took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00026869773864746094s
Believability | Calculation of trust value for Amino Acid took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-amino-acid took 43.03105592727661s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.45481228828430176s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.021210432052612305s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0003142356872558594s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-apo took 60.781553983688354s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 8.988380432128906e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0008056163787841797s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 8.855424165725708s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020885467529296875s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00024819374084472656s
Believability | Calculation of trust value for African Traditional Medicine took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-atmo took 65.16584587097168s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 8.916854858398438e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0008218288421630859s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.3209531307220459s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.021544456481933594s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 0.00010585784912109375s
Believability | Calculation of trust value for Amphibian taxonomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ato took 87.54234147071838s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 51.8748881816864s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013840198516845703s
Believability | Calculation of trust value for BioAssay Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bao took 187.4916603565216s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.76837158203125e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 4.323628187179565s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.022580385208129883s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00041294097900390625s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 1.5497207641601562e-05s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 149.24435687065125s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 9.5367431640625e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.8417603969573975s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.021284103393554688s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.00033783912658691406s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bcgo took 22.866810083389282s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 9.942054748535156e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 59.9755961894989s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.0224761962890625s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014083385467529297s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bdo took 423.0895709991455s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0008139610290527344s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.31601929664611816s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.022091388702392578s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0012280941009521484s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0006630420684814453s
Believability | Calculation of trust value for Basic Formal Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bfo took 56.94628691673279s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 9.131431579589844e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.29091882705688477s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.022327423095703125s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007450580596923828s
Believability | Calculation of trust value for Bleeding History Phenotype took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bho took 7.5045485496521s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 8.96453857421875e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.3201158046722412s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004622936248779297s
Believability | Calculation of trust value for Bilateria anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bila took 7.662103652954102s
Availability | SPARQL endpoint availability check for BIRNLex took 0.00010657310485839844s
Availability | VoID file availability check for BIRNLex took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.46857619285583496s
Reputation | Calculation of the PageRank for BIRNLex took 0.020647525787353516s
Interlinking | Calculation of Degree of Connection for BIRNLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.001474142074584961s
Believability | Calculation of trust value for BIRNLex took 2.6226043701171875e-05s
INFO | --- Analysis for bioportal-birnlex took 7.5904364585876465s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 1.0237793922424316s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020819664001464844s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007805824279785156s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bootstrep took 9.650288581848145s
Availability | SPARQL endpoint availability check for BioPAX took 9.250640869140625e-05s
Availability | VoID file availability check for BioPAX took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2997581958770752s
Reputation | Calculation of the PageRank for BioPAX took 0.022980928421020508s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0009481906890869141s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00011038780212402344s
Believability | Calculation of trust value for BioPAX took 1.7881393432617188e-05s
INFO | --- Analysis for bioportal-bp took 6.133419036865234s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.31415772438049316s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020518779754638672s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003294944763183594s
Believability | Calculation of trust value for Biomedical Resource Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bro_x1 took 6.545463562011719s
Availability | SPARQL endpoint availability check for Spatial Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.734534740447998s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.0212860107421875s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00021648406982421875s
Believability | Calculation of trust value for Spatial Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bspo took 6.827376127243042s
Availability | SPARQL endpoint availability check for BioTop took 9.012222290039062e-05s
Availability | VoID file availability check for BioTop took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for BioTop took 0.3503232002258301s
Reputation | Calculation of the PageRank for BioTop took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for BioTop took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioTop took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006766319274902344s
Believability | Calculation of trust value for BioTop took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-bt took 7.304102182388306s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 8.845329284667969e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.34992265701293945s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.021914243698120117s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0009877681732177734s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-bto took 6.969643592834473s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.399212121963501s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018246173858642578s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.340576171875e-05s
INFO | --- Analysis for bioportal-canco took 8.147360563278198s
Availability | SPARQL endpoint availability check for CAO took 9.012222290039062e-05s
Availability | VoID file availability check for CAO took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for CAO took 0.42487120628356934s
Reputation | Calculation of the PageRank for CAO took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for CAO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CAO took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006220340728759766s
Believability | Calculation of trust value for CAO took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cao took 9.604564666748047s
Availability | SPARQL endpoint availability check for CareLex took 8.988380432128906e-05s
Availability | VoID file availability check for CareLex took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for CareLex took 0.31773972511291504s
Reputation | Calculation of the PageRank for CareLex took 0.02100515365600586s
Interlinking | Calculation of Degree of Connection for CareLex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.364418029785156e-05s
Believability | Calculation of trust value for CareLex took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-carelex took 7.4239583015441895s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 0.0001266002655029297s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.34176135063171387s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02129220962524414s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007700920104980469s
Believability | Calculation of trust value for Cell Cycle Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cco took 7.238257884979248s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.3211054801940918s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.02057194709777832s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00026297569274902344s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cdao took 8.16340947151184s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 9.632110595703125e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0013034343719482422s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.31406164169311523s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02051067352294922s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007803440093994141s
Believability | Calculation of trust value for Chemical entities of biological interest took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-chebi took 6.472622632980347s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 0.00012564659118652344s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.6971161365509033s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00027108192443847656s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 8.842612028121948s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.29439496994018555s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.021937131881713867s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007452964782714844s
Believability | Calculation of trust value for Chemical Information Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cheminf took 6.59584641456604s
Availability | SPARQL endpoint availability check for Cell type took 0.00010800361633300781s
Availability | VoID file availability check for Cell type took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Cell type took 0.3266479969024658s
Reputation | Calculation of the PageRank for Cell type took 0.020941734313964844s
Interlinking | Calculation of Degree of Connection for Cell type took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00040459632873535156s
Believability | Calculation of trust value for Cell type took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cl took 7.529329299926758s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.42977428436279297s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0007944107055664062s
Believability | Calculation of trust value for Cell Line Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-clo took 7.379778623580933s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.3282506465911865s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02261042594909668s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001742839813232422s
Believability | Calculation of trust value for Clinical Measurement Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cmo took 6.878895282745361s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.42336106300354004s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.02109694480895996s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0008711814880371094s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002605915069580078s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cno took 7.380492210388184s
Availability | SPARQL endpoint availability check for Wheat trait took 4.363059997558594e-05s
Availability | VoID file availability check for Wheat trait took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for Wheat trait took 2.1189589500427246s
Reputation | Calculation of the PageRank for Wheat trait took 0.03560280799865723s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0014030933380126953s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 0.00010848045349121094s
Believability | Calculation of trust value for Wheat trait took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-co_wheat took 9.48389983177185s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.482269287109375e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.3133723735809326s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02149677276611328s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003445148468017578s
Believability | Calculation of trust value for Cognitive Atlas took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cogat took 7.3038649559021s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 2.8694183826446533s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007712841033935547s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cogpo took 10.056581735610962s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 9.012222290039062e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.32808589935302734s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.02112269401550293s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0011873245239257812s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0005171298980712891s
Believability | Calculation of trust value for Current Procedural Terminology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cpt took 7.805360555648804s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 9.083747863769531e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.5440630912780762s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017697811126708984s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-csp took 7.688772678375244s
Availability | SPARQL endpoint availability check for COSTART took 0.00011706352233886719s
Availability | VoID file availability check for COSTART took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for COSTART took 0.3182559013366699s
Reputation | Calculation of the PageRank for COSTART took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0008585453033447266s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0010771751403808594s
Believability | Calculation of trust value for COSTART took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cst took 6.660810232162476s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 8.845329284667969e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.317302942276001s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020295143127441406s
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.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005037784576416016s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ctcae took 8.336228609085083s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 0.00013065338134765625s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.500499963760376s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004394054412841797s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ctx took 7.593106508255005s
Availability | SPARQL endpoint availability check for Dendritic cell took 9.036064147949219e-05s
Availability | VoID file availability check for Dendritic cell took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.40443992614746094s
Reputation | Calculation of the PageRank for Dendritic cell took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.000354766845703125s
Believability | Calculation of trust value for Dendritic cell took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-dc_cl took 8.043479681015015s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 8.96453857421875e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.000743865966796875s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.31905698776245117s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.021434307098388672s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.001010894775390625s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 0.00011920928955078125s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ddanat took 7.096583604812622s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.076957702636719e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.31165552139282227s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02147984504699707s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009586811065673828s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ddi took 8.038162469863892s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.32656311988830566s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.7738037109375e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-diagnosticont took 7.520931720733643s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.33677196502685547s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00016617774963378906s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 6.862421751022339s
Availability | SPARQL endpoint availability check for Human disease ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Human disease ontology took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.32236242294311523s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006265640258789062s
Believability | Calculation of trust value for Human disease ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-doid took 6.623262882232666s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0006964206695556641s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.30545544624328613s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007760524749755859s
Believability | Calculation of trust value for Electrocardiography Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ecg took 6.079420804977417s
Availability | SPARQL endpoint availability check for Evidence codes took 8.511543273925781e-05s
Availability | VoID file availability check for Evidence codes took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.3070344924926758s
Reputation | Calculation of the PageRank for Evidence codes took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for Evidence codes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 2.8371810913085938e-05s
Believability | Calculation of trust value for Evidence codes took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-eco took 9.40463900566101s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.38440489768981934s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017254352569580078s
Believability | Calculation of trust value for Experimental Factor Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-efo took 6.836834669113159s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 9.036064147949219e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.3180990219116211s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020830869674682617s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0011076927185058594s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0012819766998291016s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ehda took 7.757430076599121s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 0.0001068115234375s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.35837316513061523s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020679473876953125s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007283687591552734s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ehdaa took 7.979385137557983s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 0.00013184547424316406s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.4432036876678467s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.00052642822265625s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 7.129206895828247s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 9.1552734375e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.32901716232299805s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.022111892700195312s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.86102294921875e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-emap took 6.723794221878052s
Availability | SPARQL endpoint availability check for Environment Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Environment Ontology took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.31185269355773926s
Reputation | Calculation of the PageRank for Environment Ontology took 0.02114558219909668s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00039196014404296875s
Believability | Calculation of trust value for Environment Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-envo took 9.825767755508423s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 8.606910705566406e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.3127579689025879s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02093338966369629s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.000308990478515625s
Believability | Calculation of trust value for Plant environmental conditions took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-eo took 6.821178197860718s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.3162498474121094s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.001394510269165039s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 2.384185791015625e-05s
INFO | --- Analysis for bioportal-ep took 6.861421823501587s
Availability | SPARQL endpoint availability check for Epilepsy took 8.678436279296875e-05s
Availability | VoID file availability check for Epilepsy took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.30132532119750977s
Reputation | Calculation of the PageRank for Epilepsy took 0.02101898193359375s
Interlinking | Calculation of Degree of Connection for Epilepsy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00013566017150878906s
Believability | Calculation of trust value for Epilepsy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-epileponto took 6.937021732330322s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 0.00010967254638671875s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.3340437412261963s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.001142740249633789s
Believability | Calculation of trust value for eagle-i research resource ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ero took 6.123011589050293s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.363059997558594e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.34043073654174805s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0010755062103271484s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ev took 7.25459361076355s
Availability | SPARQL endpoint availability check for ExO took 8.869171142578125e-05s
Availability | VoID file availability check for ExO took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for ExO took 0.3161776065826416s
Reputation | Calculation of the PageRank for ExO took 0.02357339859008789s
Interlinking | Calculation of Degree of Connection for ExO took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for ExO took 0.0013091564178466797s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0003731250762939453s
Believability | Calculation of trust value for ExO took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-exo took 7.034136772155762s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 8.821487426757812e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.4490818977355957s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020987272262573242s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011181831359863281s
Believability | Calculation of trust value for Fungal gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fao took 7.506771087646484s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.482269287109375e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.321591854095459s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.021258115768432617s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0008280277252197266s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00025963783264160156s
Believability | Calculation of trust value for Biological imaging methods took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fbbi took 8.053486824035645s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 0.0001285076141357422s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0012080669403076172s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 1.553107738494873s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020964384078979492s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006570816040039062s
Believability | Calculation of trust value for Drosophila gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fbbt took 8.539009809494019s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 8.845329284667969e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.4273722171783447s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.00041675567626953125s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fbcv took 6.852478742599487s
Availability | SPARQL endpoint availability check for Drosophila development took 8.606910705566406e-05s
Availability | VoID file availability check for Drosophila development took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.3144378662109375s
Reputation | Calculation of the PageRank for Drosophila development took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for Drosophila development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.57763671875e-05s
Believability | Calculation of trust value for Drosophila development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fbdv took 6.883402347564697s
Availability | SPARQL endpoint availability check for Fly taxonomy took 0.0001125335693359375s
Availability | VoID file availability check for Fly taxonomy took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.31612062454223633s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0005655288696289062s
Believability | Calculation of trust value for Fly taxonomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fbsp took 8.451363563537598s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 9.107589721679688e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.33956336975097656s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022721290588378906s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 7.235097408294678s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.43208789825439453s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.02183055877685547s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.001065969467163086s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004942417144775391s
Believability | Calculation of trust value for Family Health History Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fhho took 8.229117393493652s
Availability | SPARQL endpoint availability check for Influenza Ontology took 0.00010776519775390625s
Availability | VoID file availability check for Influenza Ontology took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.3155825138092041s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010347366333007812s
Believability | Calculation of trust value for Influenza Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-flu took 7.530828952789307s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 0.00012373924255371094s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.3245580196380615s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.699562072753906e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fma took 7.385927200317383s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.3139674663543701s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.022020578384399414s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.001020193099975586s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00017261505126953125s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fypo took 6.904963970184326s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.34424710273742676s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.021527767181396484s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0010159015655517578s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 0.00011849403381347656s
Believability | Calculation of trust value for GeoSpecies Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-geospecies took 6.863391637802124s
Availability | SPARQL endpoint availability check for General Formal Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.3159480094909668s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.02113962173461914s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016450881958007812s
Believability | Calculation of trust value for General Formal Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-gfo took 6.938733339309692s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 0.0002655982971191406s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0007822513580322266s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.307431697845459s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005924701690673828s
Believability | Calculation of trust value for General Formal Ontology: Biology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-gfo-bio took 6.436281442642212s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 8.893013000488281e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0003960132598876953s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 2.00907826423645s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.021953582763671875s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008890628814697266s
Believability | Calculation of trust value for Gene Ontology Extension took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-go_x1 took 7.990216493606567s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Gene Ontology took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.328113317489624s
Reputation | Calculation of the PageRank for Gene Ontology took 0.021520376205444336s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0008168220520019531s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0009372234344482422s
Believability | Calculation of trust value for Gene Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-go_x2 took 7.659799814224243s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.506111145019531e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.303478479385376s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.1948089599609375e-05s
Believability | Calculation of trust value for Cereal Plant Development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gro took 6.8559722900390625s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 8.749961853027344e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.4450364112854004s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.025985002517700195s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0012388229370117188s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0005970001220703125s
Believability | Calculation of trust value for Cereal plant gross anatomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-gro_x1 took 6.847682952880859s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.424454927444458s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.0214383602142334s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007846355438232422s
Believability | Calculation of trust value for Gene Regulation Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-gro_x2 took 7.210371494293213s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 0.00010776519775390625s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.3202250003814697s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020679473876953125s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005705356597900391s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-hao took 6.9196977615356445s
Availability | SPARQL endpoint availability check for HCPCS took 4.506111145019531e-05s
Availability | VoID file availability check for HCPCS took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for HCPCS took 0.30271387100219727s
Reputation | Calculation of the PageRank for HCPCS took 0.022609710693359375s
Interlinking | Calculation of Degree of Connection for HCPCS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for HCPCS took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00022602081298828125s
Believability | Calculation of trust value for HCPCS took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-hcpcs took 7.4220263957977295s
Availability | SPARQL endpoint availability check for Health Level Seven took 8.58306884765625e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.43316197395324707s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02109384536743164s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012884140014648438s
Believability | Calculation of trust value for Health Level Seven took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-hl7 took 9.073476076126099s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 8.535385131835938e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.32333850860595703s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020336151123046875s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003380775451660156s
Believability | Calculation of trust value for HEALTH_INDICATORS took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-hlth_indics took 7.425562620162964s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 9.107589721679688e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.30938053131103516s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.022013187408447266s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0013880729675292969s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 5.459785461425781e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-hom took 8.387661695480347s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 8.7738037109375e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 1.4117705821990967s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.021372079849243164s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.218650817871094e-05s
Believability | Calculation of trust value for HOM-HARVARD took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-hom_harvard took 7.336168527603149s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.3059561252593994s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006124973297119141s
Believability | Calculation of trust value for Human Phenotype Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hp_x1 took 8.245651245117188s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 6.890296936035156e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.299715518951416s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.0223391056060791s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0009999275207519531s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-hpio took 8.500814437866211s
Availability | SPARQL endpoint availability check for HUGO took 9.274482727050781e-05s
Availability | VoID file availability check for HUGO took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for HUGO took 0.31282496452331543s
Reputation | Calculation of the PageRank for HUGO took 0.020953655242919922s
Interlinking | Calculation of Degree of Connection for HUGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.654594421386719e-05s
Believability | Calculation of trust value for HUGO took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hugo took 9.459945440292358s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 0.0001373291015625s
Availability | VoID file availability check for Information Artifact Ontology took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.31293535232543945s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006470680236816406s
Believability | Calculation of trust value for Information Artifact Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-iao took 8.316877841949463s
Availability | SPARQL endpoint availability check for ICD10 took 4.553794860839844e-05s
Availability | VoID file availability check for ICD10 took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for ICD10 took 0.3287069797515869s
Reputation | Calculation of the PageRank for ICD10 took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0010364055633544922s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.00092315673828125s
Believability | Calculation of trust value for ICD10 took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icd10 took 7.264795303344727s
Availability | SPARQL endpoint availability check for ICD10CM took 4.458427429199219e-05s
Availability | VoID file availability check for ICD10CM took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.5493273735046387s
Reputation | Calculation of the PageRank for ICD10CM took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006062984466552734s
Believability | Calculation of trust value for ICD10CM took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-icd10cm took 7.0628862380981445s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 8.630752563476562e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.44019293785095215s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.021813154220581055s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00017023086547851562s
Believability | Calculation of trust value for ICD-10-PCS took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-icd10pcs took 6.207240104675293s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 8.988380432128906e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0007340908050537109s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.3123512268066406s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006368160247802734s
Believability | Calculation of trust value for International Classification of Diseases took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-icd9cm took 7.051668167114258s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 8.869171142578125e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.4165349006652832s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.00044417381286621094s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icf_x1 took 8.04286503791809s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 8.845329284667969e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0007581710815429688s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.29785919189453125s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.024408340454101562s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0012178421020507812s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.001443624496459961s
Believability | Calculation of trust value for International Classification for Nursing Practice took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icnp took 6.842378854751587s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 8.606910705566406e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.32959842681884766s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.02323126792907715s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0010256767272949219s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0005526542663574219s
Believability | Calculation of trust value for International Classification of Primary Care took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-icpc took 7.607572555541992s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 9.72747802734375e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.3419761657714844s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0008623600006103516s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0009794235229492188s
Believability | Calculation of trust value for ICPC-2 PLUS took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icpc2p took 7.95482063293457s
Availability | SPARQL endpoint availability check for ICPS Network took 8.440017700195312e-05s
Availability | VoID file availability check for ICPS Network took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.3059680461883545s
Reputation | Calculation of the PageRank for ICPS Network took 0.022519826889038086s
Interlinking | Calculation of Degree of Connection for ICPS Network took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00023102760314941406s
Believability | Calculation of trust value for ICPS Network took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icps took 6.868126392364502s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.40782833099365234s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008234977722167969s
Believability | Calculation of trust value for Infectious Disease Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ido took 7.996896028518677s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0007617473602294922s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.4254591464996338s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02292633056640625s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0010933876037597656s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0013091564178466797s
Believability | Calculation of trust value for Brucellosis Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-idobru took 7.182910680770874s
Availability | SPARQL endpoint availability check for Malaria Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0004124641418457031s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.3107759952545166s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012738704681396484s
Believability | Calculation of trust value for Malaria Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-idomal took 6.97716498374939s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 0.00011897087097167969s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.337343692779541s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003261566162109375s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-iev took 7.7681450843811035s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 9.059906005859375e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.4212000370025635s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.02067279815673828s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00015616416931152344s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-imgt took 7.006992816925049s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 8.559226989746094e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.3046140670776367s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020816564559936523s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005424022674560547s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-imr took 7.491885662078857s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.5349991321563721s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007817745208740234s
Believability | Calculation of trust value for Interaction Network Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ino took 7.399498701095581s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.506111145019531e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.4349980354309082s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.4809112548828125e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-invertebrata took 7.164682388305664s
Availability | SPARQL endpoint availability check for IxnO took 8.559226989746094e-05s
Availability | VoID file availability check for IxnO took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for IxnO took 0.32452845573425293s
Reputation | Calculation of the PageRank for IxnO took 0.023148536682128906s
Interlinking | Calculation of Degree of Connection for IxnO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0009200572967529297s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.0002396106719970703s
Believability | Calculation of trust value for IxnO took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ixno took 6.674053907394409s
Availability | SPARQL endpoint availability check for SysMO-JERM took 8.344650268554688e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.3257863521575928s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003783702850341797s
Believability | Calculation of trust value for SysMO-JERM took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-jerm took 7.324882507324219s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.00042247772216796875s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.31312990188598633s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.02172231674194336s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0008485317230224609s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.5762786865234375e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-kisao took 7.0587053298950195s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 8.606910705566406e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.3005197048187256s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020854711532592773s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00020742416381835938s
Believability | Calculation of trust value for Loggerhead nesting took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-lhn took 7.336334228515625s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Lipid Ontology took 0.00038743019104003906s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.3136861324310303s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.02080392837524414s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0008172988891601562s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00022149085998535156s
Believability | Calculation of trust value for Lipid Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-lipro took 7.627359867095947s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.315376281738281e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.4574589729309082s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.0209047794342041s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.001804351806640625s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-lnc took 7.121093988418579s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 5.6743621826171875e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.31535983085632324s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006577968597412109s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ma took 7.128071546554565s
Availability | SPARQL endpoint availability check for Multiple alignment took 0.00010251998901367188s
Availability | VoID file availability check for Multiple alignment took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.4303455352783203s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020496845245361328s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00020956993103027344s
Believability | Calculation of trust value for Multiple alignment took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mao took 9.448980331420898s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 8.916854858398438e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.5036628246307373s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.02100515365600586s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007011890411376953s
Believability | Calculation of trust value for Minimal anatomical terminology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mat took 7.696714162826538s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 8.797645568847656e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.29939794540405273s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.02183675765991211s
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.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004131793975830078s
Believability | Calculation of trust value for Breast tissue cell lines took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mcbcc took 7.432383060455322s
Availability | SPARQL endpoint availability check for Cell line ontology took 0.00013113021850585938s
Availability | VoID file availability check for Cell line ontology took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.40929722785949707s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02073836326599121s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.000774383544921875s
Believability | Calculation of trust value for Cell line ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mccl took 7.049341440200806s
Availability | SPARQL endpoint availability check for Cell line ontology took 9.703636169433594e-05s
Availability | VoID file availability check for Cell line ontology took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.463059663772583s
Reputation | Calculation of the PageRank for Cell line ontology took 0.026631593704223633s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.001220703125s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.001674652099609375s
Believability | Calculation of trust value for Cell line ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 7.886792898178101s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 8.916854858398438e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.45813488960266113s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02218031883239746s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00025200843811035156s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mcv took 8.916385650634766s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 9.036064147949219e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.000682830810546875s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.3107335567474365s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020856142044067383s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00016880035400390625s
Believability | Calculation of trust value for Master Drug Data Base took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mddb took 7.336348295211792s
Availability | SPARQL endpoint availability check for MedDRA took 8.821487426757812e-05s
Availability | VoID file availability check for MedDRA took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for MedDRA took 0.31848740577697754s
Reputation | Calculation of the PageRank for MedDRA took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011098384857177734s
Believability | Calculation of trust value for MedDRA took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-mdr took 9.608196496963501s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 8.58306884765625e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.32718515396118164s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.021253347396850586s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008704662322998047s
Believability | Calculation of trust value for MedlinePlus Health Topics took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-medlineplus took 7.336883306503296s
Availability | SPARQL endpoint availability check for MeGO took 9.369850158691406e-05s
Availability | VoID file availability check for MeGO took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for MeGO took 1.7347843647003174s
Reputation | Calculation of the PageRank for MeGO took 0.020810365676879883s
Interlinking | Calculation of Degree of Connection for MeGO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014829635620117188s
Believability | Calculation of trust value for MeGO took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mego took 10.38723611831665s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 8.96453857421875e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.7642996311187744s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.021607398986816406s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.001043081283569336s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0019845962524414062s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-mesh-owl took 8.102633953094482s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.31720447540283203s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006330013275146484s
Believability | Calculation of trust value for Mental Functioning Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mf took 7.634252309799194s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 8.797645568847656e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0007574558258056641s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.3185892105102539s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020691633224487305s
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.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.000553131103515625s
Believability | Calculation of trust value for Medaka fish anatomy and development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mfo took 7.2202324867248535s
Availability | SPARQL endpoint availability check for Emotion Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.42699694633483887s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.025246620178222656s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0010595321655273438s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0009033679962158203s
Believability | Calculation of trust value for Emotion Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mfoem took 7.930941343307495s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.001407623291015625s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2944040298461914s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.021435022354125977s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0011553764343261719s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.0001513957977294922s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mhc took 7.595782995223999s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 8.606910705566406e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.31284427642822266s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.021764278411865234s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0009276866912841797s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0008549690246582031s
Believability | Calculation of trust value for Protein-protein interaction took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mi took 7.122780799865723s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.291534423828125e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.4976005554199219s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.02209949493408203s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0010766983032226562s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0008666515350341797s
Believability | Calculation of trust value for Mosquito insecticide resistance took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-miro took 8.48734712600708s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.506427526473999s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020911693572998047s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001480579376220703s
Believability | Calculation of trust value for Measurement Method Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mmo took 7.8900086879730225s
Availability | SPARQL endpoint availability check for MGED Ontology took 0.0001227855682373047s
Availability | VoID file availability check for MGED Ontology took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.4068624973297119s
Reputation | Calculation of the PageRank for MGED Ontology took 0.021728515625s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0010056495666503906s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0004627704620361328s
Believability | Calculation of trust value for MGED Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mo took 8.643730878829956s
Availability | SPARQL endpoint availability check for Protein modification took 9.179115295410156e-05s
Availability | VoID file availability check for Protein modification took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Protein modification took 0.30280590057373047s
Reputation | Calculation of the PageRank for Protein modification took 0.020778417587280273s
Interlinking | Calculation of Degree of Connection for Protein modification took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002288818359375s
Believability | Calculation of trust value for Protein modification took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mod took 7.170019865036011s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 9.179115295410156e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.4219367504119873s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.001018524169921875s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006709098815917969s
Believability | Calculation of trust value for Mammalian phenotype took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mp took 7.842136383056641s
Availability | SPARQL endpoint availability check for Mouse pathology took 8.463859558105469e-05s
Availability | VoID file availability check for Mouse pathology took 0.00037932395935058594s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.3132917881011963s
Reputation | Calculation of the PageRank for Mouse pathology took 0.021431684494018555s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00047135353088378906s
Believability | Calculation of trust value for Mouse pathology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mpath took 7.2818520069122314s
Availability | SPARQL endpoint availability check for Mass spectrometry took 8.7738037109375e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.39565229415893555s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020410776138305664s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003502368927001953s
Believability | Calculation of trust value for Mass spectrometry took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ms took 7.866478681564331s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 8.726119995117188e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.34351682662963867s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020362377166748047s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018720626831054688s
Believability | Calculation of trust value for Medical Subject Headings took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-msh took 10.141943454742432s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 0.00010657310485839844s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.3130207061767578s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020943403244018555s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0001785755157470703s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mthch took 8.13243842124939s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 5.459785461425781e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.3059713840484619s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.021091461181640625s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0010099411010742188s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0009915828704833984s
Believability | Calculation of trust value for Natural Products Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-natpro took 7.460034132003784s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 0.00010180473327636719s
Availability | VoID file availability check for NCBI organismal classification took 0.0008187294006347656s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.4151327610015869s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008211135864257812s
Believability | Calculation of trust value for NCBI organismal classification took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 7.297382831573486s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.38690185546875e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.4841275215148926s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020268678665161133s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0019230842590332031s
Believability | Calculation of trust value for NCI Thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ncit took 7.144323110580444s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.2438507080078125e-05s
Availability | VoID file availability check for National Drug Data File took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.3000447750091553s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006368160247802734s
Believability | Calculation of trust value for National Drug Data File took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nddf took 7.034045219421387s
Availability | SPARQL endpoint availability check for National Drug File took 9.179115295410156e-05s
Availability | VoID file availability check for National Drug File took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for National Drug File took 0.4776034355163574s
Reputation | Calculation of the PageRank for National Drug File took 0.02109694480895996s
Interlinking | Calculation of Degree of Connection for National Drug File took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012242794036865234s
Believability | Calculation of trust value for National Drug File took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ndfrt took 7.258468151092529s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 8.821487426757812e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.32695460319519043s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.022141456604003906s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.001115560531616211s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 7.312639474868774s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.317795991897583s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006639957427978516s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-neomark took 7.786615610122681s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.6952686309814453s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020877599716186523s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0008649826049804688s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.0001671314239501953s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-neomarkontology took 6.809664249420166s
Availability | SPARQL endpoint availability check for NIFSTD took 4.506111145019531e-05s
Availability | VoID file availability check for NIFSTD took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.38727664947509766s
Reputation | Calculation of the PageRank for NIFSTD took 0.021085739135742188s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019161701202392578s
Believability | Calculation of trust value for NIFSTD took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nif took 7.780159950256348s
Availability | SPARQL endpoint availability check for NIF Cell took 0.00012683868408203125s
Availability | VoID file availability check for NIF Cell took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.4472801685333252s
Reputation | Calculation of the PageRank for NIF Cell took 0.021558046340942383s
Interlinking | Calculation of Degree of Connection for NIF Cell took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0013418197631835938s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0017216205596923828s
Believability | Calculation of trust value for NIF Cell took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nif_cell took 7.97756814956665s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.3392181396484375e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.31654906272888184s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020360469818115234s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014071464538574219s
Believability | Calculation of trust value for NIF Dysfunction took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-nif_dysfunction took 8.581616163253784s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.31595659255981445s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02310919761657715s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005788803100585938s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-nigo took 7.075225353240967s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 8.678436279296875e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.29276394844055176s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.022040367126464844s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0010340213775634766s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0006909370422363281s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-nmr took 8.883500099182129s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0010521411895751953s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.33408617973327637s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.027434110641479492s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0014162063598632812s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00017142295837402344s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-nonrctontology took 7.82869291305542s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 0.00010800361633300781s
Availability | VoID file availability check for NanoParticle Ontology took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.3150608539581299s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0012123584747314453s
Believability | Calculation of trust value for NanoParticle Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-npo took 7.0639026165008545s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 9.703636169433594e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0010688304901123047s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.3315622806549072s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007178783416748047s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-oae took 7.167189598083496s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 8.535385131835938e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.00039577484130859375s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 2.8827669620513916s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.022090435028076172s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0009720325469970703s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0015773773193359375s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-obi took 9.842559337615967s
Availability | SPARQL endpoint availability check for OBOE took 8.749961853027344e-05s
Availability | VoID file availability check for OBOE took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for OBOE took 0.4101598262786865s
Reputation | Calculation of the PageRank for OBOE took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for OBOE took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011229515075683594s
Believability | Calculation of trust value for OBOE took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-oboe took 6.795422315597534s
Availability | SPARQL endpoint availability check for OBOE SBC took 8.916854858398438e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.3104848861694336s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007996559143066406s
Believability | Calculation of trust value for OBOE SBC took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 7.37021279335022s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.4218475818634033s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0006089210510253906s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ocre took 7.2665910720825195s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 8.344650268554688e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.325300931930542s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008373260498046875s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-odgi took 6.825638055801392s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 8.845329284667969e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 1.3065431118011475s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020935773849487305s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008904933929443359s
Believability | Calculation of trust value for Ontology for Genetic Interval took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ogi took 8.567480564117432s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 9.107589721679688e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0008504390716552734s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.41622161865234375s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.021395444869995117s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00034165382385253906s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ogmd took 7.4918482303619385s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 9.012222290039062e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0007755756378173828s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.34218597412109375s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.021251916885375977s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006895065307617188s
Believability | Calculation of trust value for Ontology for General Medical Science took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ogms took 8.863027811050415s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 8.559226989746094e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.43471479415893555s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020832061767578125s
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.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011210441589355469s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-omim took 7.393796682357788s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 8.988380432128906e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.34849977493286133s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.021619796752929688s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0010559558868408203s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0005695819854736328s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-omit took 7.027611970901489s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 8.845329284667969e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.3793375492095947s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.022935152053833008s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0011420249938964844s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0007472038269042969s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-omrse took 8.241074323654175s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 9.131431579589844e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.34296560287475586s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020260334014892578s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007545948028564453s
Believability | Calculation of trust value for Ontology of Data Mining took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ontodm took 9.289365291595459s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 0.00010800361633300781s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.46948933601379395s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.021030664443969727s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002384185791015625s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ontodt took 7.437555551528931s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 8.845329284667969e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.45062756538391113s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.00061798095703125s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ontoorpha took 7.6479456424713135s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 8.749961853027344e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 1.3648326396942139s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.027065515518188477s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0014367103576660156s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0012497901916503906s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-opl took 8.309111833572388s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.267692565917969e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.5085582733154297s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0009188652038574219s
Believability | Calculation of trust value for Phenotypic quality took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pato took 8.397157907485962s
Availability | SPARQL endpoint availability check for Physician Data Query took 8.916854858398438e-05s
Availability | VoID file availability check for Physician Data Query took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.3713948726654053s
Reputation | Calculation of the PageRank for Physician Data Query took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0008540153503417969s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008749961853027344s
Believability | Calculation of trust value for Physician Data Query took 7.62939453125e-06s
INFO | --- Analysis for bioportal-pdq took 7.3880956172943115s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 9.679794311523438e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0003764629364013672s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 1.0850825309753418s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008175373077392578s
Believability | Calculation of trust value for Pediatric Terminology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pedterm took 7.5532495975494385s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 1.9917359352111816s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.0213162899017334s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00018858909606933594s
Believability | Calculation of trust value for Parasite Experiment Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-peo took 8.409234523773193s
Availability | SPARQL endpoint availability check for PHARE took 8.869171142578125e-05s
Availability | VoID file availability check for PHARE took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for PHARE took 0.39714694023132324s
Reputation | Calculation of the PageRank for PHARE took 0.021139860153198242s
Interlinking | Calculation of Degree of Connection for PHARE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006308555603027344s
Believability | Calculation of trust value for PHARE took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-phare took 7.5954625606536865s
Availability | SPARQL endpoint availability check for PKO_Re took 8.940696716308594e-05s
Availability | VoID file availability check for PKO_Re took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.35030412673950195s
Reputation | Calculation of the PageRank for PKO_Re took 0.023166418075561523s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001876354217529297s
Believability | Calculation of trust value for PKO_Re took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-pko took 7.838345050811768s
Availability | SPARQL endpoint availability check for PMA 2010 took 8.940696716308594e-05s
Availability | VoID file availability check for PMA 2010 took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.41571998596191406s
Reputation | Calculation of the PageRank for PMA 2010 took 0.021456003189086914s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008885860443115234s
Believability | Calculation of trust value for PMA 2010 took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pma took 7.750872373580933s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 8.416175842285156e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.3530435562133789s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00017189979553222656s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pmr took 6.958302736282349s
Availability | SPARQL endpoint availability check for Plant Anatomy took 8.7738037109375e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.3003087043762207s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020892620086669922s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0004050731658935547s
Believability | Calculation of trust value for Plant Anatomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-po took 8.81366515159607s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 8.702278137207031e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.32126736640930176s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02099752426147461s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.343292236328125e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-po_x1 took 10.939045667648315s
Availability | SPARQL endpoint availability check for Plant Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Plant Ontology took 0.0007123947143554688s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.304302453994751s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004477500915527344s
Believability | Calculation of trust value for Plant Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-po_x2 took 9.059131622314453s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 5.078315734863281e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.30968284606933594s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.02078104019165039s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0008461475372314453s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0007090568542480469s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pr took 7.92481255531311s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 0.00013399124145507812s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2997748851776123s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02283453941345215s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00027298927307128906s
Believability | Calculation of trust value for Proteomics data and process provenance took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-propreo took 7.831904649734497s
Availability | SPARQL endpoint availability check for Pathway ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Pathway ontology took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.3236424922943115s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00014162063598632812s
Believability | Calculation of trust value for Pathway ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pw took 7.327363729476929s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.3103480339050293s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.4332275390625e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-qibo took 7.527668714523315s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.363059997558594e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3597846031188965s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017313957214355469s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rcd took 7.362647771835327s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.3087186813354492s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.0001418590545654297s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-rctontology took 7.619625091552734s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.30326104164123535s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02631664276123047s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.00011181831359863281s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-repo took 9.847355604171753s
Availability | SPARQL endpoint availability check for Physico-chemical process took 8.511543273925781e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.33135199546813965s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0002040863037109375s
Believability | Calculation of trust value for Physico-chemical process took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rex took 8.175026178359985s
Availability | SPARQL endpoint availability check for RadLex took 9.226799011230469e-05s
Availability | VoID file availability check for RadLex took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for RadLex took 0.3320908546447754s
Reputation | Calculation of the PageRank for RadLex took 0.020786285400390625s
Interlinking | Calculation of Degree of Connection for RadLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015060901641845703s
Believability | Calculation of trust value for RadLex took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-rid took 7.672578811645508s
Availability | SPARQL endpoint availability check for RNA ontology took 8.678436279296875e-05s
Availability | VoID file availability check for RNA ontology took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.4768986701965332s
Reputation | Calculation of the PageRank for RNA ontology took 0.021788835525512695s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005595684051513672s
Believability | Calculation of trust value for RNA ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-rnao took 7.436067342758179s
Availability | SPARQL endpoint availability check for Role Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Role Ontology took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Role Ontology took 1.0185327529907227s
Reputation | Calculation of the PageRank for Role Ontology took 0.020605802536010742s
Interlinking | Calculation of Degree of Connection for Role Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00019240379333496094s
Believability | Calculation of trust value for Role Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-roleo took 7.223154067993164s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.42045021057128906s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02090620994567871s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00018310546875s
Believability | Calculation of trust value for Rat Strain Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-rs took 7.161465167999268s
Availability | SPARQL endpoint availability check for RxNORM took 9.369850158691406e-05s
Availability | VoID file availability check for RxNORM took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for RxNORM took 2.187896966934204s
Reputation | Calculation of the PageRank for RxNORM took 0.020806550979614258s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006482601165771484s
Believability | Calculation of trust value for RxNORM took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-rxnorm took 8.809154987335205s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.9591064453125e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.32746243476867676s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010175704956054688s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-sao took 7.623534440994263s
Availability | SPARQL endpoint availability check for Systems Biology took 8.7738037109375e-05s
Availability | VoID file availability check for Systems Biology took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.4151153564453125s
Reputation | Calculation of the PageRank for Systems Biology took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for Systems Biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004417896270751953s
Believability | Calculation of trust value for Systems Biology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sbo took 7.665405511856079s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.525282621383667s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.021376609802246094s
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.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010633468627929688s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sbro took 10.540316343307495s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.32106947898864746s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.02100515365600586s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013141632080078125s
Believability | Calculation of trust value for Sleep Domain Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-sdo took 7.172434329986572s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 8.916854858398438e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.44617724418640137s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003330707550048828s
Believability | Calculation of trust value for Sample processing and separation techniques took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sep took 8.616447925567627s
Availability | SPARQL endpoint availability check for Student Health Record took 9.560585021972656e-05s
Availability | VoID file availability check for Student Health Record took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.5352001190185547s
Reputation | Calculation of the PageRank for Student Health Record took 0.02089977264404297s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004458427429199219s
Believability | Calculation of trust value for Student Health Record took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-shr took 7.62183141708374s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.32159948348999023s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.021222829818725586s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012009143829345703s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-sio took 8.363518953323364s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 7.367134094238281e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0003955364227294922s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 1.285886287689209s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0002105236053466797s
Believability | Calculation of trust value for Situation-Based Access Control took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sitbac took 8.127898931503296s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 8.630752563476562e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0003876686096191406s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.40606260299682617s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0018935203552246094s
Believability | Calculation of trust value for SNOMED Clinical Terms took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-snomedct took 7.607148885726929s
Availability | SPARQL endpoint availability check for SNP-Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.7909853458404541s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.021312713623046875s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006797313690185547s
Believability | Calculation of trust value for SNP-Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-snpo took 7.8584184646606445s
Availability | SPARQL endpoint availability check for Sequence types and features took 0.0001609325408935547s
Availability | VoID file availability check for Sequence types and features took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.3210585117340088s
Reputation | Calculation of the PageRank for Sequence types and features took 0.02155017852783203s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0010223388671875s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0006811618804931641s
Believability | Calculation of trust value for Sequence types and features took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-so_x1 took 9.61376142501831s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 8.678436279296875e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.00034499168395996094s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.7511050701141357s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.021152973175048828s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015704631805419922s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sopharm took 7.808406591415405s
Availability | SPARQL endpoint availability check for SoyOntology took 8.96453857421875e-05s
Availability | VoID file availability check for SoyOntology took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.36148834228515625s
Reputation | Calculation of the PageRank for SoyOntology took 0.020622968673706055s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00013184547424316406s
Believability | Calculation of trust value for SoyOntology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-soy took 6.786048173904419s
Availability | SPARQL endpoint availability check for Spider Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.3104715347290039s
Reputation | Calculation of the PageRank for Spider Ontology took 0.02094578742980957s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00039696693420410156s
Believability | Calculation of trust value for Spider Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-spd took 7.6611104011535645s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 0.00015163421630859375s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.00034999847412109375s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.44202494621276855s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.022066831588745117s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00028204917907714844s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-spto took 7.85565447807312s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0003437995910644531s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.3122246265411377s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004572868347167969s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-sso took 7.262201309204102s
Availability | SPARQL endpoint availability check for Software Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for Software Ontology took 0.00033545494079589844s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.8789582252502441s
Reputation | Calculation of the PageRank for Software Ontology took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00042176246643066406s
Believability | Calculation of trust value for Software Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-swo took 8.328288078308105s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 8.7738037109375e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.45876383781433105s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.021405458450317383s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.001138448715209961s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00030040740966796875s
Believability | Calculation of trust value for Tick gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-tads took 9.385767698287964s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.40471982955932617s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008928775787353516s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-tao took 8.730814456939697s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 8.869171142578125e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.00040721893310546875s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.9167060852050781s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.02143549919128418s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.000978708267211914s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 0.00012350082397460938s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-taxrank took 14.3722083568573s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.4345855712890625e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.3104097843170166s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02248096466064453s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.605552673339844e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-teddy took 7.344014883041382s
Availability | SPARQL endpoint availability check for Time Event Ontology took 0.00010156631469726562s
Availability | VoID file availability check for Time Event Ontology took 0.00041365623474121094s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.4347374439239502s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008111000061035156s
Believability | Calculation of trust value for Time Event Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-teo took 7.1802356243133545s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 8.702278137207031e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 1.0910093784332275s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020847797393798828s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00042057037353515625s
Believability | Calculation of trust value for Mosquito gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-tgma took 9.59782075881958s
Availability | SPARQL endpoint availability check for thesaurus took 8.916854858398438e-05s
Availability | VoID file availability check for thesaurus took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for thesaurus took 1.373584270477295s
Reputation | Calculation of the PageRank for thesaurus took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.05718994140625e-05s
Believability | Calculation of trust value for thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-thesaurus took 9.033145427703857s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 5.7220458984375e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.4736330509185791s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020690202713012695s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003552436828613281s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 8.480888366699219s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.31591176986694336s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.0214083194732666s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.000827789306640625s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tmo took 9.710355043411255s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.395308256149292s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020756959915161133s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00016808509826660156s
Believability | Calculation of trust value for Plant Trait Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-to took 9.147130012512207s
Availability | SPARQL endpoint availability check for TOK_Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.30448174476623535s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00019216537475585938s
Believability | Calculation of trust value for TOK_Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tok took 7.392642498016357s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 8.869171142578125e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.3179633617401123s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.021781444549560547s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.0002522468566894531s
Believability | Calculation of trust value for Teleost taxonomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tto took 9.375552654266357s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.33116579055786133s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020302534103393555s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.001051187515258789s
Believability | Calculation of trust value for Uber anatomy ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-uberon took 9.066201210021973s
Availability | SPARQL endpoint availability check for Units Ontology took 0.00012540817260742188s
Availability | VoID file availability check for Units Ontology took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.3086838722229004s
Reputation | Calculation of the PageRank for Units Ontology took 0.0211184024810791s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0008118152618408203s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002620220184326172s
Believability | Calculation of trust value for Units Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-unitsontology took 10.179973840713501s
Availability | SPARQL endpoint availability check for Units of measurement took 8.559226989746094e-05s
Availability | VoID file availability check for Units of measurement took 0.0004062652587890625s
Completeness | Calculation of interlinking completeness for Units of measurement took 1.1750330924987793s
Reputation | Calculation of the PageRank for Units of measurement took 0.02179718017578125s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0009696483612060547s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00033974647521972656s
Believability | Calculation of trust value for Units of measurement took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-uo took 8.45134973526001s
Availability | SPARQL endpoint availability check for VANDF took 8.463859558105469e-05s
Availability | VoID file availability check for VANDF took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for VANDF took 0.4690530300140381s
Reputation | Calculation of the PageRank for VANDF took 0.02106332778930664s
Interlinking | Calculation of Degree of Connection for VANDF took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0012483596801757812s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0008909702301025391s
Believability | Calculation of trust value for VANDF took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-vandf took 8.014153718948364s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0007445812225341797s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.31026554107666016s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.025945186614990234s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.000431060791015625s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-vao took 9.23067855834961s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.1961669921875e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 1.091085433959961s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.021349191665649414s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0008375644683837891s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006797313690185547s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-vhog took 9.886430501937866s
Availability | SPARQL endpoint availability check for VIVO took 0.00010633468627929688s
Availability | VoID file availability check for VIVO took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for VIVO took 0.5060141086578369s
Reputation | Calculation of the PageRank for VIVO took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for VIVO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003619194030761719s
Believability | Calculation of trust value for VIVO took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-vivo took 7.050422191619873s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.29724979400634766s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.024604082107543945s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0011281967163085938s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0013799667358398438s
Believability | Calculation of trust value for Vaccine Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vo took 9.381160259246826s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0006470680236816406s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.3356149196624756s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020560026168823242s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.0002117156982421875s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-vt took 6.837406635284424s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 8.487701416015625e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0007522106170654297s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.32270050048828125s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0004992485046386719s
Believability | Calculation of trust value for C. elegans gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-wbbt took 8.287959337234497s
Availability | SPARQL endpoint availability check for C. elegans development took 0.0001316070556640625s
Availability | VoID file availability check for C. elegans development took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.41727447509765625s
Reputation | Calculation of the PageRank for C. elegans development took 0.021949052810668945s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.5299530029296875e-05s
Believability | Calculation of trust value for C. elegans development took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-wbls took 7.388821601867676s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 8.893013000488281e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.36065173149108887s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.02143549919128418s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0008080005645751953s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 9.5367431640625e-05s
Believability | Calculation of trust value for C. elegans phenotype took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-wbphenotype took 6.31277322769165s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 0.00012683868408203125s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.3130488395690918s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005941390991210938s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-who took 8.048797607421875s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 8.606910705566406e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 1.9342899322509766s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006835460662841797s
Believability | Calculation of trust value for Xenopus anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-xao took 10.537693977355957s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 1.0981593132019043s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00024080276489257812s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-xco took 9.354269981384277s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 0.00011038780212402344s
Availability | VoID file availability check for Yeast phenotypes took 0.0007994174957275391s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 1.960892677307129s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.025365114212036133s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0012142658233642578s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0003628730773925781s
Believability | Calculation of trust value for Yeast phenotypes took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ypo took 10.406020164489746s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 9.059906005859375e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.000820159912109375s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 1.9988656044006348s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020987749099731445s
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.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007531642913818359s
Believability | Calculation of trust value for Zebrafish anatomy and development took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-zfa took 7.9176599979400635s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 0.00010561943054199219s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0003807544708251953s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.32350707054138184s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.023267745971679688s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0011408329010009766s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 4.1484832763671875e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.2159347534179688e-05s
INFO | --- Analysis for Bioportal_link took 4.309197664260864s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.5500118732452393s
Availability | VoID file availability check for BioSamples RDF took 0.08616471290588379s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.5013985633850098s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020932674407958984s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.1682510375976562e-05s
INFO | --- Analysis for biosamples-rdf took 2.9920010566711426s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.09800100326538086s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.33953285217285156s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.021005868911743164s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011706352233886719s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for bis-linked-data took 2.449022054672241s
Availability | SPARQL endpoint availability check for Bitzi took 0.00010895729064941406s
Availability | VoID file availability check for Bitzi took 0.00030875205993652344s
Completeness | Calculation of interlinking completeness for Bitzi took 0.3155505657196045s
Reputation | Calculation of the PageRank for Bitzi took 0.021392345428466797s
Interlinking | Calculation of Degree of Connection for Bitzi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bitzi took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.147125244140625e-05s
Believability | Calculation of trust value for Bitzi took 1.1444091796875e-05s
INFO | --- Analysis for bitzi took 2.407240390777588s
Availability | SPARQL endpoint availability check for BizkaiSense took 0.2586350440979004s
Availability | VoID file availability check for BizkaiSense took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.9619596004486084s
Reputation | Calculation of the PageRank for BizkaiSense took 0.021730661392211914s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.695487976074219e-05s
Believability | Calculation of trust value for BizkaiSense took 1.0013580322265625e-05s
INFO | --- Analysis for bizkaisense took 5.720760107040405s
Availability | SPARQL endpoint availability check for blabla.itemlist took 9.512901306152344e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0008783340454101562s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 1.341585397720337s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.0208432674407959s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.409385681152344e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.1682510375976562e-05s
INFO | --- Analysis for blabla-itemlist took 33.09902572631836s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.363059997558594e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0009493827819824219s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.33780550956726074s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0517578125e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.33514404296875e-05s
INFO | --- Analysis for blabla_itemlist took 32.14320206642151s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.58306884765625e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.3171374797821045s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.021292924880981445s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.00543212890625e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for bll-thesaurus took 3.1604695320129395s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.0455849170684814s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.32912373542785645s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.699562072753906e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for bluk-bnb took 9.756723642349243s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.24950098991394043s
Availability | VoID file availability check for Thesaurus BNCF took 0.0007221698760986328s
Extra | Recovery of all triples for Thesaurus BNCF took 42.771777868270874s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6468222141265869s
Amount of data | Number of triples check for Thesaurus BNCF took 0.5928988456726074s
Interoperability | New terms check for Thesaurus BNCF took 1.4684734344482422s
Versatility | Languages check for Thesaurus BNCF took 6.317803144454956s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8351638317108154s
Security | Check HTTPS for Thesaurus BNCF took 0.08170962333679199s
Interpretability | RDF structures check for Thesaurus BNCF took 0.12323880195617676s
Versatility | Serialization formats check for Thesaurus BNCF took 0.11515402793884277s
Availability | RDF dump link check for Thesaurus BNCF took 0.13019537925720215s
License | MR license check for Thesaurus BNCF took 0.11762285232543945s
License | HR license check for Thesaurus BNCF took 0.18505167961120605s
Amount of data | Number of property check for Thesaurus BNCF took 0.11971259117126465s
Understandability | Number of label check for Thesaurus BNCF took 0.26523494720458984s
Understandability | URI regex check for Thesaurus BNCF took 0.22212457656860352s
Understandability | Vocabs check for Thesaurus BNCF took 0.11901402473449707s
Verifiability | Authors check for Thesaurus BNCF took 0.11195206642150879s
Verifiability | Publishers check for Thesaurus BNCF took 0.13396167755126953s
Performance | Throughput check for Thesaurus BNCF took 10.575680255889893s
Amount of data | Check the number of entities for Thesaurus BNCF took 7.557868957519531e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.12067914009094238s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.12465310096740723s
Interlinking | skos check for Thesaurus BNCF took 0.16638422012329102s
Interlinking | skos check for Thesaurus BNCF took 0.13335108757019043s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.11468696594238281s
Currency | Creation date check for Thesaurus BNCF took 0.24037790298461914s
Currency | Modification date check for Thesaurus BNCF took 0.24552631378173828s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.977754592895508s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.12095403671264648s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.12081098556518555s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.12482452392578125s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.024757146835327s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4925196170806885s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.876568555831909s
Consistency | Disjoint class check for Thesaurus BNCF took 0.11310195922851562s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8283782005310059s
Consistency | Misplaced classes for Thesaurus BNCF took 6.816179037094116s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.218790292739868s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4623641967773438s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.1881327629089355s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.384049415588379s
Security | Sign check for Thesaurus BNCF took 0.11008000373840332s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 22.3015718460083s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.5409753322601318s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.023485422134399414s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0009963512420654297s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 9.608268737792969e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.1457672119140625e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.1682510375976562e-05s
INFO | --- Analysis for bncf-ns took 181.37455773353577s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.505495309829712s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0012793540954589844s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9116785526275635s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.352842330932617s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42037463188171387s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.19022274017334s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 61.40833234786987s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42861151695251465s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.640794277191162s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6043603420257568s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3515462875366211s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.40241551399230957s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4452486038208008s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.395681381225586s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2750673294067383s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3258488178253174s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.492586851119995s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.2329633235931396s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39943790435791016s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.445582628250122s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.870419979095459s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.2479248046875e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33760881423950195s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.434861421585083s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.28854799270629883s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3491787910461426s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3948943614959717s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.5432982444763184s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5277211666107178s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 21.369869470596313s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.4708666801452637s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9121260643005371s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03010249137878418s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03022146224975586s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.28701043128967285s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.002023458480835s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5643274784088135s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3013923168182373s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5720839500427246s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.835407018661499s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.031092405319213867s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5558364391326904s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.43822765350341797s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.448931694030762s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36035656929016113s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02210521697998047s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00010967254638671875s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-05s
INFO | --- Analysis for bpr took 499.9925711154938s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.982948303222656e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.31045031547546387s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020989179611206055s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.961822509765625e-05s
Believability | Calculation of trust value for Brazilian Politicians took 8.344650268554688e-06s
INFO | --- Analysis for brazilian-politicians took 3.3732993602752686s
Availability | SPARQL endpoint availability check for BrazilianCities took 382.1110372543335s
Availability | VoID file availability check for BrazilianCities took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.3426172733306885s
Reputation | Calculation of the PageRank for BrazilianCities took 0.021542072296142578s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0010154247283935547s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.743171691894531e-05s
Believability | Calculation of trust value for BrazilianCities took 1.239776611328125e-05s
INFO | --- Analysis for braziliancities took 638.9319880008698s
Availability | SPARQL endpoint availability check for Bricklink took 1.4511597156524658s
Availability | VoID file availability check for Bricklink took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Bricklink took 0.3147428035736084s
Reputation | Calculation of the PageRank for Bricklink took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for Bricklink took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bricklink took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.367134094238281e-05s
Believability | Calculation of trust value for Bricklink took 1.0967254638671875e-05s
INFO | --- Analysis for bricklink took 10.14069390296936s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.349828958511353s
Availability | VoID file availability check for British Museum Collection took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for British Museum Collection took 1.8327105045318604s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 4.291534423828125e-05s
Believability | Calculation of trust value for British Museum Collection took 1.239776611328125e-05s
INFO | --- Analysis for british-museum-collection took 56.21812915802002s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 0.0001049041748046875s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.43823695182800293s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.021405696868896484s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.9114227294921875e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 7.152557373046875e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 6.646899938583374s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 0.08522939682006836s
Availability | VoID file availability check for French Plant Health Bulletins took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.4221527576446533s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.021515369415283203s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0010461807250976562s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 3.695487976074219e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 1.049041748046875e-05s
INFO | --- Analysis for bsv took 2.2541961669921875s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.21561098098754883s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006933212280273438s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 11.069882154464722s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.5988733768463135s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2204744815826416s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.8965837955474854s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.327182054519653s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.962092399597168s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13467621803283691s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1344432830810547s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12277889251708984s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11717653274536133s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 21.049755334854126s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11479043960571289s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2476062774658203s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24419069290161133s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13147950172424316s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12593603134155273s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12341594696044922s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.823446273803711s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.176399230957031e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12207388877868652s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11526083946228027s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12188935279846191s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12146592140197754s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12079524993896484s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2496044635772705s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24340581893920898s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 11.401264905929565s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13090038299560547s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12058472633361816s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12830042839050293s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.1692376136779785s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24661779403686523s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.563525199890137s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1173093318939209s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.2869691848754883s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.309773206710815s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2840392589569092s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.500209093093872s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.7392048835754395s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12049102783203125s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3619.2082154750824s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.1869094371795654s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.021230697631835938s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.7642974853515625e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.430511474609375e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2874603271484375e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3732.2601280212402s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 0.00010752677917480469s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.3004312515258789s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.023187637329101562s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 2.956390380859375e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.0967254638671875e-05s
INFO | --- Analysis for bund-offener-haushalt took 3.0677168369293213s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 0.029479265213012695s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 4.7165234088897705s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.022422075271606445s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.001199483871459961s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 4.887580871582031e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 1.2874603271484375e-05s
INFO | --- Analysis for bundestagnebeneinkuenfte took 13.882702112197876s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.24404525756835938s
Availability | VoID file availability check for business.data.gov.uk took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 2.4495956897735596s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.054473876953125e-05s
Believability | Calculation of trust value for business.data.gov.uk took 8.344650268554688e-06s
INFO | --- Analysis for business-data-gov-uk took 5.995019912719727s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.4326794147491455s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0005955696105957031s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 3.198263168334961s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.4393372535705566s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.6649410724639893s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7924339771270752s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 60.269272804260254s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.46241259574890137s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.191115140914917s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 2.2312941551208496s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.4853787422180176s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.30083799362182617s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.6973299980163574s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 15.867550134658813s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3403303623199463s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 4.471820592880249s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.6233091354370117s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.3589301109313965s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 7.810364723205566s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.2917771339416504s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 12.481739282608032s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 6.914138793945312e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.36409544944763184s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.35105323791503906s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.4680502414703369s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.30789780616760254s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.47533273696899414s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.9090867042541504s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 1.1856615543365479s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 4.540260076522827s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.30623412132263184s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.3841822147369385s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.36173009872436523s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.4369721412658691s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03135967254638672s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.02854180335998535s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.4058372974395752s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.5010695457458496s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.42311787605285645s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 3.535825252532959s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2992610931396484s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.412015914916992s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.034835100173950195s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.3401663303375244s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.391432523727417s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1509.2467596530914s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 7.959237337112427s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.022362232208251953s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0009205341339111328s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 6.437301635742188e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.1682510375976562e-05s
INFO | --- Analysis for BVMC took 1693.5322864055634s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 8.988380432128906e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 11.47495698928833s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.695487976074219e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.152557373046875e-06s
INFO | --- Analysis for cabbage took 45.37738823890686s
Availability | SPARQL endpoint availability check for cablegate took 1.2379868030548096s
Availability | VoID file availability check for cablegate took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for cablegate took 2.7877233028411865s
Reputation | Calculation of the PageRank for cablegate took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for cablegate took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.890296936035156e-05s
Believability | Calculation of trust value for cablegate took 1.1444091796875e-05s
INFO | --- Analysis for cablegate took 51.220008850097656s
Availability | SPARQL endpoint availability check for Calames took 8.702278137207031e-05s
Availability | VoID file availability check for Calames took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Calames took 1.541839838027954s
Reputation | Calculation of the PageRank for Calames took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for Calames took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Calames took 3.62396240234375e-05s
Believability | Calculation of trust value for Calames took 1.1920928955078125e-05s
INFO | --- Analysis for calames took 21.67724633216858s
Availability | SPARQL endpoint availability check for CaLiGraph took 30.12056064605713s
Availability | VoID file availability check for CaLiGraph took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.5021417140960693s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021480321884155273s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0008778572082519531s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.0517578125e-05s
Believability | Calculation of trust value for CaLiGraph took 1.1444091796875e-05s
INFO | --- Analysis for CaLiGraph took 34.433584213256836s
Availability | SPARQL endpoint availability check for CaLiGraph took 30.282870054244995s
Availability | VoID file availability check for CaLiGraph took 0.00040435791015625s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.5177316665649414s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021116971969604492s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.414817810058594e-05s
Believability | Calculation of trust value for CaLiGraph took 1.1444091796875e-05s
INFO | --- Analysis for caligraph took 56.33439588546753s
Availability | SPARQL endpoint availability check for can-link took 0.7354400157928467s
Availability | VoID file availability check for can-link took 0.2442488670349121s
Completeness | Calculation of interlinking completeness for can-link took 0.9387545585632324s
Reputation | Calculation of the PageRank for can-link took 0.02104973793029785s
Interlinking | Calculation of Degree of Connection for can-link took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for can-link took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for can-link took 3.361701965332031e-05s
Believability | Calculation of trust value for can-link took 1.1444091796875e-05s
INFO | --- Analysis for can-link took 13.620178937911987s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.06465983390808105s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.31620335578918457s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.022148847579956055s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.361701965332031e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.049041748046875e-05s
INFO | --- Analysis for cap-italy-rdf took 2.1002180576324463s
Availability | SPARQL endpoint availability check for person took 8.58306884765625e-05s
Availability | VoID file availability check for person took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for person took 0.4500753879547119s
Reputation | Calculation of the PageRank for person took 0.021071910858154297s
Interlinking | Calculation of Degree of Connection for person took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for person took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for person took 3.314018249511719e-05s
Believability | Calculation of trust value for person took 7.152557373046875e-06s
INFO | --- Analysis for card took 2.26330828666687s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 8.821487426757812e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 1.3236560821533203s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020873308181762695s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.076957702636719e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.1205673217773438e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 4.736283540725708s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 0.26834845542907715s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.39896535873413086s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.024379730224609375s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.5762786865234375e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 1.2159347534179688e-05s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 6.141842603683472s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.5177414417266846s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0006299018859863281s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 101.41297435760498s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9416742324829102s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.763187408447266s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.106303215026855s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.21393179893494s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.1350595951080322s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.2981429100036621s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 8.31272029876709s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.35013604164123535s
License | MR license check for Norway catch records dataset @PSNC took 0.8175656795501709s
License | HR license check for Norway catch records dataset @PSNC took 300.2104606628418s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.22037911415100098s
Understandability | Number of label check for Norway catch records dataset @PSNC took 1.9072637557983398s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.6876564025878906s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.3190932273864746s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.2040567398071289s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.23153901100158691s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.60364556312561s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 9.369850158691406e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.18288898468017578s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.1840672492980957s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.49196338653564453s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.45577192306518555s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 4.929830074310303s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.46605420112609863s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.22945666313171387s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 150.7112476825714s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.1941540241241455s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.32666993141174316s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.3527548313140869s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 39.74287486076355s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.6830925941467285s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.6431753635406494s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.1860804557800293s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 85.67837333679199s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.369960069656372s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 32.42805051803589s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.3992855548858643s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 87.2116186618805s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.7720704078674316s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.531256914138794s
Security | Sign check for Norway catch records dataset @PSNC took 1.0931310653686523s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 20.399468421936035s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 2.2003285884857178s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.020833492279052734s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2258.229150056839s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 8.988380432128906e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.3464329242706299s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020821332931518555s
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.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0001049041748046875s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1205673217773438e-05s
INFO | --- Analysis for ce4r took 22.452547311782837s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.394345760345459s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005764961242675781s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.1532528400421143s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.893589973449707s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3194255828857422s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6644468307495117s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.141035318374634s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16153693199157715s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.32332301139831543s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1987473964691162s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2300279140472412s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2717559337615967s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3549215793609619s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16622495651245117s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2903265953063965s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3615114688873291s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15734601020812988s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21361017227172852s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18799686431884766s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.7667818069458s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 0.00010919570922851562s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24752497673034668s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14413881301879883s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 1.111992597579956s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17983508110046387s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18850326538085938s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6627776622772217s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4324042797088623s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.0494892597198486s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1548163890838623s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.33698248863220215s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.3494260311126709s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6719770431518555s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028680801391601562s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02771782875061035s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4873538017272949s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 0.41188478469848633s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.947662115097046s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.2866718769073486s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.5109467506408691s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.033121347427368164s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.19038152694702148s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18393707275390625s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2205.4349508285522s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.101424217224121s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.025382280349731445s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.267692565917969e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.1920928955078125e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.2874603271484375e-05s
INFO | --- Analysis for ceo took 2334.3045496940613s
Availability | SPARQL endpoint availability check for Charging Stations took 0.00048804283142089844s
Availability | VoID file availability check for Charging Stations took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Charging Stations took 3.7879745960235596s
Reputation | Calculation of the PageRank for Charging Stations took 0.020748376846313477s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.123283386230469e-05s
Believability | Calculation of trust value for Charging Stations took 1.2636184692382812e-05s
INFO | --- Analysis for charging-stations took 16.204573392868042s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.363059997558594e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 1.0332074165344238s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02324533462524414s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.62396240234375e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.2636184692382812e-05s
INFO | --- Analysis for chat-game-corpus took 17.260602235794067s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 2.2935893535614014s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.4363114833831787s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020769357681274414s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.910064697265625e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 1.1920928955078125e-05s
INFO | --- Analysis for chebi took 12.65525197982788s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.506111145019531e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 4.192935943603516s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.022899389266967773s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.698204040527344e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.2874603271484375e-05s
INFO | --- Analysis for chem2bio2rdf took 15.89698052406311s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.3995232582092285s
Availability | VoID file availability check for ChEMBL RDF took 0.08675932884216309s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 4.720703363418579s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.125999450683594e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.1920928955078125e-05s
INFO | --- Analysis for chembl-rdf took 17.84683585166931s
Availability | SPARQL endpoint availability check for chemdb  dataset took 2.273286819458008s
Availability | VoID file availability check for chemdb  dataset took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.5947263240814209s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.02091217041015625s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 6.580352783203125e-05s
Believability | Calculation of trust value for chemdb  dataset took 1.1920928955078125e-05s
INFO | --- Analysis for chemdb-basicInfo took 13.480633974075317s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 2.8850066661834717s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.3534722328186035s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 4.172325134277344e-05s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 7.850430727005005s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 2.2104082107543945s
Availability | VoID file availability check for chemdb phase transition dataset took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.3526468276977539s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.020612239837646484s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.2159347534179688e-05s
INFO | --- Analysis for chemdb-phaseTransition took 9.367838382720947s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 2.2087161540985107s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 1.9835529327392578s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 5.3882598876953125e-05s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-thermochemistry took 6.592339515686035s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 9.012222290039062e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0007812976837158203s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 1.5552685260772705s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020833492279052734s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.123283386230469e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.2159347534179688e-05s
INFO | --- Analysis for chempedia-rdf took 13.88100790977478s
Availability | SPARQL endpoint availability check for Chiman Maru took 8.869171142578125e-05s
Availability | VoID file availability check for Chiman Maru took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.38896822929382324s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.0040740966796875e-05s
Believability | Calculation of trust value for Chiman Maru took 1.2636184692382812e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 7.5103349685668945s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.9390721321106s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.000762939453125s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.8109796047210693s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02133798599243164s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.3392181396484375e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.3589859008789062e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 536.7744934558868s
Availability | SPARQL endpoint availability check for Chronicling America took 8.749961853027344e-05s
Availability | VoID file availability check for Chronicling America took 0.0009000301361083984s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.37352561950683594s
Reputation | Calculation of the PageRank for Chronicling America took 0.020795106887817383s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010967254638671875s
Believability | Calculation of trust value for Chronicling America took 1.2159347534179688e-05s
INFO | --- Analysis for chronicling-america took 253.86266613006592s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.5540854930877686s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0005588531494140625s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 78.63660907745361s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.5044794082641602s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 2.6280717849731445s
Interoperability | New terms check for Cultural Heritage Thesaurus took 3.5999789237976074s
Versatility | Languages check for Cultural Heritage Thesaurus took 7.113658905029297s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 1.9176123142242432s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3374154567718506s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.3326735496520996s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 6.273053169250488s
License | MR license check for Cultural Heritage Thesaurus took 0.33937525749206543s
License | HR license check for Cultural Heritage Thesaurus took 0.6277837753295898s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.2828342914581299s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.38779664039611816s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5598366260528564s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.29351162910461426s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.3138546943664551s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.28572607040405273s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.905178308486938s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 0.00011491775512695312s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2898287773132324s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.30533576011657715s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.35922861099243164s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.33143186569213867s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.30323100090026855s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6425156593322754s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6123392581939697s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 25.492080688476562s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 3.014788866043091s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.29651331901550293s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.2878875732421875s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.29827213287353516s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 6.729734182357788s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.222822904586792s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3333134651184082s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 4.935550212860107s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.2729530334472656s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 8.255652904510498s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 3.5244345664978027s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.000156402587890625s
Security | Sign check for Cultural Heritage Thesaurus took 0.3125951290130615s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 363.66223669052124s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 1.0313091278076172s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.0213925838470459s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00010395050048828125s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.436992883682251s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for cht took 579.6257259845734s
Availability | SPARQL endpoint availability check for ciard-ring took 8.916854858398438e-05s
Availability | VoID file availability check for ciard-ring took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.29547810554504395s
Reputation | Calculation of the PageRank for ciard-ring took 0.023317575454711914s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0009958744049072266s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 6.175041198730469e-05s
Believability | Calculation of trust value for ciard-ring took 1.1682510375976562e-05s
INFO | --- Analysis for ciard-ring took 12.179278135299683s
Availability | SPARQL endpoint availability check for Cine Figure took 8.678436279296875e-05s
Availability | VoID file availability check for Cine Figure took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.29822540283203125s
Reputation | Calculation of the PageRank for Cine Figure took 0.02167367935180664s
Interlinking | Calculation of Degree of Connection for Cine Figure took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.5299530029296875e-05s
Believability | Calculation of trust value for Cine Figure took 6.9141387939453125e-06s
INFO | --- Analysis for Cine_Figure took 2.372722864151001s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 0.4039139747619629s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.6928956508636475s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.8160552978515625e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 6.069795608520508s
Availability | SPARQL endpoint availability check for CIPFA took 8.988380432128906e-05s
Availability | VoID file availability check for CIPFA took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for CIPFA took 0.31159067153930664s
Reputation | Calculation of the PageRank for CIPFA took 0.021445512771606445s
Interlinking | Calculation of Degree of Connection for CIPFA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.314018249511719e-05s
Believability | Calculation of trust value for CIPFA took 8.821487426757812e-06s
INFO | --- Analysis for cipfa took 5.229862689971924s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 4.084407091140747s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.33273935317993164s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.021571636199951172s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00040531158447265625s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.2636184692382812e-05s
INFO | --- Analysis for ckan took 20.88636612892151s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5542430877685547s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0016272068023682s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.021065711975097656s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for CLaSSES took 7.170240879058838s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 8.797645568847656e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.5242905616760254s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02168750762939453s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.3855438232421875e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.2159347534179688e-05s
INFO | --- Analysis for classical_temples took 8.75457763671875s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 0.7898075580596924s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 2.2612719535827637s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.021404504776000977s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.177757263183594e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 5.0067901611328125e-06s
INFO | --- Analysis for clean-energy-data-reegle took 10.237185716629028s
Availability | SPARQL endpoint availability check for CLLD-afbo took 8.869171142578125e-05s
Availability | VoID file availability check for CLLD-afbo took 0.481640100479126s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 4.574511289596558s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 8.96453857421875e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-afbo took 2.6226043701171875e-06s
Believability | Calculation of trust value for CLLD-afbo took 7.152557373046875e-06s
INFO | --- Analysis for clld-afbo took 15.247189044952393s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.3392181396484375e-05s
Availability | VoID file availability check for CLLD-APICS took 0.4637265205383301s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 1.3891713619232178s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 8.082389831542969e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-APICS took 2.384185791015625e-06s
Believability | Calculation of trust value for CLLD-APICS took 1.1682510375976562e-05s
INFO | --- Analysis for clld-apics took 8.771761178970337s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.3392181396484375e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.4785141944885254s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.4768190383911133s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-EWAVE took 2.86102294921875e-06s
Believability | Calculation of trust value for CLLD-EWAVE took 1.1444091796875e-05s
INFO | --- Analysis for clld-ewave took 5.472255229949951s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 8.535385131835938e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.4660065174102783s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.3962900638580322s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00012993812561035156s
Interoperability | Check the re-using of existing vocabs for CLLD-GLOTTOLOG took 1.6689300537109375e-06s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.0967254638671875e-05s
INFO | --- Analysis for clld-glottolog took 4.788325309753418s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 8.58306884765625e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.4623086452484131s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.3082010746002197s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020175933837890625s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.82012939453125e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-PHOIBLE took 1.9073486328125e-06s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.239776611328125e-05s
INFO | --- Analysis for clld-phoible took 4.167668342590332s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.3392181396484375e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.5083246231079102s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 1.151637315750122s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.021500825881958008s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.677078247070312e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-SAILS took 2.384185791015625e-06s
Believability | Calculation of trust value for CLLD-SAILS took 6.67572021484375e-06s
INFO | --- Analysis for clld-sails took 16.784093379974365s
Availability | SPARQL endpoint availability check for CLLD-WALS took 0.00016045570373535156s
Availability | VoID file availability check for CLLD-WALS took 0.4809684753417969s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.6785345077514648s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.021583080291748047s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.797645568847656e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WALS took 2.86102294921875e-06s
Believability | Calculation of trust value for CLLD-WALS took 7.152557373046875e-06s
INFO | --- Analysis for clld-wals took 7.243796110153198s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 6.365776062011719e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.44689321517944336s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 1.7331140041351318s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.677078247070312e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WOLD took 2.6226043701171875e-06s
Believability | Calculation of trust value for CLLD-WOLD took 9.298324584960938e-06s
INFO | --- Analysis for clld-wold took 6.6653406620025635s
Availability | SPARQL endpoint availability check for COD inventory took 0.278151273727417s
Availability | VoID file availability check for COD inventory took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for COD inventory took 0.3127319812774658s
Reputation | Calculation of the PageRank for COD inventory took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.314018249511719e-05s
Believability | Calculation of trust value for COD inventory took 6.67572021484375e-06s
INFO | --- Analysis for cod-inventory took 4.9221320152282715s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.2616133689880371s
Availability | VoID file availability check for Cooperation Databank took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.4783940315246582s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02230048179626465s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0008494853973388672s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 4.172325134277344e-05s
Believability | Calculation of trust value for Cooperation Databank took 7.152557373046875e-06s
INFO | --- Analysis for CoDa took 6.821837663650513s
Availability | SPARQL endpoint availability check for CODE Endpoint took 391.8680148124695s
Availability | VoID file availability check for CODE Endpoint took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 7.968940258026123s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.021164894104003906s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 4.124641418457031e-05s
Believability | Calculation of trust value for CODE Endpoint took 7.867813110351562e-06s
INFO | --- Analysis for code-endpoint took 542.333954334259s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.9391880035400391s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 4.633550405502319s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02071690559387207s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 2.9325485229492188e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 5.245208740234375e-06s
INFO | --- Analysis for coins-openuplabs took 25.59706449508667s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.1711506843566895s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 1.0183589458465576s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02160334587097168s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.702278137207031e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 7.62939453125e-06s
INFO | --- Analysis for CoLChina_sp2000 took 12.67028284072876s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.05839848518371582s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.49657535552978516s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.9577484130859375e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for colinda took 5.242910385131836s
Availability | SPARQL endpoint availability check for CN  2012 took 27.017653465270996s
Availability | VoID file availability check for CN  2012 took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for CN  2012 took 1.1256787776947021s
Reputation | Calculation of the PageRank for CN  2012 took 0.022356510162353516s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.458427429199219e-05s
Believability | Calculation of trust value for CN  2012 took 5.4836273193359375e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 113.96346068382263s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.18719220161438s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0006744861602783203s
Extra | Recovery of all triples for Comments on Literature in Literature (CoLiL) took 135.76011204719543s
Performance | Total latancy measurement for Comments on Literature in Literature (CoLiL) took 8.107712507247925s
Amount of data | Number of triples check for Comments on Literature in Literature (CoLiL) took 195.3883752822876s
Interoperability | New terms check for Comments on Literature in Literature (CoLiL) took 130.80678009986877s
Versatility | Languages check for Comments on Literature in Literature (CoLiL) took 301.4556293487549s
Interpretability | Number of blank nodes check for Comments on Literature in Literature (CoLiL) took 238.00977873802185s
Security | Check HTTPS for Comments on Literature in Literature (CoLiL) took 1.12691330909729s
Interpretability | RDF structures check for Comments on Literature in Literature (CoLiL) took 1.8169686794281006s
Versatility | Serialization formats check for Comments on Literature in Literature (CoLiL) took 1.7344565391540527s
Availability | RDF dump link check for Comments on Literature in Literature (CoLiL) took 1.6253294944763184s
License | MR license check for Comments on Literature in Literature (CoLiL) took 1.7776291370391846s
License | HR license check for Comments on Literature in Literature (CoLiL) took 1.8152291774749756s
Amount of data | Number of property check for Comments on Literature in Literature (CoLiL) took 1.6676256656646729s
Understandability | Number of label check for Comments on Literature in Literature (CoLiL) took 1.9418444633483887s
Understandability | URI regex check for Comments on Literature in Literature (CoLiL) took 3.310166597366333s
Understandability | Vocabs check for Comments on Literature in Literature (CoLiL) took 1.683258295059204s
Verifiability | Authors check for Comments on Literature in Literature (CoLiL) took 1.7389609813690186s
Verifiability | Publishers check for Comments on Literature in Literature (CoLiL) took 1.6746735572814941s
Performance | Throughput check for Comments on Literature in Literature (CoLiL) took 17.463451623916626s
Amount of data | Check the number of entities for Comments on Literature in Literature (CoLiL) took 0.00011968612670898438s
Verifiability | Contribs. check for Comments on Literature in Literature (CoLiL) took 1.6396636962890625s
Interlinking | sameAs chians check for Comments on Literature in Literature (CoLiL) took 1.636340856552124s
Interlinking | skos check for Comments on Literature in Literature (CoLiL) took 2.7303988933563232s
Interlinking | skos check for Comments on Literature in Literature (CoLiL) took 2.1223185062408447s
Timeliness | dataset update frequency check for Comments on Literature in Literature (CoLiL) took 1.7876005172729492s
Currency | Creation date check for Comments on Literature in Literature (CoLiL) took 3.570728302001953s
Currency | Modification date check for Comments on Literature in Literature (CoLiL) took 3.2782628536224365s
Rep.Conc. | URIs length for Comments on Literature in Literature (CoLiL) took 480.01464009284973s
Interoperability | New vocabularies check for Comments on Literature in Literature (CoLiL) took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Comments on Literature in Literature (CoLiL) took 1.677086591720581s
Accuracy | Check Functional Property for Comments on Literature in Literature (CoLiL) took 1.6840622425079346s
Accuracy | Check Inverse Functional Property for Comments on Literature in Literature (CoLiL) took 1.6543138027191162s
Accuracy | Check Empty annotation labels for Comments on Literature in Literature (CoLiL) took 2.403837203979492s
Accuracy | Check White space in annotation for Comments on Literature in Literature (CoLiL) took 0.0019023418426513672s
Accuracy | Check Datatype consistency for Comments on Literature in Literature (CoLiL) took 2.6597955226898193s
Consistency | Disjoint class check for Comments on Literature in Literature (CoLiL) took 1.659759521484375s
Consistency | Check Misplaced properties for Comments on Literature in Literature (CoLiL) took 303.09842920303345s
Consistency | Misplaced classes for Comments on Literature in Literature (CoLiL) took 10.702563762664795s
Consistency | Check Ontology hijacking for Comments on Literature in Literature (CoLiL) took 35.77067589759827s
Consistency | Check Invalid usage of undefined classes for Comments on Literature in Literature (CoLiL) took 1.2617199420928955s
Consistency | Check Invalid usage of undefined properties for Comments on Literature in Literature (CoLiL) took 302.77554750442505s
Conciseness | Check Extensional conciseness for Comments on Literature in Literature (CoLiL) took 2.774437427520752s
Conciseness | Check Intensional conciseness for Comments on Literature in Literature (CoLiL) took 2.241610288619995s
Security | Sign check for Comments on Literature in Literature (CoLiL) took 2.5537874698638916s
Availability | Check URIs Dereferenciability for Comments on Literature in Literature (CoLiL) took 11.630173921585083s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 48.466259479522705s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.021402597427368164s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Comments on Literature in Literature (CoLiL) took 2.384185791015625e-06s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 1.1205673217773438e-05s
INFO | --- Analysis for comments-on-literature-in-literature took 3505.88747882843s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 9.179115295410156e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.34643054008483887s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.023367881774902344s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 4.00543212890625e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 1.33514404296875e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 56.78618407249451s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 8.988380432128906e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.4635810852050781s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.0517578125e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 1.1920928955078125e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 14.681246280670166s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 5.984306335449219e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.4438443183898926s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 3.2901763916015625e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 1.1920928955078125e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 66.3085708618164s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 9.059906005859375e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0007593631744384766s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.3271002769470215s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.021184444427490234s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 4.00543212890625e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 1.33514404296875e-05s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 34.353747606277466s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.5603387355804443s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0003883838653564453s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.5179917812347412s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for CompHistSem took 3.644580841064453s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 0.20203566551208496s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 3.382524013519287s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.933906555175781e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.239776611328125e-05s
INFO | --- Analysis for comsode-d3-2 took 7.373636245727539s
Availability | SPARQL endpoint availability check for ConceptNet took 0.00010395050048828125s
Availability | VoID file availability check for ConceptNet took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.47610950469970703s
Reputation | Calculation of the PageRank for ConceptNet took 0.021558284759521484s
Interlinking | Calculation of Degree of Connection for ConceptNet took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.7894973754882812e-05s
Believability | Calculation of trust value for ConceptNet took 1.1205673217773438e-05s
INFO | --- Analysis for conceptnet took 8.537928342819214s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.4345855712890625e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.4265315532684326s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.0214536190032959s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.392333984375e-05s
Believability | Calculation of trust value for 2011 US Congress People took 9.775161743164062e-06s
INFO | --- Analysis for congresspeople took 3.210700035095215s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 1.7074387073516846s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.30559754371643066s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.021860837936401367s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.0517578125e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for connectivity-of-lod-datasets took 31.674912929534912s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.11117744445800781s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.32158541679382324s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.2901763916015625e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.2159347534179688e-05s
INFO | --- Analysis for copac-library-catalogue took 1.9311254024505615s
Availability | SPARQL endpoint availability check for Copyright Free Music took 0.00010251998901367188s
Availability | VoID file availability check for Copyright Free Music took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.5854325294494629s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020943403244018555s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.8371810913085938e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.1205673217773438e-05s
INFO | --- Analysis for Copyright_Free_Music took 8.004449844360352s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 9.250640869140625e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.5866756439208984s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.02084064483642578s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.842613220214844e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.1920928955078125e-05s
INFO | --- Analysis for copyrighttermbank took 34.66280245780945s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.7104945182800293s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.33335232734680176s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.910064697265625e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.1682510375976562e-05s
INFO | --- Analysis for core took 14.684043407440186s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.34911155700683594s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005071163177490234s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 98.65045166015625s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9923703670501709s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.419053554534912s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.073781728744507s
Versatility | Languages check for Corine linked dataset @PSNC took 300.2299773693085s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.1571645736694336s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.20257186889648438s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 9.85676884651184s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.30076169967651367s
License | MR license check for Corine linked dataset @PSNC took 0.6970195770263672s
License | HR license check for Corine linked dataset @PSNC took 300.25096559524536s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.2288196086883545s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.4740617275238037s
Understandability | URI regex check for Corine linked dataset @PSNC took 1.2445061206817627s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.5487291812896729s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.20218133926391602s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.23062682151794434s
Performance | Throughput check for Corine linked dataset @PSNC took 11.475963830947876s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 0.00014138221740722656s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.19951319694519043s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.19544506072998047s
Interlinking | skos check for Corine linked dataset @PSNC took 0.5027027130126953s
Interlinking | skos check for Corine linked dataset @PSNC took 0.43579745292663574s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.700538158416748s
Currency | Creation date check for Corine linked dataset @PSNC took 0.5061986446380615s
Currency | Modification date check for Corine linked dataset @PSNC took 0.23781108856201172s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 148.09999132156372s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.2115335464477539s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.35962653160095215s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.36301159858703613s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 34.113388776779175s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.662569761276245s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.65293288230896s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.19756007194519043s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 86.32810187339783s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.321538925170898s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 28.88473653793335s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.4734468460083008s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 86.86641454696655s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.756782293319702s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.49013400077819824s
Security | Sign check for Corine linked dataset @PSNC took 1.076490879058838s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 10.457847356796265s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.8358132839202881s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021227121353149414s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.4066696166992188e-05s
INFO | --- Analysis for Corine_linked_dataset took 2230.4891510009766s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 9.298324584960938e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.3013317584991455s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.933906555175781e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.1682510375976562e-05s
INFO | --- Analysis for corn took 94.80052447319031s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00013709068298339844s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.3206329345703125s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.337860107421875e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 1.1920928955078125e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 40.86368370056152s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 8.654594421386719e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.2990438938140869s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.022330284118652344s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.8848648071289062e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.239776611328125e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 38.02848482131958s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 8.654594421386719e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.49066686630249023s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.8650970458984375e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.049041748046875e-05s
INFO | --- Analysis for cornetto took 16.75795865058899s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.1469430923461914s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005676746368408203s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 172.37829780578613s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.593336820602417s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 44.9781928062439s
Interoperability | New terms check for Corporate Body Named Authority List  took 52.552916288375854s
Versatility | Languages check for Corporate Body Named Authority List  took 300.1229929924011s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 55.49531030654907s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.36324357986450195s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.5482113361358643s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 2.6975066661834717s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.1859288215637207s
License | MR license check for Corporate Body Named Authority List  took 0.4899148941040039s
License | HR license check for Corporate Body Named Authority List  took 300.04558992385864s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.1633608341217041s
Understandability | Number of label check for Corporate Body Named Authority List  took 1.6050519943237305s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.4051799774169922s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.1448664665222168s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.26165008544921875s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.13488435745239258s
Performance | Throughput check for Corporate Body Named Authority List  took 10.600411415100098s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 4.839897155761719e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.11992502212524414s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 6.085431814193726s
Interlinking | skos check for Corporate Body Named Authority List  took 0.1554393768310547s
Interlinking | skos check for Corporate Body Named Authority List  took 0.31685376167297363s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.312241792678833s
Currency | Creation date check for Corporate Body Named Authority List  took 0.3058967590332031s
Currency | Modification date check for Corporate Body Named Authority List  took 0.1540360450744629s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 420.0554552078247s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.1832258701324463s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.16703081130981445s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.1817774772644043s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 38.11454653739929s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.093351364135742s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6424922943115234s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.15207719802856445s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 294.31912183761597s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.514695644378662s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 52.237972259521484s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 2.019832134246826s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 294.51212096214294s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.057115316390991s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.36385297775268555s
Security | Sign check for Corporate Body Named Authority List  took 0.2057497501373291s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 11.197267770767212s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.4275531768798828s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.034700870513916016s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.6743621826171875e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.1920928955078125e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.33514404296875e-05s
INFO | --- Analysis for corporate-body took 12463.190783500671s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.5894787311553955s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.4265756607055664s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 4.553794860839844e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for CorpusFibonacci took 4.401069402694702s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.2089219093322754s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 1.5447039604187012s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.02286219596862793s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for corscheck took 3.803893804550171s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.11777186393737793s
Availability | VoID file availability check for Country Name Authority List took 0.0006880760192871094s
Extra | Recovery of all triples for Country Name Authority List took 193.414489030838s
Performance | Total latancy measurement for Country Name Authority List took 0.621453046798706s
Amount of data | Number of triples check for Country Name Authority List took 37.252845287323s
Interoperability | New terms check for Country Name Authority List took 52.00583744049072s
Versatility | Languages check for Country Name Authority List took 300.0539319515228s
Interpretability | Number of blank nodes check for Country Name Authority List took 13.652227401733398s
Security | Check HTTPS for Country Name Authority List took 0.3683948516845703s
Interpretability | RDF structures check for Country Name Authority List took 0.2802257537841797s
Versatility | Serialization formats check for Country Name Authority List took 3.3686797618865967s
Availability | RDF dump link check for Country Name Authority List took 0.29247379302978516s
License | MR license check for Country Name Authority List took 0.3879265785217285s
License | HR license check for Country Name Authority List took 300.104896068573s
Amount of data | Number of property check for Country Name Authority List took 0.16457867622375488s
Understandability | Number of label check for Country Name Authority List took 1.620063304901123s
Understandability | URI regex check for Country Name Authority List took 0.3420064449310303s
Understandability | Vocabs check for Country Name Authority List took 0.1625654697418213s
Verifiability | Authors check for Country Name Authority List took 0.13025188446044922s
Verifiability | Publishers check for Country Name Authority List took 0.20555591583251953s
Performance | Throughput check for Country Name Authority List took 10.639463663101196s
Amount of data | Check the number of entities for Country Name Authority List took 7.224082946777344e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.33339762687683105s
Interlinking | sameAs chians check for Country Name Authority List took 6.117235422134399s
Interlinking | skos check for Country Name Authority List took 0.34754490852355957s
Interlinking | skos check for Country Name Authority List took 0.14854192733764648s
Timeliness | dataset update frequency check for Country Name Authority List took 0.22821044921875s
Currency | Creation date check for Country Name Authority List took 0.5425221920013428s
Currency | Modification date check for Country Name Authority List took 0.1486060619354248s
Rep.Conc. | URIs length for Country Name Authority List took 427.48896884918213s
Interoperability | New vocabularies check for Country Name Authority List took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.16728448867797852s
Accuracy | Check Functional Property for Country Name Authority List took 0.2005317211151123s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.15385127067565918s
Accuracy | Check Empty annotation labels for Country Name Authority List took 39.83998489379883s
Accuracy | Check White space in annotation for Country Name Authority List took 3.0781383514404297s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.83894681930542s
Consistency | Disjoint class check for Country Name Authority List took 0.17500996589660645s
Consistency | Check Misplaced properties for Country Name Authority List took 300.4527180194855s
Consistency | Misplaced classes for Country Name Authority List took 8.725112438201904s
Consistency | Check Ontology hijacking for Country Name Authority List took 38.621249198913574s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.7229986190795898s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 294.51075434684753s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.102144241333008s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.34318089485168457s
Security | Sign check for Country Name Authority List took 0.21563243865966797s
Availability | Check URIs Dereferenciability for Country Name Authority List took 11.146222829818726s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.7004094123840332s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.021602392196655273s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 0.00025844573974609375s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 2.6226043701171875e-06s
Believability | Calculation of trust value for Country Name Authority List took 8.58306884765625e-06s
INFO | --- Analysis for country-authority-list took 9895.670959472656s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.07140159606933594s
Availability | VoID file availability check for Courts thesaurus took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 3.568861961364746s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.021623849868774414s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.677078247070312e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for courts-thesaurus took 24.17170739173889s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.27588820457458496s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.00044274330139160156s
Extra | Recovery of all triples for Covid-on-the-Web Dataset took 2.4377574920654297s
Performance | Total latancy measurement for Covid-on-the-Web Dataset took 0.6067414283752441s
Amount of data | Number of triples check for Covid-on-the-Web Dataset took 55.466018199920654s
Interoperability | New terms check for Covid-on-the-Web Dataset took 8.71295428276062s
Versatility | Languages check for Covid-on-the-Web Dataset took 300.1581299304962s
Interpretability | Number of blank nodes check for Covid-on-the-Web Dataset took 68.64842629432678s
Interpretability | RDF structures check for Covid-on-the-Web Dataset took 0.15805506706237793s
Versatility | Serialization formats check for Covid-on-the-Web Dataset took 0.17415642738342285s
Availability | RDF dump link check for Covid-on-the-Web Dataset took 3.927340030670166s
License | MR license check for Covid-on-the-Web Dataset took 0.23936820030212402s
License | HR license check for Covid-on-the-Web Dataset took 300.08340525627136s
Amount of data | Number of property check for Covid-on-the-Web Dataset took 0.140610933303833s
Understandability | Number of label check for Covid-on-the-Web Dataset took 1.5452475547790527s
Understandability | URI regex check for Covid-on-the-Web Dataset took 0.4241299629211426s
Understandability | Vocabs check for Covid-on-the-Web Dataset took 0.1249847412109375s
Verifiability | Authors check for Covid-on-the-Web Dataset took 0.128753662109375s
Verifiability | Publishers check for Covid-on-the-Web Dataset took 0.10738587379455566s
Performance | Throughput check for Covid-on-the-Web Dataset took 10.544129371643066s
Amount of data | Check the number of entities for Covid-on-the-Web Dataset took 0.12216949462890625s
Verifiability | Contribs. check for Covid-on-the-Web Dataset took 0.15802836418151855s
Interlinking | sameAs chians check for Covid-on-the-Web Dataset took 0.11849021911621094s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.13860726356506348s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.11929917335510254s
Timeliness | dataset update frequency check for Covid-on-the-Web Dataset took 0.5750162601470947s
Currency | Creation date check for Covid-on-the-Web Dataset took 0.23076820373535156s
Currency | Modification date check for Covid-on-the-Web Dataset took 0.2536773681640625s
Rep.Conc. | URIs length for Covid-on-the-Web Dataset took 49.72111201286316s
Interoperability | New vocabularies check for Covid-on-the-Web Dataset took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for Covid-on-the-Web Dataset took 0.10610628128051758s
Accuracy | Check Functional Property for Covid-on-the-Web Dataset took 0.3675837516784668s
Accuracy | Check Inverse Functional Property for Covid-on-the-Web Dataset took 0.35757994651794434s
Accuracy | Check Empty annotation labels for Covid-on-the-Web Dataset took 1.113492727279663s
Accuracy | Check White space in annotation for Covid-on-the-Web Dataset took 0.05880141258239746s
Accuracy | Check Datatype consistency for Covid-on-the-Web Dataset took 0.08675360679626465s
Consistency | Disjoint class check for Covid-on-the-Web Dataset took 0.11795544624328613s
Consistency | Check Misplaced properties for Covid-on-the-Web Dataset took 46.22686195373535s
Consistency | Misplaced classes for Covid-on-the-Web Dataset took 1.0879249572753906s
Consistency | Check Ontology hijacking for Covid-on-the-Web Dataset took 2.508608818054199s
Consistency | Check Invalid usage of undefined classes for Covid-on-the-Web Dataset took 1.4198613166809082s
Consistency | Check Invalid usage of undefined properties for Covid-on-the-Web Dataset took 29.030813694000244s
Conciseness | Check Extensional conciseness for Covid-on-the-Web Dataset took 0.08999085426330566s
Conciseness | Check Intensional conciseness for Covid-on-the-Web Dataset took 1.3336474895477295s
Security | Sign check for Covid-on-the-Web Dataset took 0.6312224864959717s
Availability | Check URIs Dereferenciability for Covid-on-the-Web Dataset took 10.258187055587769s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 2.191413402557373s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.02416706085205078s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.000888824462890625s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 0.0001010894775390625s
Interoperability | Check the re-using of existing vocabs for Covid-on-the-Web Dataset took 6.9141387939453125e-06s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 7.62939453125e-06s
INFO | --- Analysis for Covid-on-the-Web took 8842.158074140549s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.578211069107056s
Availability | VoID file availability check for CPA 2008 took 0.0008683204650878906s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.3196117877960205s
Reputation | Calculation of the PageRank for CPA 2008 took 0.022482872009277344s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0015785694122314453s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 0.00010848045349121094s
Believability | Calculation of trust value for CPA 2008 took 6.4373016357421875e-06s
INFO | --- Analysis for cpa-2008 took 100.76434326171875s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.29749560356140137s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0003979206085205078s
Extra | Recovery of all triples for Cooperative Patent Classification took 23.434054374694824s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.609382152557373s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.1035566329956s
Versatility | Languages check for Cooperative Patent Classification took 120.10019993782043s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.19194316864014s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.14856266975402832s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.11455845832824707s
Availability | RDF dump link check for Cooperative Patent Classification took 0.13540387153625488s
License | MR license check for Cooperative Patent Classification took 0.10283946990966797s
License | HR license check for Cooperative Patent Classification took 90.12120819091797s
Amount of data | Number of property check for Cooperative Patent Classification took 0.1730349063873291s
Understandability | Number of label check for Cooperative Patent Classification took 90.1271185874939s
Understandability | URI regex check for Cooperative Patent Classification took 0.25594449043273926s
Understandability | Vocabs check for Cooperative Patent Classification took 0.1329941749572754s
Verifiability | Authors check for Cooperative Patent Classification took 0.1341707706451416s
Verifiability | Publishers check for Cooperative Patent Classification took 0.15043997764587402s
Performance | Throughput check for Cooperative Patent Classification took 10.705007314682007s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.486343383789062e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.11444711685180664s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.10681772232055664s
Interlinking | skos check for Cooperative Patent Classification took 0.15468716621398926s
Interlinking | skos check for Cooperative Patent Classification took 0.12853145599365234s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.11798882484436035s
Currency | Creation date check for Cooperative Patent Classification took 0.2365131378173828s
Currency | Modification date check for Cooperative Patent Classification took 0.22082304954528809s
Rep.Conc. | URIs length for Cooperative Patent Classification took 150.11370253562927s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.12000322341918945s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 14.589472532272339s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 3.0081002712249756s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 5.15333890914917s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.13280987739562988s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.30461144447327s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 18.304717540740967s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.9580051898956299s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.95586514472961s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 3.3674278259277344s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 114.93531084060669s
Security | Sign check for Cooperative Patent Classification took 0.11910557746887207s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.068080186843872s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.6542515754699707s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.021761417388916016s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 5.435943603515625e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.9073486328125e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.2874603271484375e-05s
INFO | --- Analysis for CPC took 1388.5410287380219s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.541157960891724s
Availability | VoID file availability check for CPC 2008 took 0.0008544921875s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.4555015563964844s
Reputation | Calculation of the PageRank for CPC 2008 took 0.02164173126220703s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.696846008300781e-05s
Believability | Calculation of trust value for CPC 2008 took 1.0013580322265625e-05s
INFO | --- Analysis for cpc-2008 took 100.2274558544159s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.898651599884033s
Availability | VoID file availability check for CPV  2003 took 0.0008761882781982422s
Completeness | Calculation of interlinking completeness for CPV  2003 took 1.328395128250122s
Reputation | Calculation of the PageRank for CPV  2003 took 0.021411657333374023s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.1961669921875e-05s
Believability | Calculation of trust value for CPV  2003 took 9.5367431640625e-06s
INFO | --- Analysis for cpv-2003 took 94.63980340957642s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.525925397872925s
Availability | VoID file availability check for CPV 2008 took 0.0008547306060791016s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.433762788772583s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020948171615600586s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.435943603515625e-05s
Believability | Calculation of trust value for CPV 2008 took 8.58306884765625e-06s
INFO | --- Analysis for cpv-2008 took 99.80450654029846s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 262.264639377594s
Availability | VoID file availability check for crowdsourcing-fb took 0.0008728504180908203s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.8482904434204102s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.025007247924804688s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 5.0067901611328125e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.2636184692382812e-05s
INFO | --- Analysis for crowdsourcing-fb took 397.0657260417938s
Availability | SPARQL endpoint availability check for CRTM took 30.35795569419861s
Availability | VoID file availability check for CRTM took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for CRTM took 0.31275177001953125s
Reputation | Calculation of the PageRank for CRTM took 0.021292924880981445s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for CRTM took 4.363059997558594e-05s
Believability | Calculation of trust value for CRTM took 1.33514404296875e-05s
INFO | --- Analysis for crtm took 52.432432889938354s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 1.8865373134613037s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0009512901306152344s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.4558095932006836s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.025151968002319336s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0012416839599609375s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 4.792213439941406e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 2.2172927856445312e-05s
INFO | --- Analysis for crystal-eye took 5.3066370487213135s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.534688949584961s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0007066726684570312s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 2.665616273880005s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.024255752563476562s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0012493133544921875s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 8.225440979003906e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 1.2159347534179688e-05s
INFO | --- Analysis for ctic-public-dataset took 43.526859998703s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 8.559226989746094e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 16.036904096603394s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.02645587921142578s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.123283386230469e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 1.2874603271484375e-05s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 77.71864891052246s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 2.2941362857818604s
Availability | VoID file availability check for CulturaLinkedData took 0.0006148815155029297s
Extra | Recovery of all triples for CulturaLinkedData took 132.03510284423828s
Performance | Total latancy measurement for CulturaLinkedData took 6.474144697189331s
Amount of data | Number of triples check for CulturaLinkedData took 0.7708985805511475s
Interoperability | New terms check for CulturaLinkedData took 4.152554750442505s
Versatility | Languages check for CulturaLinkedData took 61.347259521484375s
Interpretability | Number of blank nodes check for CulturaLinkedData took 2.006455898284912s
Interpretability | RDF structures check for CulturaLinkedData took 2.2958595752716064s
Versatility | Serialization formats check for CulturaLinkedData took 0.522742509841919s
Availability | RDF dump link check for CulturaLinkedData took 2.1759488582611084s
License | MR license check for CulturaLinkedData took 2.550227403640747s
License | HR license check for CulturaLinkedData took 61.35711908340454s
Amount of data | Number of property check for CulturaLinkedData took 0.2048790454864502s
Understandability | Number of label check for CulturaLinkedData took 2.8948960304260254s
Understandability | URI regex check for CulturaLinkedData took 2.5091962814331055s
Understandability | Vocabs check for CulturaLinkedData took 2.072939872741699s
Verifiability | Authors check for CulturaLinkedData took 2.1175649166107178s
Verifiability | Publishers check for CulturaLinkedData took 0.27748560905456543s
Performance | Throughput check for CulturaLinkedData took 21.624670267105103s
Amount of data | Check the number of entities for CulturaLinkedData took 6.842613220214844e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.27849674224853516s
Interlinking | sameAs chians check for CulturaLinkedData took 2.0208446979522705s
Interlinking | skos check for CulturaLinkedData took 2.334459066390991s
Interlinking | skos check for CulturaLinkedData took 2.0703084468841553s
Timeliness | dataset update frequency check for CulturaLinkedData took 2.210391044616699s
Currency | Creation date check for CulturaLinkedData took 0.49381327629089355s
Currency | Modification date check for CulturaLinkedData took 4.001622676849365s
Rep.Conc. | URIs length for CulturaLinkedData took 57.106290340423584s
Interoperability | New vocabularies check for CulturaLinkedData took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 2.024535894393921s
Accuracy | Check Functional Property for CulturaLinkedData took 2.08017635345459s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.22861361503601074s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 43.58359241485596s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6192548274993896s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.340601921081543s
Consistency | Disjoint class check for CulturaLinkedData took 0.23419880867004395s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.166626691818237s
Consistency | Misplaced classes for CulturaLinkedData took 6.093041181564331s
Consistency | Check Ontology hijacking for CulturaLinkedData took 57.58862614631653s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3512208461761475s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 11.436436653137207s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.4463012218475342s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.19061565399169922s
Security | Sign check for CulturaLinkedData took 0.8907322883605957s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 10.37641453742981s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 38.12627387046814s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.02268671989440918s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0012331008911132812s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.384185791015625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 7.152557373046875e-06s
INFO | --- Analysis for culturalinkeddata took 728.4724757671356s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.171705961227417s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.4038879871368408s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.02094292640686035s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.076957702636719e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ares-or took 2.164410352706909s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11304926872253418s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.32431936264038086s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02979445457458496s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0012454986572265625s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.245208740234375e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.298324584960938e-06s
INFO | --- Analysis for cz-ares-rzp took 2.185786724090576s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11365199089050293s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.8464889526367188s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.021260738372802734s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.719329833984375e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 1.0967254638671875e-05s
INFO | --- Analysis for cz-cenia-irz-chemicals took 4.476006031036377s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.12027311325073242s
Availability | VoID file availability check for Integrated pollution registry took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.5226442813873291s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.933906555175781e-05s
Believability | Calculation of trust value for Integrated pollution registry took 1.239776611328125e-05s
INFO | --- Analysis for cz-cenia-pollution took 4.450950860977173s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.11132621765136719s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.31769371032714844s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.023749351501464844s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0012586116790771484s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 5.626678466796875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 7.319450378417969e-05s
INFO | --- Analysis for cz-contracts took 2.2414023876190186s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 0.08488845825195312s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.3159067630767822s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.02686619758605957s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0014247894287109375s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 5.125999450683594e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for cz-courts took 2.0477304458618164s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.11413073539733887s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0008258819580078125s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.3214383125305176s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.4809112548828125e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 9.775161743164062e-06s
INFO | --- Analysis for cz-ctia-bans took 10.352757692337036s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10859322547912598s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.4066901206970215s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.026756763458251953s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0013060569763183594s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 5.2928924560546875e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 9.5367431640625e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.452172040939331s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11808252334594727s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0007781982421875s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.29460787773132324s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.028197050094604492s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.001504659652709961s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 6.341934204101562e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 1.049041748046875e-05s
INFO | --- Analysis for cz-ctia-focus took 2.0775930881500244s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.12612509727478027s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0007672309875488281s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.40772366523742676s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.02625107765197754s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0011296272277832031s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 5.14984130859375e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 1.0728836059570312e-05s
INFO | --- Analysis for cz-ctia-inspections took 2.534654378890991s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.12451291084289551s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0009281635284423828s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.32387638092041016s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.0210726261138916s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.886222839355469e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 8.344650268554688e-06s
INFO | --- Analysis for cz-ctia-sanctions took 9.469786405563354s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.1715397834777832s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.3159019947052002s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.001041412353515625s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.3392181396484375e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 9.059906005859375e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.471158504486084s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.11676025390625s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.3019435405731201s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.5762786865234375e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 1.0251998901367188e-05s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.7371363639831543s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.5399537086486816s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.33221912384033203s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.021754741668701172s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.076957702636719e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.000718832015991s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3664131164550781s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.32698583602905273s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.021076202392578125s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0011599063873291016s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 5.078315734863281e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 1.3828277587890625e-05s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 2.560019016265869s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3596506118774414s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.31014204025268555s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.03143906593322754s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0013966560363769531s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 6.29425048828125e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 2.731462240219116s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.3553924560546875s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.318636417388916s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.886222839355469e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-czso-job-applicants took 2.736330986022949s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.3652219772338867s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.33704566955566406s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.021207094192504883s
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.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.1484832763671875e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 2.7727670669555664s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.35712409019470215s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0013585090637207031s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.30345654487609863s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0207827091217041s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.886222839355469e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-regions took 2.2886667251586914s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.35352158546447754s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.29934072494506836s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.02093672752380371s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 2.6115314960479736s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.36832523345947266s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.32392358779907227s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.021531105041503906s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.1484832763671875e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 1.0251998901367188e-05s
INFO | --- Analysis for cz-czso-social-service-facilities took 2.792541027069092s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.35689258575439453s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.32648539543151855s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.024835586547851562s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0012798309326171875s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 5.364418029785156e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 1.0967254638671875e-05s
INFO | --- Analysis for cz-czso-unemployment-rate took 2.49819278717041s
Availability | SPARQL endpoint availability check for ATC groups took 0.11833786964416504s
Availability | VoID file availability check for ATC groups took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for ATC groups took 0.31355714797973633s
Reputation | Calculation of the PageRank for ATC groups took 0.02686905860900879s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0013260841369628906s
Interlinking | Calculation of Clustering coefficient for ATC groups took 9.894371032714844e-05s
Believability | Calculation of trust value for ATC groups took 1.52587890625e-05s
INFO | --- Analysis for cz-eh-1-atc took 2.2056148052215576s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10962343215942383s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.4325556755065918s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020827531814575195s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.9577484130859375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 9.775161743164062e-06s
INFO | --- Analysis for cz-fulfillments took 3.4596669673919678s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.038869380950927734s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.30008935928344727s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.0211942195892334s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.9114227294921875e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ic took 2.757359743118286s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.1211698055267334s
Availability | VoID file availability check for List of Czech data boxes took 0.25853681564331055s
Extra | Recovery of all triples for List of Czech data boxes took 139.77304363250732s
Performance | Total latancy measurement for List of Czech data boxes took 0.583669900894165s
Amount of data | Number of triples check for List of Czech data boxes took 11.046684503555298s
Interoperability | New terms check for List of Czech data boxes took 11.000355243682861s
Versatility | Languages check for List of Czech data boxes took 300.18546748161316s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.4848804473876953s
Interpretability | RDF structures check for List of Czech data boxes took 0.17405438423156738s
Versatility | Serialization formats check for List of Czech data boxes took 0.17603754997253418s
Availability | RDF dump link check for List of Czech data boxes took 17.00895047187805s
License | MR license check for List of Czech data boxes took 0.4726600646972656s
License | HR license check for List of Czech data boxes took 53.95294237136841s
Amount of data | Number of property check for List of Czech data boxes took 0.12111592292785645s
Understandability | Number of label check for List of Czech data boxes took 1.7007660865783691s
Understandability | URI regex check for List of Czech data boxes took 0.49053001403808594s
Understandability | Vocabs check for List of Czech data boxes took 0.12702202796936035s
Verifiability | Authors check for List of Czech data boxes took 0.2610008716583252s
Verifiability | Publishers check for List of Czech data boxes took 0.11474061012268066s
Performance | Throughput check for List of Czech data boxes took 10.826208353042603s
Amount of data | Check the number of entities for List of Czech data boxes took 3.16837739944458s
Verifiability | Contribs. check for List of Czech data boxes took 0.14407038688659668s
Interlinking | sameAs chians check for List of Czech data boxes took 0.3031325340270996s
Interlinking | skos check for List of Czech data boxes took 0.1810159683227539s
Interlinking | skos check for List of Czech data boxes took 0.1254746913909912s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.298722505569458s
Currency | Creation date check for List of Czech data boxes took 0.5510399341583252s
Currency | Modification date check for List of Czech data boxes took 0.11064720153808594s
Rep.Conc. | URIs length for List of Czech data boxes took 109.91633009910583s
Interoperability | New vocabularies check for List of Czech data boxes took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.532630443572998s
Accuracy | Check Functional Property for List of Czech data boxes took 0.19473791122436523s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.1650252342224121s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 30.62030005455017s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.1904454231262207s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.9326696395874023s
Consistency | Disjoint class check for List of Czech data boxes took 0.1210930347442627s
Consistency | Check Misplaced properties for List of Czech data boxes took 67.14596056938171s
Consistency | Misplaced classes for List of Czech data boxes took 7.8420538902282715s
Consistency | Check Ontology hijacking for List of Czech data boxes took 31.182246446609497s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.4599432945251465s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 60.69474720954895s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.6710124015808105s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.3623466491699219s
Security | Sign check for List of Czech data boxes took 0.15328693389892578s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 422.89622473716736s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.5424108505249023s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.02704620361328125s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0013549327850341797s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 6.628036499023438e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 3.0994415283203125e-06s
Believability | Calculation of trust value for List of Czech data boxes took 9.059906005859375e-06s
INFO | --- Analysis for cz-list-of-databoxes took 1634.1344978809357s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12285852432250977s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.269573450088501s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 137.13977575302124s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5968978404998779s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.853884220123291s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 11.112765550613403s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.17961597442627s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3149423599243164s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14637184143066406s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.20468640327453613s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 15.476009607315063s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4215421676635742s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 54.240805864334106s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12069845199584961s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4519710540771484s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.44835758209228516s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12936043739318848s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1248626708984375s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12331390380859375s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.691047430038452s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.319608211517334s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1266028881072998s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.29805779457092285s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.18296456336975098s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12964487075805664s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.22058844566345215s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.24730157852172852s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10907149314880371s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 105.52147197723389s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3828277587890625e-05s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.49573636054992676s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1814420223236084s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11156368255615234s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 30.083014249801636s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.1556992530822754s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.806365728378296s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13132047653198242s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 65.14032101631165s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.88985013961792s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.08476424217224s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.554250717163086s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 59.90833020210266s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.7872424125671387s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3868532180786133s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1351485252380371s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 421.6435945034027s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3460218906402588s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.02399301528930664s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.001264810562133789s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 6.413459777832031e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.384185791015625e-06s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.1682510375976562e-05s
INFO | --- Analysis for cz-nace took 1607.5259428024292s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.591435432434082s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0008344650268554688s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 410.2924964427948s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8206624984741211s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.35176730155944824s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.0047543048858643s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 100.33964252471924s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6527414321899414s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.432051658630371s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.208226203918457s
