Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 9.202957153320312e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.42528200149536133s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.4238619804382324s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0003573894500732422s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.1920928955078125e-05s
INFO | --- Analysis for 0080-3626 took 5.802921295166016s
Availability | SPARQL endpoint availability check for 土地利用图 took 9.131431579589844e-05s
Availability | VoID file availability check for 土地利用图 took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.32806921005249023s
Reputation | Calculation of the PageRank for 土地利用图 took 0.019913196563720703s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 2.8848648071289062e-05s
Believability | Calculation of trust value for 土地利用图 took 1.2636184692382812e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 3.1041829586029053s
Availability | SPARQL endpoint availability check for 113322 took 6.175041198730469e-05s
Availability | VoID file availability check for 113322 took 0.0015692710876464844s
Completeness | Calculation of interlinking completeness for 113322 took 0.31542444229125977s
Reputation | Calculation of the PageRank for 113322 took 0.020107507705688477s
Interlinking | Calculation of Degree of Connection for 113322 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.8133392333984375e-05s
Believability | Calculation of trust value for 113322 took 1.2874603271484375e-05s
INFO | --- Analysis for 11 took 4.831167221069336s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.410743713378906e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.33900880813598633s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.022258758544921875s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 2.86102294921875e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.2636184692382812e-05s
INFO | --- Analysis for 12323 took 3.099867343902588s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.08947205543518066s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.33770060539245605s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.022236347198486328s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.845329284667969e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.1920928955078125e-05s
INFO | --- Analysis for 2000-us-census-rdf took 3.196078300476074s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.2798078060150146s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.35022521018981934s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.02189493179321289s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.9577484130859375e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 9.775161743164062e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 7.269033670425415s
Availability | SPARQL endpoint availability check for Open Data Web took 45.7438907623291s
Availability | VoID file availability check for Open Data Web took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.3782942295074463s
Reputation | Calculation of the PageRank for Open Data Web took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.3855438232421875e-05s
Believability | Calculation of trust value for Open Data Web took 1.33514404296875e-05s
INFO | --- Analysis for _data.odw.tw took 73.68310594558716s
Availability | SPARQL endpoint availability check for 土地利用 took 4.649162292480469e-05s
Availability | VoID file availability check for 土地利用 took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.3644695281982422s
Reputation | Calculation of the PageRank for 土地利用 took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.218650817871094e-05s
Believability | Calculation of trust value for 土地利用 took 1.2636184692382812e-05s
INFO | --- Analysis for _data1.odw.tw took 3.10551118850708s
Availability | SPARQL endpoint availability check for 土地利用模型 took 8.940696716308594e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.325345516204834s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.9802322387695312e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.0967254638671875e-05s
INFO | --- Analysis for _data2.odw.tw took 5.070446014404297s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.202957153320312e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3507075309753418s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021275997161865234s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7894973754882812e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.239776611328125e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 4.600362777709961s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 9.179115295410156e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.33124852180480957s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.0517578125e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.2159347534179688e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.806960105895996s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 9.059906005859375e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0003612041473388672s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.34671807289123535s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 2.9325485229492188e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 1.0013580322265625e-05s
INFO | --- Analysis for A1 took 4.282453775405884s
Availability | SPARQL endpoint availability check for SummerOlympics took 2.0393893718719482s
Availability | VoID file availability check for SummerOlympics took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.3363804817199707s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02135920524597168s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.127357482910156e-05s
Believability | Calculation of trust value for SummerOlympics took 1.2636184692382812e-05s
INFO | --- Analysis for abc took 13.831660985946655s
Availability | SPARQL endpoint availability check for Test_m took 8.96453857421875e-05s
Availability | VoID file availability check for Test_m took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Test_m took 0.3371133804321289s
Reputation | Calculation of the PageRank for Test_m took 0.020336151123046875s
Interlinking | Calculation of Degree of Connection for Test_m took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Test_m took 2.9087066650390625e-05s
Believability | Calculation of trust value for Test_m took 1.049041748046875e-05s
INFO | --- Analysis for ABC took 3.1392643451690674s
Availability | SPARQL endpoint availability check for my intro took 0.00011610984802246094s
Availability | VoID file availability check for my intro took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for my intro took 0.3167152404785156s
Reputation | Calculation of the PageRank for my intro took 0.022472143173217773s
Interlinking | Calculation of Degree of Connection for my intro took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for my intro took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for my intro took 3.2901763916015625e-05s
Believability | Calculation of trust value for my intro took 1.1205673217773438e-05s
INFO | --- Analysis for abhay_intro took 3.1324586868286133s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.19640159606933594s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.34540677070617676s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.022049427032470703s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 9.72747802734375e-05s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for abs-linked-data took 3.313584804534912s
Availability | SPARQL endpoint availability check for AcadOnto took 4.9591064453125e-05s
Availability | VoID file availability check for AcadOnto took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.34871840476989746s
Reputation | Calculation of the PageRank for AcadOnto took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.9087066650390625e-05s
Believability | Calculation of trust value for AcadOnto took 1.2159347534179688e-05s
INFO | --- Analysis for acadonto took 3.729069948196411s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.129145383834839s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.3309905529022217s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020223617553710938s
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.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.457069396972656e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 8.821487426757812e-06s
INFO | --- Analysis for acorn-sat took 36.12791419029236s
Availability | SPARQL endpoint availability check for Addgene took 9.322166442871094e-05s
Availability | VoID file availability check for Addgene took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for Addgene took 0.360034704208374s
Reputation | Calculation of the PageRank for Addgene took 0.020163297653198242s
Interlinking | Calculation of Degree of Connection for Addgene took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.1948089599609375e-05s
Believability | Calculation of trust value for Addgene took 1.0967254638671875e-05s
INFO | --- Analysis for addgene took 16.345230102539062s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 9.036064147949219e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.3600325584411621s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020135879516601562s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 8.702278137207031e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.1444091796875e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 7.453029155731201s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.49430418014526367s
Availability | VoID file availability check for AEMET metereological dataset took 0.0012254714965820312s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.3238236904144287s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.600120544433594e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.2874603271484375e-05s
INFO | --- Analysis for aemet took 5.504915237426758s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.0495295524597168s
Availability | VoID file availability check for AgriNepalData took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.3650782108306885s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020839929580688477s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.557868957519531e-05s
Believability | Calculation of trust value for AgriNepalData took 1.0013580322265625e-05s
INFO | --- Analysis for agrinepaldata took 3.3240303993225098s
Availability | SPARQL endpoint availability check for AGRIS took 261.22474479675293s
Availability | VoID file availability check for AGRIS took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for AGRIS took 0.4523582458496094s
Reputation | Calculation of the PageRank for AGRIS took 0.020481109619140625s
Interlinking | Calculation of Degree of Connection for AGRIS took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.891654968261719e-05s
Believability | Calculation of trust value for AGRIS took 1.0728836059570312e-05s
INFO | --- Analysis for agris took 550.4572689533234s
Availability | SPARQL endpoint availability check for AGROVOC took 0.18340468406677246s
Availability | VoID file availability check for AGROVOC took 0.0005908012390136719s
Extra | Recovery of all triples for AGROVOC took 30.242353200912476s
Performance | Total latancy measurement for AGROVOC took 0.47157716751098633s
Amount of data | Number of triples check for AGROVOC took 20.11029815673828s
Interoperability | New terms check for AGROVOC took 2.8648359775543213s
Versatility | Languages check for AGROVOC took 82.54143357276917s
Interpretability | Number of blank nodes check for AGROVOC took 19.184425354003906s
Interpretability | RDF structures check for AGROVOC took 0.0939033031463623s
Versatility | Serialization formats check for AGROVOC took 0.09270763397216797s
Availability | RDF dump link check for AGROVOC took 0.09233403205871582s
License | MR license check for AGROVOC took 0.08194446563720703s
License | HR license check for AGROVOC took 0.38900113105773926s
Amount of data | Number of property check for AGROVOC took 0.09818625450134277s
Understandability | Number of label check for AGROVOC took 21.10487151145935s
Understandability | URI regex check for AGROVOC took 0.19527673721313477s
Understandability | Vocabs check for AGROVOC took 0.10629558563232422s
Verifiability | Authors check for AGROVOC took 0.0926215648651123s
Verifiability | Publishers check for AGROVOC took 0.10285425186157227s
Performance | Throughput check for AGROVOC took 10.348310470581055s
Amount of data | Check the number of entities for AGROVOC took 0.00011277198791503906s
Verifiability | Contribs. check for AGROVOC took 0.10100007057189941s
Interlinking | sameAs chians check for AGROVOC took 0.09261798858642578s
Interlinking | skos check for AGROVOC took 0.4239177703857422s
Interlinking | skos check for AGROVOC took 0.1507854461669922s
Timeliness | dataset update frequency check for AGROVOC took 0.0919039249420166s
Currency | Creation date check for AGROVOC took 0.19557690620422363s
Currency | Modification date check for AGROVOC took 0.18357157707214355s
Rep.Conc. | URIs length for AGROVOC took 43.42680811882019s
Interoperability | New vocabularies check for AGROVOC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.09029531478881836s
Accuracy | Check Functional Property for AGROVOC took 0.09927010536193848s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.09237337112426758s
Accuracy | Check Empty annotation labels for AGROVOC took 16.815290927886963s
Accuracy | Check White space in annotation for AGROVOC took 2.98056960105896s
Accuracy | Check Datatype consistency for AGROVOC took 4.469428539276123s
Consistency | Disjoint class check for AGROVOC took 0.10186171531677246s
Consistency | Check Misplaced properties for AGROVOC took 13.547949314117432s
Consistency | Check Ontology hijacking for AGROVOC took 25.38078737258911s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.479706048965454s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 13.742083311080933s
Conciseness | Check Extensional conciseness for AGROVOC took 2.502079725265503s
Conciseness | Check Intensional conciseness for AGROVOC took 0.09490823745727539s
Security | Sign check for AGROVOC took 0.09393811225891113s
Availability | Check URIs Dereferenciability for AGROVOC took 2398.6569135189056s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.49332571029663086s
Reputation | Calculation of the PageRank for AGROVOC took 0.0210113525390625s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.0001895427703857422s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.6689300537109375e-06s
Believability | Calculation of trust value for AGROVOC took 1.2159347534179688e-05s
INFO | --- Analysis for agrovoc took 2761.574815273285s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.5355417728424072s
Availability | VoID file availability check for Analytics India Magazine took 0.0006105899810791016s
Extra | Recovery of all triples for Analytics India Magazine took 2.5624608993530273s
Performance | Total latancy measurement for Analytics India Magazine took 2.5287787914276123s
Amount of data | Number of triples check for Analytics India Magazine took 1.4832136631011963s
Versatility | Languages check for Analytics India Magazine took 1.785015344619751s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.8167803287506104s
Interpretability | RDF structures check for Analytics India Magazine took 1.189896821975708s
Versatility | Serialization formats check for Analytics India Magazine took 1.1370131969451904s
Availability | RDF dump link check for Analytics India Magazine took 1.4426205158233643s
License | MR license check for Analytics India Magazine took 1.3769958019256592s
License | HR license check for Analytics India Magazine took 1.321573257446289s
Amount of data | Number of property check for Analytics India Magazine took 1.124253273010254s
Understandability | Number of label check for Analytics India Magazine took 1.471053123474121s
Understandability | URI regex check for Analytics India Magazine took 3.025063991546631s
Understandability | Vocabs check for Analytics India Magazine took 1.19718337059021s
Verifiability | Authors check for Analytics India Magazine took 1.22267746925354s
Verifiability | Publishers check for Analytics India Magazine took 1.7577874660491943s
Performance | Throughput check for Analytics India Magazine took 16.810893535614014s
Amount of data | Check the number of entities for Analytics India Magazine took 0.0001201629638671875s
Verifiability | Contribs. check for Analytics India Magazine took 1.395927906036377s
Interlinking | sameAs chians check for Analytics India Magazine took 1.3899805545806885s
Interlinking | skos check for Analytics India Magazine took 1.3085699081420898s
Interlinking | skos check for Analytics India Magazine took 0.10938000679016113s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.4375107288360596s
Currency | Creation date check for Analytics India Magazine took 2.4013724327087402s
Currency | Modification date check for Analytics India Magazine took 2.4392025470733643s
Rep.Conc. | URIs length for Analytics India Magazine took 2.6820247173309326s
Interoperability | New vocabularies check for Analytics India Magazine took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.38737154006958s
Consistency | Disjoint class check for Analytics India Magazine took 1.2448909282684326s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.0851421356201172s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 3.140320301055908s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.0001595020294189453s
Security | Sign check for Analytics India Magazine took 2.061736583709717s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.380448579788208s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.021425962448120117s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.361701965332031e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 1.430511474609375e-06s
Believability | Calculation of trust value for Analytics India Magazine took 1.2159347534179688e-05s
INFO | --- Analysis for AIM took 101.1633050441742s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.506111145019531e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.28977108001708984s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020292043685913086s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 2.956390380859375e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.239776611328125e-05s
INFO | --- Analysis for AISHE took 2.6072535514831543s
Availability | SPARQL endpoint availability check for  equipment ontology took 9.059906005859375e-05s
Availability | VoID file availability check for  equipment ontology took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.2684006690979004s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for  equipment ontology took 1.0728836059570312e-05s
INFO | --- Analysis for akash took 2.5819756984710693s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 262.7944209575653s
Availability | VoID file availability check for aliada-scanbit-net took 0.0008368492126464844s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.42119789123535156s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.000125885009765625s
Believability | Calculation of trust value for aliada-scanbit-net took 1.33514404296875e-05s
INFO | --- Analysis for aliada-scanbit-net took 1452.2153544425964s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.8416547775268555s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.00072479248046875s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 136.96752738952637s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7166783809661865s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.385087013244629s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.5953311920166016s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.05158138275146s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.6083459854125977s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.855318546295166s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.7975692749023438s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.7719433307647705s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5706703662872314s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 1.6057968139648438s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 33.44502091407776s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5758709907531738s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 1.3526973724365234s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.126645803451538s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5807926654815674s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6859972476959229s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5923047065734863s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.974170446395874s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 3.409385681152344e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5911140441894531s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.6400880813598633s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6107323169708252s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5896477699279785s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5812761783599854s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.8434560298919678s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1277854442596436s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 52.61567521095276s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 5.1749162673950195s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5665481090545654s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.7408256530761719s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6424899101257324s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 35.67912793159485s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.018972873687744s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.5476584434509277s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.5991995334625244s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.460625171661377s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.556894779205322s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 33.1908974647522s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3971683979034424s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.334503650665283s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.701409101486206s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8476247787475586s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.558387279510498s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 14352.991847753525s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.627213716506958s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.022292613983154297s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 7.390975952148438e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 6.503668308258057s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.2874603271484375e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 15112.907470941544s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.3095874786376953s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.3368103504180908s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.62396240234375e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.1444091796875e-05s
INFO | --- Analysis for alpino-rdf took 4.278762102127075s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.267692565917969e-05s
Availability | VoID file availability check for AAT-atawil took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.3115692138671875s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 2.7418136596679688e-05s
Believability | Calculation of trust value for AAT-atawil took 1.239776611328125e-05s
INFO | --- Analysis for Altawil took 2.733067750930786s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.267692565917969e-05s
Availability | VoID file availability check for Amer Nejma took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.29909300804138184s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.0994415283203125e-05s
Believability | Calculation of trust value for Amer Nejma took 1.1682510375976562e-05s
INFO | --- Analysis for Amer_Nejma took 2.786827802658081s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7557847499847412s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.3138136863708496s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 8.821487426757812e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0728836059570312e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 4.356170415878296s
Availability | SPARQL endpoint availability check for Anime Dataset took 9.059906005859375e-05s
Availability | VoID file availability check for Anime Dataset took 0.0008344650268554688s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.31235647201538086s
Reputation | Calculation of the PageRank for Anime Dataset took 0.021158218383789062s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.218650817871094e-05s
Believability | Calculation of trust value for Anime Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Anime took 4.181994915008545s
Availability | SPARQL endpoint availability check for ANNO took 4.291534423828125e-05s
Availability | VoID file availability check for ANNO took 0.0007636547088623047s
Completeness | Calculation of interlinking completeness for ANNO took 0.27481770515441895s
Reputation | Calculation of the PageRank for ANNO took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.552436828613281e-05s
Believability | Calculation of trust value for ANNO took 1.33514404296875e-05s
INFO | --- Analysis for anno took 8.481250762939453s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.458427429199219e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.2894761562347412s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.021216630935668945s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.534027099609375e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.2159347534179688e-05s
INFO | --- Analysis for AntiqueCarsCollection took 3.1324915885925293s
Availability | SPARQL endpoint availability check for apache took 8.916854858398438e-05s
Availability | VoID file availability check for apache took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for apache took 0.2879502773284912s
Reputation | Calculation of the PageRank for apache took 0.0203094482421875s
Interlinking | Calculation of Degree of Connection for apache took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for apache took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for apache took 5.412101745605469e-05s
Believability | Calculation of trust value for apache took 1.1682510375976562e-05s
INFO | --- Analysis for apache took 3.497997522354126s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.31943392753601074s
Reputation | Calculation of the PageRank for Apertium RDF took 0.021580219268798828s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf took 6.541044473648071s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.3135197162628174s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 5.976139783859253s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 8.988380432128906e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.3142714500427246s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 6.029564619064331s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 0.00014734268188476562s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.3267636299133301s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.021391868591308594s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-en-es took 6.0300939083099365s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 9.083747863769531e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.28926849365234375s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 5.840353965759277s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 0.000110626220703125s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2938554286956787s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.430511474609375e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.98575496673584s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 8.916854858398438e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.3423953056335449s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.021308183670043945s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 5.974150657653809s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 8.726119995117188e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.2916741371154785s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.02036428451538086s
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.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 5.888566493988037s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 8.845329284667969e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.32418274879455566s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020371437072753906s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 6.241129636764526s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2969052791595459s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02034735679626465s
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.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-es-an took 6.325262546539307s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 8.893013000488281e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.33974409103393555s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.021079063415527344s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.1444091796875e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 5.937180280685425s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 8.797645568847656e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0007605552673339844s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.29514336585998535s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 25.3716459274292s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 6.67572021484375e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.3151123523712158s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 5.971369504928589s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.3375663757324219s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 6.0970072746276855s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 8.58306884765625e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.3039090633392334s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 5.7853004932403564s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 8.702278137207031e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.27220940589904785s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.022284269332885742s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 5.880705833435059s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.696846008300781e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.2662816047668457s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 5.757354736328125s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 9.560585021972656e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0007822513580322266s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.28629469871520996s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.743990182876587s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2872443199157715s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.022171497344970703s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 5.777798652648926s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0007574558258056641s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.3169283866882324s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02278757095336914s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0010178089141845703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 5.412101745605469e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.886189222335815s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 8.797645568847656e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2911257743835449s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 5.902331352233887s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 8.702278137207031e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.3054225444793701s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 5.030632019042969e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.896567344665527s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2981386184692383s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0010356903076171875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 5.412101745605469e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.7744972705841064s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 0.716975212097168s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.0006563663482666016s
Extra | Recovery of all triples for AragoDBpedia - aragon open data took 3.1406211853027344s
Performance | Total latancy measurement for AragoDBpedia - aragon open data took 1.9612038135528564s
Amount of data | Number of triples check for AragoDBpedia - aragon open data took 0.8331351280212402s
Interoperability | New terms check for AragoDBpedia - aragon open data took 2.181457281112671s
Versatility | Languages check for AragoDBpedia - aragon open data took 60.50822925567627s
Interpretability | Number of blank nodes check for AragoDBpedia - aragon open data took 3.934138774871826s
Security | Check HTTPS for AragoDBpedia - aragon open data took 0.26287078857421875s
Interpretability | RDF structures check for AragoDBpedia - aragon open data took 0.7948200702667236s
Versatility | Serialization formats check for AragoDBpedia - aragon open data took 0.985027551651001s
Availability | RDF dump link check for AragoDBpedia - aragon open data took 0.41736483573913574s
License | MR license check for AragoDBpedia - aragon open data took 0.6477069854736328s
License | HR license check for AragoDBpedia - aragon open data took 6.17036771774292s
Amount of data | Number of property check for AragoDBpedia - aragon open data took 0.4118082523345947s
Understandability | Number of label check for AragoDBpedia - aragon open data took 0.5512244701385498s
Understandability | URI regex check for AragoDBpedia - aragon open data took 0.980421781539917s
Understandability | Vocabs check for AragoDBpedia - aragon open data took 0.4834401607513428s
Verifiability | Authors check for AragoDBpedia - aragon open data took 0.5267622470855713s
Verifiability | Publishers check for AragoDBpedia - aragon open data took 0.40577077865600586s
Performance | Throughput check for AragoDBpedia - aragon open data took 11.399178266525269s
Amount of data | Check the number of entities for AragoDBpedia - aragon open data took 7.009506225585938e-05s
Verifiability | Contribs. check for AragoDBpedia - aragon open data took 0.5036013126373291s
Interlinking | sameAs chians check for AragoDBpedia - aragon open data took 0.43436574935913086s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.6409707069396973s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.3786196708679199s
Timeliness | dataset update frequency check for AragoDBpedia - aragon open data took 0.5365767478942871s
Currency | Creation date check for AragoDBpedia - aragon open data took 1.3047962188720703s
Currency | Modification date check for AragoDBpedia - aragon open data took 0.3910861015319824s
Rep.Conc. | URIs length for AragoDBpedia - aragon open data took 5.8010094165802s
Interoperability | New vocabularies check for AragoDBpedia - aragon open data took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for AragoDBpedia - aragon open data took 0.38421058654785156s
Accuracy | Check Functional Property for AragoDBpedia - aragon open data took 0.45717287063598633s
Accuracy | Check Inverse Functional Property for AragoDBpedia - aragon open data took 0.5153439044952393s
Accuracy | Check Empty annotation labels for AragoDBpedia - aragon open data took 1.3061399459838867s
Accuracy | Check White space in annotation for AragoDBpedia - aragon open data took 0.029918909072875977s
Accuracy | Check Datatype consistency for AragoDBpedia - aragon open data took 0.027583599090576172s
Consistency | Disjoint class check for AragoDBpedia - aragon open data took 0.43329405784606934s
Consistency | Check Misplaced properties for AragoDBpedia - aragon open data took 4.450620651245117s
Consistency | Misplaced classes for AragoDBpedia - aragon open data took 0.642524242401123s
Consistency | Check Ontology hijacking for AragoDBpedia - aragon open data took 2.5622315406799316s
Consistency | Check Invalid usage of undefined classes for AragoDBpedia - aragon open data took 1.348825216293335s
Consistency | Check Invalid usage of undefined properties for AragoDBpedia - aragon open data took 5.271548509597778s
Conciseness | Check Extensional conciseness for AragoDBpedia - aragon open data took 0.03162717819213867s
Conciseness | Check Intensional conciseness for AragoDBpedia - aragon open data took 0.5870537757873535s
Security | Sign check for AragoDBpedia - aragon open data took 0.635465145111084s
Availability | Check URIs Dereferenciability for AragoDBpedia - aragon open data took 3326.8073058128357s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 0.591956377029419s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.020704984664916992s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBpedia - aragon open data took 1.430511474609375e-06s
Believability | Calculation of trust value for AragoDBpedia - aragon open data took 9.775161743164062e-06s
INFO | --- Analysis for aragodbpedia took 3608.211078643799s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.190828800201416s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2922673225402832s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 4.982948303222656e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for archiveshub-linkeddata took 83.18281745910645s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.313877820968628s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.000354766845703125s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.2879757881164551s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020193815231323242s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.528594970703125e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 7.152557373046875e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 20.17506504058838s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.8789124488830566s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.00031447410583496094s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.26860690116882324s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007357597351074219s
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 8.106231689453125e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.740049839019775s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.38690185546875e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0003986358642578125s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.2921292781829834s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020243406295776367s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.870529174804688e-05s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 9.059826135635376s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.1961669921875e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0004115104675292969s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.3084831237792969s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020865678787231445s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010371208190917969s
Believability | Calculation of trust value for Arthroscopy community took 6.67572021484375e-06s
INFO | --- Analysis for arthroscopy took 24.82349991798401s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.7299842834472656s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0004088878631591797s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 51.39226007461548s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 1.0740466117858887s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.18476438522339s
Interoperability | New terms check for Wikidata entry for Art × Science International took 1.9227137565612793s
Versatility | Languages check for Wikidata entry for Art × Science International took 60.20311212539673s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.20416569709778s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.3510587215423584s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.23573756217956543s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.19273900985717773s
License | MR license check for Wikidata entry for Art × Science International took 0.17563366889953613s
License | HR license check for Wikidata entry for Art × Science International took 65.16685771942139s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.33237409591674805s
Understandability | Number of label check for Wikidata entry for Art × Science International took 65.17853856086731s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.415973424911499s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.18323206901550293s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.22235798835754395s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.2731306552886963s
Performance | Throughput check for Wikidata entry for Art × Science International took 10.880078554153442s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 7.677078247070312e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.20828700065612793s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 65.16862535476685s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.30060505867004395s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.07888579368591309s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.1947939395904541s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.37112927436828613s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.38904452323913574s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 32.63728308677673s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.3501756191253662s
Accuracy | Check Empty annotation labels for Wikidata entry for Art × Science International took 20.195496559143066s
Accuracy | Check White space in annotation for Wikidata entry for Art × Science International took 2.657209634780884s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.5841288566589355s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.3439774513244629s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 11.114761352539062s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 23.128464698791504s
Consistency | Check Invalid usage of undefined classes for Wikidata entry for Art × Science International took 1.4460337162017822s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 1.5938396453857422s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.749448776245117s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.6366589069366455s
Security | Sign check for Wikidata entry for Art × Science International took 0.2636833190917969s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 8.544501304626465s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.3791160583496094s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.02103424072265625s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 1.430511474609375e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.1444091796875e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 950.7397372722626s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.8406221866607666s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.3118598461151123s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.022894859313964844s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.20159912109375e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.0728836059570312e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 14.252073049545288s
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.7031729221343994s
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.0005290508270263672s
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.3399331569671631s
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.020895957946777344s
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.0967254638671875e-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.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.653236389160156e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 9.5367431640625e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 12.65939974784851s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.6773746013641357s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.3443644046783447s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.021778583526611328s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.703636169433594e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.298324584960938e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 13.692596435546875s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.698629379272461s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.30941104888916016s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.022532224655151367s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.3392181396484375e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 9.775161743164062e-06s
INFO | --- Analysis for ASCDC-CRB took 16.113821268081665s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.699235439300537s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.29840898513793945s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020809173583984375s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.845329284667969e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.775161743164062e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 13.101003170013428s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.6973202228546143s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.28808116912841797s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020902156829833984s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 4.172325134277344e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 9.775161743164062e-06s
INFO | --- Analysis for ASCDC-DQOT took 14.244667768478394s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.679260015487671s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2642652988433838s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020802974700927734s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.867813110351562e-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 14.266520023345947s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.5600833892822266s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.33100128173828125s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.082389831542969e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.0013580322265625e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 17.043904781341553s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.677123785018921s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.29816627502441406s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.02124166488647461s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.269050598144531e-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.1920928955078125e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 13.188077211380005s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.6940829753875732s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.3251767158508301s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020680665969848633s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.984306335449219e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0013580322265625e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 13.072931289672852s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.1993567943573s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.31868600845336914s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020731210708618164s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.839897155761719e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.0013580322265625e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 17.8677396774292s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.685328722000122s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2878756523132324s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.510185241699219e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 12.425020933151245s
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.718876838684082s
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.0006842613220214844s
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.29755640029907227s
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.020782470703125s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007386207580566406s
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.0013580322265625e-05s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 14.42420482635498s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.67546010017395s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.27419161796569824s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.021625280380249023s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.553794860839844e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.0728836059570312e-05s
INFO | --- Analysis for ASCDC_-_DNB took 12.613379716873169s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 8.845329284667969e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2715895175933838s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.771087646484375e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.0013580322265625e-05s
INFO | --- Analysis for asit took 8.18414568901062s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 8.96453857421875e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.3386673927307129s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.02099442481994629s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.981590270996094e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.0728836059570312e-05s
INFO | --- Analysis for asjp took 5.037842750549316s
Availability | SPARQL endpoint availability check for ASN:US took 2.1566002368927s
Availability | VoID file availability check for ASN:US took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2761714458465576s
Reputation | Calculation of the PageRank for ASN:US took 0.0223541259765625s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.914138793945312e-05s
Believability | Calculation of trust value for ASN:US took 8.821487426757812e-06s
INFO | --- Analysis for asn-us took 13.357448816299438s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.38690185546875e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.29936838150024414s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.021326541900634766s
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.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.170967102050781e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 8.106231689453125e-06s
INFO | --- Analysis for aspire-mmu took 4.6756432056427s
Availability | SPARQL endpoint availability check for associations took 0.0001201629638671875s
Availability | VoID file availability check for associations took 0.0007843971252441406s
Completeness | Calculation of interlinking completeness for associations took 0.27263426780700684s
Reputation | Calculation of the PageRank for associations took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for associations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for associations took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for associations took 6.437301635742188e-05s
Believability | Calculation of trust value for associations took 1.2874603271484375e-05s
INFO | --- Analysis for associations took 7.372557878494263s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 9.202957153320312e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.3139650821685791s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020322561264038086s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.869171142578125e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.1920928955078125e-05s
INFO | --- Analysis for athelia-rfid took 5.7414023876190186s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.7465248107910156s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0008087158203125s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.30476808547973633s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020586252212524414s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.340576171875e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.3113021850585938e-05s
INFO | --- Analysis for AugustiniConfessiones took 4.6906983852386475s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.5673973560333252s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.30635643005371094s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.1444091796875e-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 0.00010251998901367188s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 9.298324584960938e-06s
INFO | --- Analysis for austrian_ski_racers took 3.9595322608947754s
Availability | SPARQL endpoint availability check for AVsOnto took 9.1552734375e-05s
Availability | VoID file availability check for AVsOnto took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.277421236038208s
Reputation | Calculation of the PageRank for AVsOnto took 0.020761966705322266s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.123283386230469e-05s
Believability | Calculation of trust value for AVsOnto took 1.2159347534179688e-05s
INFO | --- Analysis for AVsOnto took 3.525225877761841s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21386504173278809s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005667209625244141s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 202.83853840827942s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5206940174102783s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.01148080825806s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 212.36813378334045s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0804126262665s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10112047195435s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24373316764831543s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5808966159820557s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17975687980651855s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1021718978881836s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 47.14956450462341s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0952785015106s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19063782691955566s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 166.25197911262512s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.28580379486083984s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1564180850982666s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09166932106018066s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10919761657714844s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.416345834732056s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.557868957519531e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12696337699890137s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0654845237732s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1558830738067627s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1327686309814453s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14378118515014648s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2233293056488037s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24840378761291504s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 896.8602364063263s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1705007553100586s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.575717687606812s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.17695951461792s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.776625394821167s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1397252082824707s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1658365726471s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 26.298563718795776s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.4383316040039062s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.58810687065125s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.7910804748535156s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.31421852111816406s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.083498477935791s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.7544510364532471s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.02191472053527832s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.9073486328125e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.298324584960938e-06s
INFO | --- Analysis for b3kat took 4340.147048950195s
Availability | SPARQL endpoint availability check for BabelNet took 0.5797617435455322s
Availability | VoID file availability check for BabelNet took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for BabelNet took 0.3124809265136719s
Reputation | Calculation of the PageRank for BabelNet took 0.021053552627563477s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00016641616821289062s
Believability | Calculation of trust value for BabelNet took 1.0251998901367188e-05s
INFO | --- Analysis for babelnet took 4.881234884262085s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 8.940696716308594e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.2758939266204834s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.023455142974853516s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.0517578125e-05s
Believability | Calculation of trust value for Bacevicius.lt took 9.775161743164062e-06s
INFO | --- Analysis for Bacevicius.lt took 2.736288547515869s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5349905490875244s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.32778239250183105s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.021519184112548828s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.601478576660156e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 7.3909759521484375e-06s
INFO | --- Analysis for bag took 4.428096532821655s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.08554530143737793s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.28777313232421875s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.022897720336914062s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.3855438232421875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.3113021850585938e-05s
INFO | --- Analysis for baixue took 2.7821216583251953s
Availability | SPARQL endpoint availability check for baixue composer took 9.131431579589844e-05s
Availability | VoID file availability check for baixue composer took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for baixue composer took 0.28885817527770996s
Reputation | Calculation of the PageRank for baixue composer took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.170967102050781e-05s
Believability | Calculation of trust value for baixue composer took 7.867813110351562e-06s
INFO | --- Analysis for baixue_composer took 3.1234500408172607s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.322166442871094e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.3198869228363037s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02089715003967285s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.3855438232421875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.33514404296875e-05s
INFO | --- Analysis for baixue_imagery took 3.191662073135376s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.869171142578125e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0012967586517333984s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.30887913703918457s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02134418487548828s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.2901763916015625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.049041748046875e-05s
INFO | --- Analysis for baixue_imagery1 took 4.112897634506226s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 8.916854858398438e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2888355255126953s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.021036148071289062s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.2438507080078125e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.1444091796875e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.1567811965942383s
Availability | SPARQL endpoint availability check for BBC Music took 0.5187196731567383s
Availability | VoID file availability check for BBC Music took 0.0008068084716796875s
Completeness | Calculation of interlinking completeness for BBC Music took 0.3152754306793213s
Reputation | Calculation of the PageRank for BBC Music took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001246929168701172s
Believability | Calculation of trust value for BBC Music took 1.2874603271484375e-05s
INFO | --- Analysis for bbc-music took 3.8540446758270264s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.27874159812927246s
Availability | VoID file availability check for BBC Programmes took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2880434989929199s
Reputation | Calculation of the PageRank for BBC Programmes took 0.021063566207885742s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 9.989738464355469e-05s
Believability | Calculation of trust value for BBC Programmes took 1.1682510375976562e-05s
INFO | --- Analysis for bbc-programmes took 12.233323097229004s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.35310816764831543s
Availability | VoID file availability check for BBC Wildlife Finder took 0.000782012939453125s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.29071927070617676s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020868301391601562s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.000102996826171875s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.239776611328125e-05s
INFO | --- Analysis for bbc-wildlife-finder took 9.999552726745605s
Availability | SPARQL endpoint availability check for BBOP took 8.821487426757812e-05s
Availability | VoID file availability check for BBOP took 0.0007581710815429688s
Completeness | Calculation of interlinking completeness for BBOP took 0.3276984691619873s
Reputation | Calculation of the PageRank for BBOP took 0.023423194885253906s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.1948089599609375e-05s
Believability | Calculation of trust value for BBOP took 7.152557373046875e-06s
INFO | --- Analysis for bbop-selected took 20.68125581741333s
Availability | SPARQL endpoint availability check for Bdgp took 1.1970672607421875s
Availability | VoID file availability check for Bdgp took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Bdgp took 0.3359079360961914s
Reputation | Calculation of the PageRank for Bdgp took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.123283386230469e-05s
Believability | Calculation of trust value for Bdgp took 1.239776611328125e-05s
INFO | --- Analysis for bdgp took 5.77886962890625s
Availability | SPARQL endpoint availability check for Bendev Junior took 9.298324584960938e-05s
Availability | VoID file availability check for Bendev Junior took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.2889597415924072s
Reputation | Calculation of the PageRank for Bendev Junior took 0.021242380142211914s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bendev Junior took 1.3113021850585938e-05s
INFO | --- Analysis for bendevoficial took 3.233053207397461s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 7.9176695346832275s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0007786750793457031s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.29218602180480957s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020701885223388672s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.176399230957031e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 9.298324584960938e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 21.436323165893555s
Availability | SPARQL endpoint availability check for berlios took 4.267692565917969e-05s
Availability | VoID file availability check for berlios took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for berlios took 0.3086106777191162s
Reputation | Calculation of the PageRank for berlios took 0.0225372314453125s
Interlinking | Calculation of Degree of Connection for berlios took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for berlios took 8.845329284667969e-05s
Believability | Calculation of trust value for berlios took 1.1205673217773438e-05s
INFO | --- Analysis for berlios took 3.1355860233306885s
Availability | SPARQL endpoint availability check for Between Our Worlds took 9.107589721679688e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.3675086498260498s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.022421598434448242s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.628036499023438e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.3589859008789062e-05s
INFO | --- Analysis for betweenourworlds took 9.207691192626953s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.10748863220214844s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.28665614128112793s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.021382808685302734s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00010967254638671875s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for bfs-linked-data took 2.8291497230529785s
Availability | SPARQL endpoint availability check for BibBase took 0.0822904109954834s
Availability | VoID file availability check for BibBase took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for BibBase took 0.27282285690307617s
Reputation | Calculation of the PageRank for BibBase took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for BibBase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.250640869140625e-05s
Believability | Calculation of trust value for BibBase took 1.0967254638671875e-05s
INFO | --- Analysis for bibbase took 2.761215925216675s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 8.678436279296875e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.000858306884765625s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.2878119945526123s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.02073359489440918s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.584426879882812e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.049041748046875e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 9.93733263015747s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.506111145019531e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.308396577835083s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.021833419799804688s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010085105895996094s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.0251998901367188e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 6.8877434730529785s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.4345855712890625e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.001458883285522461s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.31755566596984863s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.02099609375s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.790855407714844e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.049041748046875e-05s
INFO | --- Analysis for BibSonomy took 11.050779581069946s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 8.559226989746094e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0007846355438232422s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.3059978485107422s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.022560834884643555s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.743171691894531e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.2636184692382812e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 20.79017448425293s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.410743713378906e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.2800285816192627s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02067255973815918s
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.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.314018249511719e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.239776611328125e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.906879186630249s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.900954008102417s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006499290466308594s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 18.77481698989868s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5009016990661621s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 46.33379554748535s
Interoperability | New terms check for Bio2RDF::Affymetrix took 42.42233610153198s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.1256468296051s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.13812875747680664s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.6585845947265625s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.19286417961120605s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.421210527420044s
License | MR license check for Bio2RDF::Affymetrix took 0.3615994453430176s
License | HR license check for Bio2RDF::Affymetrix took 60.09346628189087s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.14052128791809082s
Understandability | Number of label check for Bio2RDF::Affymetrix took 10.632944107055664s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.4057765007019043s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.1281874179840088s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.14385986328125s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.13202118873596191s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.639923334121704s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 74.20914149284363s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.47100186347961426s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.23233604431152344s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.6522858142852783s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.1926126480102539s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.10602998733520508s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2877500057220459s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.23813748359680176s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 108.26961922645569s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 12.028427362442017s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.30892324447631836s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.48253893852233887s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12149286270141602s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.210058927536011s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8851954936981201s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6560604572296143s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.27591848373413086s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.3519675731659s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.2740671634674072s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 5.832304000854492s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.2968556880950928s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.355398178100586s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.6788935661315918s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3450906276702881s
Security | Sign check for Bio2RDF::Affymetrix took 0.11525630950927734s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 19.539612531661987s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.37687206268310547s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010991096496582031s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 47.4182505607605s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1071.7158720493317s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5065052509307861s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0006062984466552734s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.764890670776367s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.222269058227539s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 45.97105836868286s
Interoperability | New terms check for Bio2RDF::Biomodels took 40.90571331977844s
Versatility | Languages check for Bio2RDF::Biomodels took 60.25731825828552s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.255631685256958s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.15392708778381348s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.35036230087280273s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.3240375518798828s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.3397514820098877s
License | MR license check for Bio2RDF::Biomodels took 0.3731503486633301s
License | HR license check for Bio2RDF::Biomodels took 60.26062369346619s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.24812650680541992s
Understandability | Number of label check for Bio2RDF::Biomodels took 9.317996501922607s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5660731792449951s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.260861873626709s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.23665165901184082s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.24743127822875977s
Performance | Throughput check for Bio2RDF::Biomodels took 10.36515212059021s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 73.11550426483154s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.6063191890716553s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.25141358375549316s
Interlinking | skos check for Bio2RDF::Biomodels took 0.779381513595581s
Interlinking | skos check for Bio2RDF::Biomodels took 0.3440067768096924s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2768375873565674s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5095443725585938s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5254204273223877s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 107.20184826850891s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 59.73885703086853s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.4178917407989502s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.270427942276001s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.27143049240112305s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 6.918258190155029s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8872275352478027s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6517016887664795s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.41773438453674316s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.46235847473145s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.410677433013916s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 5.81263279914856s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.2749707698822021s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.50808930397034s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.6877655982971191s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 1.4230530261993408s
Security | Sign check for Bio2RDF::Biomodels took 0.2576301097869873s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 19.48412847518921s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.4862806797027588s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011157989501953125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 65.53043985366821s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1136.0403974056244s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.4660947322845459s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0005950927734375s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 18.299408197402954s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.225914716720581s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 45.66534090042114s
Interoperability | New terms check for Bio2RDF::Bioportal took 41.91575026512146s
Versatility | Languages check for Bio2RDF::Bioportal took 60.263426542282104s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.26264190673828125s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.15491843223571777s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.3326897621154785s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.3110051155090332s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.5207467079162598s
License | MR license check for Bio2RDF::Bioportal took 0.3555030822753906s
License | HR license check for Bio2RDF::Bioportal took 60.26544666290283s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2935185432434082s
Understandability | Number of label check for Bio2RDF::Bioportal took 9.702555894851685s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.6337592601776123s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.25145554542541504s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2550034523010254s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.2571594715118408s
Performance | Throughput check for Bio2RDF::Bioportal took 11.001838445663452s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 74.56229829788208s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.5780355930328369s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.2623937129974365s
Interlinking | skos check for Bio2RDF::Bioportal took 1.0246446132659912s
Interlinking | skos check for Bio2RDF::Bioportal took 0.3452157974243164s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.25127577781677246s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5139851570129395s
Currency | Modification date check for Bio2RDF::Bioportal took 0.49663686752319336s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 107.0470712184906s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 41.996411085128784s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4217805862426758s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.2660868167877197s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.27988409996032715s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.5913920402526855s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8784716129302979s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6568713188171387s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.2529933452606201s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.2188150882721s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.395779848098755s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.195596218109131s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3284022808074951s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.595569133758545s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7104885578155518s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.41863203048706055s
Security | Sign check for Bio2RDF::Bioportal took 0.25563478469848633s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 10.536720752716064s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.4772014617919922s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0005640983581542969s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 22.032488346099854s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1077.121562719345s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.1354665756225586s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.37276148796081543s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.745887756347656e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-chembl took 16.429468870162964s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.4762876033782959s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006172657012939453s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 19.05319333076477s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2929491996765137s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 45.25790047645569s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 42.116974115371704s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.2464497089386s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.30701375007629395s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.14974546432495117s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.5282347202301025s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.30160069465637207s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.3041763305664062s
License | MR license check for Bio2RDF::Clinicaltrials took 0.4526042938232422s
License | HR license check for Bio2RDF::Clinicaltrials took 60.25s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.23724961280822754s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 9.856332778930664s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5886759757995605s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.24725699424743652s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2699887752532959s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.24029326438903809s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 10.602185487747192s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 73.77000069618225s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.7159225940704346s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.2640511989593506s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.7684085369110107s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.332139253616333s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.2534213066101074s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5013763904571533s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5049448013305664s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 106.97463154792786s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 35.44476509094238s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.42386889457702637s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.26560187339782715s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.2606327533721924s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 5.901382207870483s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8873107433319092s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6472878456115723s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.4458432197570801s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 64.98489451408386s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.3535478115081787s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.1603381633758545s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.265859842300415s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.48804593086243s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.6866495609283447s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.4209880828857422s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.26940178871154785s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 9.861464500427246s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.4552288055419922s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020994901657104492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 44.27276539802551s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1082.278472661972s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 1.2667834758758545s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005970001220703125s
Extra | Recovery of all triples for Bio2RDF::Ctd took 19.79875349998474s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2713642120361328s
Amount of data | Number of triples check for Bio2RDF::Ctd took 45.90349769592285s
Interoperability | New terms check for Bio2RDF::Ctd took 39.55767512321472s
Versatility | Languages check for Bio2RDF::Ctd took 60.263806104660034s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2712240219116211s
Security | Check HTTPS for Bio2RDF::Ctd took 0.15592432022094727s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.5204715728759766s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3085930347442627s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.5093259811401367s
License | MR license check for Bio2RDF::Ctd took 0.4780857563018799s
License | HR license check for Bio2RDF::Ctd took 60.25505828857422s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2501997947692871s
Understandability | Number of label check for Bio2RDF::Ctd took 10.434109926223755s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5767548084259033s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.25867199897766113s
Verifiability | Authors check for Bio2RDF::Ctd took 0.26650261878967285s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.24672818183898926s
Performance | Throughput check for Bio2RDF::Ctd took 11.199074983596802s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 72.9329514503479s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.5538387298583984s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.2663114070892334s
Interlinking | skos check for Bio2RDF::Ctd took 0.6248714923858643s
Interlinking | skos check for Bio2RDF::Ctd took 0.3389298915863037s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2599327564239502s
Currency | Creation date check for Bio2RDF::Ctd took 0.5179624557495117s
Currency | Modification date check for Bio2RDF::Ctd took 0.502244234085083s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 106.45247340202332s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 24.68419122695923s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4139676094055176s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2485826015472412s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2865183353424072s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 6.682254314422607s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8908636569976807s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6446423530578613s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.43880295753479004s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.03126454353333s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.3712520599365234s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.430470705032349s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3055577278137207s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.50992250442505s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.6813015937805176s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.4283416271209717s
Security | Sign check for Bio2RDF::Ctd took 0.2788558006286621s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 11.293566226959229s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.4226875305175781s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020926475524902344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 8.821487426757812e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 40.61012578010559s
Believability | Calculation of trust value for Bio2RDF::Ctd took 6.222724914550781e-05s
INFO | --- Analysis for bio2rdf-ctd took 1078.6333448886871s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.315376281738281e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.3162827491760254s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.023627042770385742s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.696846008300781e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-dataset took 2.93823504447937s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.4679715633392334s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.00034117698669433594s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 19.266378164291382s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.3072583675384521s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 45.82711148262024s
Interoperability | New terms check for Bio2RDF::Dbsnp took 43.71659874916077s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.23939085006714s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.2587771415710449s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.15617775917053223s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.25531554222106934s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.3118593692779541s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.2496438026428223s
License | MR license check for Bio2RDF::Dbsnp took 0.44737768173217773s
License | HR license check for Bio2RDF::Dbsnp took 60.26885104179382s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.24660301208496094s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.027685165405273s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.6132707595825195s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.24341344833374023s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.250765323638916s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.24919939041137695s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.575336694717407s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 73.11423754692078s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.6162340641021729s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.36029505729675293s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.7083892822265625s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.32937192916870117s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.27670907974243164s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5246872901916504s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.509497880935669s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 107.71482300758362s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 12.078312397003174s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4302089214324951s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2495279312133789s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2762746810913086s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.314507961273193s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.885422945022583s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6526284217834473s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.3641359806060791s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 64.86949324607849s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.3729045391082764s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.312130928039551s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.2980353832244873s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.53234791755676s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.700169563293457s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.45207858085632324s
Security | Sign check for Bio2RDF::Dbsnp took 0.27161264419555664s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 10.03843879699707s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.45499396324157715s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020888566970825195s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.389617919921875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 47.79227638244629s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1065.6909544467926s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.4937608242034912s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0005838871002197266s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 19.002009391784668s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2319412231445312s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 45.99036526679993s
Interoperability | New terms check for Bio2RDF::Drugbank took 45.33941435813904s
Versatility | Languages check for Bio2RDF::Drugbank took 60.22698521614075s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.265857458114624s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.15558314323425293s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.2773292064666748s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.31473875045776367s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.362476348876953s
License | MR license check for Bio2RDF::Drugbank took 0.40104174613952637s
License | HR license check for Bio2RDF::Drugbank took 60.24940752983093s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.24709630012512207s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.02141547203064s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5974748134613037s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.27145862579345703s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.27301478385925293s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2566652297973633s
Performance | Throughput check for Bio2RDF::Drugbank took 11.238115787506104s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 73.04161047935486s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.7209177017211914s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.3466312885284424s
Interlinking | skos check for Bio2RDF::Drugbank took 0.7116978168487549s
Interlinking | skos check for Bio2RDF::Drugbank took 0.34421491622924805s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.27498388290405273s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5066690444946289s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5312559604644775s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 109.810800075531s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 29.12691354751587s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.39331626892089844s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.2518784999847412s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.24556612968444824s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 6.8011274337768555s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8843438625335693s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6543903350830078s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.3868279457092285s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.17993116378784s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.381660223007202s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.105303525924683s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3235483169555664s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.56829810142517s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6834559440612793s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.4820544719696045s
Security | Sign check for Bio2RDF::Drugbank took 0.2664036750793457s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 10.321435689926147s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.5102989673614502s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011205673217773438s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 62.163596630096436s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1107.9876317977905s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.4763481616973877s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0005159378051757812s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.7426655292511s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2469902038574219s
Amount of data | Number of triples check for Bio2RDF::Genage took 45.74519062042236s
Interoperability | New terms check for Bio2RDF::Genage took 41.02241659164429s
Versatility | Languages check for Bio2RDF::Genage took 60.25967741012573s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.25887227058410645s
Security | Check HTTPS for Bio2RDF::Genage took 0.16755270957946777s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.24326848983764648s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3113985061645508s
Availability | RDF dump link check for Bio2RDF::Genage took 2.593173027038574s
License | MR license check for Bio2RDF::Genage took 0.35212230682373047s
License | HR license check for Bio2RDF::Genage took 60.25450372695923s
Amount of data | Number of property check for Bio2RDF::Genage took 0.25118041038513184s
Understandability | Number of label check for Bio2RDF::Genage took 9.091917753219604s
Understandability | URI regex check for Bio2RDF::Genage took 0.6123805046081543s
Understandability | Vocabs check for Bio2RDF::Genage took 0.25304150581359863s
Verifiability | Authors check for Bio2RDF::Genage took 0.24858379364013672s
Verifiability | Publishers check for Bio2RDF::Genage took 0.26071691513061523s
Performance | Throughput check for Bio2RDF::Genage took 11.937902450561523s
Amount of data | Check the number of entities for Bio2RDF::Genage took 75.07318139076233s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.5680844783782959s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3453803062438965s
Interlinking | skos check for Bio2RDF::Genage took 0.6079230308532715s
Interlinking | skos check for Bio2RDF::Genage took 0.33836841583251953s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.258502721786499s
Currency | Creation date check for Bio2RDF::Genage took 0.5420215129852295s
Currency | Modification date check for Bio2RDF::Genage took 0.49228978157043457s
Rep.Conc. | URIs length for Bio2RDF::Genage took 108.15869474411011s
Interoperability | New vocabularies check for Bio2RDF::Genage took 59.325774908065796s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4852588176727295s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.27463269233703613s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.23811578750610352s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 6.287843704223633s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8872144222259521s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6517894268035889s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.37205076217651367s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.09933614730835s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.376760721206665s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.229389190673828s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.2812302112579346s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.575042486190796s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.6962733268737793s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.7531108856201172s
Security | Sign check for Bio2RDF::Genage took 0.26741647720336914s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 9.914732217788696s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.5142114162445068s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.91278076171875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 49.0285005569458s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-genage took 1118.4201006889343s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.47321295738220215s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0003457069396972656s
Extra | Recovery of all triples for Bio2RDF::Gendr took 19.24678897857666s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2366888523101807s
Amount of data | Number of triples check for Bio2RDF::Gendr took 45.71253490447998s
Interoperability | New terms check for Bio2RDF::Gendr took 42.41323494911194s
Versatility | Languages check for Bio2RDF::Gendr took 60.236021995544434s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2747819423675537s
Security | Check HTTPS for Bio2RDF::Gendr took 0.15598201751708984s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.5453200340270996s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.3051464557647705s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.414569139480591s
License | MR license check for Bio2RDF::Gendr took 0.46014857292175293s
License | HR license check for Bio2RDF::Gendr took 60.25482654571533s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.25272274017333984s
Understandability | Number of label check for Bio2RDF::Gendr took 9.896794557571411s
Understandability | URI regex check for Bio2RDF::Gendr took 0.6033148765563965s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.24431586265563965s
Verifiability | Authors check for Bio2RDF::Gendr took 0.25647592544555664s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2655303478240967s
Performance | Throughput check for Bio2RDF::Gendr took 12.060482501983643s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 74.5155074596405s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.6085796356201172s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.38951754570007324s
Interlinking | skos check for Bio2RDF::Gendr took 0.5604391098022461s
Interlinking | skos check for Bio2RDF::Gendr took 0.3461172580718994s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2530801296234131s
Currency | Creation date check for Bio2RDF::Gendr took 0.5159423351287842s
Currency | Modification date check for Bio2RDF::Gendr took 0.5402367115020752s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 108.68536734580994s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 53.36272644996643s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.43949460983276367s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.267101526260376s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.23716235160827637s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 6.41417670249939s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8804917335510254s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6616017818450928s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.25762176513671875s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.19575071334839s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.373013496398926s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 5.922003269195557s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.278975009918213s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.52299451828003s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.6881880760192871s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.7272653579711914s
Security | Sign check for Bio2RDF::Gendr took 0.2600438594818115s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 11.780073881149292s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.3946683406829834s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.021106481552124023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 55.12851858139038s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-gendr took 1123.3286001682281s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.47011661529541016s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0006806850433349609s
Extra | Recovery of all triples for Bio2RDF::Goa took 18.441070079803467s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2327313423156738s
Amount of data | Number of triples check for Bio2RDF::Goa took 46.5189483165741s
Interoperability | New terms check for Bio2RDF::Goa took 40.516098976135254s
Versatility | Languages check for Bio2RDF::Goa took 60.26139569282532s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.26775360107421875s
Security | Check HTTPS for Bio2RDF::Goa took 0.16644620895385742s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.2486727237701416s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.3358731269836426s
Availability | RDF dump link check for Bio2RDF::Goa took 2.2118630409240723s
License | MR license check for Bio2RDF::Goa took 0.2614767551422119s
License | HR license check for Bio2RDF::Goa took 60.24953818321228s
Amount of data | Number of property check for Bio2RDF::Goa took 0.2854750156402588s
Understandability | Number of label check for Bio2RDF::Goa took 9.430996894836426s
Understandability | URI regex check for Bio2RDF::Goa took 0.5730836391448975s
Understandability | Vocabs check for Bio2RDF::Goa took 0.23482084274291992s
Verifiability | Authors check for Bio2RDF::Goa took 0.2618753910064697s
Verifiability | Publishers check for Bio2RDF::Goa took 0.2569923400878906s
Performance | Throughput check for Bio2RDF::Goa took 11.700096845626831s
Amount of data | Check the number of entities for Bio2RDF::Goa took 76.59666347503662s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.5751361846923828s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3742194175720215s
Interlinking | skos check for Bio2RDF::Goa took 0.575594425201416s
Interlinking | skos check for Bio2RDF::Goa took 0.38115358352661133s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.259075403213501s
Currency | Creation date check for Bio2RDF::Goa took 0.5197012424468994s
Currency | Modification date check for Bio2RDF::Goa took 0.5207486152648926s
Rep.Conc. | URIs length for Bio2RDF::Goa took 106.0743055343628s
Interoperability | New vocabularies check for Bio2RDF::Goa took 55.432331800460815s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.4405250549316406s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.28323841094970703s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.29483795166015625s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.1194469928741455s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8781583309173584s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.667635440826416s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4026033878326416s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.78491258621216s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.400075912475586s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.072027206420898s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3595302104949951s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.537383794784546s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.708275318145752s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 1.5346612930297852s
Security | Sign check for Bio2RDF::Goa took 0.25038838386535645s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 12.03108525276184s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.5057380199432373s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 47.20408248901367s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-goa took 1124.3908867835999s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.4890289306640625s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0005190372467041016s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 19.29412865638733s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.20424485206604s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 45.54819893836975s
Interoperability | New terms check for Bio2RDF::Hgnc took 41.990142583847046s
Versatility | Languages check for Bio2RDF::Hgnc took 60.29448056221008s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2627096176147461s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.1566758155822754s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.5500218868255615s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.32878875732421875s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.467249631881714s
License | MR license check for Bio2RDF::Hgnc took 0.26003050804138184s
License | HR license check for Bio2RDF::Hgnc took 60.26439452171326s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.25884556770324707s
Understandability | Number of label check for Bio2RDF::Hgnc took 10.13651156425476s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5759975910186768s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.26035547256469727s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.26543140411376953s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.26398253440856934s
Performance | Throughput check for Bio2RDF::Hgnc took 11.640903949737549s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 75.10571098327637s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.6766276359558105s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.34107470512390137s
Interlinking | skos check for Bio2RDF::Hgnc took 0.8258852958679199s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3361513614654541s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2452540397644043s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5433053970336914s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5261404514312744s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 106.95009446144104s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 44.939940452575684s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.4266059398651123s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.27486729621887207s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2626078128814697s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 6.772284984588623s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8805429935455322s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6642677783966064s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.28894805908203125s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.39509797096252s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.3863277435302734s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 5.963590860366821s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3204772472381592s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.587337255477905s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7112894058227539s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.620262861251831s
Security | Sign check for Bio2RDF::Hgnc took 0.2689945697784424s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 10.63846468925476s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.4067251682281494s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011610984802246094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 61.67665123939514s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.621246337890625e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1116.5168962478638s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.47568678855895996s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006642341613769531s
Extra | Recovery of all triples for Bio2RDF::Homologene took 17.957377433776855s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.1947333812713623s
Amount of data | Number of triples check for Bio2RDF::Homologene took 46.23893213272095s
Interoperability | New terms check for Bio2RDF::Homologene took 39.69195342063904s
Versatility | Languages check for Bio2RDF::Homologene took 60.2351438999176s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.26031041145324707s
Security | Check HTTPS for Bio2RDF::Homologene took 0.1555800437927246s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.2542436122894287s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.29851317405700684s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.3378982543945312s
License | MR license check for Bio2RDF::Homologene took 0.3738088607788086s
License | HR license check for Bio2RDF::Homologene took 60.27512192726135s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.24285507202148438s
Understandability | Number of label check for Bio2RDF::Homologene took 10.260889768600464s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5734944343566895s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.24582552909851074s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2562863826751709s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.2499070167541504s
Performance | Throughput check for Bio2RDF::Homologene took 11.408925533294678s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 75.96999168395996s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.7048943042755127s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.2801511287689209s
Interlinking | skos check for Bio2RDF::Homologene took 0.9548733234405518s
Interlinking | skos check for Bio2RDF::Homologene took 0.33745884895324707s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.24766325950622559s
Currency | Creation date check for Bio2RDF::Homologene took 0.517136812210083s
Currency | Modification date check for Bio2RDF::Homologene took 0.5113937854766846s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 107.22642350196838s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 57.08851909637451s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.39803624153137207s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.26700615882873535s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.25492334365844727s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 6.877171277999878s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.879080057144165s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6535720825195312s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.39687442779541016s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.17085099220276s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.402373790740967s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.14297080039978s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.2900733947753906s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.53765869140625s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7108385562896729s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.6365587711334229s
Security | Sign check for Bio2RDF::Homologene took 0.2791416645050049s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 24.156943559646606s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.4594733715057373s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020174264907836914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 59.732470750808716s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-homologene took 1138.074180841446s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 1.283515214920044s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0005793571472167969s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.604922771453857s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2093603610992432s
Amount of data | Number of triples check for Bio2RDF::Interpro took 45.720216035842896s
Interoperability | New terms check for Bio2RDF::Interpro took 40.99107789993286s
Versatility | Languages check for Bio2RDF::Interpro took 60.25808644294739s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.27089762687683105s
Security | Check HTTPS for Bio2RDF::Interpro took 0.15660333633422852s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.24458885192871094s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.3242647647857666s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.4715914726257324s
License | MR license check for Bio2RDF::Interpro took 0.37310290336608887s
License | HR license check for Bio2RDF::Interpro took 60.24423933029175s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2497570514678955s
Understandability | Number of label check for Bio2RDF::Interpro took 9.74422812461853s
Understandability | URI regex check for Bio2RDF::Interpro took 0.6014723777770996s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2448880672454834s
Verifiability | Authors check for Bio2RDF::Interpro took 0.259796142578125s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.2557222843170166s
Performance | Throughput check for Bio2RDF::Interpro took 11.032907962799072s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 73.32984256744385s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.5749108791351318s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.38002800941467285s
Interlinking | skos check for Bio2RDF::Interpro took 0.937096357345581s
Interlinking | skos check for Bio2RDF::Interpro took 0.3402538299560547s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2473287582397461s
Currency | Creation date check for Bio2RDF::Interpro took 0.5160651206970215s
Currency | Modification date check for Bio2RDF::Interpro took 0.4963951110839844s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 108.14135146141052s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 58.84733176231384s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.4368860721588135s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.29149675369262695s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2801344394683838s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.0045366287231445s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8801796436309814s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6569502353668213s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.39440226554870605s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.17264318466187s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.4075090885162354s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.003176689147949s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.2852485179901123s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.58733057975769s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7275562286376953s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.7467164993286133s
Security | Sign check for Bio2RDF::Interpro took 0.258195161819458s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 21.273879051208496s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.36813783645629883s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 9.441375732421875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 54.48777437210083s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-interpro took 1131.0137729644775s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.13866543769836426s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.30680274963378906s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.534027099609375e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-iproclass took 16.745225429534912s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.48250365257263184s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.000583648681640625s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 19.246268272399902s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2776734828948975s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 45.84745144844055s
Interoperability | New terms check for Bio2RDF::Irefindex took 39.804617404937744s
Versatility | Languages check for Bio2RDF::Irefindex took 60.24345517158508s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2581446170806885s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.1556081771850586s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.43477511405944824s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3001389503479004s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.2407190799713135s
License | MR license check for Bio2RDF::Irefindex took 0.37595415115356445s
License | HR license check for Bio2RDF::Irefindex took 60.25395393371582s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2452080249786377s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.301524639129639s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5424017906188965s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.2596609592437744s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.26722121238708496s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2599666118621826s
Performance | Throughput check for Bio2RDF::Irefindex took 11.288082361221313s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 73.87007331848145s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6168239116668701s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.35104799270629883s
Interlinking | skos check for Bio2RDF::Irefindex took 0.7454612255096436s
Interlinking | skos check for Bio2RDF::Irefindex took 0.35529112815856934s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2605750560760498s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5336441993713379s
Currency | Modification date check for Bio2RDF::Irefindex took 0.512641191482544s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 112.11630320549011s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 19.389753103256226s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.4438910484313965s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.273665189743042s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.274341344833374s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 6.323785781860352s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8873729705810547s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6402161121368408s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.39615488052368164s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 64.80138301849365s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.364302635192871s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.507680416107178s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.2710387706756592s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.504921197891235s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.6955327987670898s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.39944887161254883s
Security | Sign check for Bio2RDF::Irefindex took 0.2515530586242676s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 11.888588905334473s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.6018552780151367s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 14.894241571426392s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1045.2437176704407s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.1461803913116455s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.29503726959228516s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020165205001831055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 9.342594146728516s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.49457597732543945s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0007357597351074219s
Extra | Recovery of all triples for Bio2RDF::Lsr took 18.9925057888031s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2701473236083984s
Amount of data | Number of triples check for Bio2RDF::Lsr took 46.88761830329895s
Interoperability | New terms check for Bio2RDF::Lsr took 43.94781255722046s
Versatility | Languages check for Bio2RDF::Lsr took 60.25890302658081s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2696068286895752s
Security | Check HTTPS for Bio2RDF::Lsr took 0.1441020965576172s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.3523745536804199s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3028852939605713s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.376854181289673s
License | MR license check for Bio2RDF::Lsr took 0.3372223377227783s
License | HR license check for Bio2RDF::Lsr took 60.26464915275574s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.28095364570617676s
Understandability | Number of label check for Bio2RDF::Lsr took 10.669897556304932s
Understandability | URI regex check for Bio2RDF::Lsr took 0.583721399307251s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.24767446517944336s
Verifiability | Authors check for Bio2RDF::Lsr took 0.24905824661254883s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.2655344009399414s
Performance | Throughput check for Bio2RDF::Lsr took 10.795125007629395s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 75.35672760009766s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.633439302444458s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3614833354949951s
Interlinking | skos check for Bio2RDF::Lsr took 0.7048916816711426s
Interlinking | skos check for Bio2RDF::Lsr took 0.4101574420928955s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.2646934986114502s
Currency | Creation date check for Bio2RDF::Lsr took 0.4965786933898926s
Currency | Modification date check for Bio2RDF::Lsr took 0.49070143699645996s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 109.90508937835693s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 56.12092566490173s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.3914523124694824s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.2893054485321045s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.272571325302124s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 6.4774205684661865s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8896968364715576s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6423544883728027s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.29369616508483887s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.40971302986145s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.406752824783325s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.393131494522095s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.2997314929962158s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.54131627082825s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.6995606422424316s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 1.5418198108673096s
Security | Sign check for Bio2RDF::Lsr took 0.24363183975219727s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 10.501546621322632s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.37694787979125977s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 53.816527366638184s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-lsr took 1126.4148752689362s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.47029924392700195s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0006144046783447266s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.903980255126953s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2331223487854004s
Amount of data | Number of triples check for Bio2RDF::Mesh took 46.403188705444336s
Interoperability | New terms check for Bio2RDF::Mesh took 40.89220142364502s
Versatility | Languages check for Bio2RDF::Mesh took 60.246943950653076s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.27373647689819336s
Security | Check HTTPS for Bio2RDF::Mesh took 0.15618419647216797s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.26375794410705566s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.30850672721862793s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.337449073791504s
License | MR license check for Bio2RDF::Mesh took 0.24649381637573242s
License | HR license check for Bio2RDF::Mesh took 60.247905254364014s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.291717529296875s
Understandability | Number of label check for Bio2RDF::Mesh took 9.80046820640564s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5547654628753662s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.2559351921081543s
Verifiability | Authors check for Bio2RDF::Mesh took 0.2677011489868164s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2521986961364746s
Performance | Throughput check for Bio2RDF::Mesh took 11.297579526901245s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 70.86861753463745s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.600287914276123s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.2685220241546631s
Interlinking | skos check for Bio2RDF::Mesh took 0.7193267345428467s
Interlinking | skos check for Bio2RDF::Mesh took 0.375429630279541s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.2556345462799072s
Currency | Creation date check for Bio2RDF::Mesh took 0.5085186958312988s
Currency | Modification date check for Bio2RDF::Mesh took 0.5090687274932861s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 109.18958353996277s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 52.42094898223877s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.4303627014160156s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.256725549697876s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.23792076110839844s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 6.751848220825195s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8896071910858154s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6595640182495117s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.24800777435302734s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 66.17390608787537s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.352997064590454s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.7187180519104s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3179922103881836s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.55882525444031s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.685490608215332s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.6048316955566406s
Security | Sign check for Bio2RDF::Mesh took 0.25110602378845215s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 10.441234350204468s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.5236999988555908s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 8.487701416015625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 49.35849142074585s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-mesh took 1110.3562035560608s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.4868912696838379s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0005807876586914062s
Extra | Recovery of all triples for Bio2RDF::Mgi took 20.188698291778564s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2728397846221924s
Amount of data | Number of triples check for Bio2RDF::Mgi took 45.35864329338074s
Interoperability | New terms check for Bio2RDF::Mgi took 40.34458661079407s
Versatility | Languages check for Bio2RDF::Mgi took 60.286351442337036s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.26000142097473145s
Security | Check HTTPS for Bio2RDF::Mgi took 0.15698957443237305s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.2757110595703125s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.31287550926208496s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.184845209121704s
License | MR license check for Bio2RDF::Mgi took 0.3705434799194336s
License | HR license check for Bio2RDF::Mgi took 60.25754475593567s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.25638389587402344s
Understandability | Number of label check for Bio2RDF::Mgi took 9.433365821838379s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5632896423339844s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.2489469051361084s
Verifiability | Authors check for Bio2RDF::Mgi took 0.2474045753479004s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2658243179321289s
Performance | Throughput check for Bio2RDF::Mgi took 11.038413286209106s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 75.54073452949524s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.5964763164520264s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.2771313190460205s
Interlinking | skos check for Bio2RDF::Mgi took 0.5723519325256348s
Interlinking | skos check for Bio2RDF::Mgi took 0.36550474166870117s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.24538159370422363s
Currency | Creation date check for Bio2RDF::Mgi took 0.5022430419921875s
Currency | Modification date check for Bio2RDF::Mgi took 0.48323893547058105s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 50.3984649181366s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 56.48430156707764s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.4222376346588135s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.24772095680236816s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.28621506690979004s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 6.617829322814941s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8795504570007324s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6622743606567383s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.40930962562561035s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 64.80089259147644s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.38574481010437s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 5.732599258422852s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3338067531585693s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.576786041259766s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7228481769561768s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.42313289642333984s
Security | Sign check for Bio2RDF::Mgi took 0.2506828308105469s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 11.326823472976685s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.39255666732788086s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.298324584960938e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 55.17823934555054s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-mgi took 1063.5591502189636s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.4971144199371338s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0005905628204345703s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 17.994016408920288s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.3069381713867188s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 45.33000683784485s
Interoperability | New terms check for Bio2RDF::Ncbigene took 40.18102431297302s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.25418400764465s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.29312753677368164s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.1468820571899414s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.25484371185302734s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.30741381645202637s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.3796019554138184s
License | MR license check for Bio2RDF::Ncbigene took 0.3541097640991211s
License | HR license check for Bio2RDF::Ncbigene took 60.23103213310242s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.24961256980895996s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.464719772338867s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5935664176940918s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.2632417678833008s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2581655979156494s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2573258876800537s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.145334243774414s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 72.2112557888031s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.6184420585632324s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.37731027603149414s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.6506879329681396s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.37722253799438477s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2363910675048828s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5005457401275635s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5065877437591553s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 107.88353443145752s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 53.141780853271484s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4388740062713623s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.28584766387939453s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.272019624710083s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 6.772206783294678s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8931601047515869s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6558835506439209s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.28186607360839844s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.64938688278198s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.384007453918457s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.3612847328186035s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.2788383960723877s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.59931564331055s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.6916754245758057s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.600316047668457s
Security | Sign check for Bio2RDF::Ncbigene took 0.2569541931152344s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 10.041480302810669s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.5724749565124512s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00011324882507324219s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 57.01956486701965s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1119.1779086589813s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.47280430793762207s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0005891323089599609s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.52771306037903s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2362964153289795s
Amount of data | Number of triples check for Bio2RDF::Ndc took 46.02092623710632s
Interoperability | New terms check for Bio2RDF::Ndc took 39.55720853805542s
Versatility | Languages check for Bio2RDF::Ndc took 60.23887276649475s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2859318256378174s
Security | Check HTTPS for Bio2RDF::Ndc took 0.15648245811462402s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.38443875312805176s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.3107776641845703s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.1845436096191406s
License | MR license check for Bio2RDF::Ndc took 0.340839147567749s
License | HR license check for Bio2RDF::Ndc took 60.26991009712219s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.26480674743652344s
Understandability | Number of label check for Bio2RDF::Ndc took 9.28476095199585s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5981695652008057s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2636415958404541s
Verifiability | Authors check for Bio2RDF::Ndc took 0.25464892387390137s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.26993346214294434s
Performance | Throughput check for Bio2RDF::Ndc took 11.319535732269287s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 75.90294337272644s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.5758039951324463s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.2858445644378662s
Interlinking | skos check for Bio2RDF::Ndc took 0.5588767528533936s
Interlinking | skos check for Bio2RDF::Ndc took 0.33518218994140625s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.26543378829956055s
Currency | Creation date check for Bio2RDF::Ndc took 0.5105788707733154s
Currency | Modification date check for Bio2RDF::Ndc took 0.5242254734039307s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 108.10576605796814s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 53.07450866699219s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.44847893714904785s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2717256546020508s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.25623059272766113s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 6.5858519077301025s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8882408142089844s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6592097282409668s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.2953317165374756s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 64.93601751327515s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.373211622238159s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.001803874969482s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3291335105895996s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.58615708351135s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.715519905090332s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.5817439556121826s
Security | Sign check for Bio2RDF::Ndc took 0.2527179718017578s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 10.669372320175171s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.3857400417327881s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.3882598876953125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 41.3976891040802s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-ndc took 1100.5347573757172s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.1397080421447754s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.3117496967315674s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 6.67572021484375e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-nextprot took 3.7035915851593018s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.471602201461792s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0005631446838378906s
Extra | Recovery of all triples for Bio2RDF::Omim took 19.680700302124023s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.279104232788086s
Amount of data | Number of triples check for Bio2RDF::Omim took 46.072774171829224s
Interoperability | New terms check for Bio2RDF::Omim took 39.331480741500854s
Versatility | Languages check for Bio2RDF::Omim took 60.27719807624817s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2834022045135498s
Security | Check HTTPS for Bio2RDF::Omim took 0.1672060489654541s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.37948179244995117s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.29979991912841797s
Availability | RDF dump link check for Bio2RDF::Omim took 2.3328278064727783s
License | MR license check for Bio2RDF::Omim took 0.35129857063293457s
License | HR license check for Bio2RDF::Omim took 60.2404944896698s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2377331256866455s
Understandability | Number of label check for Bio2RDF::Omim took 9.554757356643677s
Understandability | URI regex check for Bio2RDF::Omim took 0.5598866939544678s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2584671974182129s
Verifiability | Authors check for Bio2RDF::Omim took 0.26674675941467285s
Verifiability | Publishers check for Bio2RDF::Omim took 0.25638747215270996s
Performance | Throughput check for Bio2RDF::Omim took 11.427392482757568s
Amount of data | Check the number of entities for Bio2RDF::Omim took 76.47601199150085s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.5810561180114746s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.37404799461364746s
Interlinking | skos check for Bio2RDF::Omim took 0.5652725696563721s
Interlinking | skos check for Bio2RDF::Omim took 0.3915069103240967s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.2554633617401123s
Currency | Creation date check for Bio2RDF::Omim took 0.5254316329956055s
Currency | Modification date check for Bio2RDF::Omim took 0.5278234481811523s
Rep.Conc. | URIs length for Bio2RDF::Omim took 107.32067775726318s
Interoperability | New vocabularies check for Bio2RDF::Omim took 52.20886754989624s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4250223636627197s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.24978971481323242s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2843508720397949s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.767128944396973s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8845117092132568s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6605277061462402s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.27997684478759766s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 64.8659815788269s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.3643558025360107s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.355136156082153s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3030774593353271s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.504125118255615s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.6956474781036377s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 1.3705623149871826s
Security | Sign check for Bio2RDF::Omim took 0.27189135551452637s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 9.984183311462402s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.4523277282714844s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00012993812561035156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 56.8340699672699s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-omim took 1115.8160407543182s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.458427429199219e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.30815935134887695s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.022532939910888672s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 5.507469177246094e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 3.0405116081237793s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.4617195129394531s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0005648136138916016s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.124494075775146s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2686407566070557s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 45.750956773757935s
Interoperability | New terms check for Bio2RDF::Orphanet took 39.65471863746643s
Versatility | Languages check for Bio2RDF::Orphanet took 60.25851321220398s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.2690558433532715s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.16558361053466797s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.45745253562927246s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.29806065559387207s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.446727752685547s
License | MR license check for Bio2RDF::Orphanet took 0.5158624649047852s
License | HR license check for Bio2RDF::Orphanet took 60.269110441207886s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.26860499382019043s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.828901529312134s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5773406028747559s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.24158334732055664s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.2672274112701416s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2671318054199219s
Performance | Throughput check for Bio2RDF::Orphanet took 10.761744976043701s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 74.9020483493805s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.6024892330169678s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.35147762298583984s
Interlinking | skos check for Bio2RDF::Orphanet took 0.6739559173583984s
Interlinking | skos check for Bio2RDF::Orphanet took 0.325045108795166s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2646000385284424s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5188517570495605s
Currency | Modification date check for Bio2RDF::Orphanet took 0.52986741065979s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 111.47031688690186s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 55.2221782207489s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.40213727951049805s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.29100775718688965s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2771141529083252s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.243413686752319s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8904085159301758s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.663250207901001s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.40398693084716797s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.17734003067017s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.352677822113037s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.380468130111694s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.2664084434509277s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.50192904472351s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.6853735446929932s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.6352279186248779s
Security | Sign check for Bio2RDF::Orphanet took 0.26754331588745117s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 11.135751724243164s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.4703395366668701s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.082389831542969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 53.292181730270386s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1122.9050979614258s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.13811731338500977s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.31966137886047363s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.02112865447998047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.393718242645264s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.46239352226257324s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0006625652313232422s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 18.528918504714966s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2587687969207764s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 45.877426862716675s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 40.09286713600159s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.258872509002686s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.27316880226135254s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.14604806900024414s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.38744235038757324s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.3191068172454834s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.4850902557373047s
License | MR license check for Bio2RDF::Pharmgkb took 0.4167323112487793s
License | HR license check for Bio2RDF::Pharmgkb took 60.250638246536255s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.27631425857543945s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.712162017822266s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5872454643249512s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.23424720764160156s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.24350500106811523s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.2768666744232178s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.431630373001099s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 75.70447278022766s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.5703811645507812s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.33872437477111816s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.7295107841491699s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.3692636489868164s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2550039291381836s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.505354642868042s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5134329795837402s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 106.6257553100586s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 58.64997100830078s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4805870056152344s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2915782928466797s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.2816784381866455s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.005430221557617s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8917160034179688s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6638548374176025s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.3600335121154785s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.55638766288757s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4117794036865234s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.0214574337005615s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.2733776569366455s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.50703454017639s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.691699743270874s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.7373733520507812s
Security | Sign check for Bio2RDF::Pharmgkb took 0.26999855041503906s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 24.308269262313843s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.4980440139770508s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.176399230957031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 32.85855317115784s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1114.2024295330048s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.48932909965515137s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0004305839538574219s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 18.159292697906494s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2483282089233398s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 45.84176731109619s
Interoperability | New terms check for Bio2RDF::Pubmed took 39.77212452888489s
Versatility | Languages check for Bio2RDF::Pubmed took 60.258546590805054s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.26685619354248047s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.145890474319458s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.3700590133666992s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.32172250747680664s
Availability | RDF dump link check for Bio2RDF::Pubmed took 2.390516757965088s
License | MR license check for Bio2RDF::Pubmed took 0.3777451515197754s
License | HR license check for Bio2RDF::Pubmed took 60.24827432632446s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.24260711669921875s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.697646617889404s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5719351768493652s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.25361132621765137s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.25433874130249023s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.26783061027526855s
Performance | Throughput check for Bio2RDF::Pubmed took 11.893593311309814s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 70.91579580307007s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.550471305847168s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.39807701110839844s
Interlinking | skos check for Bio2RDF::Pubmed took 0.845625638961792s
Interlinking | skos check for Bio2RDF::Pubmed took 0.3409545421600342s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.23379731178283691s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5250024795532227s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5034639835357666s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 108.29820656776428s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 50.51306915283203s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.45539188385009766s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.2852752208709717s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.25310826301574707s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 6.9721245765686035s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8858492374420166s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6432750225067139s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.3574545383453369s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 64.97937846183777s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.354524612426758s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 5.852366209030151s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.3322086334228516s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.55937337875366s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.6845440864562988s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.631145715713501s
Security | Sign check for Bio2RDF::Pubmed took 0.24888825416564941s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 13.830378770828247s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.41067051887512207s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020882129669189453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.000141143798828125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 33.4621205329895s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1087.3851482868195s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.1385200023651123s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.32065534591674805s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020905733108520508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 8.034706115722656e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-sabiork took 9.454082489013672s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.4856891632080078s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0005841255187988281s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.748538970947266s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2690908908843994s
Amount of data | Number of triples check for Bio2RDF::Sgd took 45.91003394126892s
Interoperability | New terms check for Bio2RDF::Sgd took 40.26835918426514s
Versatility | Languages check for Bio2RDF::Sgd took 60.24722218513489s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.28632116317749023s
Security | Check HTTPS for Bio2RDF::Sgd took 0.15837526321411133s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.5863523483276367s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.31708621978759766s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.5194478034973145s
License | MR license check for Bio2RDF::Sgd took 0.5218286514282227s
License | HR license check for Bio2RDF::Sgd took 60.256693601608276s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2567870616912842s
Understandability | Number of label check for Bio2RDF::Sgd took 9.34118103981018s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5697872638702393s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.23636865615844727s
Verifiability | Authors check for Bio2RDF::Sgd took 0.2398991584777832s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.2600715160369873s
Performance | Throughput check for Bio2RDF::Sgd took 10.771528244018555s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 74.40188121795654s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.6086452007293701s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3654496669769287s
Interlinking | skos check for Bio2RDF::Sgd took 0.854503870010376s
Interlinking | skos check for Bio2RDF::Sgd took 0.3486175537109375s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2755405902862549s
Currency | Creation date check for Bio2RDF::Sgd took 0.4966576099395752s
Currency | Modification date check for Bio2RDF::Sgd took 0.5115463733673096s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 109.42237329483032s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 46.631460428237915s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.40362071990966797s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.26596784591674805s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2471606731414795s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.087282180786133s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.9080290794372559s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6637105941772461s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.3121354579925537s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 64.83056092262268s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.3548245429992676s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.232617616653442s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3037853240966797s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.5205442905426s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7138960361480713s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.5973036289215088s
Security | Sign check for Bio2RDF::Sgd took 0.24856233596801758s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 16.285466194152832s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.5550382137298584s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010204315185546875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 46.860732078552246s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-sgd took 1103.3673467636108s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 9.584426879882812e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.30402684211730957s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.838539123535156e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 3.1147658824920654s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.4788022041320801s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006270408630371094s
Extra | Recovery of all triples for Bio2RDF::Sider took 18.939218759536743s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2251200675964355s
Amount of data | Number of triples check for Bio2RDF::Sider took 44.61715364456177s
Interoperability | New terms check for Bio2RDF::Sider took 40.2256383895874s
Versatility | Languages check for Bio2RDF::Sider took 60.23610019683838s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.25745105743408203s
Security | Check HTTPS for Bio2RDF::Sider took 0.16707348823547363s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.3722686767578125s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3205714225769043s
Availability | RDF dump link check for Bio2RDF::Sider took 2.433626890182495s
License | MR license check for Bio2RDF::Sider took 0.2722494602203369s
License | HR license check for Bio2RDF::Sider took 60.24244737625122s
Amount of data | Number of property check for Bio2RDF::Sider took 0.286454439163208s
Understandability | Number of label check for Bio2RDF::Sider took 9.636592149734497s
Understandability | URI regex check for Bio2RDF::Sider took 0.586432695388794s
Understandability | Vocabs check for Bio2RDF::Sider took 0.26364707946777344s
Verifiability | Authors check for Bio2RDF::Sider took 0.25075459480285645s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2634086608886719s
Performance | Throughput check for Bio2RDF::Sider took 11.044713973999023s
Amount of data | Check the number of entities for Bio2RDF::Sider took 75.05657601356506s
Verifiability | Contribs. check for Bio2RDF::Sider took 1.3747467994689941s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3632621765136719s
Interlinking | skos check for Bio2RDF::Sider took 0.8385043144226074s
Interlinking | skos check for Bio2RDF::Sider took 0.34955525398254395s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2652015686035156s
Currency | Creation date check for Bio2RDF::Sider took 0.49672913551330566s
Currency | Modification date check for Bio2RDF::Sider took 0.5036525726318359s
Rep.Conc. | URIs length for Bio2RDF::Sider took 109.53589987754822s
Interoperability | New vocabularies check for Bio2RDF::Sider took 43.67571568489075s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.44971799850463867s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.22882437705993652s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.23782110214233398s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 6.25999116897583s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.886420726776123s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6587107181549072s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.36409449577331543s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.1050488948822s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.385629177093506s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 5.952588319778442s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.2661793231964111s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.505263328552246s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.6852335929870605s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.608844518661499s
Security | Sign check for Bio2RDF::Sider took 0.24865365028381348s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 11.649985551834106s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.4517488479614258s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020913362503051758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 52.4863543510437s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-sider took 1109.3173224925995s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 9.179115295410156e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.2988739013671875s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.00067901611328125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.076957702636719e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-taxon took 2.9372060298919678s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.4912991523742676s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006396770477294922s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 20.126118183135986s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2349178791046143s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 45.48813724517822s
Interoperability | New terms check for Bio2RDF::Taxonomy took 42.02009463310242s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.26781129837036s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.28368258476257324s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.16048622131347656s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.2683982849121094s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.31653714179992676s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.366208076477051s
License | MR license check for Bio2RDF::Taxonomy took 0.6509888172149658s
License | HR license check for Bio2RDF::Taxonomy took 60.25325274467468s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2465801239013672s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.386980533599854s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.573352575302124s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.25090837478637695s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.23858976364135742s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.23599720001220703s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.425402164459229s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 75.26141238212585s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.7064473628997803s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.2569453716278076s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.6439774036407471s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.3570842742919922s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.25279879570007324s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5373146533966064s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.4874567985534668s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 106.39790987968445s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 54.962157249450684s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.45052289962768555s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.27722716331481934s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.27852630615234375s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.438732624053955s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8959159851074219s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6510865688323975s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.39038968086242676s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 64.53916335105896s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.3831048011779785s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 5.971171617507935s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.2904996871948242s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.50158357620239s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.6941919326782227s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.607335090637207s
Security | Sign check for Bio2RDF::Taxonomy took 0.2638983726501465s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 12.120306253433228s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.4936854839324951s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010347366333007812s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 56.57001447677612s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.9073486328125e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1126.1751747131348s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.13883137702941895s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0007240772247314453s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.2797367572784424s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020019054412841797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 17.03444480895996s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.4573233127593994s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006966590881347656s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 17.97390127182007s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2513511180877686s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.604928970336914s
Interoperability | New terms check for Bio2RDF::Wormbase took 41.580810546875s
Versatility | Languages check for Bio2RDF::Wormbase took 60.243351221084595s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.27812695503234863s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.14464402198791504s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.3846113681793213s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.3110463619232178s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.404247522354126s
License | MR license check for Bio2RDF::Wormbase took 0.39789247512817383s
License | HR license check for Bio2RDF::Wormbase took 60.26959180831909s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.2411975860595703s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.716621160507202s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5679779052734375s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.27317333221435547s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.25369906425476074s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.265531063079834s
Performance | Throughput check for Bio2RDF::Wormbase took 11.034584760665894s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 72.34588313102722s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.7249305248260498s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.34990525245666504s
Interlinking | skos check for Bio2RDF::Wormbase took 0.43084168434143066s
Interlinking | skos check for Bio2RDF::Wormbase took 0.34749865531921387s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.2557840347290039s
Currency | Creation date check for Bio2RDF::Wormbase took 0.504798412322998s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5190021991729736s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 107.73021912574768s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 54.570284605026245s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.4034097194671631s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2583010196685791s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.24292397499084473s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.309627294540405s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8892896175384521s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6494486331939697s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.40026402473449707s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.03387784957886s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.38232684135437s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.414772987365723s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.2608168125152588s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.53000044822693s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.6899020671844482s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.6092307567596436s
Security | Sign check for Bio2RDF::Wormbase took 0.2681729793548584s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 10.395548343658447s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.40039753913879395s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.700920104980469e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 55.41937255859375s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1118.8552687168121s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.4345855712890625e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.29846954345703125s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.02015972137451172s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.1920928955078125e-05s
Believability | Calculation of trust value for Biografías y Vidas took 1.1205673217773438e-05s
INFO | --- Analysis for biografiasyvidas took 2.7401363849639893s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.2673757076263428s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.2976975440979004s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.368492126464844e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 9.298324584960938e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 2.955455780029297s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 5.9604644775390625e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.37630510330200195s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.021187305450439453s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.719329833984375e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.1920928955078125e-05s
INFO | --- Analysis for biolod-pdb took 7.652187824249268s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6164751052856445s
Availability | VoID file availability check for BioModels RDF took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2904376983642578s
Reputation | Calculation of the PageRank for BioModels RDF took 0.02023768424987793s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.528594970703125e-05s
Believability | Calculation of trust value for BioModels RDF took 1.1205673217773438e-05s
INFO | --- Analysis for biomodels-rdf took 4.0377442836761475s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.280078172683716s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.00037860870361328125s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2929203510284424s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020709991455078125s
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.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.3909759521484375e-06s
INFO | --- Analysis for Biop took 6.325512886047363s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.00011920928955078125s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0012640953063964844s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.3285186290740967s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.361701965332031e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.5020370483398438e-05s
INFO | --- Analysis for Bioportal took 2.961516857147217s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 9.036064147949219e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.3260066509246826s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.021149158477783203s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006139278411865234s
Believability | Calculation of trust value for Amphibian gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-aao took 3.0851376056671143s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.315376281738281e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2881319522857666s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02230215072631836s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00030517578125s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-aba took 2.966649293899536s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 9.894371032714844e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2882499694824219s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020815610885620117s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0014901161193847656s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-acgt took 2.9602720737457275s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 0.00010561943054199219s
Availability | VoID file availability check for Animal natural history and life history took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.2761971950531006s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.00031685829162597656s
Believability | Calculation of trust value for Animal natural history and life history took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-adw took 2.953958034515381s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 0.00012302398681640625s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.31067585945129395s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.022515296936035156s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0009539127349853516s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0005235671997070312s
Believability | Calculation of trust value for Anatomical Entity Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-aeo took 3.028749465942383s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.3396148681640625s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02146768569946289s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009562969207763672s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-aero took 3.083232879638672s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.458427429199219e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.28862786293029785s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.02097296714782715s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0003933906555175781s
Believability | Calculation of trust value for AI/RHEUM took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-air took 3.218194007873535s
Availability | SPARQL endpoint availability check for Amino Acid took 8.487701416015625e-05s
Availability | VoID file availability check for Amino Acid took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.3153400421142578s
Reputation | Calculation of the PageRank for Amino Acid took 0.020734310150146484s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002567768096923828s
Believability | Calculation of trust value for Amino Acid took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-amino-acid took 3.019157886505127s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 8.416175842285156e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.2850921154022217s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020217418670654297s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002932548522949219s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-apo took 2.9331183433532715s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 0.000148773193359375s
Availability | VoID file availability check for African Traditional Medicine took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.3180735111236572s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020972251892089844s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0009815692901611328s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00029468536376953125s
Believability | Calculation of trust value for African Traditional Medicine took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-atmo took 3.020059585571289s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.57763671875e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.00035500526428222656s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.3183739185333252s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.320808410644531e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ato took 2.93255877494812s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.31904101371765137s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.021829605102539062s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013260841369628906s
Believability | Calculation of trust value for BioAssay Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bao took 3.0326931476593018s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.38690185546875e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2984044551849365s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003733634948730469s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.916332244873047s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.3187732696533203s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.021178483963012695s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003209114074707031s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bcgo took 2.992872714996338s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.3071117401123047s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0013599395751953125s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bdo took 2.9952588081359863s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2801210880279541s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.024104595184326172s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005056858062744141s
Believability | Calculation of trust value for Basic Formal Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-bfo took 3.0019190311431885s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.2438507080078125e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0004096031188964844s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.3329660892486572s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.02156352996826172s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007221698760986328s
Believability | Calculation of trust value for Bleeding History Phenotype took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bho took 3.0356242656707764s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 9.107589721679688e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.2970407009124756s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.022322893142700195s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0010864734649658203s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0005137920379638672s
Believability | Calculation of trust value for Bilateria anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bila took 2.8955554962158203s
Availability | SPARQL endpoint availability check for BIRNLex took 4.363059997558594e-05s
Availability | VoID file availability check for BIRNLex took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.28716397285461426s
Reputation | Calculation of the PageRank for BIRNLex took 0.02110600471496582s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014770030975341797s
Believability | Calculation of trust value for BIRNLex took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-birnlex took 3.0246541500091553s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0003616809844970703s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2984921932220459s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007157325744628906s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-bootstrep took 3.0086488723754883s
Availability | SPARQL endpoint availability check for BioPAX took 4.124641418457031e-05s
Availability | VoID file availability check for BioPAX took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2981135845184326s
Reputation | Calculation of the PageRank for BioPAX took 0.020270824432373047s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.322166442871094e-05s
Believability | Calculation of trust value for BioPAX took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bp took 2.941051721572876s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0008940696716308594s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2921926975250244s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.025170326232910156s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0011272430419921875s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0004220008850097656s
Believability | Calculation of trust value for Biomedical Resource Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.844301223754883s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.27536559104919434s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.02190089225769043s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00020360946655273438s
Believability | Calculation of trust value for Spatial Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-bspo took 2.9831442832946777s
Availability | SPARQL endpoint availability check for BioTop took 4.38690185546875e-05s
Availability | VoID file availability check for BioTop took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for BioTop took 0.30855607986450195s
Reputation | Calculation of the PageRank for BioTop took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for BioTop took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006737709045410156s
Believability | Calculation of trust value for BioTop took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-bt took 3.0315968990325928s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 8.893013000488281e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.34241223335266113s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008544921875s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-bto took 3.066826105117798s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 0.00010061264038085938s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3357663154602051s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.021007537841796875s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018372535705566406s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-canco took 3.4816555976867676s
Availability | SPARQL endpoint availability check for CAO took 8.678436279296875e-05s
Availability | VoID file availability check for CAO took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for CAO took 0.301511287689209s
Reputation | Calculation of the PageRank for CAO took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for CAO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CAO took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005872249603271484s
Believability | Calculation of trust value for CAO took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cao took 3.0215811729431152s
Availability | SPARQL endpoint availability check for CareLex took 0.00010752677917480469s
Availability | VoID file availability check for CareLex took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for CareLex took 0.27447080612182617s
Reputation | Calculation of the PageRank for CareLex took 0.02097797393798828s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.9114227294921875e-05s
Believability | Calculation of trust value for CareLex took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-carelex took 3.000168561935425s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.30615830421447754s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.021366357803344727s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007762908935546875s
Believability | Calculation of trust value for Cell Cycle Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cco took 2.9156179428100586s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.28348231315612793s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.02187061309814453s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00026988983154296875s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cdao took 2.906886577606201s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 7.557868957519531e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0004119873046875s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.287278413772583s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.0202939510345459s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007698535919189453s
Believability | Calculation of trust value for Chemical entities of biological interest took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-chebi took 2.8714101314544678s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 8.726119995117188e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.272857666015625s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020992279052734375s
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.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002493858337402344s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.8688578605651855s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.27508115768432617s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020241260528564453s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007469654083251953s
Believability | Calculation of trust value for Chemical Information Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cheminf took 2.957594394683838s
Availability | SPARQL endpoint availability check for Cell type took 9.655952453613281e-05s
Availability | VoID file availability check for Cell type took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Cell type took 0.2981083393096924s
Reputation | Calculation of the PageRank for Cell type took 0.020816564559936523s
Interlinking | Calculation of Degree of Connection for Cell type took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell type took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00037217140197753906s
Believability | Calculation of trust value for Cell type took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cl took 2.9788482189178467s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.33612823486328125s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020669937133789062s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008006095886230469s
Believability | Calculation of trust value for Cell Line Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-clo took 3.052849054336548s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.36707258224487305s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020587921142578125s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017118453979492188s
Believability | Calculation of trust value for Clinical Measurement Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-cmo took 2.9396188259124756s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.3159475326538086s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.02145695686340332s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00020575523376464844s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-cno took 3.0427393913269043s
Availability | SPARQL endpoint availability check for Wheat trait took 4.7206878662109375e-05s
Availability | VoID file availability check for Wheat trait took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.28668761253356934s
Reputation | Calculation of the PageRank for Wheat trait took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.364418029785156e-05s
Believability | Calculation of trust value for Wheat trait took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.9850375652313232s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.1961669921875e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.3215813636779785s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02087879180908203s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00033473968505859375s
Believability | Calculation of trust value for Cognitive Atlas took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-cogat took 3.0746288299560547s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2821159362792969s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007328987121582031s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-cogpo took 2.9676623344421387s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 5.4836273193359375e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.27196383476257324s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020790576934814453s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004177093505859375s
Believability | Calculation of trust value for Current Procedural Terminology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cpt took 2.8633792400360107s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.6253204345703125e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3580806255340576s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017557144165039062s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-csp took 3.4303982257843018s
Availability | SPARQL endpoint availability check for COSTART took 4.410743713378906e-05s
Availability | VoID file availability check for COSTART took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for COSTART took 0.30008697509765625s
Reputation | Calculation of the PageRank for COSTART took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for COSTART took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COSTART took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009784698486328125s
Believability | Calculation of trust value for COSTART took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-cst took 2.9594995975494385s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 9.202957153320312e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.33376193046569824s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.022355318069458008s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005030632019042969s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ctcae took 2.940842866897583s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 9.179115295410156e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.290802001953125s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004436969757080078s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ctx took 3.0292015075683594s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.410743713378906e-05s
Availability | VoID file availability check for Dendritic cell took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.3090956211090088s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0002894401550292969s
Believability | Calculation of trust value for Dendritic cell took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.9911797046661377s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 8.726119995117188e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.32705140113830566s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 9.417533874511719e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ddanat took 3.010270595550537s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.5299530029296875e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.29959630966186523s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009241104125976562s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ddi took 3.0459213256835938s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.29343366622924805s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.021850109100341797s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.845329284667969e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-diagnosticont took 2.9219424724578857s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 9.417533874511719e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.30031871795654297s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.02162480354309082s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001614093780517578s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 3.0067217350006104s
Availability | SPARQL endpoint availability check for Human disease ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2974131107330322s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006284713745117188s
Believability | Calculation of trust value for Human disease ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-doid took 2.986372470855713s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.29320788383483887s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.021210432052612305s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007848739624023438s
Believability | Calculation of trust value for Electrocardiography Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ecg took 2.984951972961426s
Availability | SPARQL endpoint availability check for Evidence codes took 4.57763671875e-05s
Availability | VoID file availability check for Evidence codes took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.3018016815185547s
Reputation | Calculation of the PageRank for Evidence codes took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.123283386230469e-05s
Believability | Calculation of trust value for Evidence codes took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-eco took 3.0017189979553223s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 8.487701416015625e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.35223913192749023s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0016925334930419922s
Believability | Calculation of trust value for Experimental Factor Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-efo took 3.444293975830078s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.363059997558594e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.3289823532104492s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011539459228515625s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ehda took 2.9938812255859375s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.2438507080078125e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.3052816390991211s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020337581634521484s
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.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007059574127197266s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ehdaa took 3.020240545272827s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 8.702278137207031e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.3191194534301758s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.02020549774169922s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.000518798828125s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 3.0080060958862305s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 8.487701416015625e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.3361492156982422s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.021404504776000977s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.2901763916015625e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-emap took 3.0493156909942627s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Environment Ontology took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.27550315856933594s
Reputation | Calculation of the PageRank for Environment Ontology took 0.021910667419433594s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00038886070251464844s
Believability | Calculation of trust value for Environment Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-envo took 3.0356953144073486s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 8.940696716308594e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.28608059883117676s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02131056785583496s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0002961158752441406s
Believability | Calculation of trust value for Plant environmental conditions took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-eo took 2.975269317626953s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.27597665786743164s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012056827545166016s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ep took 2.99922513961792s
Availability | SPARQL endpoint availability check for Epilepsy took 4.315376281738281e-05s
Availability | VoID file availability check for Epilepsy took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.28783369064331055s
Reputation | Calculation of the PageRank for Epilepsy took 0.02325296401977539s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00012636184692382812s
Believability | Calculation of trust value for Epilepsy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-epileponto took 3.0045533180236816s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 8.511543273925781e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.30110597610473633s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011570453643798828s
Believability | Calculation of trust value for eagle-i research resource ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ero took 2.998199224472046s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 8.749961853027344e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.27818846702575684s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.021004438400268555s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011022090911865234s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ev took 2.8716976642608643s
Availability | SPARQL endpoint availability check for ExO took 8.940696716308594e-05s
Availability | VoID file availability check for ExO took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for ExO took 0.29468488693237305s
Reputation | Calculation of the PageRank for ExO took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for ExO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00024008750915527344s
Believability | Calculation of trust value for ExO took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-exo took 3.050896167755127s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.601478576660156e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.30108642578125s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.021055936813354492s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011086463928222656s
Believability | Calculation of trust value for Fungal gross anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-fao took 2.9463961124420166s
Availability | SPARQL endpoint availability check for Biological imaging methods took 9.369850158691406e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.29839444160461426s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020825624465942383s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00022339820861816406s
Believability | Calculation of trust value for Biological imaging methods took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-fbbi took 3.130143642425537s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.29139041900634766s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.0217745304107666s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006232261657714844s
Believability | Calculation of trust value for Drosophila gross anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-fbbt took 3.051746368408203s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.4345855712890625e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.29161810874938965s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.021509647369384766s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004451274871826172s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fbcv took 2.999925374984741s
Availability | SPARQL endpoint availability check for Drosophila development took 4.410743713378906e-05s
Availability | VoID file availability check for Drosophila development took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.33691835403442383s
Reputation | Calculation of the PageRank for Drosophila development took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.601478576660156e-05s
Believability | Calculation of trust value for Drosophila development took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-fbdv took 2.9111337661743164s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.506111145019531e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.27695226669311523s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020758867263793945s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003693103790283203s
Believability | Calculation of trust value for Fly taxonomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-fbsp took 2.8669559955596924s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.38690185546875e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2869884967803955s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.022313833236694336s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022125244140625s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.9523797035217285s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.29267406463623047s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0003998279571533203s
Believability | Calculation of trust value for Family Health History Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-fhho took 2.9573349952697754s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.3268706798553467s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.021336078643798828s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0011000633239746094s
Believability | Calculation of trust value for Influenza Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-flu took 3.0659844875335693s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.2854752540588379s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.021830320358276367s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.270408630371094e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fma took 2.856403350830078s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.30553150177001953s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.021638870239257812s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00012683868408203125s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fypo took 2.9804036617279053s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.2912940979003906s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 8.940696716308594e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-geospecies took 2.99638032913208s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.49762535095214844s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.02277541160583496s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0001590251922607422s
Believability | Calculation of trust value for General Formal Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-gfo took 3.218878984451294s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.363059997558594e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2932896614074707s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.022640228271484375s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006048679351806641s
Believability | Calculation of trust value for General Formal Ontology: Biology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.86629319190979s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.410743713378906e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.28168749809265137s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020878076553344727s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008444786071777344s
Believability | Calculation of trust value for Gene Ontology Extension took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.95559024810791s
Availability | SPARQL endpoint availability check for Gene Ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Gene Ontology took 0.0010874271392822266s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.33867406845092773s
Reputation | Calculation of the PageRank for Gene Ontology took 0.0220186710357666s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008370876312255859s
Believability | Calculation of trust value for Gene Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-go_x2 took 3.0734901428222656s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 8.797645568847656e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.29277849197387695s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.021126985549926758s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.24249267578125e-05s
Believability | Calculation of trust value for Cereal Plant Development took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-gro took 2.9675276279449463s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.3166828155517578s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.021639347076416016s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004367828369140625s
Believability | Calculation of trust value for Cereal plant gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.9679505825042725s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 5.221366882324219e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2889547348022461s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020671844482421875s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007274150848388672s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.894016742706299s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.28851938247680664s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005550384521484375s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-hao took 2.888108491897583s
Availability | SPARQL endpoint availability check for HCPCS took 4.315376281738281e-05s
Availability | VoID file availability check for HCPCS took 0.0011358261108398438s
Completeness | Calculation of interlinking completeness for HCPCS took 0.28484535217285156s
Reputation | Calculation of the PageRank for HCPCS took 0.02097606658935547s
Interlinking | Calculation of Degree of Connection for HCPCS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for HCPCS took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002193450927734375s
Believability | Calculation of trust value for HCPCS took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.9034993648529053s
Availability | SPARQL endpoint availability check for Health Level Seven took 8.845329284667969e-05s
Availability | VoID file availability check for Health Level Seven took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.2769930362701416s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02030324935913086s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012652873992919922s
Believability | Calculation of trust value for Health Level Seven took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-hl7 took 2.9856607913970947s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 9.799003601074219e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2846660614013672s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020284652709960938s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003445148468017578s
Believability | Calculation of trust value for HEALTH_INDICATORS took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.7332658767700195s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2854170799255371s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.02061295509338379s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.075599670410156e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hom took 2.9127447605133057s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.3392181396484375e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.3183295726776123s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 2.9087066650390625e-05s
Believability | Calculation of trust value for HOM-HARVARD took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.9063305854797363s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.29755091667175293s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020786046981811523s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006477832794189453s
Believability | Calculation of trust value for Human Phenotype Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-hp_x1 took 3.198094606399536s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.2771875858306885s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02023792266845703s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010004043579101562s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hpio took 2.8798940181732178s
Availability | SPARQL endpoint availability check for HUGO took 8.749961853027344e-05s
Availability | VoID file availability check for HUGO took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for HUGO took 0.30754923820495605s
Reputation | Calculation of the PageRank for HUGO took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for HUGO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HUGO took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.295608520507812e-05s
Believability | Calculation of trust value for HUGO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hugo took 2.984632968902588s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0003905296325683594s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.2772097587585449s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006434917449951172s
Believability | Calculation of trust value for Information Artifact Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-iao took 2.884871006011963s
Availability | SPARQL endpoint availability check for ICD10 took 4.8160552978515625e-05s
Availability | VoID file availability check for ICD10 took 0.0003886222839355469s
Completeness | Calculation of interlinking completeness for ICD10 took 0.3032519817352295s
Reputation | Calculation of the PageRank for ICD10 took 0.020407915115356445s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007963180541992188s
Believability | Calculation of trust value for ICD10 took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-icd10 took 2.8821120262145996s
Availability | SPARQL endpoint availability check for ICD10CM took 7.605552673339844e-05s
Availability | VoID file availability check for ICD10CM took 0.00039458274841308594s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.3249485492706299s
Reputation | Calculation of the PageRank for ICD10CM took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006096363067626953s
Believability | Calculation of trust value for ICD10CM took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.929421901702881s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 8.296966552734375e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.288837194442749s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.0001518726348876953s
Believability | Calculation of trust value for ICD-10-PCS took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icd10pcs took 3.0572009086608887s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.2438507080078125e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.00041103363037109375s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.2867848873138428s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020174503326416016s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006403923034667969s
Believability | Calculation of trust value for International Classification of Diseases took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.9069535732269287s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.291534423828125e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0004222393035888672s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.2798285484313965s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004355907440185547s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.844071388244629s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 8.535385131835938e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.3008148670196533s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012230873107910156s
Believability | Calculation of trust value for International Classification for Nursing Practice took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-icnp took 3.01664662361145s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.363059997558594e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.3054635524749756s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00045013427734375s
Believability | Calculation of trust value for International Classification of Primary Care took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icpc took 2.959502935409546s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 7.510185241699219e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2797069549560547s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.02038407325744629s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008533000946044922s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.9394657611846924s
Availability | SPARQL endpoint availability check for ICPS Network took 4.1484832763671875e-05s
Availability | VoID file availability check for ICPS Network took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2873106002807617s
Reputation | Calculation of the PageRank for ICPS Network took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.000217437744140625s
Believability | Calculation of trust value for ICPS Network took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icps took 2.7707791328430176s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.283797025680542s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.02021193504333496s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008380413055419922s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ido took 2.918802499771118s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.00036716461181640625s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.28311657905578613s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02032780647277832s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011081695556640625s
Believability | Calculation of trust value for Brucellosis Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-idobru took 2.850088119506836s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Malaria Ontology took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2679152488708496s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013031959533691406s
Believability | Calculation of trust value for Malaria Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-idomal took 2.8885157108306885s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 7.534027099609375e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2970311641693115s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020305395126342773s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003037452697753906s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-iev took 2.9538683891296387s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.8160552978515625e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.2693772315979004s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.022121667861938477s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00014734268188476562s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-imgt took 3.0252785682678223s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 8.702278137207031e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2942826747894287s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020764589309692383s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005238056182861328s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-imr took 2.949276924133301s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 5.1975250244140625e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.28896260261535645s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007572174072265625s
Believability | Calculation of trust value for Interaction Network Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ino took 2.9351747035980225s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 0.00014328956604003906s
Availability | VoID file availability check for Hewan Invertebrata took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2974555492401123s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.021504878997802734s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.0040740966796875e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-invertebrata took 3.084653377532959s
Availability | SPARQL endpoint availability check for IxnO took 8.797645568847656e-05s
Availability | VoID file availability check for IxnO took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for IxnO took 0.30582118034362793s
Reputation | Calculation of the PageRank for IxnO took 0.021975994110107422s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IxnO took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018525123596191406s
Believability | Calculation of trust value for IxnO took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ixno took 2.935044288635254s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.673004150390625e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2680063247680664s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020825862884521484s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00037479400634765625s
Believability | Calculation of trust value for SysMO-JERM took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-jerm took 2.892151117324829s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.28696274757385254s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020838260650634766s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-kisao took 2.89361572265625s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 0.0001163482666015625s
Availability | VoID file availability check for Loggerhead nesting took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2863476276397705s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.022502422332763672s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00019931793212890625s
Believability | Calculation of trust value for Loggerhead nesting took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-lhn took 2.886899709701538s
Availability | SPARQL endpoint availability check for Lipid Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.31232333183288574s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0001983642578125s
Believability | Calculation of trust value for Lipid Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-lipro took 2.936643362045288s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.5299530029296875e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.36046814918518066s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.021253585815429688s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018167495727539062s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-lnc took 3.4106154441833496s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.57763671875e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2788088321685791s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006690025329589844s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ma took 2.9691414833068848s
Availability | SPARQL endpoint availability check for Multiple alignment took 8.916854858398438e-05s
Availability | VoID file availability check for Multiple alignment took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2976405620574951s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00019979476928710938s
Believability | Calculation of trust value for Multiple alignment took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mao took 2.945831537246704s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 8.940696716308594e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.3027939796447754s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020191431045532227s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006773471832275391s
Believability | Calculation of trust value for Minimal anatomical terminology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mat took 2.9094340801239014s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 8.7738037109375e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0011208057403564453s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.2760343551635742s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.000415802001953125s
Believability | Calculation of trust value for Breast tissue cell lines took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.8857460021972656s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.27146387100219727s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007312297821044922s
Believability | Calculation of trust value for Cell line ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mccl took 2.9981160163879395s
Availability | SPARQL endpoint availability check for Cell line ontology took 0.0001773834228515625s
Availability | VoID file availability check for Cell line ontology took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.29541730880737305s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021636247634887695s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.001432180404663086s
Believability | Calculation of trust value for Cell line ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.982253074645996s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.267692565917969e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.28559017181396484s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00023174285888671875s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mcv took 3.2236268520355225s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.7206878662109375e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2933061122894287s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02186274528503418s
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.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00017189979553222656s
Believability | Calculation of trust value for Master Drug Data Base took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mddb took 2.9292855262756348s
Availability | SPARQL endpoint availability check for MedDRA took 4.315376281738281e-05s
Availability | VoID file availability check for MedDRA took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for MedDRA took 0.29732227325439453s
Reputation | Calculation of the PageRank for MedDRA took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011548995971679688s
Believability | Calculation of trust value for MedDRA took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-mdr took 2.9342780113220215s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.220008850097656e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.29277515411376953s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02211308479309082s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008821487426757812s
Believability | Calculation of trust value for MedlinePlus Health Topics took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.926724433898926s
Availability | SPARQL endpoint availability check for MeGO took 4.363059997558594e-05s
Availability | VoID file availability check for MeGO took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for MeGO took 0.31865882873535156s
Reputation | Calculation of the PageRank for MeGO took 0.02046489715576172s
Interlinking | Calculation of Degree of Connection for MeGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014472007751464844s
Believability | Calculation of trust value for MeGO took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mego took 3.0499041080474854s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.315376281738281e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.35462284088134766s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.001804351806640625s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mesh-owl took 3.3537895679473877s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 9.965896606445312e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2828822135925293s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020203113555908203s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006372928619384766s
Believability | Calculation of trust value for Mental Functioning Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mf took 2.8934102058410645s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 0.00011014938354492188s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2871830463409424s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.021497488021850586s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005555152893066406s
Believability | Calculation of trust value for Medaka fish anatomy and development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mfo took 2.933317184448242s
Availability | SPARQL endpoint availability check for Emotion Ontology took 0.0001201629638671875s
Availability | VoID file availability check for Emotion Ontology took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.28626179695129395s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007314682006835938s
Believability | Calculation of trust value for Emotion Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mfoem took 2.861961841583252s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2985239028930664s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010323524475097656s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mhc took 3.022573947906494s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.3392181396484375e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.26910877227783203s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.021173954010009766s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006515979766845703s
Believability | Calculation of trust value for Protein-protein interaction took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mi took 3.018859624862671s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 9.059906005859375e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2908151149749756s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020708322525024414s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0006995201110839844s
Believability | Calculation of trust value for Mosquito insecticide resistance took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-miro took 3.0230414867401123s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.275432825088501s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001323223114013672s
Believability | Calculation of trust value for Measurement Method Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mmo took 2.911813974380493s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.34532666206359863s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003917217254638672s
Believability | Calculation of trust value for MGED Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mo took 2.9949252605438232s
Availability | SPARQL endpoint availability check for Protein modification took 8.702278137207031e-05s
Availability | VoID file availability check for Protein modification took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2881913185119629s
Reputation | Calculation of the PageRank for Protein modification took 0.021600961685180664s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.000225067138671875s
Believability | Calculation of trust value for Protein modification took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mod took 2.952092170715332s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.482269287109375e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.3072941303253174s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.022637367248535156s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0007665157318115234s
Believability | Calculation of trust value for Mammalian phenotype took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mp took 3.0179502964019775s
Availability | SPARQL endpoint availability check for Mouse pathology took 8.916854858398438e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.29823923110961914s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004801750183105469s
Believability | Calculation of trust value for Mouse pathology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mpath took 2.980780839920044s
Availability | SPARQL endpoint availability check for Mass spectrometry took 0.0001068115234375s
Availability | VoID file availability check for Mass spectrometry took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.30373287200927734s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.021357297897338867s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.00035452842712402344s
Believability | Calculation of trust value for Mass spectrometry took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ms took 2.928502321243286s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 0.00016069412231445312s
Availability | VoID file availability check for Medical Subject Headings took 0.0003540515899658203s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.35146045684814453s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018870830535888672s
Believability | Calculation of trust value for Medical Subject Headings took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-msh took 3.483640193939209s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 7.891654968261719e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0003724098205566406s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2717766761779785s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0001976490020751953s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mthch took 2.9551920890808105s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.3143293857574463s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.02028632164001465s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007741451263427734s
Believability | Calculation of trust value for Natural Products Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-natpro took 2.928760528564453s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.744529724121094e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.30004358291625977s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0007958412170410156s
Believability | Calculation of trust value for NCBI organismal classification took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ncbitaxon took 3.0132124423980713s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 9.131431579589844e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.34420156478881836s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02103114128112793s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0019686222076416016s
Believability | Calculation of trust value for NCI Thesaurus took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ncit took 3.5362441539764404s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.267692565917969e-05s
Availability | VoID file availability check for National Drug Data File took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.27333974838256836s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020351886749267578s
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.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006282329559326172s
Believability | Calculation of trust value for National Drug Data File took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nddf took 2.9568421840667725s
Availability | SPARQL endpoint availability check for National Drug File took 4.482269287109375e-05s
Availability | VoID file availability check for National Drug File took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for National Drug File took 0.3058140277862549s
Reputation | Calculation of the PageRank for National Drug File took 0.021076679229736328s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012247562408447266s
Believability | Calculation of trust value for National Drug File took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.8863255977630615s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.363059997558594e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.290691614151001s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011692047119140625s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-nemo_x1 took 3.028566598892212s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.314624547958374s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.021305084228515625s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006492137908935547s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-neomark took 3.0049567222595215s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.3049466609954834s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.0001227855682373047s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-neomarkontology took 3.0285041332244873s
Availability | SPARQL endpoint availability check for NIFSTD took 8.821487426757812e-05s
Availability | VoID file availability check for NIFSTD took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.3443899154663086s
Reputation | Calculation of the PageRank for NIFSTD took 0.021982431411743164s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0010807514190673828s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0020875930786132812s
Believability | Calculation of trust value for NIFSTD took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-nif took 3.3097198009490967s
Availability | SPARQL endpoint availability check for NIF Cell took 4.458427429199219e-05s
Availability | VoID file availability check for NIF Cell took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.3100855350494385s
Reputation | Calculation of the PageRank for NIF Cell took 0.021095752716064453s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013210773468017578s
Believability | Calculation of trust value for NIF Cell took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.957951545715332s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.363059997558594e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.2976233959197998s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.021735429763793945s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014488697052001953s
Believability | Calculation of trust value for NIF Dysfunction took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-nif_dysfunction took 3.243394613265991s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2949538230895996s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.0206143856048584s
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.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005521774291992188s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nigo took 3.084061861038208s
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.0005254745483398438s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.29210782051086426s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005314350128173828s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nmr took 3.050495147705078s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.28960204124450684s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.0001087188720703125s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.8993654251098633s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.31819844245910645s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.021869659423828125s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0012106895446777344s
Believability | Calculation of trust value for NanoParticle Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-npo took 2.9948782920837402s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 8.96453857421875e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.3362152576446533s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02034139633178711s
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.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007293224334716797s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-oae took 2.9806020259857178s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 5.316734313964844e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.278275728225708s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.021022319793701172s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.00147247314453125s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-obi took 2.959475517272949s
Availability | SPARQL endpoint availability check for OBOE took 5.626678466796875e-05s
Availability | VoID file availability check for OBOE took 0.0011212825775146484s
Completeness | Calculation of interlinking completeness for OBOE took 0.2773137092590332s
Reputation | Calculation of the PageRank for OBOE took 0.020424365997314453s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.0001125335693359375s
Believability | Calculation of trust value for OBOE took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-oboe took 2.952345371246338s
Availability | SPARQL endpoint availability check for OBOE SBC took 5.125999450683594e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.28861308097839355s
Reputation | Calculation of the PageRank for OBOE SBC took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007686614990234375s
Believability | Calculation of trust value for OBOE SBC took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.947213888168335s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 8.678436279296875e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.3048369884490967s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.02243781089782715s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005731582641601562s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ocre took 2.8435075283050537s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 8.940696716308594e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2900352478027344s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008370876312255859s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-odgi took 2.8887104988098145s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 8.511543273925781e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.3114349842071533s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.021793603897094727s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008604526519775391s
Believability | Calculation of trust value for Ontology for Genetic Interval took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ogi took 2.9465067386627197s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 8.630752563476562e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.30090999603271484s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00029850006103515625s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ogmd took 2.914935350418091s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.3145327568054199s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.021552085876464844s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0010056495666503906s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0007750988006591797s
Believability | Calculation of trust value for Ontology for General Medical Science took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ogms took 2.9490296840667725s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 9.059906005859375e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.29053401947021484s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020982027053833008s
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.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0012669563293457031s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-omim took 2.912487745285034s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 8.821487426757812e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.282149076461792s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.022278308868408203s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 3.0040740966796875e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.00037169456481933594s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-omit took 2.9963443279266357s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.57763671875e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.27271223068237305s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02085566520690918s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005955696105957031s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-omrse took 2.6749348640441895s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 8.440017700195312e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.32393741607666016s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02064824104309082s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007836818695068359s
Believability | Calculation of trust value for Ontology of Data Mining took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ontodm took 2.983461380004883s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 9.250640869140625e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.2797691822052002s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002536773681640625s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ontodt took 3.7276053428649902s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.220008850097656e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.25660085678100586s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.02041769027709961s
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.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006163120269775391s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.870647430419922s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.458427429199219e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2938194274902344s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009191036224365234s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-opl took 2.8831470012664795s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.553794860839844e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0003771781921386719s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2676393985748291s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008645057678222656s
Believability | Calculation of trust value for Phenotypic quality took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pato took 2.9351272583007812s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.291534423828125e-05s
Availability | VoID file availability check for Physician Data Query took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2870204448699951s
Reputation | Calculation of the PageRank for Physician Data Query took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008034706115722656s
Believability | Calculation of trust value for Physician Data Query took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pdq took 2.7749578952789307s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.2438507080078125e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0003783702850341797s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2681734561920166s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020392417907714844s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008206367492675781s
Believability | Calculation of trust value for Pediatric Terminology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pedterm took 2.9867002964019775s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0003523826599121094s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.3080871105194092s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.02042102813720703s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.000186920166015625s
Believability | Calculation of trust value for Parasite Experiment Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-peo took 3.010437250137329s
Availability | SPARQL endpoint availability check for PHARE took 4.315376281738281e-05s
Availability | VoID file availability check for PHARE took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for PHARE took 0.3002498149871826s
Reputation | Calculation of the PageRank for PHARE took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for PHARE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006284713745117188s
Believability | Calculation of trust value for PHARE took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-phare took 2.9186136722564697s
Availability | SPARQL endpoint availability check for PKO_Re took 4.3392181396484375e-05s
Availability | VoID file availability check for PKO_Re took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.27359509468078613s
Reputation | Calculation of the PageRank for PKO_Re took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for PKO_Re took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001735687255859375s
Believability | Calculation of trust value for PKO_Re took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pko took 2.86024808883667s
Availability | SPARQL endpoint availability check for PMA 2010 took 5.6743621826171875e-05s
Availability | VoID file availability check for PMA 2010 took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2918534278869629s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008928775787353516s
Believability | Calculation of trust value for PMA 2010 took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-pma took 3.045292377471924s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.267692565917969e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.28449130058288574s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.021691560745239258s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00016188621520996094s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pmr took 2.8908956050872803s
Availability | SPARQL endpoint availability check for Plant Anatomy took 8.988380432128906e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2774999141693115s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020143747329711914s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0004088878631591797s
Believability | Calculation of trust value for Plant Anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-po took 2.9808897972106934s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.38690185546875e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.29160451889038086s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020919322967529297s
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.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.67572021484375e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-po_x1 took 2.9187796115875244s
Availability | SPARQL endpoint availability check for Plant Ontology took 9.489059448242188e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.3437774181365967s
Reputation | Calculation of the PageRank for Plant Ontology took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004305839538574219s
Believability | Calculation of trust value for Plant Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.994011640548706s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 9.441375732421875e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2677171230316162s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.021982192993164062s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006601810455322266s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pr took 2.9287362098693848s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 8.535385131835938e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.28878068923950195s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00025463104248046875s
Believability | Calculation of trust value for Proteomics data and process provenance took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-propreo took 2.9600565433502197s
Availability | SPARQL endpoint availability check for Pathway ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.29425525665283203s
Reputation | Calculation of the PageRank for Pathway ontology took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012135505676269531s
Believability | Calculation of trust value for Pathway ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-pw took 2.965108633041382s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.28602027893066406s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-qibo took 2.908310651779175s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.1961669921875e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3659968376159668s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.001749277114868164s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-rcd took 3.389355421066284s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 5.14984130859375e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2902817726135254s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012683868408203125s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rctontology took 2.986417293548584s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.3409709930419922s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.021728515625s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0012273788452148438s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.00013327598571777344s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-repo took 3.0192058086395264s
Availability | SPARQL endpoint availability check for Physico-chemical process took 8.821487426757812e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.31658172607421875s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.021255016326904297s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019025802612304688s
Believability | Calculation of trust value for Physico-chemical process took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rex took 3.0490829944610596s
Availability | SPARQL endpoint availability check for RadLex took 8.845329284667969e-05s
Availability | VoID file availability check for RadLex took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for RadLex took 0.28853416442871094s
Reputation | Calculation of the PageRank for RadLex took 0.02070450782775879s
Interlinking | Calculation of Degree of Connection for RadLex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0014903545379638672s
Believability | Calculation of trust value for RadLex took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-rid took 3.0018908977508545s
Availability | SPARQL endpoint availability check for RNA ontology took 8.7738037109375e-05s
Availability | VoID file availability check for RNA ontology took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.31032633781433105s
Reputation | Calculation of the PageRank for RNA ontology took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for RNA ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005316734313964844s
Believability | Calculation of trust value for RNA ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rnao took 2.968876600265503s
Availability | SPARQL endpoint availability check for Role Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Role Ontology took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.27935051918029785s
Reputation | Calculation of the PageRank for Role Ontology took 0.02232980728149414s
Interlinking | Calculation of Degree of Connection for Role Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00019168853759765625s
Believability | Calculation of trust value for Role Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-roleo took 2.9123141765594482s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.3050541877746582s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00018835067749023438s
Believability | Calculation of trust value for Rat Strain Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-rs took 2.9736976623535156s
Availability | SPARQL endpoint availability check for RxNORM took 9.822845458984375e-05s
Availability | VoID file availability check for RxNORM took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for RxNORM took 0.3113749027252197s
Reputation | Calculation of the PageRank for RxNORM took 0.021265029907226562s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006017684936523438s
Believability | Calculation of trust value for RxNORM took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rxnorm took 3.017282009124756s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 8.821487426757812e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.31714677810668945s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02125096321105957s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010101795196533203s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-sao took 3.0388972759246826s
Availability | SPARQL endpoint availability check for Systems Biology took 4.5299530029296875e-05s
Availability | VoID file availability check for Systems Biology took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.30843091011047363s
Reputation | Calculation of the PageRank for Systems Biology took 0.021089553833007812s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004343986511230469s
Believability | Calculation of trust value for Systems Biology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-sbo took 3.0542006492614746s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.2808856964111328s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.021797657012939453s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010251998901367188s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-sbro took 2.857374668121338s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.31409287452697754s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020380735397338867s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013127326965332031s
Believability | Calculation of trust value for Sleep Domain Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sdo took 3.0310657024383545s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.220008850097656e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2821033000946045s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02152562141418457s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003306865692138672s
Believability | Calculation of trust value for Sample processing and separation techniques took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-sep took 3.151308298110962s
Availability | SPARQL endpoint availability check for Student Health Record took 8.869171142578125e-05s
Availability | VoID file availability check for Student Health Record took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.28647279739379883s
Reputation | Calculation of the PageRank for Student Health Record took 0.02275848388671875s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.000965118408203125s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0005300045013427734s
Believability | Calculation of trust value for Student Health Record took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-shr took 2.9257984161376953s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 0.00010156631469726562s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0011966228485107422s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.318418025970459s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 0.00010728836059570312s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012350082397460938s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sio took 3.6874301433563232s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 8.821487426757812e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.29975318908691406s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02030324935913086s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0001938343048095703s
Believability | Calculation of trust value for Situation-Based Access Control took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sitbac took 2.9744553565979004s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 9.584426879882812e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3696897029876709s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020340681076049805s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0018994808197021484s
Believability | Calculation of trust value for SNOMED Clinical Terms took 3.147125244140625e-05s
INFO | --- Analysis for bioportal-snomedct took 3.527651309967041s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for SNP-Ontology took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.3239939212799072s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006737709045410156s
Believability | Calculation of trust value for SNP-Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-snpo took 2.9529168605804443s
Availability | SPARQL endpoint availability check for Sequence types and features took 8.96453857421875e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.3106346130371094s
Reputation | Calculation of the PageRank for Sequence types and features took 0.021290063858032227s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005605220794677734s
Believability | Calculation of trust value for Sequence types and features took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.98245906829834s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 8.654594421386719e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.33541417121887207s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.023546457290649414s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0009584426879882812s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0017249584197998047s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-sopharm took 3.5509753227233887s
Availability | SPARQL endpoint availability check for SoyOntology took 8.559226989746094e-05s
Availability | VoID file availability check for SoyOntology took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.30490779876708984s
Reputation | Calculation of the PageRank for SoyOntology took 0.02137899398803711s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001220703125s
Believability | Calculation of trust value for SoyOntology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-soy took 2.942939281463623s
Availability | SPARQL endpoint availability check for Spider Ontology took 9.131431579589844e-05s
Availability | VoID file availability check for Spider Ontology took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.27524423599243164s
Reputation | Calculation of the PageRank for Spider Ontology took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003075599670410156s
Believability | Calculation of trust value for Spider Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-spd took 2.8702285289764404s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.3187417984008789s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00026798248291015625s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-spto took 2.9732980728149414s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.289384126663208s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020479440689086914s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004482269287109375s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sso took 2.9037182331085205s
Availability | SPARQL endpoint availability check for Software Ontology took 9.322166442871094e-05s
Availability | VoID file availability check for Software Ontology took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.3045363426208496s
Reputation | Calculation of the PageRank for Software Ontology took 0.021417617797851562s
Interlinking | Calculation of Degree of Connection for Software Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004012584686279297s
Believability | Calculation of trust value for Software Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-swo took 3.0394442081451416s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 0.00014734268188476562s
Availability | VoID file availability check for Tick gross anatomy took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2773606777191162s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02254343032836914s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002353191375732422s
Believability | Calculation of trust value for Tick gross anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-tads took 3.065098285675049s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 0.00011944770812988281s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.28708648681640625s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02250385284423828s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008533000946044922s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-tao took 2.967203140258789s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 8.416175842285156e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.3040347099304199s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020812273025512695s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.988380432128906e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-taxrank took 2.971466302871704s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 0.00010585784912109375s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.31074953079223633s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.271766662597656e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 3.814697265625e-06s
INFO | --- Analysis for bioportal-teddy took 3.131289482116699s
Availability | SPARQL endpoint availability check for Time Event Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.3053295612335205s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.02054882049560547s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008111000061035156s
Believability | Calculation of trust value for Time Event Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-teo took 2.9318716526031494s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.3134431838989258s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020287036895751953s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00038909912109375s
Believability | Calculation of trust value for Mosquito gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-tgma took 2.9719109535217285s
Availability | SPARQL endpoint availability check for thesaurus took 9.322166442871094e-05s
Availability | VoID file availability check for thesaurus took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for thesaurus took 0.3112661838531494s
Reputation | Calculation of the PageRank for thesaurus took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.413459777832031e-05s
Believability | Calculation of trust value for thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.8891518115997314s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.124641418457031e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.2950742244720459s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020249366760253906s
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.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003466606140136719s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.8893778324127197s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 9.369850158691406e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.32991671562194824s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008273124694824219s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-tmo took 2.9851937294006348s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2867088317871094s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015425682067871094s
Believability | Calculation of trust value for Plant Trait Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-to took 2.925966739654541s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2922804355621338s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020407915115356445s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001747608184814453s
Believability | Calculation of trust value for TOK_Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-tok took 2.986477851867676s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 8.630752563476562e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.28880882263183594s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.0001995563507080078s
Believability | Calculation of trust value for Teleost taxonomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-tto took 2.971585512161255s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.3219130039215088s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.02145242691040039s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010287761688232422s
Believability | Calculation of trust value for Uber anatomy ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-uberon took 2.990304708480835s
Availability | SPARQL endpoint availability check for Units Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Units Ontology took 0.0013980865478515625s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.2845923900604248s
Reputation | Calculation of the PageRank for Units Ontology took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0009961128234863281s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00027179718017578125s
Believability | Calculation of trust value for Units Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-unitsontology took 3.0589523315429688s
Availability | SPARQL endpoint availability check for Units of measurement took 8.559226989746094e-05s
Availability | VoID file availability check for Units of measurement took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.28863978385925293s
Reputation | Calculation of the PageRank for Units of measurement took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002765655517578125s
Believability | Calculation of trust value for Units of measurement took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-uo took 2.930124521255493s
Availability | SPARQL endpoint availability check for VANDF took 7.939338684082031e-05s
Availability | VoID file availability check for VANDF took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for VANDF took 0.2759106159210205s
Reputation | Calculation of the PageRank for VANDF took 0.021065950393676758s
Interlinking | Calculation of Degree of Connection for VANDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006785392761230469s
Believability | Calculation of trust value for VANDF took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-vandf took 3.168184995651245s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.3166084289550781s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00041937828063964844s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-vao took 3.030041217803955s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 9.059906005859375e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.3417940139770508s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006327629089355469s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-vhog took 2.9441418647766113s
Availability | SPARQL endpoint availability check for VIVO took 7.081031799316406e-05s
Availability | VoID file availability check for VIVO took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for VIVO took 0.3043832778930664s
Reputation | Calculation of the PageRank for VIVO took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003681182861328125s
Believability | Calculation of trust value for VIVO took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vivo took 2.950932264328003s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.3006558418273926s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012259483337402344s
Believability | Calculation of trust value for Vaccine Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-vo took 2.845827579498291s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.301206111907959s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.021537303924560547s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020170211791992188s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-vt took 2.792736291885376s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.2438507080078125e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2926003932952881s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005085468292236328s
Believability | Calculation of trust value for C. elegans gross anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-wbbt took 3.043530225753784s
Availability | SPARQL endpoint availability check for C. elegans development took 8.726119995117188e-05s
Availability | VoID file availability check for C. elegans development took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.32839226722717285s
Reputation | Calculation of the PageRank for C. elegans development took 0.020691394805908203s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.3392181396484375e-05s
Believability | Calculation of trust value for C. elegans development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-wbls took 2.96549129486084s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 8.702278137207031e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.3120138645172119s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.463859558105469e-05s
Believability | Calculation of trust value for C. elegans phenotype took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-wbphenotype took 3.0200765132904053s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.38690185546875e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.3259623050689697s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005955696105957031s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-who took 2.971029043197632s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 8.869171142578125e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.27816033363342285s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.021013975143432617s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.000995635986328125s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0007576942443847656s
Believability | Calculation of trust value for Xenopus anatomy and development took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-xao took 2.9885096549987793s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 9.560585021972656e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.287341833114624s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00023031234741210938s
Believability | Calculation of trust value for Experimental Conditions Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-xco took 2.870495557785034s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.220008850097656e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0011296272277832031s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.293834924697876s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020831823348999023s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002562999725341797s
Believability | Calculation of trust value for Yeast phenotypes took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ypo took 3.0149316787719727s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 8.988380432128906e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.2817871570587158s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020238399505615234s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007567405700683594s
Believability | Calculation of trust value for Zebrafish anatomy and development took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-zfa took 2.9599132537841797s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.124641418457031e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.28022336959838867s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.0728836059570312e-05s
INFO | --- Analysis for Bioportal_link took 4.029784917831421s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.4167311191558838s
Availability | VoID file availability check for BioSamples RDF took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.2681450843811035s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.3855438232421875e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.1920928955078125e-05s
INFO | --- Analysis for biosamples-rdf took 3.7300286293029785s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.10607719421386719s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.28761816024780273s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011086463928222656s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for bis-linked-data took 2.8315141201019287s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2889091968536377s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.022297143936157227s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.62396240234375e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for bll-thesaurus took 3.7713072299957275s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.2329761981964111s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.2745707035064697s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.341934204101562e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for bluk-bnb took 13.164963722229004s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.2823801040649414s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006122589111328125s
Extra | Recovery of all triples for Thesaurus BNCF took 46.29200887680054s
Performance | Total latancy measurement for Thesaurus BNCF took 0.665992021560669s
Amount of data | Number of triples check for Thesaurus BNCF took 0.7047483921051025s
Interoperability | New terms check for Thesaurus BNCF took 1.5061469078063965s
Versatility | Languages check for Thesaurus BNCF took 6.569253921508789s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8775572776794434s
Security | Check HTTPS for Thesaurus BNCF took 0.09504842758178711s
Interpretability | RDF structures check for Thesaurus BNCF took 0.1287088394165039s
Versatility | Serialization formats check for Thesaurus BNCF took 0.13676095008850098s
Availability | RDF dump link check for Thesaurus BNCF took 0.11909365653991699s
License | MR license check for Thesaurus BNCF took 0.13332176208496094s
License | HR license check for Thesaurus BNCF took 0.19812726974487305s
Amount of data | Number of property check for Thesaurus BNCF took 0.13710474967956543s
Understandability | Number of label check for Thesaurus BNCF took 0.2505664825439453s
Understandability | URI regex check for Thesaurus BNCF took 0.23947787284851074s
Understandability | Vocabs check for Thesaurus BNCF took 0.11643576622009277s
Verifiability | Authors check for Thesaurus BNCF took 0.13173580169677734s
Verifiability | Publishers check for Thesaurus BNCF took 0.1208200454711914s
Performance | Throughput check for Thesaurus BNCF took 10.516928434371948s
Amount of data | Check the number of entities for Thesaurus BNCF took 7.128715515136719e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.11988353729248047s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.12572169303894043s
Interlinking | skos check for Thesaurus BNCF took 0.19672846794128418s
Interlinking | skos check for Thesaurus BNCF took 0.14656424522399902s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.1255936622619629s
Currency | Creation date check for Thesaurus BNCF took 0.2649378776550293s
Currency | Modification date check for Thesaurus BNCF took 0.2525312900543213s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.43533158302307s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.12386202812194824s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.12563562393188477s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.12327742576599121s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.906046867370605s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4898505210876465s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.8944523334503174s
Consistency | Disjoint class check for Thesaurus BNCF took 0.1256561279296875s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.99373459815979s
Consistency | Misplaced classes for Thesaurus BNCF took 6.701396703720093s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.715531587600708s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4838385581970215s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.348281145095825s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.359938621520996s
Security | Sign check for Thesaurus BNCF took 0.13745689392089844s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 22.498996019363403s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.3331151008605957s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02136969566345215s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0011348724365234375s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 0.00010013580322265625s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.1457672119140625e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 7.62939453125e-06s
INFO | --- Analysis for bncf-ns took 185.188494682312s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6250710487365723s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0008203983306884766s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.538811445236206s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.932248592376709s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.6804370880126953s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.9434897899627686s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.202186584472656s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.3726882934570312s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2767918109893799s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.32430195808410645s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.520078182220459s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.535189151763916s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3672807216644287s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.26400089263916s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38017964363098145s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8579714298248291s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7591602802276611s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4912898540496826s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36035966873168945s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37794923782348633s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.264787912368774s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.128715515136719e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3554503917694092s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3918485641479492s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38765525817871094s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39449167251586914s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.49129581451416016s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7967607975006104s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3732643127441406s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.74852156639099s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3845791816711426s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36909031867980957s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3685774803161621s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7589030265808105s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030251264572143555s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.028495311737060547s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37668943405151367s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.608700037002563s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4324760437011719s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3105006217956543s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6781511306762695s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.71310544013977s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.029894351959228516s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42435479164123535s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36982250213623047s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.850416660308838s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.369234561920166s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.021262645721435547s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.817413330078125e-05s
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 2.8371810913085938e-05s
INFO | --- Analysis for bpr took 399.7557888031006s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 9.107589721679688e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.2782907485961914s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.961822509765625e-05s
Believability | Calculation of trust value for Brazilian Politicians took 1.0013580322265625e-05s
INFO | --- Analysis for brazilian-politicians took 2.823763132095337s
Availability | SPARQL endpoint availability check for Bricklink took 1.6597654819488525s
Availability | VoID file availability check for Bricklink took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Bricklink took 0.2998809814453125s
Reputation | Calculation of the PageRank for Bricklink took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.67572021484375e-05s
Believability | Calculation of trust value for Bricklink took 1.1444091796875e-05s
INFO | --- Analysis for bricklink took 10.753535270690918s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.237446546554565s
Availability | VoID file availability check for British Museum Collection took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.3057420253753662s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02060079574584961s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.0517578125e-05s
Believability | Calculation of trust value for British Museum Collection took 1.2159347534179688e-05s
INFO | --- Analysis for british-museum-collection took 73.03880500793457s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 9.775161743164062e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.30427002906799316s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.124641418457031e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.2636184692382812e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.9002676010131836s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.20523571968078613s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0005497932434082031s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 12.090361595153809s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.5911769866943359s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.174330711364746s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.827298641204834s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.8197853565216064s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.9412589073181152s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12363886833190918s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11493897438049316s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12819600105285645s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12217187881469727s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 21.389962911605835s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11475682258605957s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.20841550827026367s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24277973175048828s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12136721611022949s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12194180488586426s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12816643714904785s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.88912034034729s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.534027099609375e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12944650650024414s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12136125564575195s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11405086517333984s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12842154502868652s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11381316184997559s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2415602207183838s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.23537802696228027s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.420991897583008s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1304309368133545s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11977219581604004s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1278853416442871s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.1713056564331055s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24798274040222168s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.599865198135376s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.129868745803833s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.1003201007843018s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.163048267364502s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2344000339508057s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.3188300132751465s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.6926045417785645s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12012934684753418s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3558.8889017105103s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.7261128425598145s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.02056407928466797s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.2172927856445312e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.5762786865234375e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2636184692382812e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3670.8217027187347s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.23233342170715332s
Availability | VoID file availability check for business.data.gov.uk took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.31694936752319336s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.555152893066406e-05s
Believability | Calculation of trust value for business.data.gov.uk took 9.059906005859375e-06s
INFO | --- Analysis for business-data-gov-uk took 3.152982473373413s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.4665946960449219s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0007674694061279297s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 4.1257593631744385s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.5185413360595703s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.4155869483947754s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.617889404296875s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 42.58871912956238s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.31497955322265625s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.1845552921295166s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.3164680004119873s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.33783411979675293s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.2970259189605713s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.2950124740600586s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 20.04486870765686s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3454864025115967s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.3426837921142578s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.5972657203674316s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.2953517436981201s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.3230924606323242s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.27239418029785156s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 13.107783794403076s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.414817810058594e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.31255173683166504s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3034403324127197s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.29076647758483887s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.31903076171875s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.29793739318847656s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.6166102886199951s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.5854301452636719s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 4.477520704269409s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.3190169334411621s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.47201013565063477s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.45693516731262207s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.6518237590789795s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03354668617248535s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.027981042861938477s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.3482394218444824s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.4594447612762451s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.39028143882751465s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.369138240814209s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2633323669433594s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.4339401721954346s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03136920928955078s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.3074965476989746s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.31406259536743164s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1471.3824679851532s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.3414337635040283s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.021471023559570312s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.7220458984375e-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.1920928955078125e-05s
INFO | --- Analysis for BVMC took 1607.9755835533142s
Availability | SPARQL endpoint availability check for cablegate took 1.4950344562530518s
Availability | VoID file availability check for cablegate took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for cablegate took 0.28226780891418457s
Reputation | Calculation of the PageRank for cablegate took 0.020676851272583008s
Interlinking | Calculation of Degree of Connection for cablegate took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for cablegate took 8.273124694824219e-05s
Believability | Calculation of trust value for cablegate took 1.33514404296875e-05s
INFO | --- Analysis for cablegate took 16.582852125167847s
Availability | SPARQL endpoint availability check for Calames took 8.916854858398438e-05s
Availability | VoID file availability check for Calames took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for Calames took 0.29723024368286133s
Reputation | Calculation of the PageRank for Calames took 0.022876262664794922s
Interlinking | Calculation of Degree of Connection for Calames took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Calames took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Calames took 3.6716461181640625e-05s
Believability | Calculation of trust value for Calames took 1.33514404296875e-05s
INFO | --- Analysis for calames took 4.433414697647095s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.444716215133667s
Availability | VoID file availability check for CaLiGraph took 0.0005013942718505859s
Extra | Recovery of all triples for CaLiGraph took 1.1973469257354736s
Performance | Total latancy measurement for CaLiGraph took 1.2070903778076172s
Amount of data | Number of triples check for CaLiGraph took 13.631827592849731s
Interoperability | New terms check for CaLiGraph took 1.9262094497680664s
Versatility | Languages check for CaLiGraph took 60.28690195083618s
Interpretability | Number of blank nodes check for CaLiGraph took 0.26610827445983887s
Security | Check HTTPS for CaLiGraph took 0.1394813060760498s
Interpretability | RDF structures check for CaLiGraph took 0.32143449783325195s
Versatility | Serialization formats check for CaLiGraph took 0.2798581123352051s
Availability | RDF dump link check for CaLiGraph took 0.2715485095977783s
License | MR license check for CaLiGraph took 0.2969064712524414s
License | HR license check for CaLiGraph took 60.305198669433594s
Amount of data | Number of property check for CaLiGraph took 0.2694387435913086s
Understandability | Number of label check for CaLiGraph took 3.3204903602600098s
Understandability | URI regex check for CaLiGraph took 0.5152702331542969s
Understandability | Vocabs check for CaLiGraph took 0.2911183834075928s
Verifiability | Authors check for CaLiGraph took 0.2529175281524658s
Verifiability | Publishers check for CaLiGraph took 0.2646677494049072s
Performance | Throughput check for CaLiGraph took 11.549793481826782s
Amount of data | Check the number of entities for CaLiGraph took 0.01491093635559082s
Verifiability | Contribs. check for CaLiGraph took 0.2664608955383301s
Interlinking | sameAs chians check for CaLiGraph took 0.6842703819274902s
Interlinking | skos check for CaLiGraph took 0.3168516159057617s
Interlinking | skos check for CaLiGraph took 0.24315810203552246s
Timeliness | dataset update frequency check for CaLiGraph took 0.2744760513305664s
Currency | Creation date check for CaLiGraph took 0.5756819248199463s
Currency | Modification date check for CaLiGraph took 0.5362918376922607s
Rep.Conc. | URIs length for CaLiGraph took 61.05407738685608s
Interoperability | New vocabularies check for CaLiGraph took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.27292442321777344s
Accuracy | Check Functional Property for CaLiGraph took 0.2621631622314453s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.26552677154541016s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5469090938568115s
Accuracy | Check White space in annotation for CaLiGraph took 0.026145458221435547s
Accuracy | Check Datatype consistency for CaLiGraph took 0.049840688705444336s
Consistency | Disjoint class check for CaLiGraph took 0.2667198181152344s
Consistency | Check Misplaced properties for CaLiGraph took 60.96390342712402s
Consistency | Misplaced classes for CaLiGraph took 0.4668452739715576s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9833533763885498s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2918362617492676s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.572051763534546s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03277277946472168s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.47159528732299805s
Security | Sign check for CaLiGraph took 0.33028388023376465s
Availability | Check URIs Dereferenciability for CaLiGraph took 9.969666481018066s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.5024452209472656s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021229028701782227s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.2874603271484375e-05s
INFO | --- Analysis for CaLiGraph took 1448.4508655071259s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2596700191497803s
Availability | VoID file availability check for CaLiGraph took 0.0006229877471923828s
Extra | Recovery of all triples for CaLiGraph took 1.7123446464538574s
Performance | Total latancy measurement for CaLiGraph took 1.1992356777191162s
Amount of data | Number of triples check for CaLiGraph took 13.65979290008545s
Interoperability | New terms check for CaLiGraph took 1.921729326248169s
Versatility | Languages check for CaLiGraph took 60.29969882965088s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2801806926727295s
Security | Check HTTPS for CaLiGraph took 0.13924932479858398s
Interpretability | RDF structures check for CaLiGraph took 0.2890033721923828s
Versatility | Serialization formats check for CaLiGraph took 0.25539541244506836s
Availability | RDF dump link check for CaLiGraph took 0.26035642623901367s
License | MR license check for CaLiGraph took 0.2592782974243164s
License | HR license check for CaLiGraph took 60.3278124332428s
Amount of data | Number of property check for CaLiGraph took 0.2656857967376709s
Understandability | Number of label check for CaLiGraph took 3.2800583839416504s
Understandability | URI regex check for CaLiGraph took 0.5037381649017334s
Understandability | Vocabs check for CaLiGraph took 0.2684152126312256s
Verifiability | Authors check for CaLiGraph took 0.260528564453125s
Verifiability | Publishers check for CaLiGraph took 0.2650620937347412s
Performance | Throughput check for CaLiGraph took 11.424803495407104s
Amount of data | Check the number of entities for CaLiGraph took 0.015305757522583008s
Verifiability | Contribs. check for CaLiGraph took 0.26062536239624023s
Interlinking | sameAs chians check for CaLiGraph took 0.6674597263336182s
Interlinking | skos check for CaLiGraph took 0.26427435874938965s
Interlinking | skos check for CaLiGraph took 0.23867321014404297s
Timeliness | dataset update frequency check for CaLiGraph took 0.2645437717437744s
Currency | Creation date check for CaLiGraph took 0.5320050716400146s
Currency | Modification date check for CaLiGraph took 0.5192413330078125s
Rep.Conc. | URIs length for CaLiGraph took 61.03283333778381s
Interoperability | New vocabularies check for CaLiGraph took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.25930333137512207s
Accuracy | Check Functional Property for CaLiGraph took 0.25295019149780273s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.24899673461914062s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5774810314178467s
Accuracy | Check White space in annotation for CaLiGraph took 0.026276588439941406s
Accuracy | Check Datatype consistency for CaLiGraph took 0.04964852333068848s
Consistency | Disjoint class check for CaLiGraph took 0.2723991870880127s
Consistency | Check Misplaced properties for CaLiGraph took 60.883331537246704s
Consistency | Misplaced classes for CaLiGraph took 0.5197868347167969s
Consistency | Check Ontology hijacking for CaLiGraph took 2.0443596839904785s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.276707410812378s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.58664584159851s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.02966618537902832s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.44774794578552246s
Security | Sign check for CaLiGraph took 0.26126551628112793s
Availability | Check URIs Dereferenciability for CaLiGraph took 10.995128870010376s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.38274359703063965s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020506620407104492s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.414817810058594e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.239776611328125e-05s
INFO | --- Analysis for caligraph took 1448.75382065773s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.07415127754211426s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2795839309692383s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.02095508575439453s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0010042190551757812s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.62396240234375e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.239776611328125e-05s
INFO | --- Analysis for cap-italy-rdf took 2.852943181991577s
Availability | SPARQL endpoint availability check for person took 4.696846008300781e-05s
Availability | VoID file availability check for person took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for person took 0.2881584167480469s
Reputation | Calculation of the PageRank for person took 0.0228269100189209s
Interlinking | Calculation of Degree of Connection for person took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for person took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for person took 2.8371810913085938e-05s
Believability | Calculation of trust value for person took 1.3113021850585938e-05s
INFO | --- Analysis for card took 2.593649387359619s
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.0005228519439697266s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2962455749511719s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.790855407714844e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.1444091796875e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.228394031524658s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.584000825881958s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0005137920379638672s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 112.68679404258728s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9730854034423828s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.193678617477417s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.187673330307007s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.2581584453583s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.2740206718444824s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.32265377044677734s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 8.970926761627197s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.3729434013366699s
License | MR license check for Norway catch records dataset @PSNC took 0.8456563949584961s
License | HR license check for Norway catch records dataset @PSNC took 300.2188050746918s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.2201244831085205s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.9799718856811523s
Understandability | URI regex check for Norway catch records dataset @PSNC took 1.1530227661132812s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.5998795032501221s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.20915818214416504s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.2635347843170166s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.525232553482056s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 7.033348083496094e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.21605134010314941s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.18468117713928223s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.5097630023956299s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.42942357063293457s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 6.57225227355957s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.4450411796569824s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.243239164352417s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 152.13597631454468s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 1.4066696166992188e-05s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.18334317207336426s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.4853544235229492s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.45168066024780273s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 39.12016749382019s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.6494743824005127s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.633195161819458s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.18241596221923828s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 85.95846056938171s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.251840829849243s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 29.449393033981323s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.32188081741333s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 86.90616393089294s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.696302890777588s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.522162675857544s
Security | Sign check for Norway catch records dataset @PSNC took 1.2798702716827393s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 13.065880060195923s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.32172346115112305s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.02117133140563965s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.76837158203125e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 4.0531158447265625e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2273.7245078086853s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.6253204345703125e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.267627477645874s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.021670818328857422s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010323524475097656s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0728836059570312e-05s
INFO | --- Analysis for ce4r took 13.863553524017334s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5673184394836426s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0002663135528564453s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.110626220703125s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.8021419048309326s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.37598443031311035s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6461694240570068s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.17445421218872s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21007084846496582s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23807477951049805s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17590618133544922s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1751079559326172s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.30606627464294434s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3611736297607422s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24322795867919922s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.32640719413757324s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4113349914550781s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2247769832611084s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22305798530578613s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24974560737609863s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.935717344284058s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.271766662597656e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.35735416412353516s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2064838409423828s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7646269798278809s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1565845012664795s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22079062461853027s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7361984252929688s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5253598690032959s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.172553539276123s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16685247421264648s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6399698257446289s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.02850651741027832s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.027425527572631836s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3659942150115967s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.337224006652832s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9308087825775146s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 2.1906819343566895s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.4433674812316895s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.02965998649597168s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.22520709037780762s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4402620792388916s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 3306.993981361389s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.7514452934265137s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020253658294677734s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.553794860839844e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.0967254638671875e-05s
INFO | --- Analysis for ceo took 3435.173588037491s
Availability | SPARQL endpoint availability check for Chat Game corpus took 8.916854858398438e-05s
Availability | VoID file availability check for Chat Game corpus took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.2904050350189209s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.021826982498168945s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.001094818115234375s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 4.4345855712890625e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.1920928955078125e-05s
INFO | --- Analysis for chat-game-corpus took 12.862557888031006s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 8.869171142578125e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0007824897766113281s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.3180365562438965s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020612001419067383s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.53131103515625e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.6450881958007812e-05s
INFO | --- Analysis for chem2bio2rdf took 134.3536732196808s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.6078445911407471s
Availability | VoID file availability check for ChEMBL RDF took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.3063697814941406s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.76837158203125e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.3589859008789062e-05s
INFO | --- Analysis for chembl-rdf took 4.022404909133911s
Availability | SPARQL endpoint availability check for chemdb  dataset took 0.815838098526001s
Availability | VoID file availability check for chemdb  dataset took 0.0005247592926025391s
Extra | Recovery of all triples for chemdb  dataset took 4.949916839599609s
Performance | Total latancy measurement for chemdb  dataset took 2.4831199645996094s
Amount of data | Number of triples check for chemdb  dataset took 0.5443024635314941s
Interoperability | New terms check for chemdb  dataset took 3.400155782699585s
Versatility | Languages check for chemdb  dataset took 22.465286254882812s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5200700759887695s
Interpretability | RDF structures check for chemdb  dataset took 1.0640983581542969s
Versatility | Serialization formats check for chemdb  dataset took 0.9157698154449463s
Availability | RDF dump link check for chemdb  dataset took 0.6426708698272705s
License | MR license check for chemdb  dataset took 1.4645001888275146s
License | HR license check for chemdb  dataset took 3.3900256156921387s
Amount of data | Number of property check for chemdb  dataset took 0.514075756072998s
Understandability | Number of label check for chemdb  dataset took 2.4311881065368652s
Understandability | URI regex check for chemdb  dataset took 1.3789434432983398s
Understandability | Vocabs check for chemdb  dataset took 0.6145737171173096s
Verifiability | Authors check for chemdb  dataset took 0.7482383251190186s
Verifiability | Publishers check for chemdb  dataset took 0.6264898777008057s
Performance | Throughput check for chemdb  dataset took 14.043854713439941s
Amount of data | Check the number of entities for chemdb  dataset took 0.0002319812774658203s
Verifiability | Contribs. check for chemdb  dataset took 0.6260364055633545s
Interlinking | sameAs chians check for chemdb  dataset took 0.6955735683441162s
Interlinking | skos check for chemdb  dataset took 1.1011953353881836s
Interlinking | skos check for chemdb  dataset took 0.49843883514404297s
Timeliness | dataset update frequency check for chemdb  dataset took 0.6626925468444824s
Currency | Creation date check for chemdb  dataset took 1.147284984588623s
Currency | Modification date check for chemdb  dataset took 1.0081899166107178s
Rep.Conc. | URIs length for chemdb  dataset took 2.897660255432129s
Interoperability | New vocabularies check for chemdb  dataset took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5224368572235107s
Accuracy | Check Functional Property for chemdb  dataset took 0.6216540336608887s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.5959548950195312s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.1553282737731934s
Accuracy | Check White space in annotation for chemdb  dataset took 0.03044581413269043s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03287220001220703s
Consistency | Disjoint class check for chemdb  dataset took 0.6063666343688965s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2248055934906006s
Consistency | Misplaced classes for chemdb  dataset took 0.6082596778869629s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.3889689445495605s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.232431173324585s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 1.9459218978881836s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03131985664367676s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5305821895599365s
Security | Sign check for chemdb  dataset took 1.0161256790161133s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2501.978965997696s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.48185038566589355s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.021037817001342773s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.390975952148438e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb  dataset took 1.3113021850585938e-05s
INFO | --- Analysis for chemdb-basicInfo took 4752.477008342743s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5130612850189209s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0004878044128417969s
Extra | Recovery of all triples for chemdb estimated properties dataset took 4.879194736480713s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.497633457183838s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5560312271118164s
Interoperability | New terms check for chemdb estimated properties dataset took 3.4537549018859863s
Versatility | Languages check for chemdb estimated properties dataset took 22.937021732330322s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5176117420196533s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5199391841888428s
Versatility | Serialization formats check for chemdb estimated properties dataset took 0.5151612758636475s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.4977574348449707s
License | MR license check for chemdb estimated properties dataset took 0.5544688701629639s
License | HR license check for chemdb estimated properties dataset took 3.1540939807891846s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5369307994842529s
Understandability | Number of label check for chemdb estimated properties dataset took 0.5358154773712158s
Understandability | URI regex check for chemdb estimated properties dataset took 0.9981594085693359s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.5040292739868164s
Verifiability | Authors check for chemdb estimated properties dataset took 0.49739933013916016s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.4995861053466797s
Performance | Throughput check for chemdb estimated properties dataset took 13.442722797393799s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 3.2901763916015625e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.48920583724975586s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.5200779438018799s
Interlinking | skos check for chemdb estimated properties dataset took 0.4922969341278076s
Interlinking | skos check for chemdb estimated properties dataset took 0.4927349090576172s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.4894740581512451s
Currency | Creation date check for chemdb estimated properties dataset took 1.0387718677520752s
Currency | Modification date check for chemdb estimated properties dataset took 1.0342488288879395s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 2.948631763458252s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.49962425231933594s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.519073486328125s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.5042917728424072s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 2.157097578048706s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.02979564666748047s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.0335078239440918s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.4944586753845215s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2232356071472168s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6119413375854492s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.4129724502563477s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.2722563743591309s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.9832980632781982s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03523993492126465s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5248100757598877s
Security | Sign check for chemdb estimated properties dataset took 0.5104002952575684s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2495.6748683452606s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.546377420425415s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.021157264709472656s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 5.2928924560546875e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.239776611328125e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 4723.614843606949s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5269627571105957s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0005137920379638672s
Extra | Recovery of all triples for chemdb phase transition dataset took 13.304139852523804s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.5041253566741943s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5553343296051025s
Interoperability | New terms check for chemdb phase transition dataset took 3.887648344039917s
Versatility | Languages check for chemdb phase transition dataset took 22.71286964416504s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5250802040100098s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5214827060699463s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.5318038463592529s
Availability | RDF dump link check for chemdb phase transition dataset took 0.49947142601013184s
License | MR license check for chemdb phase transition dataset took 0.5015881061553955s
License | HR license check for chemdb phase transition dataset took 3.1212165355682373s
Amount of data | Number of property check for chemdb phase transition dataset took 0.509040117263794s
Understandability | Number of label check for chemdb phase transition dataset took 0.5245389938354492s
Understandability | URI regex check for chemdb phase transition dataset took 0.9793803691864014s
Understandability | Vocabs check for chemdb phase transition dataset took 0.4990224838256836s
Verifiability | Authors check for chemdb phase transition dataset took 0.5001652240753174s
Verifiability | Publishers check for chemdb phase transition dataset took 0.49584341049194336s
Performance | Throughput check for chemdb phase transition dataset took 12.955684661865234s
Amount of data | Check the number of entities for chemdb phase transition dataset took 9.083747863769531e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.49524998664855957s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.5238988399505615s
Interlinking | skos check for chemdb phase transition dataset took 0.5041725635528564s
Interlinking | skos check for chemdb phase transition dataset took 0.4842410087585449s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.48450517654418945s
Currency | Creation date check for chemdb phase transition dataset took 1.01582932472229s
Currency | Modification date check for chemdb phase transition dataset took 1.002953290939331s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.395399332046509s
Interoperability | New vocabularies check for chemdb phase transition dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.4806947708129883s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.5208227634429932s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.4958925247192383s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 2.8463706970214844s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.030137062072753906s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.032808780670166016s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.4961705207824707s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2374024391174316s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6035914421081543s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.8846890926361084s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.2302331924438477s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 1.942939043045044s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.031976938247680664s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5346152782440186s
Security | Sign check for chemdb phase transition dataset took 0.5055544376373291s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2509.2713990211487s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.5162994861602783s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.02124810218811035s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 6.318092346191406e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.054473876953125e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 2.1457672119140625e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.0251998901367188e-05s
INFO | --- Analysis for chemdb-phaseTransition took 4740.317206859589s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5178062915802002s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.00025343894958496094s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 9.12174367904663s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.500150680541992s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5436532497406006s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.8774991035461426s
Versatility | Languages check for chemdb thermochemistry dataset took 22.71892738342285s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5186548233032227s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5337293148040771s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.5272605419158936s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.5039575099945068s
License | MR license check for chemdb thermochemistry dataset took 0.5008463859558105s
License | HR license check for chemdb thermochemistry dataset took 3.157895565032959s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5266745090484619s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.5377230644226074s
Understandability | URI regex check for chemdb thermochemistry dataset took 0.977470874786377s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.4908919334411621s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.4974355697631836s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.48354482650756836s
Performance | Throughput check for chemdb thermochemistry dataset took 13.927704095840454s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.081031799316406e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.4919247627258301s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.5210530757904053s
Interlinking | skos check for chemdb thermochemistry dataset took 0.4917261600494385s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5036585330963135s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.49579691886901855s
Currency | Creation date check for chemdb thermochemistry dataset took 1.0172700881958008s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0342872142791748s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.4381842613220215s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.489377498626709s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.5269670486450195s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.49145078659057617s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 2.88757061958313s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.0299072265625s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03343605995178223s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.5032527446746826s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2164978981018066s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6091241836547852s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.886622190475464s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.2716200351715088s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 1.9786498546600342s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03581809997558594s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5373075008392334s
Security | Sign check for chemdb thermochemistry dataset took 0.48247551918029785s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2501.5208666324615s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.47736477851867676s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.151199340820312e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-thermochemistry took 4718.764678478241s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.267692565917969e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0008330345153808594s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.30899548530578613s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02183699607849121s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.170967102050781e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.239776611328125e-05s
INFO | --- Analysis for chempedia-rdf took 10.309158086776733s
Availability | SPARQL endpoint availability check for Chiman Maru took 8.916854858398438e-05s
Availability | VoID file availability check for Chiman Maru took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.29442691802978516s
Reputation | Calculation of the PageRank for Chiman Maru took 0.02339768409729004s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.0994415283203125e-05s
Believability | Calculation of trust value for Chiman Maru took 1.239776611328125e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.64064359664917s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.55979084968567s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.2820572853088379s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02152729034423828s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.601478576660156e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 799.7417967319489s
Availability | SPARQL endpoint availability check for Chronicling America took 9.226799011230469e-05s
Availability | VoID file availability check for Chronicling America took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.31576085090637207s
Reputation | Calculation of the PageRank for Chronicling America took 0.020833253860473633s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 9.775161743164062e-05s
Believability | Calculation of trust value for Chronicling America took 1.0967254638671875e-05s
INFO | --- Analysis for chronicling-america took 14.254612684249878s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.6641764640808105s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006177425384521484s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 81.2638828754425s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.6542229652404785s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 1.8096511363983154s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.1238813400268555s
Versatility | Languages check for Cultural Heritage Thesaurus took 4.713057279586792s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 1.1273162364959717s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3415231704711914s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.3173980712890625s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 6.314291477203369s
License | MR license check for Cultural Heritage Thesaurus took 0.32967567443847656s
License | HR license check for Cultural Heritage Thesaurus took 0.659031867980957s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.29276013374328613s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.4371168613433838s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.6036851406097412s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.3181157112121582s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.30167675018310547s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.3075554370880127s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.86730432510376s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.653236389160156e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.3329753875732422s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.3352532386779785s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.4163246154785156s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3695671558380127s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.330355167388916s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6471197605133057s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6302096843719482s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 25.478002548217773s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 3.2023513317108154s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.31419825553894043s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.2831578254699707s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.3300034999847412s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 5.5732808113098145s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21701622009277344s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.2679870128631592s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 2.288484573364258s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.3021829128265381s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.351213693618774s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.9556891918182373s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00014519691467285156s
Security | Sign check for Cultural Heritage Thesaurus took 0.27803492546081543s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 362.87428426742554s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.4544548988342285s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.1539607048034668s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007183551788330078s
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 1.5679032802581787s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for cht took 560.3303899765015s
Availability | SPARQL endpoint availability check for ciard-ring took 8.988380432128906e-05s
Availability | VoID file availability check for ciard-ring took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2890493869781494s
Reputation | Calculation of the PageRank for ciard-ring took 0.021155834197998047s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.6253204345703125e-05s
Believability | Calculation of trust value for ciard-ring took 1.049041748046875e-05s
INFO | --- Analysis for ciard-ring took 6.354154825210571s
Availability | SPARQL endpoint availability check for Cine Figure took 4.220008850097656e-05s
Availability | VoID file availability check for Cine Figure took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.3108980655670166s
Reputation | Calculation of the PageRank for Cine Figure took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.935264587402344e-05s
Believability | Calculation of trust value for Cine Figure took 1.1444091796875e-05s
INFO | --- Analysis for Cine_Figure took 2.7389166355133057s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 1.367142677307129s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.30521202087402344s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.02067279815673828s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.506111145019531e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 5.776355028152466s
Availability | SPARQL endpoint availability check for CIPFA took 4.291534423828125e-05s
Availability | VoID file availability check for CIPFA took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for CIPFA took 0.31812310218811035s
Reputation | Calculation of the PageRank for CIPFA took 0.02176070213317871s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.647804260253906e-05s
Believability | Calculation of trust value for CIPFA took 8.58306884765625e-06s
INFO | --- Analysis for cipfa took 2.7516090869903564s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 3.89017915725708s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.2774028778076172s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.022296667098999023s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00037980079650878906s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.049041748046875e-05s
INFO | --- Analysis for ckan took 19.35478448867798s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6845793724060059s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.2853565216064453s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.02046346664428711s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for CLaSSES took 4.430579900741577s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.100799560546875e-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.3014962673187256s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.022031307220458984s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.123283386230469e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.0013580322265625e-05s
INFO | --- Analysis for classical_temples took 4.456348896026611s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.0798256397247314s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.29565906524658203s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.249282836914062e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 4.5299530029296875e-06s
INFO | --- Analysis for clean-energy-data-reegle took 5.6238532066345215s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.673004150390625e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.3144679069519043s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.700920104980469e-05s
Believability | Calculation of trust value for CLLD-afbo took 9.775161743164062e-06s
INFO | --- Analysis for clld-afbo took 3.674553871154785s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.0531158447265625e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.2870979309082031s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.021062135696411133s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.414817810058594e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.0013580322265625e-05s
INFO | --- Analysis for clld-apics took 3.719672679901123s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.172325134277344e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.3376157283782959s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020915985107421875s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.886222839355469e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 9.775161743164062e-06s
INFO | --- Analysis for clld-ewave took 3.8681583404541016s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 8.511543273925781e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.3231923580169678s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.021509647369384766s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.584426879882812e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 9.5367431640625e-06s
INFO | --- Analysis for clld-glottolog took 3.8688526153564453s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 5.221366882324219e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.28717494010925293s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020616531372070312s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.915496826171875e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.049041748046875e-05s
INFO | --- Analysis for clld-phoible took 3.702153444290161s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.678436279296875e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.2756209373474121s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.319450378417969e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.0013580322265625e-05s
INFO | --- Analysis for clld-sails took 3.783851146697998s
Availability | SPARQL endpoint availability check for CLLD-WALS took 0.00010824203491210938s
Availability | VoID file availability check for CLLD-WALS took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2973899841308594s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.106231689453125e-05s
Believability | Calculation of trust value for CLLD-WALS took 9.775161743164062e-06s
INFO | --- Analysis for clld-wals took 3.963162899017334s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.3071892261505127s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020874500274658203s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.534027099609375e-05s
Believability | Calculation of trust value for CLLD-WOLD took 9.775161743164062e-06s
INFO | --- Analysis for clld-wold took 3.6912219524383545s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.12964344024658203s
Availability | VoID file availability check for Cooperation Databank took 0.0002086162567138672s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.3145895004272461s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02079176902770996s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.552436828613281e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.049041748046875e-05s
INFO | --- Analysis for CoDa took 2.8071651458740234s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.0012657642364502s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.3180062770843506s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.022675752639770508s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.075599670410156e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 8.821487426757812e-06s
INFO | --- Analysis for coins-openuplabs took 3.747283935546875s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 2.9484758377075195s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.30268335342407227s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.273124694824219e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.2159347534179688e-05s
INFO | --- Analysis for CoLChina_sp2000 took 7.0783164501190186s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.0616450309753418s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.2644612789154053s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.022480010986328125s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.910064697265625e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for colinda took 2.689234733581543s
Availability | SPARQL endpoint availability check for CN  2012 took 25.24031925201416s
Availability | VoID file availability check for CN  2012 took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.27841615676879883s
Reputation | Calculation of the PageRank for CN  2012 took 0.021592378616333008s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.00543212890625e-05s
Believability | Calculation of trust value for CN  2012 took 8.58306884765625e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 124.13860630989075s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.48537373542785645s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.30073022842407227s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02122807502746582s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.049041748046875e-05s
INFO | --- Analysis for CompHistSem took 4.182452201843262s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 1.7919337749481201s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.328533411026001s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.528594970703125e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 9.5367431640625e-06s
INFO | --- Analysis for comsode-d3-2 took 7.414004802703857s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 8.630752563476562e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2816741466522217s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.440017700195312e-05s
Believability | Calculation of trust value for 2011 US Congress People took 8.106231689453125e-06s
INFO | --- Analysis for congresspeople took 3.2256505489349365s
Availability | SPARQL endpoint availability check for MIMO took 0.3800971508026123s
Availability | VoID file availability check for MIMO took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for MIMO took 0.33365345001220703s
Reputation | Calculation of the PageRank for MIMO took 0.021341562271118164s
Interlinking | Calculation of Degree of Connection for MIMO took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.1682510375976562e-05s
Believability | Calculation of trust value for MIMO took 1.049041748046875e-05s
INFO | --- Analysis for CONNECTED took 4.298614263534546s
Availability | SPARQL endpoint availability check for Copyright Free Music took 9.417533874511719e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.3082888126373291s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.022077560424804688s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.9802322387695312e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.049041748046875e-05s
INFO | --- Analysis for Copyright_Free_Music took 3.505681037902832s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.673004150390625e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.3287019729614258s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.67572021484375e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.239776611328125e-05s
INFO | --- Analysis for copyrighttermbank took 34.40837216377258s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 3.101727247238159s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.3060433864593506s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0006988048553466797s
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.0251998901367188e-05s
INFO | --- Analysis for core took 8.352024555206299s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.6181480884552002s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005092620849609375s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 100.01234030723572s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9771661758422852s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.564991235733032s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.357305526733398s
Versatility | Languages check for Corine linked dataset @PSNC took 300.1901500225067s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.1325736045837402s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.34921717643737793s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 9.051870107650757s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.359682559967041s
License | MR license check for Corine linked dataset @PSNC took 0.9140734672546387s
License | HR license check for Corine linked dataset @PSNC took 300.17804431915283s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.2208857536315918s
Understandability | Number of label check for Corine linked dataset @PSNC took 3.12780499458313s
Understandability | URI regex check for Corine linked dataset @PSNC took 1.170670509338379s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.6374673843383789s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.2126150131225586s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.2528343200683594s
Performance | Throughput check for Corine linked dataset @PSNC took 11.586491346359253s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 0.00011348724365234375s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.20258164405822754s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.2099916934967041s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4609642028808594s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4308936595916748s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 4.422877550125122s
Currency | Creation date check for Corine linked dataset @PSNC took 0.5470490455627441s
Currency | Modification date check for Corine linked dataset @PSNC took 0.2528057098388672s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 148.70953941345215s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.2000720500946045s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.4517505168914795s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.5046176910400391s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 35.226699352264404s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6742753982543945s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.604116439819336s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.18258452415466309s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 86.26876163482666s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.25996446609497s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 37.52532196044922s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.3199665546417236s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 88.50738549232483s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.6696455478668213s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.5654840469360352s
Security | Sign check for Corine linked dataset @PSNC took 1.5835411548614502s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 18.08506464958191s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.525050163269043s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021084070205688477s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 4.0531158447265625e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.049041748046875e-05s
INFO | --- Analysis for Corine_linked_dataset took 2259.594526529312s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.458427429199219e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.2848317623138428s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02151203155517578s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 6.437301635742188e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.0013580322265625e-05s
INFO | --- Analysis for cornetto took 13.428891897201538s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.15843534469604492s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0004451274871826172s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 223.22507452964783s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5511553287506104s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 87.62162399291992s
Interoperability | New terms check for Corporate Body Named Authority List  took 58.768452644348145s
Versatility | Languages check for Corporate Body Named Authority List  took 300.0788679122925s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 17.673590183258057s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.35982584953308105s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.5106158256530762s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 4.350623607635498s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.2023158073425293s
License | MR license check for Corporate Body Named Authority List  took 0.4259967803955078s
License | HR license check for Corporate Body Named Authority List  took 300.05788397789s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.1669778823852539s
Understandability | Number of label check for Corporate Body Named Authority List  took 1.582169771194458s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.39488911628723145s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.09917116165161133s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.24500274658203125s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.2141890525817871s
Performance | Throughput check for Corporate Body Named Authority List  took 10.548906087875366s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 0.00010848045349121094s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.16187834739685059s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 7.740378141403198s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3126671314239502s
Interlinking | skos check for Corporate Body Named Authority List  took 2.4658851623535156s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.27309393882751465s
Currency | Creation date check for Corporate Body Named Authority List  took 0.4280261993408203s
Currency | Modification date check for Corporate Body Named Authority List  took 0.14319086074829102s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 419.57200479507446s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.15332317352294922s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.24832606315612793s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.15487360954284668s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 38.00413775444031s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.045957088470459s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.5685269832611084s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.16104793548583984s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.4616858959198s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.232760190963745s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 36.25726532936096s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.6594212055206299s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.3725869655609s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 2.9639487266540527s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.39611053466796875s
Security | Sign check for Corporate Body Named Authority List  took 0.3843679428100586s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 10.953967094421387s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.6618649959564209s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.040381431579589844s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0012805461883544922s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 8.726119995117188e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 2.384185791015625e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.1444091796875e-05s
INFO | --- Analysis for corporate-body took 15099.766669511795s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.6441845893859863s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.2762913703918457s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for CorpusFibonacci took 4.541614055633545s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.12124443054199219s
Availability | VoID file availability check for Country Name Authority List took 0.0007631778717041016s
Extra | Recovery of all triples for Country Name Authority List took 236.5444004535675s
Performance | Total latancy measurement for Country Name Authority List took 0.5944528579711914s
Amount of data | Number of triples check for Country Name Authority List took 43.98033857345581s
Interoperability | New terms check for Country Name Authority List took 58.851675033569336s
Versatility | Languages check for Country Name Authority List took 300.1004648208618s
Interpretability | Number of blank nodes check for Country Name Authority List took 17.447465896606445s
Security | Check HTTPS for Country Name Authority List took 0.3664839267730713s
Interpretability | RDF structures check for Country Name Authority List took 0.2744178771972656s
Versatility | Serialization formats check for Country Name Authority List took 4.148331880569458s
Availability | RDF dump link check for Country Name Authority List took 0.22561001777648926s
License | MR license check for Country Name Authority List took 0.3574180603027344s
License | HR license check for Country Name Authority List took 300.00620126724243s
Amount of data | Number of property check for Country Name Authority List took 0.16676998138427734s
Understandability | Number of label check for Country Name Authority List took 1.863544225692749s
Understandability | URI regex check for Country Name Authority List took 0.41173481941223145s
Understandability | Vocabs check for Country Name Authority List took 0.10784125328063965s
Verifiability | Authors check for Country Name Authority List took 0.20659923553466797s
Verifiability | Publishers check for Country Name Authority List took 0.24663376808166504s
Performance | Throughput check for Country Name Authority List took 10.443090200424194s
Amount of data | Check the number of entities for Country Name Authority List took 0.00010919570922851562s
Verifiability | Contribs. check for Country Name Authority List took 0.21395444869995117s
Interlinking | sameAs chians check for Country Name Authority List took 6.302199602127075s
Interlinking | skos check for Country Name Authority List took 0.35800647735595703s
Interlinking | skos check for Country Name Authority List took 0.13767242431640625s
Timeliness | dataset update frequency check for Country Name Authority List took 0.28813886642456055s
Currency | Creation date check for Country Name Authority List took 0.29119443893432617s
Currency | Modification date check for Country Name Authority List took 0.1533489227294922s
Rep.Conc. | URIs length for Country Name Authority List took 418.36969089508057s
Interoperability | New vocabularies check for Country Name Authority List took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.15888309478759766s
Accuracy | Check Functional Property for Country Name Authority List took 1.331176519393921s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.14783287048339844s
Accuracy | Check Empty annotation labels for Country Name Authority List took 39.8600070476532s
Accuracy | Check White space in annotation for Country Name Authority List took 3.0481600761413574s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6038315296173096s
Consistency | Disjoint class check for Country Name Authority List took 0.15967726707458496s
Consistency | Check Misplaced properties for Country Name Authority List took 300.4054355621338s
Consistency | Misplaced classes for Country Name Authority List took 8.298834085464478s
Consistency | Check Ontology hijacking for Country Name Authority List took 37.54326152801514s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.7234227657318115s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.50599122047424s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.0462646484375s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.4047250747680664s
Security | Sign check for Country Name Authority List took 0.29592370986938477s
Availability | Check URIs Dereferenciability for Country Name Authority List took 11.351679563522339s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.6950104236602783s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.021213054656982422s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.6689300537109375e-06s
Believability | Calculation of trust value for Country Name Authority List took 1.0728836059570312e-05s
INFO | --- Analysis for country-authority-list took 15626.57708621025s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.09343147277832031s
Availability | VoID file availability check for Courts thesaurus took 0.0004112720489501953s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.29035258293151855s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020885467529296875s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.628036499023438e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for courts-thesaurus took 2.7822446823120117s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.50985884666443s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.2815389633178711s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.02085256576538086s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.700920104980469e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.4066696166992188e-05s
INFO | --- Analysis for Covid-on-the-Web took 55.308509349823s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.66410541534424s
Availability | VoID file availability check for CPA 2008 took 0.0007898807525634766s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.3005104064941406s
Reputation | Calculation of the PageRank for CPA 2008 took 0.022609949111938477s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.1948089599609375e-05s
Believability | Calculation of trust value for CPA 2008 took 9.059906005859375e-06s
INFO | --- Analysis for cpa-2008 took 125.3421540260315s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.3639523983001709s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005488395690917969s
Extra | Recovery of all triples for Cooperative Patent Classification took 27.6573646068573s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.170616626739502s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.2156114578247s
Versatility | Languages check for Cooperative Patent Classification took 100.32766556739807s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.26303052902222s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.23423457145690918s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.2111055850982666s
Availability | RDF dump link check for Cooperative Patent Classification took 0.27123188972473145s
License | MR license check for Cooperative Patent Classification took 0.24940872192382812s
License | HR license check for Cooperative Patent Classification took 90.20791959762573s
Amount of data | Number of property check for Cooperative Patent Classification took 0.28279614448547363s
Understandability | Number of label check for Cooperative Patent Classification took 90.18268203735352s
Understandability | URI regex check for Cooperative Patent Classification took 0.4869682788848877s
Understandability | Vocabs check for Cooperative Patent Classification took 0.17702269554138184s
Verifiability | Authors check for Cooperative Patent Classification took 0.21326708793640137s
Verifiability | Publishers check for Cooperative Patent Classification took 0.31281280517578125s
Performance | Throughput check for Cooperative Patent Classification took 10.84173059463501s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.367134094238281e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.28774142265319824s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.25399231910705566s
Interlinking | skos check for Cooperative Patent Classification took 0.19437813758850098s
Interlinking | skos check for Cooperative Patent Classification took 0.2602548599243164s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.17672204971313477s
Currency | Creation date check for Cooperative Patent Classification took 0.49026989936828613s
Currency | Modification date check for Cooperative Patent Classification took 0.41095852851867676s
Rep.Conc. | URIs length for Cooperative Patent Classification took 132.11033082008362s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.29728055000305176s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 20.18914532661438s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.964620351791382s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.825895547866821s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.20367193222045898s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 100.46839785575867s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 23.559636116027832s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.551377534866333s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 101.59729361534119s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.760467767715454s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.49152088165283203s
Security | Sign check for Cooperative Patent Classification took 0.23414087295532227s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.8189549446105957s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.4286785125732422s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02093672752380371s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 2.1457672119140625e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.2159347534179688e-05s
INFO | --- Analysis for CPC took 1194.8373312950134s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.329206228256226s
Availability | VoID file availability check for CPC 2008 took 0.0008945465087890625s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.29250550270080566s
Reputation | Calculation of the PageRank for CPC 2008 took 0.021004676818847656s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.719329833984375e-05s
Believability | Calculation of trust value for CPC 2008 took 8.58306884765625e-06s
INFO | --- Analysis for cpc-2008 took 124.8035159111023s
Availability | SPARQL endpoint availability check for CPV  2003 took 21.039459466934204s
Availability | VoID file availability check for CPV  2003 took 0.0009081363677978516s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3822641372680664s
Reputation | Calculation of the PageRank for CPV  2003 took 0.021248340606689453s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.647804260253906e-05s
Believability | Calculation of trust value for CPV  2003 took 9.298324584960938e-06s
INFO | --- Analysis for cpv-2003 took 115.64215469360352s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.898217916488647s
Availability | VoID file availability check for CPV 2008 took 0.0008683204650878906s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.32028675079345703s
Reputation | Calculation of the PageRank for CPV 2008 took 0.021023273468017578s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.650520324707031e-05s
Believability | Calculation of trust value for CPV 2008 took 8.106231689453125e-06s
INFO | --- Analysis for cpv-2008 took 124.54359817504883s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.9609024524689s
Availability | VoID file availability check for crowdsourcing-fb took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.3069159984588623s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.02187371253967285s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.52587890625e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.291534423828125e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.1682510375976562e-05s
INFO | --- Analysis for crowdsourcing-fb took 535.9584174156189s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.611512899398804s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.3111720085144043s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020807981491088867s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.887580871582031e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 1.0251998901367188e-05s
INFO | --- Analysis for ctic-public-dataset took 44.17325806617737s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 2.1463422775268555s
Availability | VoID file availability check for CulturaLinkedData took 0.0005271434783935547s
Extra | Recovery of all triples for CulturaLinkedData took 129.09863924980164s
Performance | Total latancy measurement for CulturaLinkedData took 6.4041831493377686s
Amount of data | Number of triples check for CulturaLinkedData took 0.7301676273345947s
Interoperability | New terms check for CulturaLinkedData took 4.043632507324219s
Versatility | Languages check for CulturaLinkedData took 62.044971227645874s
Interpretability | Number of blank nodes check for CulturaLinkedData took 2.039649724960327s
Interpretability | RDF structures check for CulturaLinkedData took 0.48256874084472656s
Versatility | Serialization formats check for CulturaLinkedData took 0.5564513206481934s
Availability | RDF dump link check for CulturaLinkedData took 0.23107004165649414s
License | MR license check for CulturaLinkedData took 2.378645896911621s
License | HR license check for CulturaLinkedData took 63.47919058799744s
Amount of data | Number of property check for CulturaLinkedData took 2.051173448562622s
Understandability | Number of label check for CulturaLinkedData took 2.904951333999634s
Understandability | URI regex check for CulturaLinkedData took 2.3616926670074463s
Understandability | Vocabs check for CulturaLinkedData took 1.9914801120758057s
Verifiability | Authors check for CulturaLinkedData took 0.34302186965942383s
Verifiability | Publishers check for CulturaLinkedData took 0.30728888511657715s
Performance | Throughput check for CulturaLinkedData took 21.872289180755615s
Amount of data | Check the number of entities for CulturaLinkedData took 7.009506225585938e-05s
Verifiability | Contribs. check for CulturaLinkedData took 1.9589686393737793s
Interlinking | sameAs chians check for CulturaLinkedData took 0.33774471282958984s
Interlinking | skos check for CulturaLinkedData took 0.5244264602661133s
Interlinking | skos check for CulturaLinkedData took 0.1846315860748291s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.2988111972808838s
Currency | Creation date check for CulturaLinkedData took 2.318301200866699s
Currency | Modification date check for CulturaLinkedData took 0.4144136905670166s
Rep.Conc. | URIs length for CulturaLinkedData took 55.192277669906616s
Interoperability | New vocabularies check for CulturaLinkedData took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 2.0099470615386963s
Accuracy | Check Functional Property for CulturaLinkedData took 0.17229819297790527s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.18740510940551758s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 41.38335919380188s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.5984675884246826s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.2968852519989014s
Consistency | Disjoint class check for CulturaLinkedData took 0.23064231872558594s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.201476335525513s
Consistency | Misplaced classes for CulturaLinkedData took 5.902992248535156s
Consistency | Check Ontology hijacking for CulturaLinkedData took 48.23675298690796s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3253378868103027s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 11.40960693359375s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3762378692626953s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 1.91727614402771s
Security | Sign check for CulturaLinkedData took 2.73742413520813s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 10.423653602600098s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.37569475173950195s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.026893138885498047s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.384185791015625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.1920928955078125e-05s
INFO | --- Analysis for culturalinkeddata took 625.3173487186432s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.4966280460357666s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2777562141418457s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020281076431274414s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.4332275390625e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-ares-or took 3.50888729095459s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11159586906433105s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.2980682849884033s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02026820182800293s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.266334533691406e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 8.821487426757812e-06s
INFO | --- Analysis for cz-ares-rzp took 3.18538498878479s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11526751518249512s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.2899034023284912s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 2.9802322387695312e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 9.298324584960938e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.1295742988586426s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.12446117401123047s
Availability | VoID file availability check for Integrated pollution registry took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.3196074962615967s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.361701965332031e-05s
Believability | Calculation of trust value for Integrated pollution registry took 9.059906005859375e-06s
INFO | --- Analysis for cz-cenia-pollution took 3.231722593307495s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.11946439743041992s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.3402996063232422s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.021385669708251953s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.600120544433594e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 8.344650268554688e-06s
INFO | --- Analysis for cz-contracts took 3.206284523010254s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.1154787540435791s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.27626776695251465s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.361701965332031e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 8.821487426757812e-06s
INFO | --- Analysis for cz-ctia-bans took 5.067220449447632s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10709500312805176s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.29525327682495117s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.4332275390625e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 1.1920928955078125e-05s
INFO | --- Analysis for cz-ctia-confiscations took 2.983271360397339s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11593079566955566s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.3113291263580322s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.3855438232421875e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 9.775161743164062e-06s
INFO | --- Analysis for cz-ctia-focus took 3.063040256500244s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10745716094970703s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2996408939361572s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.076957702636719e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 1.049041748046875e-05s
INFO | --- Analysis for cz-ctia-inspections took 3.0696372985839844s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.10837864875793457s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2823646068572998s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.021415233612060547s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.981590270996094e-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 4.758663177490234s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.16339707374572754s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.2760493755340576s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.695487976074219e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 8.106231689453125e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 3.2869949340820312s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.11145877838134766s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0007395744323730469s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.27864766120910645s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020801305770874023s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.361701965332031e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 8.106231689453125e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 3.1115710735321045s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.5626564025878906s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2726268768310547s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.886222839355469e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.7323176860809326s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3920557498931885s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.28896617889404297s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.53279972076416s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.36712646484375s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.2977864742279053s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.9577484130859375e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.558022975921631s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.35645461082458496s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0011687278747558594s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.31978297233581543s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.814697265625e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.597338914871216s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.36151719093322754s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.2952895164489746s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.0206754207611084s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.514464855194092s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3920719623565674s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.27648019790649414s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.409385681152344e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 8.106231689453125e-06s
INFO | --- Analysis for cz-czso-regions took 3.280738115310669s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3795614242553711s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.3051340579986572s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.5649197101593018s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.36673760414123535s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.3136875629425049s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.814697265625e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.779101848602295s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.3531022071838379s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.34079837799072266s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.552436828613281e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.602625846862793s
Availability | SPARQL endpoint availability check for ATC groups took 0.11569738388061523s
Availability | VoID file availability check for ATC groups took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for ATC groups took 0.2939426898956299s
Reputation | Calculation of the PageRank for ATC groups took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for ATC groups took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ATC groups took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.628036499023438e-05s
Believability | Calculation of trust value for ATC groups took 1.1682510375976562e-05s
INFO | --- Analysis for cz-eh-1-atc took 3.143507957458496s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10469675064086914s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.29855823516845703s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.2901763916015625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 1.1205673217773438e-05s
INFO | --- Analysis for cz-fulfillments took 3.0869688987731934s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.03151416778564453s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.28686952590942383s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.458427429199219e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 7.867813110351562e-06s
INFO | --- Analysis for cz-ic took 3.4109857082366943s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.12535762786865234s
Availability | VoID file availability check for List of Czech data boxes took 0.0005710124969482422s
Extra | Recovery of all triples for List of Czech data boxes took 145.08149194717407s
Performance | Total latancy measurement for List of Czech data boxes took 0.558969259262085s
Amount of data | Number of triples check for List of Czech data boxes took 38.324079751968384s
Interoperability | New terms check for List of Czech data boxes took 10.723356246948242s
Versatility | Languages check for List of Czech data boxes took 300.18391132354736s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.3919703960418701s
Interpretability | RDF structures check for List of Czech data boxes took 0.2956862449645996s
Versatility | Serialization formats check for List of Czech data boxes took 0.21849298477172852s
Availability | RDF dump link check for List of Czech data boxes took 14.743533849716187s
License | MR license check for List of Czech data boxes took 0.710747241973877s
License | HR license check for List of Czech data boxes took 55.927252769470215s
Amount of data | Number of property check for List of Czech data boxes took 0.12398552894592285s
Understandability | Number of label check for List of Czech data boxes took 1.9369287490844727s
Understandability | URI regex check for List of Czech data boxes took 0.5616533756256104s
Understandability | Vocabs check for List of Czech data boxes took 0.251096248626709s
Verifiability | Authors check for List of Czech data boxes took 0.2094252109527588s
Verifiability | Publishers check for List of Czech data boxes took 0.11540603637695312s
Performance | Throughput check for List of Czech data boxes took 10.700675964355469s
Amount of data | Check the number of entities for List of Czech data boxes took 3.0108728408813477s
Verifiability | Contribs. check for List of Czech data boxes took 0.19973301887512207s
Interlinking | sameAs chians check for List of Czech data boxes took 0.4448375701904297s
Interlinking | skos check for List of Czech data boxes took 0.22972369194030762s
Interlinking | skos check for List of Czech data boxes took 0.10609316825866699s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.20859003067016602s
Currency | Creation date check for List of Czech data boxes took 0.2709379196166992s
Currency | Modification date check for List of Czech data boxes took 0.12505483627319336s
Rep.Conc. | URIs length for List of Czech data boxes took 113.17840123176575s
Interoperability | New vocabularies check for List of Czech data boxes took 45.27125811576843s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.40100789070129395s
Accuracy | Check Functional Property for List of Czech data boxes took 0.2087407112121582s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.20650458335876465s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 31.647782802581787s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.045978546142578s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.6116955280303955s
Consistency | Disjoint class check for List of Czech data boxes took 0.10941481590270996s
Consistency | Check Misplaced properties for List of Czech data boxes took 69.33542609214783s
Consistency | Misplaced classes for List of Czech data boxes took 7.449543714523315s
Consistency | Check Ontology hijacking for List of Czech data boxes took 30.659083366394043s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.4223034381866455s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 63.801551818847656s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.608981132507324s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.3773517608642578s
Security | Sign check for List of Czech data boxes took 0.15307378768920898s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 358.80272126197815s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.6435308456420898s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.022025585174560547s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 3.695487976074219e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 42.05976343154907s
Believability | Calculation of trust value for List of Czech data boxes took 9.298324584960938e-06s
INFO | --- Analysis for cz-list-of-databoxes took 1707.6046764850616s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10913658142089844s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006427764892578125s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 145.89446353912354s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6555604934692383s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.894959211349487s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.917317628860474s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.18015003204346s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.1619937419891357s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12325382232666016s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1823434829711914s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 15.020027875900269s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11587285995483398s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 55.168275594711304s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11092686653137207s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3764123916625977s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4021031856536865s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1229395866394043s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1274735927581787s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10759425163269043s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.684531688690186s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.024885892868042s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11923456192016602s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2877049446105957s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10349678993225098s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11270809173583984s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1236259937286377s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.24996137619018555s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13087153434753418s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 111.80232787132263s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 42.92880058288574s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.39173007011413574s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11475157737731934s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12935829162597656s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.36505651473999s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0469632148742676s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6424176692962646s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12073969841003418s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 69.74646258354187s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.462311744689941s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 33.47474813461304s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4135677814483643s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 64.01390266418457s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.638483762741089s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.38307690620422363s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13541626930236816s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 353.74720454216003s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.40229129791259766s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.02099919319152832s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.291534423828125e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 41.10993504524231s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.298324584960938e-06s
INFO | --- Analysis for cz-nace took 1660.502023935318s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2972285747528076s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0005822181701660156s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.1 took 438.4409101009369s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8153786659240723s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.49634790420532227s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.325340986251831s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.1 took 300.2002332210541s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.38667631149292s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.9545409679412842s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.414669513702393s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.38425683975219727s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.6908187866210938s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.3387482166290283s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.16942119598388672s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.4294991493225098s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.47264790534973145s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.23644638061523438s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4758756160736084s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3572673797607422s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.1 took 10.983556032180786s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.1 took 9.417533874511719e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.20836448669433594s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.22838425636291504s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.44964098930358887s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.1776134967803955s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.5103237628936768s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7727062702178955s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3668825626373291s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.1 took 89.1586103439331s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.1660914421081543s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.403287410736084s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.40247464179992676s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.1 took 77.31412863731384s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.4183521270751953s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.6952285766601562s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.31023335456848145s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.1196067333221436s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.137275218963623s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.1 took 83.44525027275085s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.7744944095611572s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.812780380249023s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.1062538623809814s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2578165531158447s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.9239099025726318s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.1 took 959.5262796878815s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7608819007873535s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.02150440216064453s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.606910705566406e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.6450881958007812e-05s
INFO | --- Analysis for cz-nkod took 27785.236742019653s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.22040700912475586s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.30846214294433594s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.02204298973083496s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0009264945983886719s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 4.76837158203125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 1.0251998901367188e-05s
INFO | --- Analysis for cz-orders took 3.249011516571045s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.19134783744812012s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0006439685821533203s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 144.05690503120422s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.583568811416626s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.88756275177002s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.739037990570068s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.105348110199s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.387455940246582s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.15031218528747559s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.1944582462310791s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 15.0733003616333s
License | MR license check for Institutions of public power of the Czech Republic took 0.12277841567993164s
License | HR license check for Institutions of public power of the Czech Republic took 54.80200004577637s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.13715171813964844s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.4830787181854248s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.4723079204559326s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.1110382080078125s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.1287097930908203s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.12160325050354004s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.754288673400879s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.0111591815948486s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.13409757614135742s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.3925211429595947s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.18279290199279785s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.12129902839660645s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.2111053466796875s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.2859163284301758s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.14134979248046875s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 113.1764268875122s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 10.170566082000732s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.3941831588745117s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.18628883361816406s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.20075345039367676s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 33.20403742790222s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0284831523895264s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.651068687438965s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.13620376586914062s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 69.35553312301636s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.410393714904785s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 32.26545810699463s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.240067481994629s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 63.63558793067932s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.5886144638061523s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.37645530700683594s
Security | Sign check for Institutions of public power of the Czech Republic took 0.1336357593536377s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 358.84445357322693s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.38492250442504883s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.02140974998474121s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 10.03892970085144s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-ovm took 1602.9625883102417s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.11592292785644531s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.2995791435241699s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.021442413330078125s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.814697265625e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-ovm-agendas took 2.9995336532592773s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10232973098754883s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0002982616424560547s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 59.013530254364014s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6042575836181641s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 102.92095017433167s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 33.31080365180969s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.1761038303375s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14911937713623047s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.4684021472930908s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.17877960205078125s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7954332828521729s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.15143799781799316s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14585256576538086s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11697554588317871s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.9499142169952393s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.22731733322143555s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12345409393310547s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1853165626525879s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.16811776161193848s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.469138383865356s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.271766662597656e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11568117141723633s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10471081733703613s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1280205249786377s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1137704849243164s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11886930465698242s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2489321231842041s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12064862251281738s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 222.44711995124817s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.19096636772155762s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13396716117858887s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12287640571594238s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 13.181776523590088s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.170483112335205s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.588827610015869s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12109875679016113s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 167.96468687057495s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.225022554397583s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 17.419283628463745s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.2510950565338135s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 169.4219000339508s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.8408446311950684s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.24462413787841797s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11445927619934082s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.449355363845825s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6444230079650879s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.022606372833251953s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.796287536621094e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 4.76837158203125e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-ruian took 1590.4330117702484s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7587428092956543s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.2825486660003662s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.02083897590637207s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.367134094238281e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 4.224368572235107s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.5209307670593262s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.318143367767334s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020615577697753906s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0009756088256835938s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.9114227294921875e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.9186482429504395s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.4562239646911621s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.32677698135375977s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.0517578125e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 1.1205673217773438e-05s
INFO | --- Analysis for cz-sao-check-actions-law took 3.900880813598633s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.11529898643493652s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.3041541576385498s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.600120544433594e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.3113021850585938e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.0023772716522217s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.1114654541015625s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.28643107414245605s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.021823883056640625s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.3855438232421875e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.9619874954223633s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11272120475769043s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.3113536834716797s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.022139549255371094s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.743171691894531e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for cz-sidc-drugs took 3.1420817375183105s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.2036292552947998s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0005764961242675781s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 144.8338005542755s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5831310749053955s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.78573751449585s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.63052225112915s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1550238132477s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.3747940063476562s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.1420912742614746s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.19142436981201172s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.948345184326172s
License | MR license check for Summary types of Czech institutions of public power took 0.3800804615020752s
License | HR license check for Summary types of Czech institutions of public power took 55.066227197647095s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.10687613487243652s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.361387014389038s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.2376408576965332s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.11197733879089355s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.14197897911071777s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.11922645568847656s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.828541040420532s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 2.956561326980591s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.14286231994628906s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.4339582920074463s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.1281735897064209s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.11696600914001465s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.13873839378356934s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.24965810775756836s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.13683557510375977s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 113.47497797012329s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 9.203885793685913s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.3720571994781494s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.13011407852172852s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.13007736206054688s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 30.584054231643677s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.0352959632873535s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6486940383911133s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.13168597221374512s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 69.4551522731781s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.435121059417725s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 32.05806016921997s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.2324330806732178s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 64.28106570243835s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.6096630096435547s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.42238497734069824s
Security | Sign check for Summary types of Czech institutions of public power took 0.11550092697143555s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 354.6895170211792s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.6350739002227783s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.021832704544067383s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 3.337860107421875e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 9.978335618972778s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 9.5367431640625e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 1598.6310381889343s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.11530804634094238s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2996506690979004s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.123283386230469e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 3.118366003036499s
Availability | SPARQL endpoint availability check for State funding providers took 0.11878705024719238s
Availability | VoID file availability check for State funding providers took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for State funding providers took 0.2783365249633789s
Reputation | Calculation of the PageRank for State funding providers took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0009622573852539062s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.553794860839844e-05s
Believability | Calculation of trust value for State funding providers took 9.059906005859375e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.012624740600586s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.11169028282165527s
Availability | VoID file availability check for Organizations active in R&D took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.2922947406768799s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.7670135498046875e-05s
Believability | Calculation of trust value for Organizations active in R&D took 9.5367431640625e-06s
INFO | --- Analysis for cz-vavai-organizations took 3.216933012008667s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.11182045936584473s
Availability | VoID file availability check for R&D Programmes took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.28411030769348145s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020264863967895508s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.647804260253906e-05s
Believability | Calculation of trust value for R&D Programmes took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-programmes took 3.0533509254455566s
Availability | SPARQL endpoint availability check for R&D Projects took 0.1115865707397461s
Availability | VoID file availability check for R&D Projects took 0.0007622241973876953s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.2824254035949707s
Reputation | Calculation of the PageRank for R&D Projects took 0.020410537719726562s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 3.695487976074219e-05s
Believability | Calculation of trust value for R&D Projects took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-projects took 3.030120372772217s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10853171348571777s
Availability | VoID file availability check for Institutional research plans took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.3157658576965332s
Reputation | Calculation of the PageRank for Institutional research plans took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 3.647804260253906e-05s
Believability | Calculation of trust value for Institutional research plans took 8.58306884765625e-06s
INFO | --- Analysis for cz-vavai-research-plans took 3.1387224197387695s
Availability | SPARQL endpoint availability check for Results of R&D took 0.11669087409973145s
Availability | VoID file availability check for Results of R&D took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.2666280269622803s
Reputation | Calculation of the PageRank for Results of R&D took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.100799560546875e-05s
Believability | Calculation of trust value for Results of R&D took 4.0531158447265625e-06s
INFO | --- Analysis for cz-vavai-results took 3.0820069313049316s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.12015175819396973s
Availability | VoID file availability check for Tenders in R&D took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.30666661262512207s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 3.933906555175781e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-tenders took 3.075025796890259s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 5.078315734863281e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.30499982833862305s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.147125244140625e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.1444091796875e-05s
INFO | --- Analysis for czech_addresses took 4.510244846343994s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.6794929504394531s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.28632164001464844s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.021739959716796875s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for DanteLatinLoanwords took 4.482193470001221s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3839273452758789s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0005855560302734375s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 128.75924921035767s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0115394592285156s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 14.207058191299438s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.077338695526123s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.31742596626282s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.23791289329528809s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.1107473373413086s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.27787280082702637s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.26566505432128906s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2249133586883545s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.2926146984100342s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.2875325679779s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.24445748329162598s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.3600797653198242s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.4688711166381836s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.22921013832092285s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.5145373344421387s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.2469463348388672s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.532456636428833s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 9.1552734375e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.2220144271850586s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.9366767406463623s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 2.106982469558716s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.22935819625854492s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2584359645843506s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 0.48830556869506836s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 2.003936767578125s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 86.00146198272705s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.21671152114868164s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.2832820415496826s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.28093934059143066s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 40.83187937736511s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.1083312034606934s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.591174840927124s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.281341552734375s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 22.073240280151367s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 7.482149124145508s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 43.39950680732727s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.3394579887390137s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 22.727447271347046s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.7856171131134033s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.25748562812805176s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.2546401023864746s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 15.538839101791382s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.4347076416015625s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021188974380493164s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014400482177734375s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 2.1457672119140625e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.2159347534179688e-05s
INFO | --- Analysis for data-bnf-fr took 842.0265047550201s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.443897008895874s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.3051924705505371s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 7.319450378417969e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 9.775161743164062e-06s
INFO | --- Analysis for data-cnr-it took 3.9508204460144043s
Availability | SPARQL endpoint availability check for Data.gov took 1.7018053531646729s
Availability | VoID file availability check for Data.gov took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for Data.gov took 0.2984137535095215s
Reputation | Calculation of the PageRank for Data.gov took 0.020746231079101562s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Data.gov took 2.9087066650390625e-05s
Believability | Calculation of trust value for Data.gov took 9.5367431640625e-06s
INFO | --- Analysis for data-gov took 18.77720546722412s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.04579663276672363s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.3161942958831787s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.937980651855469e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 9.059906005859375e-06s
INFO | --- Analysis for data-gov-ie took 2.8259124755859375s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 8.726119995117188e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2819702625274658s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020842790603637695s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 6.794929504394531e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 9.298324584960938e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.713258981704712s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 22.015630960464478s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.00039458274841308594s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.29710960388183594s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02093982696533203s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.29425048828125e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.2159347534179688e-05s
INFO | --- Analysis for data-hnm-hu took 166.01842951774597s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.1114654541015625s
Availability | VoID file availability check for Climb Dataincubator took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.29942893981933594s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02138352394104004s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.104873657226562e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.0967254638671875e-05s
INFO | --- Analysis for data-incubator-climb took 2.845492362976074s
Availability | SPARQL endpoint availability check for Discogs in RDF took 8.678436279296875e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.30423927307128906s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.131431579589844e-05s
Believability | Calculation of trust value for Discogs in RDF took 1.239776611328125e-05s
INFO | --- Analysis for data-incubator-discogs took 4.602947235107422s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.060575246810913086s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.2933773994445801s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.02222299575805664s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.1975250244140625e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.640923023223877s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.06858015060424805s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.2938389778137207s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020474672317504883s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.463859558105469e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.3113021850585938e-05s
INFO | --- Analysis for data-incubator-moseley took 8.094880819320679s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.05640530586242676s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0004200935363769531s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.2864205837249756s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.02181863784790039s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.440017700195312e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.1205673217773438e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 2.7835423946380615s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.6978321075439453s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.30989503860473633s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.023557186126708984s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.487701416015625e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 8.58306884765625e-06s
INFO | --- Analysis for data-incubator-nasa took 7.873572826385498s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.05363297462463379s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.32351112365722656s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.021666526794433594s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.653236389160156e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.33514404296875e-05s
INFO | --- Analysis for data-incubator-our-airports took 2.846433639526367s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.19504094123840332s
Availability | VoID file availability check for Pokedex data in RDF took 0.0011413097381591797s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.3067748546600342s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 8.916854858398438e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.0251998901367188e-05s
INFO | --- Analysis for data-incubator-pokedex took 3.6640074253082275s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0645747184753418s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.2917609214782715s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.559226989746094e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.1682510375976562e-05s
INFO | --- Analysis for data-incubator-smcjournals took 2.820915460586548s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.27509331703186035s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006070137023925781s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 19.265459060668945s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 0.6265964508056641s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 16.45674991607666s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.4321963787078857s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.157864332199097s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.14635944366455s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.15484857559204102s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.31716179847717285s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.22637629508972168s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.1455984115600586s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.2924959659576416s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.144301652908325s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.9246268272399902s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 29.73029398918152s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.3271636962890625s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.1792285442352295s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.650216817855835s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.22774386405944824s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 10.912980079650879s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 8.177757263183594e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.2709200382232666s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.611363410949707s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2446916103363037s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.3387789726257324s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.320756196975708s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.42110180854797363s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.5720405578613281s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 30.31454348564148s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 62.15046715736389s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.21856904029846191s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.2406449317932129s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.1773974895477295s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 28.544365167617798s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.9317049980163574s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.138957738876343s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.6032421588897705s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.573969841003418s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 7.841843843460083s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 23.82452130317688s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.3801627159118652s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.662764310836792s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.838596820831299s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.34773683547973633s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.2598264217376709s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.12175440788269043s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.39242005348205566s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.021112442016601562s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.747245788574219e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 60.832834005355835s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.2636184692382812e-05s
INFO | --- Analysis for data-open-ac-uk took 691.1404807567596s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8479471206665039s
Availability | VoID file availability check for Persée in RDF took 0.0007476806640625s
Extra | Recovery of all triples for Persée in RDF took 1.6650474071502686s
Performance | Total latancy measurement for Persée in RDF took 0.6363019943237305s
Amount of data | Number of triples check for Persée in RDF took 1.1308186054229736s
Interoperability | New terms check for Persée in RDF took 2.0017714500427246s
Versatility | Languages check for Persée in RDF took 120.29222893714905s
Interpretability | Number of blank nodes check for Persée in RDF took 0.4617726802825928s
Interpretability | RDF structures check for Persée in RDF took 0.7385704517364502s
Versatility | Serialization formats check for Persée in RDF took 0.8860743045806885s
Availability | RDF dump link check for Persée in RDF took 0.27115607261657715s
License | MR license check for Persée in RDF took 1.3391270637512207s
License | HR license check for Persée in RDF took 39.7931113243103s
Amount of data | Number of property check for Persée in RDF took 0.14061808586120605s
Understandability | Number of label check for Persée in RDF took 1.9120995998382568s
Understandability | URI regex check for Persée in RDF took 0.7902977466583252s
Understandability | Vocabs check for Persée in RDF took 0.3888108730316162s
Verifiability | Authors check for Persée in RDF took 0.15423798561096191s
Verifiability | Publishers check for Persée in RDF took 0.13273406028747559s
Performance | Throughput check for Persée in RDF took 10.600614070892334s
Amount of data | Check the number of entities for Persée in RDF took 7.033348083496094e-05s
Verifiability | Contribs. check for Persée in RDF took 0.11683225631713867s
Interlinking | sameAs chians check for Persée in RDF took 0.20556020736694336s
Interlinking | skos check for Persée in RDF took 0.6557083129882812s
Interlinking | skos check for Persée in RDF took 0.13197922706604004s
Timeliness | dataset update frequency check for Persée in RDF took 0.6115682125091553s
Currency | Creation date check for Persée in RDF took 0.5682501792907715s
Currency | Modification date check for Persée in RDF took 0.25286221504211426s
Rep.Conc. | URIs length for Persée in RDF took 3.5570969581604004s
Interoperability | New vocabularies check for Persée in RDF took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.12193083763122559s
Accuracy | Check Functional Property for Persée in RDF took 0.1610431671142578s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.14240574836730957s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.6941852569580078s
Accuracy | Check White space in annotation for Persée in RDF took 0.03913402557373047s
Accuracy | Check Datatype consistency for Persée in RDF took 0.027492761611938477s
Consistency | Disjoint class check for Persée in RDF took 0.2672293186187744s
Consistency | Check Misplaced properties for Persée in RDF took 2.6729822158813477s
Consistency | Misplaced classes for Persée in RDF took 0.2266397476196289s
Consistency | Check Ontology hijacking for Persée in RDF took 1.8620412349700928s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.3124971389770508s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.796584367752075s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03089618682861328s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.1892688274383545s
Security | Sign check for Persée in RDF took 0.8053109645843506s
Availability | Check URIs Dereferenciability for Persée in RDF took 1434.5395803451538s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.5224006175994873s
Reputation | Calculation of the PageRank for Persée in RDF took 0.02127814292907715s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 6.890296936035156e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010967254638671875s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Persée in RDF took 9.5367431640625e-06s
INFO | --- Analysis for data-persee-fr took 1676.481572151184s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.1037309169769287s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.3006916046142578s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020971059799194336s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011491775512695312s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.2159347534179688e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.031936168670654s
Availability | SPARQL endpoint availability check for Open Data Web took 6.457406520843506s
Availability | VoID file availability check for Open Data Web took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.28600192070007324s
Reputation | Calculation of the PageRank for Open Data Web took 0.022190570831298828s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Data Web took 1.0728836059570312e-05s
INFO | --- Analysis for data.odw.tw took 14.572429180145264s
Availability | SPARQL endpoint availability check for datahub took 4.458427429199219e-05s
Availability | VoID file availability check for datahub took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for datahub took 0.312044620513916s
Reputation | Calculation of the PageRank for datahub took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for datahub took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for datahub took 4.76837158203125e-05s
Believability | Calculation of trust value for datahub took 1.239776611328125e-05s
INFO | --- Analysis for datahub took 4.401203870773315s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.50100040435791s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0003910064697265625s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.3097968101501465s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.022557735443115234s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.2901763916015625e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 7.867813110351562e-06s
INFO | --- Analysis for datahub-kr-datamap took 13.03113079071045s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.41073036193847656s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.00040602684020996094s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2938258647918701s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.67572021484375e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.4066696166992188e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.762144565582275s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.361086130142212s
Availability | VoID file availability check for datos-artium-org took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.3352549076080322s
Reputation | Calculation of the PageRank for datos-artium-org took 0.021442413330078125s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011754035949707031s
Believability | Calculation of trust value for datos-artium-org took 1.1444091796875e-05s
INFO | --- Analysis for datos-artium-org took 165.30773377418518s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8787195682525635s
Availability | VoID file availability check for Datos.bcn.cl took 0.0005841255187988281s
Extra | Recovery of all triples for Datos.bcn.cl took 26.753151893615723s
Performance | Total latancy measurement for Datos.bcn.cl took 6.0707011222839355s
Amount of data | Number of triples check for Datos.bcn.cl took 4.58077335357666s
Interoperability | New terms check for Datos.bcn.cl took 3.8396949768066406s
Versatility | Languages check for Datos.bcn.cl took 289.5925257205963s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.2911672592163086s
Security | Check HTTPS for Datos.bcn.cl took 0.7551367282867432s
Interpretability | RDF structures check for Datos.bcn.cl took 1.3085122108459473s
Versatility | Serialization formats check for Datos.bcn.cl took 1.236217975616455s
Availability | RDF dump link check for Datos.bcn.cl took 1.2248389720916748s
License | MR license check for Datos.bcn.cl took 1.2240033149719238s
License | HR license check for Datos.bcn.cl took 31.309684991836548s
Amount of data | Number of property check for Datos.bcn.cl took 1.2377018928527832s
Understandability | Number of label check for Datos.bcn.cl took 4.14389967918396s
Understandability | URI regex check for Datos.bcn.cl took 2.424084186553955s
Understandability | Vocabs check for Datos.bcn.cl took 1.2339847087860107s
Verifiability | Authors check for Datos.bcn.cl took 1.2359914779663086s
Verifiability | Publishers check for Datos.bcn.cl took 1.2284443378448486s
Performance | Throughput check for Datos.bcn.cl took 12.251967430114746s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.033348083496094e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2142744064331055s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2445387840270996s
Interlinking | skos check for Datos.bcn.cl took 1.2417006492614746s
Interlinking | skos check for Datos.bcn.cl took 1.212906837463379s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2215745449066162s
Currency | Creation date check for Datos.bcn.cl took 2.434016466140747s
Currency | Modification date check for Datos.bcn.cl took 1.2535645961761475s
Rep.Conc. | URIs length for Datos.bcn.cl took 24.0988028049469s
Interoperability | New vocabularies check for Datos.bcn.cl took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2144896984100342s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.2248899936676025s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.214606523513794s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 16.25328826904297s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.32019686698913574s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2616589069366455s
Consistency | Disjoint class check for Datos.bcn.cl took 1.2106726169586182s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.778829097747803s
Consistency | Misplaced classes for Datos.bcn.cl took 2.019714832305908s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 11.772446393966675s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.350337266921997s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.450164794921875s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.29232096672058105s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.4859652519226074s
Security | Sign check for Datos.bcn.cl took 1.2477045059204102s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 8281.890264749527s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.7435743808746338s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02139735221862793s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 2.956390380859375e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.430511474609375e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 9.775161743164062e-06s
INFO | --- Analysis for datos-bcn-cl took 9087.51614356041s
Availability | SPARQL endpoint availability check for datos.bne.es took 2.355388879776001s
Availability | VoID file availability check for datos.bne.es took 0.0006434917449951172s
Extra | Recovery of all triples for datos.bne.es took 161.9722034931183s
Performance | Total latancy measurement for datos.bne.es took 6.816193342208862s
Amount of data | Number of triples check for datos.bne.es took 2.7849361896514893s
Interoperability | New terms check for datos.bne.es took 2.419394016265869s
Versatility | Languages check for datos.bne.es took 63.07452464103699s
Interpretability | Number of blank nodes check for datos.bne.es took 0.36454224586486816s
Security | Check HTTPS for datos.bne.es took 2.094442129135132s
Interpretability | RDF structures check for datos.bne.es took 0.6846368312835693s
Versatility | Serialization formats check for datos.bne.es took 2.6165127754211426s
Availability | RDF dump link check for datos.bne.es took 2.315031051635742s
License | MR license check for datos.bne.es took 2.704235315322876s
License | HR license check for datos.bne.es took 61.62935280799866s
Amount of data | Number of property check for datos.bne.es took 2.231051445007324s
Understandability | Number of label check for datos.bne.es took 1.2552697658538818s
Understandability | URI regex check for datos.bne.es took 2.8975472450256348s
Understandability | Vocabs check for datos.bne.es took 0.46335434913635254s
Verifiability | Authors check for datos.bne.es took 2.4252233505249023s
Verifiability | Publishers check for datos.bne.es took 2.3428142070770264s
Performance | Throughput check for datos.bne.es took 21.648449897766113s
Amount of data | Check the number of entities for datos.bne.es took 6.914138793945312e-05s
Verifiability | Contribs. check for datos.bne.es took 0.4809422492980957s
Interlinking | sameAs chians check for datos.bne.es took 0.5799579620361328s
Interlinking | skos check for datos.bne.es took 0.8084678649902344s
Interlinking | skos check for datos.bne.es took 0.3482961654663086s
Timeliness | dataset update frequency check for datos.bne.es took 0.5159873962402344s
Currency | Creation date check for datos.bne.es took 0.8608927726745605s
Currency | Modification date check for datos.bne.es took 2.5591533184051514s
Rep.Conc. | URIs length for datos.bne.es took 65.91247153282166s
Interoperability | New vocabularies check for datos.bne.es took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.3845329284667969s
Accuracy | Check Functional Property for datos.bne.es took 0.38862037658691406s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.36678266525268555s
Accuracy | Check Empty annotation labels for datos.bne.es took 48.79860281944275s
Accuracy | Check White space in annotation for datos.bne.es took 1.5930774211883545s
Accuracy | Check Datatype consistency for datos.bne.es took 1.278878927230835s
Consistency | Disjoint class check for datos.bne.es took 0.4165360927581787s
Consistency | Check Misplaced properties for datos.bne.es took 8.955283164978027s
Consistency | Misplaced classes for datos.bne.es took 4.341192960739136s
Consistency | Check Ontology hijacking for datos.bne.es took 48.00270891189575s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.2603230476379395s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 11.639284133911133s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.366051197052002s
Conciseness | Check Intensional conciseness for datos.bne.es took 2.258037567138672s
Security | Sign check for datos.bne.es took 1.1276583671569824s
Availability | Check URIs Dereferenciability for datos.bne.es took 10.470448970794678s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.4028501510620117s
Reputation | Calculation of the PageRank for datos.bne.es took 0.025370359420776367s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011897087097167969s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 1.9073486328125e-06s
Believability | Calculation of trust value for datos.bne.es took 1.1205673217773438e-05s
INFO | --- Analysis for datos-bne-es took 704.9903075695038s
Availability | SPARQL endpoint availability check for dbacademic took 0.06605172157287598s
Availability | VoID file availability check for dbacademic took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for dbacademic took 0.3250095844268799s
Reputation | Calculation of the PageRank for dbacademic took 0.022477149963378906s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for dbacademic took 4.9591064453125e-05s
Believability | Calculation of trust value for dbacademic took 4.38690185546875e-05s
INFO | --- Analysis for dbacademic took 3.002007246017456s
Availability | SPARQL endpoint availability check for DBkWik took 0.20152974128723145s
Availability | VoID file availability check for DBkWik took 0.00066375732421875s
Extra | Recovery of all triples for DBkWik took 1.4187030792236328s
Performance | Total latancy measurement for DBkWik took 0.44225072860717773s
Amount of data | Number of triples check for DBkWik took 5.260350942611694s
Interoperability | New terms check for DBkWik took 2.149866819381714s
Versatility | Languages check for DBkWik took 61.150704860687256s
Interpretability | Number of blank nodes check for DBkWik took 0.1337909698486328s
Interpretability | RDF structures check for DBkWik took 0.21697115898132324s
Versatility | Serialization formats check for DBkWik took 0.28856611251831055s
Availability | RDF dump link check for DBkWik took 2.9429779052734375s
License | MR license check for DBkWik took 0.47205185890197754s
License | HR license check for DBkWik took 60.42241549491882s
Amount of data | Number of property check for DBkWik took 0.15669512748718262s
Understandability | Number of label check for DBkWik took 2.1114771366119385s
Understandability | URI regex check for DBkWik took 0.3187441825866699s
Understandability | Vocabs check for DBkWik took 0.1323227882385254s
Verifiability | Authors check for DBkWik took 0.1285097599029541s
Verifiability | Publishers check for DBkWik took 0.09217405319213867s
Performance | Throughput check for DBkWik took 10.398284912109375s
Amount of data | Check the number of entities for DBkWik took 4.935264587402344e-05s
Verifiability | Contribs. check for DBkWik took 0.11881208419799805s
Interlinking | sameAs chians check for DBkWik took 0.4429199695587158s
Interlinking | skos check for DBkWik took 0.35305213928222656s
Interlinking | skos check for DBkWik took 0.0931098461151123s
Timeliness | dataset update frequency check for DBkWik took 0.17250776290893555s
Currency | Creation date check for DBkWik took 0.5190718173980713s
Currency | Modification date check for DBkWik took 0.21076726913452148s
Rep.Conc. | URIs length for DBkWik took 11.808397769927979s
Interoperability | New vocabularies check for DBkWik took 2.923574209213257s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.11504054069519043s
Accuracy | Check Functional Property for DBkWik took 0.311382532119751s
Accuracy | Check Inverse Functional Property for DBkWik took 0.26494908332824707s
Accuracy | Check Empty annotation labels for DBkWik took 0.8470358848571777s
Accuracy | Check White space in annotation for DBkWik took 0.02364325523376465s
Accuracy | Check Datatype consistency for DBkWik took 0.03770041465759277s
Consistency | Disjoint class check for DBkWik took 0.11109042167663574s
Consistency | Check Misplaced properties for DBkWik took 11.589349508285522s
Consistency | Misplaced classes for DBkWik took 0.6331384181976318s
Consistency | Check Ontology hijacking for DBkWik took 1.8131310939788818s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.2931058406829834s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.921232223510742s
Conciseness | Check Extensional conciseness for DBkWik took 0.03247714042663574s
Conciseness | Check Intensional conciseness for DBkWik took 0.6971786022186279s
Security | Sign check for DBkWik took 0.30734801292419434s
Availability | Check URIs Dereferenciability for DBkWik took 10.126601457595825s
Completeness | Calculation of interlinking completeness for DBkWik took 0.4123990535736084s
Reputation | Calculation of the PageRank for DBkWik took 0.20357751846313477s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for DBkWik took 8.392333984375e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 3.327697992324829s
Believability | Calculation of trust value for DBkWik took 1.1682510375976562e-05s
INFO | --- Analysis for dbkwik took 1261.9781715869904s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.410743713378906e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.31154918670654297s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00010418891906738281s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.1682510375976562e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 4.470937252044678s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.3520355224609375s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0006287097930908203s
Extra | Recovery of all triples for dblp Knowledge Graph took 7.870956182479858s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.8688437938690186s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.16415739059448242s
Interoperability | New terms check for dblp Knowledge Graph took 1.8331420421600342s
Versatility | Languages check for dblp Knowledge Graph took 0.2155594825744629s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 3.897989511489868s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.1869354248046875s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.2088453769683838s
Availability | RDF dump link check for dblp Knowledge Graph took 0.17186331748962402s
License | MR license check for dblp Knowledge Graph took 0.166792631149292s
License | HR license check for dblp Knowledge Graph took 30.17979097366333s
Amount of data | Number of property check for dblp Knowledge Graph took 0.16791534423828125s
Understandability | Number of label check for dblp Knowledge Graph took 0.47078537940979004s
Understandability | URI regex check for dblp Knowledge Graph took 0.29897475242614746s
Understandability | Vocabs check for dblp Knowledge Graph took 0.17554330825805664s
Verifiability | Authors check for dblp Knowledge Graph took 0.17708539962768555s
Verifiability | Publishers check for dblp Knowledge Graph took 0.14409232139587402s
Performance | Throughput check for dblp Knowledge Graph took 10.7902250289917s
Amount of data | Check the number of entities for dblp Knowledge Graph took 6.937980651855469e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.14436912536621094s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.23058009147644043s
Interlinking | skos check for dblp Knowledge Graph took 0.1553194522857666s
Interlinking | skos check for dblp Knowledge Graph took 0.1804351806640625s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.2008678913116455s
Currency | Creation date check for dblp Knowledge Graph took 0.3212442398071289s
Currency | Modification date check for dblp Knowledge Graph took 0.3437235355377197s
Rep.Conc. | URIs length for dblp Knowledge Graph took 15.712862253189087s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.12096142768859863s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.14047670364379883s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.16179490089416504s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 6.689465761184692s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.055858850479126s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 5.984692335128784s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.14906597137451172s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.31619763374328613s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 5.615671873092651s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 17762.021778821945s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 3.871459722518921s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.6518805027008057s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.17851591110229492s
Security | Sign check for dblp Knowledge Graph took 0.18783903121948242s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 23.200170516967773s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.7248523235321045s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.6689300537109375e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 6.0558319091796875e-05s
INFO | --- Analysis for dblp-kg took 18028.698157310486s
Availability | SPARQL endpoint availability check for DBnary took 0.37824368476867676s
Availability | VoID file availability check for DBnary took 0.0005395412445068359s
Extra | Recovery of all triples for DBnary took 1.0851154327392578s
Performance | Total latancy measurement for DBnary took 0.4102020263671875s
Amount of data | Number of triples check for DBnary took 1.3449337482452393s
Interoperability | New terms check for DBnary took 3.5777549743652344s
Versatility | Languages check for DBnary took 60.12695550918579s
Interpretability | Number of blank nodes check for DBnary took 0.8644804954528809s
Security | Check HTTPS for DBnary took 0.1754152774810791s
Interpretability | RDF structures check for DBnary took 0.149383544921875s
Versatility | Serialization formats check for DBnary took 0.2531471252441406s
Availability | RDF dump link check for DBnary took 0.07185006141662598s
License | MR license check for DBnary took 0.22655415534973145s
License | HR license check for DBnary took 55.88051676750183s
Amount of data | Number of property check for DBnary took 0.10432767868041992s
Understandability | Number of label check for DBnary took 0.8492586612701416s
Understandability | URI regex check for DBnary took 0.1432187557220459s
Understandability | Vocabs check for DBnary took 0.19737720489501953s
Verifiability | Authors check for DBnary took 0.22840666770935059s
Verifiability | Publishers check for DBnary took 0.11622214317321777s
Performance | Throughput check for DBnary took 12.733919620513916s
Amount of data | Check the number of entities for DBnary took 8.058547973632812e-05s
Verifiability | Contribs. check for DBnary took 0.11374592781066895s
Interlinking | sameAs chians check for DBnary took 0.11693239212036133s
Interlinking | skos check for DBnary took 0.24281692504882812s
Interlinking | skos check for DBnary took 0.09183216094970703s
Timeliness | dataset update frequency check for DBnary took 0.15578484535217285s
Currency | Creation date check for DBnary took 0.23649811744689941s
Currency | Modification date check for DBnary took 0.21472525596618652s
Rep.Conc. | URIs length for DBnary took 11.137842416763306s
Interoperability | New vocabularies check for DBnary took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for DBnary took 0.10209059715270996s
Accuracy | Check Functional Property for DBnary took 0.176422119140625s
Accuracy | Check Inverse Functional Property for DBnary took 0.13084959983825684s
Accuracy | Check Empty annotation labels for DBnary took 0.4916410446166992s
Accuracy | Check White space in annotation for DBnary took 0.024446964263916016s
Accuracy | Check Datatype consistency for DBnary took 0.0276486873626709s
Consistency | Disjoint class check for DBnary took 0.17228412628173828s
Consistency | Check Misplaced properties for DBnary took 8.613662958145142s
Consistency | Misplaced classes for DBnary took 0.22756457328796387s
Consistency | Check Ontology hijacking for DBnary took 1.8285636901855469s
Consistency | Check Invalid usage of undefined classes for DBnary took 1.3953616619110107s
Consistency | Check Invalid usage of undefined properties for DBnary took 9.793532609939575s
Conciseness | Check Extensional conciseness for DBnary took 0.032338857650756836s
Conciseness | Check Intensional conciseness for DBnary took 0.22624754905700684s
Security | Sign check for DBnary took 0.07271623611450195s
Availability | Check URIs Dereferenciability for DBnary took 15.297640800476074s
Completeness | Calculation of interlinking completeness for DBnary took 0.29671430587768555s
Reputation | Calculation of the PageRank for DBnary took 0.020828962326049805s
Interlinking | Calculation of Degree of Connection for DBnary took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for DBnary took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for DBnary took 5.435943603515625e-05s
Interoperability | Check the re-using of existing vocabs for DBnary took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBnary took 1.239776611328125e-05s
INFO | --- Analysis for dbnary took 287.88524651527405s
Availability | SPARQL endpoint availability check for DBpedia took 3.623507261276245s
Availability | VoID file availability check for DBpedia took 0.0006687641143798828s
Extra | Recovery of all triples for DBpedia took 38.62043356895447s
Performance | Total latancy measurement for DBpedia took 10.435791492462158s
Amount of data | Number of triples check for DBpedia took 3.230217695236206s
Versatility | Languages check for DBpedia took 38.05910062789917s
Interpretability | Number of blank nodes check for DBpedia took 0.6892509460449219s
Security | Check HTTPS for DBpedia took 0.3935885429382324s
Interpretability | RDF structures check for DBpedia took 3.4864375591278076s
Versatility | Serialization formats check for DBpedia took 4.006648063659668s
Availability | RDF dump link check for DBpedia took 4.532088041305542s
License | MR license check for DBpedia took 5.366481065750122s
License | HR license check for DBpedia took 40.646589279174805s
Amount of data | Number of property check for DBpedia took 1.9623198509216309s
Understandability | Number of label check for DBpedia took 7.201290845870972s
Understandability | URI regex check for DBpedia took 8.911536693572998s
Understandability | Vocabs check for DBpedia took 4.715080738067627s
Verifiability | Authors check for DBpedia took 5.928068399429321s
Verifiability | Publishers check for DBpedia took 4.034856081008911s
Performance | Throughput check for DBpedia took 53.011823415756226s
Amount of data | Check the number of entities for DBpedia took 7.510185241699219e-05s
Verifiability | Contribs. check for DBpedia took 4.743339538574219s
Interlinking | sameAs chians check for DBpedia took 4.742684364318848s
Interlinking | skos check for DBpedia took 14.75956678390503s
Interlinking | skos check for DBpedia took 0.5366127490997314s
Timeliness | dataset update frequency check for DBpedia took 0.8030984401702881s
Currency | Creation date check for DBpedia took 9.28645634651184s
Currency | Modification date check for DBpedia took 1.9837043285369873s
Rep.Conc. | URIs length for DBpedia took 54.04945087432861s
Interoperability | New vocabularies check for DBpedia took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 1.5424413681030273s
Accuracy | Check Functional Property for DBpedia took 4.696449518203735s
Accuracy | Check Inverse Functional Property for DBpedia took 3.750910758972168s
Accuracy | Check Empty annotation labels for DBpedia took 7.640315532684326s
Accuracy | Check White space in annotation for DBpedia took 0.029666662216186523s
Accuracy | Check Datatype consistency for DBpedia took 0.02721405029296875s
Consistency | Disjoint class check for DBpedia took 3.7490692138671875s
Consistency | Check Misplaced properties for DBpedia took 53.14531636238098s
Consistency | Check Ontology hijacking for DBpedia took 18.533717393875122s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.234985113143921s
Consistency | Check Invalid usage of undefined properties for DBpedia took 22.240986824035645s
Conciseness | Check Extensional conciseness for DBpedia took 0.0321812629699707s
Security | Sign check for DBpedia took 1.6313343048095703s
Availability | Check URIs Dereferenciability for DBpedia took 10889.717047452927s
Completeness | Calculation of interlinking completeness for DBpedia took 0.6707644462585449s
Reputation | Calculation of the PageRank for DBpedia took 0.020970582962036133s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009083747863769531s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 1.1205673217773438e-05s
INFO | --- Analysis for dbpedia took 11568.676436662674s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 8.893013000488281e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.26738739013671875s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.937980651855469e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.1920928955078125e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 7.562213182449341s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.180950403213501s
Availability | VoID file availability check for DBpedia Commons took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.278639554977417s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.270408630371094e-05s
Believability | Calculation of trust value for DBpedia Commons took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-commons took 16.548665523529053s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.9021961688995361s
Availability | VoID file availability check for DBpedia in Greek took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.29381752014160156s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00019407272338867188s
Believability | Calculation of trust value for DBpedia in Greek took 1.1444091796875e-05s
INFO | --- Analysis for dbpedia-el took 7.3746702671051025s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.44203877449035645s
Availability | VoID file availability check for DBpedia in Spanish took 0.0006091594696044922s
Extra | Recovery of all triples for DBpedia in Spanish took 2.6498782634735107s
Performance | Total latancy measurement for DBpedia in Spanish took 1.2222349643707275s
Amount of data | Number of triples check for DBpedia in Spanish took 0.8803038597106934s
Interoperability | New terms check for DBpedia in Spanish took 3.3176064491271973s
Versatility | Languages check for DBpedia in Spanish took 61.5926411151886s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.39499330520629883s
Security | Check HTTPS for DBpedia in Spanish took 0.13614153861999512s
Interpretability | RDF structures check for DBpedia in Spanish took 1.2379052639007568s
Versatility | Serialization formats check for DBpedia in Spanish took 0.6278808116912842s
Availability | RDF dump link check for DBpedia in Spanish took 0.3740365505218506s
License | MR license check for DBpedia in Spanish took 0.9851884841918945s
License | HR license check for DBpedia in Spanish took 60.642053842544556s
Amount of data | Number of property check for DBpedia in Spanish took 0.3487968444824219s
Understandability | Number of label check for DBpedia in Spanish took 2.0983242988586426s
Understandability | URI regex check for DBpedia in Spanish took 1.2709879875183105s
Understandability | Vocabs check for DBpedia in Spanish took 0.901235818862915s
Verifiability | Authors check for DBpedia in Spanish took 0.695737361907959s
Verifiability | Publishers check for DBpedia in Spanish took 0.7094807624816895s
Performance | Throughput check for DBpedia in Spanish took 12.000893831253052s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.343292236328125e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.32474660873413086s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.7634074687957764s
Interlinking | skos check for DBpedia in Spanish took 0.6585888862609863s
Interlinking | skos check for DBpedia in Spanish took 0.23034334182739258s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.4510936737060547s
Currency | Creation date check for DBpedia in Spanish took 0.596367359161377s
Currency | Modification date check for DBpedia in Spanish took 0.600841760635376s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.932459354400635s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.291766881942749s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.5010488033294678s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.457460880279541s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.4065625667572021s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.030232906341552734s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.03196859359741211s
Consistency | Disjoint class check for DBpedia in Spanish took 0.30043721199035645s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.576128721237183s
Consistency | Misplaced classes for DBpedia in Spanish took 1.125067949295044s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.4171972274780273s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.2314701080322266s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.960014343261719s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03151893615722656s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.7626426219940186s
Security | Sign check for DBpedia in Spanish took 0.6376945972442627s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 3.105361223220825s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.40088939666748047s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010228157043457031s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-es took 2777.0560824871063s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.2127878665924072s
Availability | VoID file availability check for DBpedia in Basque took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.29088640213012695s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.021688222885131836s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.409385681152344e-05s
Believability | Calculation of trust value for DBpedia in Basque took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-eu took 7.195430278778076s
Availability | SPARQL endpoint availability check for DBpedia in French took 10.758182287216187s
Availability | VoID file availability check for DBpedia in French took 0.0008790493011474609s
Extra | Recovery of all triples for DBpedia in French took 300.09681129455566s
Performance | Total latancy measurement for DBpedia in French took 119.64057564735413s
Amount of data | Number of triples check for DBpedia in French took 134.33487939834595s
Versatility | Languages check for DBpedia in French took 9.999900817871094s
Interpretability | Number of blank nodes check for DBpedia in French took 73.60176658630371s
Security | Check HTTPS for DBpedia in French took 17.130285501480103s
Interpretability | RDF structures check for DBpedia in French took 52.96597743034363s
Versatility | Serialization formats check for DBpedia in French took 100.08464169502258s
Availability | RDF dump link check for DBpedia in French took 10.000686168670654s
License | MR license check for DBpedia in French took 108.68364405632019s
License | HR license check for DBpedia in French took 10.11401915550232s
Amount of data | Number of property check for DBpedia in French took 77.82545757293701s
Understandability | Number of label check for DBpedia in French took 74.31880950927734s
Understandability | URI regex check for DBpedia in French took 99.7493462562561s
Understandability | Vocabs check for DBpedia in French took 63.91185235977173s
Verifiability | Authors check for DBpedia in French took 41.78595161437988s
Verifiability | Publishers check for DBpedia in French took 63.00067114830017s
Amount of data | Check the number of entities for DBpedia in French took 8.749961853027344e-05s
Verifiability | Contribs. check for DBpedia in French took 10.001672744750977s
Interlinking | sameAs chians check for DBpedia in French took 9.997822284698486s
Interlinking | skos check for DBpedia in French took 10.001872062683105s
Interlinking | skos check for DBpedia in French took 101.38839936256409s
Timeliness | dataset update frequency check for DBpedia in French took 68.19960069656372s
Currency | Creation date check for DBpedia in French took 43.609026193618774s
Currency | Modification date check for DBpedia in French took 46.27042031288147s
Rep.Conc. | URIs length for DBpedia in French took 346.04051065444946s
Interoperability | New vocabularies check for DBpedia in French took 7.303773403167725s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 15.896777153015137s
Accuracy | Check Functional Property for DBpedia in French took 21.31187629699707s
Accuracy | Check Inverse Functional Property for DBpedia in French took 28.994393825531006s
Consistency | Disjoint class check for DBpedia in French took 42.10131216049194s
Consistency | Check Misplaced properties for DBpedia in French took 119.54628729820251s
Consistency | Misplaced classes for DBpedia in French took 39.51029706001282s
Consistency | Check Ontology hijacking for DBpedia in French took 160.2476053237915s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 52.192036390304565s
Conciseness | Check Extensional conciseness for DBpedia in French took 0.00014591217041015625s
Conciseness | Check Intensional conciseness for DBpedia in French took 43.25965118408203s
Security | Sign check for DBpedia in French took 62.3790647983551s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.7260444164276123s
Reputation | Calculation of the PageRank for DBpedia in French took 0.021699905395507812s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00010585784912109375s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 6.2971460819244385s
Believability | Calculation of trust value for DBpedia in French took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-fr took 5036.971346378326s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.9172492027282715s
Availability | VoID file availability check for DBpedia in Japanese took 4.286721229553223s
Extra | Recovery of all triples for DBpedia in Japanese took 5.50312614440918s
Performance | Total latancy measurement for DBpedia in Japanese took 6.6351096630096436s
Amount of data | Number of triples check for DBpedia in Japanese took 28.894581079483032s
Interoperability | New terms check for DBpedia in Japanese took 17.783162593841553s
Versatility | Languages check for DBpedia in Japanese took 1.3339693546295166s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3233270645141602s
Security | Check HTTPS for DBpedia in Japanese took 0.7982218265533447s
Interpretability | RDF structures check for DBpedia in Japanese took 1.380737543106079s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3521130084991455s
Availability | RDF dump link check for DBpedia in Japanese took 1.3337671756744385s
License | MR license check for DBpedia in Japanese took 1.37026047706604s
License | HR license check for DBpedia in Japanese took 61.322617292404175s
Amount of data | Number of property check for DBpedia in Japanese took 1.3607704639434814s
Understandability | Number of label check for DBpedia in Japanese took 1.328028917312622s
Understandability | URI regex check for DBpedia in Japanese took 2.6511423587799072s
Understandability | Vocabs check for DBpedia in Japanese took 1.3140709400177002s
Verifiability | Authors check for DBpedia in Japanese took 1.3329010009765625s
Verifiability | Publishers check for DBpedia in Japanese took 1.3360178470611572s
Amount of data | Check the number of entities for DBpedia in Japanese took 6.866455078125e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3383877277374268s
Interlinking | sameAs chians check for DBpedia in Japanese took 3.0194249153137207s
Interlinking | skos check for DBpedia in Japanese took 1.3550503253936768s
Interlinking | skos check for DBpedia in Japanese took 1.3197898864746094s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3458740711212158s
Currency | Creation date check for DBpedia in Japanese took 2.70243763923645s
Currency | Modification date check for DBpedia in Japanese took 2.6593754291534424s
Rep.Conc. | URIs length for DBpedia in Japanese took 110.78947901725769s
Interoperability | New vocabularies check for DBpedia in Japanese took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3310949802398682s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3640830516815186s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.3441333770751953s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 2.966895341873169s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.026144981384277344s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.027662038803100586s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4820964336395264s
Consistency | Check Misplaced properties for DBpedia in Japanese took 62.66029715538025s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 35.98171257972717s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.2729477882385254s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 62.56757640838623s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03283977508544922s
Security | Sign check for DBpedia in Japanese took 1.3178002834320068s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 10.126571893692017s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.34227609634399414s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.021020889282226562s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 9.965896606445312e-05s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 7.152557373046875e-07s
Believability | Calculation of trust value for DBpedia in Japanese took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-ja took 794.5487861633301s
Availability | SPARQL endpoint availability check for dbpedia lite took 8.916854858398438e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.30489277839660645s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.751319885253906e-05s
Believability | Calculation of trust value for dbpedia lite took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-lite took 7.300090551376343s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.25334787368774414s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.290313720703125s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02024674415588379s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016355514526367188s
Believability | Calculation of trust value for DBpedia in Dutch took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-nl took 3.4687304496765137s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 13.390118598937988s
Availability | VoID file availability check for DBpedia in Portuguese took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.3002912998199463s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.021027803421020508s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 0.00010991096496582031s
Believability | Calculation of trust value for DBpedia in Portuguese took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-pt took 38.21970844268799s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.315376281738281e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0003974437713623047s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.2804286479949951s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020662546157836914s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.67572021484375e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.990987777709961s
Availability | SPARQL endpoint availability check for DBTropes took 8.845329284667969e-05s
Availability | VoID file availability check for DBTropes took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for DBTropes took 0.3021523952484131s
Reputation | Calculation of the PageRank for DBTropes took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for DBTropes took 8.797645568847656e-05s
Believability | Calculation of trust value for DBTropes took 1.2159347534179688e-05s
INFO | --- Analysis for dbtropes took 3.3265621662139893s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.1484832763671875e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.2811696529388428s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 4.935264587402344e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 6.9141387939453125e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 2.908623456954956s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.172325134277344e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.00041294097900390625s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.3013942241668701s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.147125244140625e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.2159347534179688e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 2.8914453983306885s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.592597961425781s
Availability | VoID file availability check for DBTune.org/classical took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.2780120372772217s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.677078247070312e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-classical took 9.175827980041504s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.556077718734741s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.3451700210571289s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.02104496955871582s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0010716915130615234s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.700920104980469e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 7.62939453125e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 11.138516187667847s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.58101224899292s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0003609657287597656s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.31340456008911133s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.4849853515625e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.6689300537109375e-05s
INFO | --- Analysis for dbtune-magnatune took 10.055080890655518s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 180.44742345809937s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.38556432723999023s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.021184206008911133s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011110305786132812s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.1920928955078125e-05s
INFO | --- Analysis for dbtune-musicbrainz took 434.8979563713074s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.33700037002563477s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.2881889343261719s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 4.792213439941406e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.049041748046875e-05s
INFO | --- Analysis for dbtune-myspace took 3.3631880283355713s
Availability | SPARQL endpoint availability check for data.dcs took 8.726119995117188e-05s
Availability | VoID file availability check for data.dcs took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for data.dcs took 0.3054988384246826s
Reputation | Calculation of the PageRank for data.dcs took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.151199340820312e-05s
Believability | Calculation of trust value for data.dcs took 1.2159347534179688e-05s
INFO | --- Analysis for dcs-sheffield took 2.829697370529175s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 8.916854858398438e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.3159458637237549s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.4332275390625e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.1920928955078125e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.776138067245483s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 8.821487426757812e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.3103759288787842s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.02186870574951172s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.38690185546875e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.33514404296875e-05s
INFO | --- Analysis for debian-package-tracking-system took 4.234162330627441s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.220008850097656e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.2890348434448242s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020734786987304688s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.3855438232421875e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.2159347534179688e-05s
INFO | --- Analysis for desaparecidos took 3.0439703464508057s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.1961669921875e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.28830575942993164s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.799003601074219e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.2159347534179688e-05s
INFO | --- Analysis for deustoentrepreneurship took 4.3554463386535645s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 0.00011730194091796875s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.32511234283447266s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.021284818649291992s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.0001010894775390625s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.0728836059570312e-05s
INFO | --- Analysis for deustotech took 4.949321508407593s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.4112138748168945s
Availability | VoID file availability check for Deutsche Biographie took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.28918027877807617s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02126479148864746s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0009424686431884766s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.100799560546875e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.239776611328125e-05s
INFO | --- Analysis for deutsche-biographie took 4.684900522232056s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.2438507080078125e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.31031107902526855s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.1682510375976562e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.837057590484619s
Availability | SPARQL endpoint availability check for dev8d took 0.00022983551025390625s
Availability | VoID file availability check for dev8d took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for dev8d took 0.3250157833099365s
Reputation | Calculation of the PageRank for dev8d took 0.020788908004760742s
Interlinking | Calculation of Degree of Connection for dev8d took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.723403930664062e-05s
Believability | Calculation of trust value for dev8d took 1.1205673217773438e-05s
INFO | --- Analysis for dev8d took 3.833167314529419s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.115196466445923s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007371902465820312s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.30354833602905273s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020765304565429688s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 6.031990051269531e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.0251998901367188e-05s
INFO | --- Analysis for dewey_decimal_classification took 92.81058597564697s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 9.083747863769531e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.27704787254333496s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020905733108520508s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.123283386230469e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.049041748046875e-05s
INFO | --- Analysis for DHSVM took 22.63494610786438s
Availability | SPARQL endpoint availability check for Diavgeia took 4.315376281738281e-05s
Availability | VoID file availability check for Diavgeia took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.30179715156555176s
Reputation | Calculation of the PageRank for Diavgeia took 0.0211334228515625s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.606910705566406e-05s
Believability | Calculation of trust value for Diavgeia took 8.344650268554688e-06s
INFO | --- Analysis for diavgeia took 5.860662460327148s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 8.559226989746094e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.35879039764404297s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02071523666381836s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011277198791503906s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.2874603271484375e-05s
INFO | --- Analysis for didactalia took 8.153824806213379s
Availability | SPARQL endpoint availability check for DisGeNET took 2.0319058895111084s
Availability | VoID file availability check for DisGeNET took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.28487706184387207s
Reputation | Calculation of the PageRank for DisGeNET took 0.021004915237426758s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00014972686767578125s
Believability | Calculation of trust value for DisGeNET took 1.239776611328125e-05s
INFO | --- Analysis for disgenet took 7.991231918334961s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 5.91278076171875e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0008289813995361328s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.3044607639312744s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.021538496017456055s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.147125244140625e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.2636184692382812e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 8.388930797576904s
Availability | SPARQL endpoint availability check for DM2E took 4.2438507080078125e-05s
Availability | VoID file availability check for DM2E took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for DM2E took 0.3085286617279053s
Reputation | Calculation of the PageRank for DM2E took 0.02106618881225586s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011396408081054688s
Believability | Calculation of trust value for DM2E took 1.33514404296875e-05s
INFO | --- Analysis for dm2e took 3.6033575534820557s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 8.845329284667969e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.37119531631469727s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.023029804229736328s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015687942504882812s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.1205673217773438e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 7.8635008335113525s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.410743713378906e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.31068992614746094s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.02103590965270996s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.365776062011719e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 1.0013580322265625e-05s
INFO | --- Analysis for doi took 7.950603008270264s
Availability | SPARQL endpoint availability check for Driggu Florentino took 8.440017700195312e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.31720519065856934s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.8848648071289062e-05s
Believability | Calculation of trust value for Driggu Florentino took 9.775161743164062e-06s
INFO | --- Analysis for Driggu took 3.7690868377685547s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.33526158332824707s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.28896522521972656s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.021423816680908203s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 4.267692565917969e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.239776611328125e-05s
INFO | --- Analysis for drug-data-hifm took 17.580284595489502s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.93041157722473s
Availability | VoID file availability check for MetaLex Document Server took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.35163187980651855s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020885229110717773s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 4.0531158447265625e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.2159347534179688e-05s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.3796951770782s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.3459980487823486s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0008161067962646484s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.3276534080505371s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020960092544555664s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.504753112792969e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.2874603271484375e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 15.270928144454956s
Availability | SPARQL endpoint availability check for DWS-Group took 8.845329284667969e-05s
Availability | VoID file availability check for DWS-Group took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.40371251106262207s
Reputation | Calculation of the PageRank for DWS-Group took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 9.799003601074219e-05s
Believability | Calculation of trust value for DWS-Group took 1.0251998901367188e-05s
INFO | --- Analysis for dws-group took 2.908827543258667s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.1961669921875e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.3255128860473633s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.7418136596679688e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.1444091796875e-05s
INFO | --- Analysis for E1 took 4.205998420715332s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.07305669784545898s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.2770068645477295s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020526409149169922s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00010895729064941406s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-alaska took 2.7786877155303955s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.05003666877746582s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.3003041744232178s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020957469940185547s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.1021575927734375e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-cau took 2.785477638244629s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.05947113037109375s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.29908251762390137s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.022347688674926758s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.532669067382812e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.8514280319213867s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.0409541130065918s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.31309938430786133s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.022072315216064453s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.72747802734375e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-cdrewu took 2.7785463333129883s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.04287457466125488s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.29593610763549805s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00014281272888183594s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-dartmouth took 2.9525487422943115s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.09806632995605469s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.28731369972229004s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02101922035217285s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.893013000488281e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-famu took 2.9835081100463867s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.18818354606628418s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.000457763671875s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.296466588973999s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020880460739135742s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.0001308917999267578s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-harvard took 3.1783361434936523s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.05057334899902344s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.288238525390625s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012493133544921875s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.4066696166992188e-05s
INFO | --- Analysis for eagle-i-hawaii took 2.7325384616851807s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.05200052261352539s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0011730194091796875s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2739906311035156s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.02248358726501465s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.270408630371094e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-howard took 2.751883029937744s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.05425381660461426s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.28832507133483887s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.022745132446289062s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.127357482910156e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.7853081226348877s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.04884934425354004s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.29664087295532227s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.022138595581054688s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.0001087188720703125s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-jsu took 2.8151848316192627s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.04645824432373047s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.31457042694091797s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.5762786865234375e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i-meharry took 2.764880657196045s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.04654192924499512s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2873218059539795s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.021706819534301758s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.799003601074219e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-montana took 2.785524368286133s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.06740832328796387s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.33792948722839355s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020594358444213867s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 0.00011610984802246094s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-msm took 2.902684450149536s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.04144430160522461s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.3392171859741211s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.021683692932128906s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00012421607971191406s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-ohsu took 2.903806447982788s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.055130720138549805s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2975955009460449s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.02104973793029785s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.508827209472656e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-psm took 2.8144052028656006s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.04978537559509277s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.28757166862487793s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.02105402946472168s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.413459777832031e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-tsu took 2.7141873836517334s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.045096635818481445s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.3261997699737549s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.389617919921875e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-tuskegee took 2.8518483638763428s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.04477047920227051s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.2793154716491699s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.020746231079101562s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00012063980102539062s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-uccaribe took 2.792584180831909s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04860496520996094s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.27413153648376465s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.021714448928833008s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0001251697540283203s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-upr took 2.749480724334717s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.04295229911804199s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.2984659671783447s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.02077937126159668s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.008148193359375e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-utep took 3.000044345855713s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.03320813179016113s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2764732837677002s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.176399230957031e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-utsa took 2.7542572021484375s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.16587352752685547s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.2751779556274414s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 0.00010037422180175781s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 2.991401433944702s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.06263160705566406s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.31035900115966797s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.021080732345581055s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.2479248046875e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-xula took 2.834350347518921s
Availability | SPARQL endpoint availability check for Emergency situation took 0.6302216053009033s
Availability | VoID file availability check for Emergency situation took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.2869577407836914s
Reputation | Calculation of the PageRank for Emergency situation took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 5.435943603515625e-05s
Believability | Calculation of trust value for Emergency situation took 1.1444091796875e-05s
INFO | --- Analysis for Earthquake took 4.047934532165527s
Availability | SPARQL endpoint availability check for ESO took 0.5215766429901123s
Availability | VoID file availability check for ESO took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for ESO took 0.28911900520324707s
Reputation | Calculation of the PageRank for ESO took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for ESO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for ESO took 7.843971252441406e-05s
Believability | Calculation of trust value for ESO took 1.2159347534179688e-05s
INFO | --- Analysis for Earthquake_case took 4.210388660430908s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.2659928798675537s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2913541793823242s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020849227905273438s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00011348724365234375s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for ecb-linked-data took 2.993774890899658s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 9.414783000946045s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0014040470123291016s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.3190133571624756s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.719329833984375e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 9.059906005859375e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 20.364910125732422s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.675865888595581s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.286773681640625s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.556510925292969e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 7.090789079666138s
Availability | SPARQL endpoint availability check for ECLAP took 20.809401035308838s
Availability | VoID file availability check for ECLAP took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for ECLAP took 0.28798675537109375s
Reputation | Calculation of the PageRank for ECLAP took 0.021259784698486328s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for ECLAP took 5.507469177246094e-05s
Believability | Calculation of trust value for ECLAP took 1.2636184692382812e-05s
INFO | --- Analysis for eclap took 53.476932764053345s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 5.0067901611328125e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.26420044898986816s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.1205673217773438e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.0251998901367188e-05s
INFO | --- Analysis for ECNU-GISer took 4.2370285987854s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 9.703636169433594e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.29359936714172363s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.022919416427612305s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.7697296142578125e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.2636184692382812e-05s
INFO | --- Analysis for ecs took 2.873875617980957s
Availability | SPARQL endpoint availability check for Edublogs took 8.869171142578125e-05s
Availability | VoID file availability check for Edublogs took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Edublogs took 0.2731029987335205s
Reputation | Calculation of the PageRank for Edublogs took 0.02103137969970703s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.703636169433594e-05s
Believability | Calculation of trust value for Edublogs took 1.0728836059570312e-05s
INFO | --- Analysis for edublogs took 3.5797901153564453s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.565955638885498s
Availability | VoID file availability check for education.data.gov.uk took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.2999613285064697s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.606910705566406e-05s
Believability | Calculation of trust value for education.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for education-data-gov-uk took 4.8884522914886475s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 393.353551864624s
Availability | VoID file availability check for Educational programs - SISVU took 0.0009257793426513672s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.38011646270751953s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.021193981170654297s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 6.175041198730469e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 5.9604644775390625e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1321.6665003299713s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.8868978023529053s
Availability | VoID file availability check for European Environment Agency Published Products took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.34973883628845215s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.838539123535156e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 8.821487426757812e-06s
INFO | --- Analysis for eea took 6.401393890380859s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.49672651290893555s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.3117482662200928s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020956993103027344s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.125999450683594e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 1.0728836059570312e-05s
INFO | --- Analysis for eea-rod took 5.548739433288574s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.16631317138671875s
Availability | VoID file availability check for EEA Vocabularies took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.3115224838256836s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.021027803421020508s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.0108642578125e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.239776611328125e-05s
INFO | --- Analysis for eea-vocabularies took 5.319504976272583s
Availability | SPARQL endpoint availability check for E-Government Ontology took 1.4766545295715332s
Availability | VoID file availability check for E-Government Ontology took 0.0012502670288085938s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.31682491302490234s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.021043062210083008s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.430511474609375e-05s
INFO | --- Analysis for EGovOntology took 5.380638122558594s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5684013366699219s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005655288696289062s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.8670856952667236s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3262276649475098s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6441891193389893s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.943103313446045s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.35565209388733s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 3.764474630355835s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6109449863433838s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7484254837036133s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2541384696960449s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5226461887359619s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.448790788650513s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25584864616394043s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4305686950683594s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6180782318115234s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29555320739746094s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.38501644134521484s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.28011417388916016s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.315956592559814s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 6.723403930664062e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.41513514518737793s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29724931716918945s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4872732162475586s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23927593231201172s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.36099743843078613s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0076758861541748s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25028395652770996s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.853535413742065s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27933788299560547s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3227500915527344s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3491170406341553s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0127403736114502s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.029531002044677734s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02819657325744629s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25072264671325684s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.013263463973999s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4508051872253418s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.2760002613067627s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2745966911315918s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.159422397613525s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03356170654296875s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.403486967086792s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5020027160644531s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3269.3795535564423s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 1.5250334739685059s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02132415771484375s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 6.794929504394531e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.9604644775390625e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1920928955078125e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 1.239776611328125e-05s
INFO | --- Analysis for ei2a took 3510.410404920578s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.5299530029296875e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.298234224319458s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00012040138244628906s
Believability | Calculation of trust value for EIONET RDF Data took 9.5367431640625e-06s
INFO | --- Analysis for eionet-rdf took 3.311356782913208s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 9.822845458984375e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.31531596183776855s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.021954059600830078s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.0517578125e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.0967254638671875e-05s
INFO | --- Analysis for ElgooG_ took 2.6839449405670166s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 6.274561882019043s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.3286778926849365s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.462501525878906e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.0967254638671875e-05s
INFO | --- Analysis for elviajero took 19.486492156982422s
Availability | SPARQL endpoint availability check for EMN took 4.100799560546875e-05s
Availability | VoID file availability check for EMN took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for EMN took 0.3016397953033447s
Reputation | Calculation of the PageRank for EMN took 0.021810293197631836s
Interlinking | Calculation of Degree of Connection for EMN took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for EMN took 3.9577484130859375e-05s
Believability | Calculation of trust value for EMN took 1.2159347534179688e-05s
INFO | --- Analysis for emn took 3.2801291942596436s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 8.797645568847656e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.3119015693664551s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 4.982948303222656e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-co2emission took 2.840022563934326s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 8.678436279296875e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.27852869033813477s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.814697265625e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 8.106231689453125e-06s
INFO | --- Analysis for enakting-crime took 2.7912662029266357s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 5.245208740234375e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.2958245277404785s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.022014141082763672s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.719329833984375e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-energy took 2.857163667678833s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 8.916854858398438e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.2748415470123291s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 8.678436279296875e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 7.867813110351562e-06s
INFO | --- Analysis for enakting-mortality took 2.654691219329834s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 8.940696716308594e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.28435373306274414s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.021689176559448242s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.910064697265625e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 8.58306884765625e-06s
INFO | --- Analysis for enakting-nhs took 2.6778385639190674s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 8.487701416015625e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.29224729537963867s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.02167654037475586s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.316734313964844e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 8.106231689453125e-06s
INFO | --- Analysis for enakting-population took 2.699883460998535s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.5054430961608887s
Availability | VoID file availability check for English Heritage Periods List took 0.0007374286651611328s
Extra | Recovery of all triples for English Heritage Periods List took 0.296494722366333s
Performance | Total latancy measurement for English Heritage Periods List took 1.4859611988067627s
Amount of data | Number of triples check for English Heritage Periods List took 0.4647860527038574s
Versatility | Languages check for English Heritage Periods List took 0.25928282737731934s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.502267599105835s
Security | Check HTTPS for English Heritage Periods List took 0.19997286796569824s
Interpretability | RDF structures check for English Heritage Periods List took 0.2943234443664551s
Versatility | Serialization formats check for English Heritage Periods List took 0.43215394020080566s
Availability | RDF dump link check for English Heritage Periods List took 0.2884979248046875s
License | MR license check for English Heritage Periods List took 0.35941219329833984s
License | HR license check for English Heritage Periods List took 0.3314046859741211s
Amount of data | Number of property check for English Heritage Periods List took 0.3557565212249756s
Understandability | Number of label check for English Heritage Periods List took 0.4445650577545166s
Understandability | URI regex check for English Heritage Periods List took 0.579646110534668s
Understandability | Vocabs check for English Heritage Periods List took 0.31003570556640625s
Verifiability | Authors check for English Heritage Periods List took 0.3412506580352783s
Verifiability | Publishers check for English Heritage Periods List took 0.3229539394378662s
Performance | Throughput check for English Heritage Periods List took 12.237416505813599s
Amount of data | Check the number of entities for English Heritage Periods List took 6.914138793945312e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.3354020118713379s
Interlinking | sameAs chians check for English Heritage Periods List took 0.3422079086303711s
Interlinking | skos check for English Heritage Periods List took 0.30806922912597656s
Interlinking | skos check for English Heritage Periods List took 0.30643343925476074s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.36446428298950195s
Currency | Creation date check for English Heritage Periods List took 0.6000916957855225s
Currency | Modification date check for English Heritage Periods List took 0.6434259414672852s
Rep.Conc. | URIs length for English Heritage Periods List took 0.6163620948791504s
Interoperability | New vocabularies check for English Heritage Periods List took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.3243753910064697s
Accuracy | Check Functional Property for English Heritage Periods List took 0.3818330764770508s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.29218053817749023s
Consistency | Disjoint class check for English Heritage Periods List took 0.31449198722839355s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3165593147277832s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.605011224746704s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0005974769592285156s
Security | Sign check for English Heritage Periods List took 0.3262138366699219s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.30340123176574707s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.0531158447265625e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Heritage Periods List took 1.0728836059570312e-05s
INFO | --- Analysis for english-heritage-periods-list took 52.95532464981079s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.49684882164001465s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0006015300750732422s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.329813003540039s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.0291917324066162s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.23621678352355957s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.5810625553131104s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.6079440116882324s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.191025733947754s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.18100428581237793s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.31881117820739746s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.20149683952331543s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 55.17360806465149s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.4252955913543701s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.240818738937378s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.14561724662780762s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.25811100006103516s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.4209284782409668s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.15097451210021973s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.14413189888000488s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.25081777572631836s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.194346189498901s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 7.343292236328125e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.13479328155517578s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.3063180446624756s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.2561299800872803s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.2112743854522705s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.18602967262268066s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 1.0428261756896973s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.3239915370941162s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 1.6411137580871582s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.13786768913269043s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.19476962089538574s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.1269228458404541s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.33917784690856934s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.7199277877807617s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 1.5429167747497559s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.6019964218139648s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.0001842975616455078s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.44957733154296875s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.19717144966125488s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.41568636894226074s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.430511474609375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 9.298324584960938e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 279.4953908920288s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.16248440742492676s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0006492137908935547s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.1129789352416992s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.891934871673584s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.1574878692626953s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.473071813583374s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 1.0283761024475098s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.26415991783142s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.18505644798278809s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.14489412307739258s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.20570778846740723s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 48.843644857406616s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.14691543579101562s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.179558515548706s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.20142221450805664s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.135498046875s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.409442663192749s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.659818172454834s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.19367098808288574s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.21158790588378906s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.543015480041504s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 0.00011110305786132812s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.19859623908996582s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.14232277870178223s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.5861403942108154s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.24843096733093262s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.1584939956665039s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.41550445556640625s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.20702004432678223s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.7243168354034424s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.2023029327392578s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.14463305473327637s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.2051832675933838s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.12893176078796387s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.44793176651000977s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.3726661205291748s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.5461277961730957s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.0001506805419921875s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.30887293815612793s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.1340491771697998s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.29078149795532227s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.075599670410156e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 9.5367431640625e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 268.07570004463196s
Availability | SPARQL endpoint availability check for English WordNet took 4.458427429199219e-05s
Availability | VoID file availability check for English WordNet took 0.0003452301025390625s
Completeness | Calculation of interlinking completeness for English WordNet took 0.3041665554046631s
Reputation | Calculation of the PageRank for English WordNet took 0.020862340927124023s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.24249267578125e-05s
Believability | Calculation of trust value for English WordNet took 7.3909759521484375e-06s
INFO | --- Analysis for english-wordnet took 3.323228120803833s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.08876180648803711s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.2785484790802002s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.845329284667969e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.1682510375976562e-05s
INFO | --- Analysis for enipedia took 2.7791213989257812s
Availability | SPARQL endpoint availability check for Enslaved.org took 8.678436279296875e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2782282829284668s
Reputation | Calculation of the PageRank for Enslaved.org took 0.021194934844970703s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 2.9802322387695312e-05s
Believability | Calculation of trust value for Enslaved.org took 1.1444091796875e-05s
INFO | --- Analysis for enslaved.org took 5.16976523399353s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.35259103775024414s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.26534461975097656s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 4.8160552978515625e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.0967254638671875e-05s
INFO | --- Analysis for entice-graph took 3.2660186290740967s
Availability | SPARQL endpoint availability check for Entrez Gene took 8.535385131835938e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008444786071777344s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.28135132789611816s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02399301528930664s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 4.1484832763671875e-05s
Believability | Calculation of trust value for Entrez Gene took 1.1920928955078125e-05s
INFO | --- Analysis for entrez_gene took 27.472514629364014s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0741209983825684s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.2760884761810303s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.02294445037841797s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.0067901611328125e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 1.0013580322265625e-05s
INFO | --- Analysis for environment-agency-bathing-water-quality took 12.042049407958984s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.2873408794403076s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.31804585456848145s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.02086329460144043s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.4345855712890625e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 9.775161743164062e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.878652095794678s
Availability | SPARQL endpoint availability check for EARTh took 272.41324973106384s
Availability | VoID file availability check for EARTh took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for EARTh took 0.2916853427886963s
Reputation | Calculation of the PageRank for EARTh took 0.02121734619140625s
Interlinking | Calculation of Degree of Connection for EARTh took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010466575622558594s
Believability | Calculation of trust value for EARTh took 1.3589859008789062e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 563.9546213150024s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.5924806594848633s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0004730224609375s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 111.96958208084106s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.951214075088501s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.309890747070312s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.162923336029053s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.2447454929352s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.231536626815796s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.36095714569091797s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 6.334056377410889s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.4392683506011963s
License | MR license check for Micka (EO metadata) @PSNC took 1.033409833908081s
License | HR license check for Micka (EO metadata) @PSNC took 109.22231245040894s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.21037840843200684s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 3.243586778640747s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 1.2638812065124512s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.6350691318511963s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.21702313423156738s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.24946928024291992s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.47736406326294s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 6.842613220214844e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.205765962600708s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.21158361434936523s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.5230007171630859s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.429978609085083s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 12.955045461654663s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.508739709854126s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.26938390731811523s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 105.6370780467987s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.20729541778564453s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.5094058513641357s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.5012695789337158s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 89.94885063171387s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.6292059421539307s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.607912540435791s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.18257832527160645s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 86.07217001914978s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.406267404556274s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 37.50028657913208s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.3629183769226074s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 88.14295887947083s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.693140983581543s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.503727912902832s
Security | Sign check for Micka (EO metadata) @PSNC took 1.5967185497283936s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 9.814734697341919s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.5480287075042725s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021595478057861328s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for EO_metadata took 2096.3141791820526s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 9.584426879882812e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.2801527976989746s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.02190113067626953s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 2.8133392333984375e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 1.2636184692382812e-05s
INFO | --- Analysis for EOKP-Datasets took 3.501917839050293s
Availability | SPARQL endpoint availability check for EPA-CDR took 8.702278137207031e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.3287227153778076s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02179265022277832s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.600120544433594e-05s
Believability | Calculation of trust value for EPA-CDR took 9.059906005859375e-06s
INFO | --- Analysis for epa-cdr took 7.225245952606201s
Availability | SPARQL endpoint availability check for EPA-FRS took 8.678436279296875e-05s
Availability | VoID file availability check for EPA-FRS took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.3041210174560547s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 6.771087646484375e-05s
Believability | Calculation of trust value for EPA-FRS took 9.5367431640625e-06s
INFO | --- Analysis for epa-frs took 6.26172947883606s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.172325134277344e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.31949782371520996s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.075599670410156e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.4836273193359375e-06s
INFO | --- Analysis for epa-rcra took 6.438215255737305s
Availability | SPARQL endpoint availability check for EPA-SRS took 9.107589721679688e-05s
Availability | VoID file availability check for EPA-SRS took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.2718949317932129s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020440340042114258s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 9.083747863769531e-05s
Believability | Calculation of trust value for EPA-SRS took 8.821487426757812e-06s
INFO | --- Analysis for epa-srs took 6.3389410972595215s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.1961669921875e-05s
Availability | VoID file availability check for EPA-TRI took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.314098596572876s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020236730575561523s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.0279159545898438e-05s
Believability | Calculation of trust value for EPA-TRI took 9.059906005859375e-06s
INFO | --- Analysis for epa-tri took 6.311565160751343s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.04323148727416992s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.2801635265350342s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00012540817260742188s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.765695810317993s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.47612762451171875s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.35147929191589355s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.022680282592773438s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 9.775161743164062e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.2159347534179688e-05s
INFO | --- Analysis for eprtr took 4.03816032409668s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.49164414405822754s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0006136894226074219s
Extra | Recovery of all triples for Railway Infrastructure KG took 58.16766858100891s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.1590697765350342s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.2413625717163086s
Interoperability | New terms check for Railway Infrastructure KG took 1.6832294464111328s
Versatility | Languages check for Railway Infrastructure KG took 84.96371269226074s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.2234790325164795s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.3769538402557373s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.2594766616821289s
Availability | RDF dump link check for Railway Infrastructure KG took 0.2782857418060303s
License | MR license check for Railway Infrastructure KG took 0.3283500671386719s
License | HR license check for Railway Infrastructure KG took 61.07058334350586s
Amount of data | Number of property check for Railway Infrastructure KG took 0.23031401634216309s
Understandability | Number of label check for Railway Infrastructure KG took 0.4524421691894531s
Understandability | URI regex check for Railway Infrastructure KG took 0.4401581287384033s
Understandability | Vocabs check for Railway Infrastructure KG took 0.23474359512329102s
Verifiability | Authors check for Railway Infrastructure KG took 0.24496245384216309s
Verifiability | Publishers check for Railway Infrastructure KG took 0.20095586776733398s
Performance | Throughput check for Railway Infrastructure KG took 11.31396770477295s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.29436492919921875s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.21910429000854492s
Interlinking | skos check for Railway Infrastructure KG took 0.2715754508972168s
Interlinking | skos check for Railway Infrastructure KG took 0.260162353515625s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.23802471160888672s
Currency | Creation date check for Railway Infrastructure KG took 0.46875953674316406s
Currency | Modification date check for Railway Infrastructure KG took 0.2146317958831787s
Rep.Conc. | URIs length for Railway Infrastructure KG took 23.11865735054016s
Interoperability | New vocabularies check for Railway Infrastructure KG took 5.675764322280884s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.251387357711792s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.26699304580688477s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.2362048625946045s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 13.62959098815918s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 2.526674747467041s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.5358028411865234s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.24001145362854004s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 1.6905629634857178s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.105103492736816s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 18.32524061203003s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.578869342803955s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 2.8426246643066406s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 2.8769912719726562s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.3399620056152344s
Security | Sign check for Railway Infrastructure KG took 0.3223121166229248s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2423.854924440384s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 5.706713438034058s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.0224149227142334s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 7.033348083496094e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0008113384246826172s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 6.747760057449341s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.2874603271484375e-05s
INFO | --- Analysis for ERAKG took 2848.5608398914337s
Availability | SPARQL endpoint availability check for reg took 8.749961853027344e-05s
Availability | VoID file availability check for reg took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for reg took 0.31183838844299316s
Reputation | Calculation of the PageRank for reg took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for reg took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for reg took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for reg took 1.0967254638671875e-05s
Believability | Calculation of trust value for reg took 1.1444091796875e-05s
INFO | --- Analysis for erg took 2.6724135875701904s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.25330328941345215s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0009253025054931641s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.29085302352905273s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.02310919761657715s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0010600090026855469s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.8623809814453125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 9.298324584960938e-06s
INFO | --- Analysis for es-msssi-drug-prices took 3.171912908554077s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 8.559226989746094e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.32923078536987305s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02079486846923828s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.678436279296875e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 6.198883056640625e-06s
INFO | --- Analysis for esd-standards took 4.646032333374023s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 8.559226989746094e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.31507158279418945s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.022919178009033203s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0008459091186523438s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 8.392333984375e-05s
Believability | Calculation of trust value for ESD-Toolkit took 5.245208740234375e-06s
INFO | --- Analysis for esd-toolkit took 3.539212465286255s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.3392181396484375e-05s
Availability | VoID file availability check for Dataset Esis took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.2966439723968506s
Reputation | Calculation of the PageRank for Dataset Esis took 0.022309064865112305s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.0279159545898438e-05s
Believability | Calculation of trust value for Dataset Esis took 1.239776611328125e-05s
INFO | --- Analysis for esislearning took 3.119985580444336s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 9.322166442871094e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.32428741455078125s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 2.9087066650390625e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 1.2636184692382812e-05s
INFO | --- Analysis for ESV took 4.588726043701172s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.6754281520843506s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.2915802001953125s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.580535173416138s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 7.963374614715576s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0007803440093994141s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.3035752773284912s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.021266698837280273s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0010144710540771484s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 9.179115295410156e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.3589859008789062e-05s
INFO | --- Analysis for eu-agencies-bodies took 22.090360403060913s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 8.702278137207031e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.3083045482635498s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.021202802658081055s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0009438991546630859s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 9.965896606445312e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 9.775161743164062e-06s
INFO | --- Analysis for eu-institutions took 9.201650142669678s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.3801374435424805s
Availability | VoID file availability check for EU Parliament Media Library took 0.0003895759582519531s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.32146525382995605s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02102494239807129s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.719329833984375e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 5.7220458984375e-06s
INFO | --- Analysis for eu-parliament-media took 10.096611738204956s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.234358310699463s
Availability | VoID file availability check for EU Who Is Who took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2765340805053711s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.021062135696411133s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0009710788726806641s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 4.3392181396484375e-05s
Believability | Calculation of trust value for EU Who Is Who took 9.059906005859375e-06s
INFO | --- Analysis for eu-who-is-who took 14.090871810913086s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.246675729751587s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.28861474990844727s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.021430253982543945s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0010657310485839844s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.8160552978515625e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for eumida-linked-data took 12.798503160476685s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.3532850742340088s
Availability | VoID file availability check for European Nature Information System took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.3214247226715088s
Reputation | Calculation of the PageRank for European Nature Information System took 0.02211785316467285s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0010662078857421875s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.000133514404296875s
Believability | Calculation of trust value for European Nature Information System took 1.239776611328125e-05s
INFO | --- Analysis for eunis took 4.7189764976501465s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 7.55800461769104s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.31130266189575195s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.033348083496094e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for eur-lex-rdf took 20.417441606521606s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.5560073852539062s
Availability | VoID file availability check for Standard Eurobarometer took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.3074820041656494s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.482269287109375e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 8.821487426757812e-06s
INFO | --- Analysis for eurobarometer-standard took 13.253164529800415s
Availability | SPARQL endpoint availability check for European Election Results took 1.595663070678711s
Availability | VoID file availability check for European Election Results took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for European Election Results took 0.29412364959716797s
Reputation | Calculation of the PageRank for European Election Results took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.2901763916015625e-05s
Believability | Calculation of trust value for European Election Results took 9.059906005859375e-06s
INFO | --- Analysis for european-election-results took 12.263601779937744s
Availability | SPARQL endpoint availability check for EPO patents took 0.6463541984558105s
Availability | VoID file availability check for EPO patents took 0.0005373954772949219s
Extra | Recovery of all triples for EPO patents took 25.90441346168518s
Performance | Total latancy measurement for EPO patents took 1.019068956375122s
Amount of data | Number of triples check for EPO patents took 90.28426480293274s
Versatility | Languages check for EPO patents took 100.32646751403809s
Interpretability | Number of blank nodes check for EPO patents took 90.30630350112915s
Interpretability | RDF structures check for EPO patents took 0.2927536964416504s
Versatility | Serialization formats check for EPO patents took 0.27507734298706055s
Availability | RDF dump link check for EPO patents took 0.22303175926208496s
License | MR license check for EPO patents took 0.21822190284729004s
License | HR license check for EPO patents took 90.17464590072632s
Amount of data | Number of property check for EPO patents took 0.25676417350769043s
Understandability | Number of label check for EPO patents took 90.21585488319397s
Understandability | URI regex check for EPO patents took 0.4492204189300537s
Understandability | Vocabs check for EPO patents took 0.23523521423339844s
Verifiability | Authors check for EPO patents took 0.31845808029174805s
Verifiability | Publishers check for EPO patents took 0.24556374549865723s
Performance | Throughput check for EPO patents took 11.155231475830078s
Amount of data | Check the number of entities for EPO patents took 7.152557373046875e-05s
Verifiability | Contribs. check for EPO patents took 0.20844292640686035s
Interlinking | sameAs chians check for EPO patents took 0.17795920372009277s
Interlinking | skos check for EPO patents took 0.16805696487426758s
Interlinking | skos check for EPO patents took 0.1710669994354248s
Timeliness | dataset update frequency check for EPO patents took 0.47582340240478516s
Currency | Creation date check for EPO patents took 0.5197999477386475s
Currency | Modification date check for EPO patents took 0.4213900566101074s
Rep.Conc. | URIs length for EPO patents took 134.12532138824463s
Interoperability | New vocabularies check for EPO patents took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.2502567768096924s
Accuracy | Check Empty annotation labels for EPO patents took 18.543621063232422s
Accuracy | Check White space in annotation for EPO patents took 2.934030055999756s
Accuracy | Check Datatype consistency for EPO patents took 4.880322694778442s
Consistency | Disjoint class check for EPO patents took 0.23579144477844238s
Consistency | Check Misplaced properties for EPO patents took 100.4381742477417s
Consistency | Check Ontology hijacking for EPO patents took 23.762465715408325s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.548297643661499s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.59973239898682s
Conciseness | Check Extensional conciseness for EPO patents took 2.7581632137298584s
Conciseness | Check Intensional conciseness for EPO patents took 0.32499217987060547s
Security | Sign check for EPO patents took 0.24180912971496582s
Availability | Check URIs Dereferenciability for EPO patents took 2.0833988189697266s
Completeness | Calculation of interlinking completeness for EPO patents took 0.46145009994506836s
Reputation | Calculation of the PageRank for EPO patents took 0.021239280700683594s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.9073486328125e-06s
Believability | Calculation of trust value for EPO patents took 1.1920928955078125e-05s
INFO | --- Analysis for European_Patent_Information took 1194.9858841896057s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.363059997558594e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.35948610305786133s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.417533874511719e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 1.2636184692382812e-05s
INFO | --- Analysis for europeana-lod-v1 took 8.061687231063843s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.4176516532897949s
Availability | VoID file availability check for Europeana SPARQL took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.2768425941467285s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.021794557571411133s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.76837158203125e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.1682510375976562e-05s
INFO | --- Analysis for europeana-sparql took 6.5690484046936035s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.10685062408447266s
Availability | VoID file availability check for EuroSentiment took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.348895788192749s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.790855407714844e-05s
Believability | Calculation of trust value for EuroSentiment took 1.0967254638671875e-05s
INFO | --- Analysis for eurosentiment took 3.58042049407959s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 8.797645568847656e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.3215465545654297s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0008056163787841797s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.700920104980469e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 8.344650268554688e-06s
INFO | --- Analysis for eurostat-rdf took 12.244694232940674s
Availability | SPARQL endpoint availability check for EuroVoc took 0.16702961921691895s
Availability | VoID file availability check for EuroVoc took 0.0007002353668212891s
Extra | Recovery of all triples for EuroVoc took 201.51122379302979s
Performance | Total latancy measurement for EuroVoc took 0.616905689239502s
Amount of data | Number of triples check for EuroVoc took 44.56482648849487s
Interoperability | New terms check for EuroVoc took 57.61207342147827s
Versatility | Languages check for EuroVoc took 300.06927514076233s
Interpretability | Number of blank nodes check for EuroVoc took 59.03471755981445s
Security | Check HTTPS for EuroVoc took 0.38825392723083496s
Interpretability | RDF structures check for EuroVoc took 0.44965481758117676s
Versatility | Serialization formats check for EuroVoc took 3.7415833473205566s
Availability | RDF dump link check for EuroVoc took 0.36125898361206055s
License | MR license check for EuroVoc took 0.3941378593444824s
License | HR license check for EuroVoc took 300.0770995616913s
Amount of data | Number of property check for EuroVoc took 0.1661663055419922s
Understandability | Number of label check for EuroVoc took 2.2012648582458496s
Understandability | URI regex check for EuroVoc took 0.4111647605895996s
Understandability | Vocabs check for EuroVoc took 0.1090397834777832s
Verifiability | Authors check for EuroVoc took 0.22085332870483398s
Verifiability | Publishers check for EuroVoc took 0.25032806396484375s
Performance | Throughput check for EuroVoc took 10.63101577758789s
Amount of data | Check the number of entities for EuroVoc took 6.890296936035156e-05s
Verifiability | Contribs. check for EuroVoc took 0.14168620109558105s
Interlinking | sameAs chians check for EuroVoc took 7.168154239654541s
Interlinking | skos check for EuroVoc took 0.35618138313293457s
Interlinking | skos check for EuroVoc took 0.14971661567687988s
Timeliness | dataset update frequency check for EuroVoc took 0.3854091167449951s
Currency | Creation date check for EuroVoc took 0.5705740451812744s
Currency | Modification date check for EuroVoc took 0.25327110290527344s
Rep.Conc. | URIs length for EuroVoc took 422.37404131889343s
Interoperability | New vocabularies check for EuroVoc took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.1651594638824463s
Accuracy | Check Functional Property for EuroVoc took 0.1959242820739746s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.1455683708190918s
Accuracy | Check Empty annotation labels for EuroVoc took 37.15701341629028s
Accuracy | Check White space in annotation for EuroVoc took 3.0843539237976074s
Accuracy | Check Datatype consistency for EuroVoc took 2.544396162033081s
Consistency | Disjoint class check for EuroVoc took 0.1826784610748291s
Consistency | Check Misplaced properties for EuroVoc took 300.42319202423096s
Consistency | Misplaced classes for EuroVoc took 8.437183856964111s
Consistency | Check Ontology hijacking for EuroVoc took 70.72096610069275s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.6433024406433105s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.4575798511505s
Conciseness | Check Extensional conciseness for EuroVoc took 2.958268404006958s
Conciseness | Check Intensional conciseness for EuroVoc took 0.4236929416656494s
Security | Sign check for EuroVoc took 0.4330737590789795s
Availability | Check URIs Dereferenciability for EuroVoc took 14.38668179512024s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.6871337890625s
Reputation | Calculation of the PageRank for EuroVoc took 0.020993947982788086s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 0.0001323223114013672s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.9073486328125e-06s
Believability | Calculation of trust value for EuroVoc took 1.2159347534179688e-05s
INFO | --- Analysis for eurovoc took 14853.061036109924s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 8.678436279296875e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2816162109375s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02129507064819336s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 5.6743621826171875e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 9.775161743164062e-06s
INFO | --- Analysis for euskadi-farmacias took 7.32295298576355s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.6724433898925781s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.2767307758331299s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020912885665893555s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.0040740966796875e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 7.3909759521484375e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.481647729873657s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.5911829471588135s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0007605552673339844s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2971980571746826s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.128715515136719e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.3113021850585938e-05s
INFO | --- Analysis for eutc-productions took 8.491109371185303s
Availability | SPARQL endpoint availability check for EventMedia took 0.395979642868042s
Availability | VoID file availability check for EventMedia took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for EventMedia took 0.32886338233947754s
Reputation | Calculation of the PageRank for EventMedia took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010538101196289062s
Believability | Calculation of trust value for EventMedia took 1.1682510375976562e-05s
INFO | --- Analysis for event-media took 19.967905044555664s
Availability | SPARQL endpoint availability check for EventKG took 5.9604644775390625e-05s
Availability | VoID file availability check for EventKG took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for EventKG took 0.27770161628723145s
Reputation | Calculation of the PageRank for EventKG took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.20159912109375e-05s
Believability | Calculation of trust value for EventKG took 9.5367431640625e-06s
INFO | --- Analysis for eventkg took 4.858940839767456s
Availability | SPARQL endpoint availability check for Eventseer took 5.569427967071533s
Availability | VoID file availability check for Eventseer took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Eventseer took 0.3122529983520508s
Reputation | Calculation of the PageRank for Eventseer took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.6253204345703125e-05s
Believability | Calculation of trust value for Eventseer took 1.2636184692382812e-05s
INFO | --- Analysis for eventseer took 8.294431686401367s
Availability | SPARQL endpoint availability check for Face Link took 9.012222290039062e-05s
Availability | VoID file availability check for Face Link took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Face Link took 0.29867124557495117s
Reputation | Calculation of the PageRank for Face Link took 0.021938085556030273s
Interlinking | Calculation of Degree of Connection for Face Link took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.5762786865234375e-05s
Believability | Calculation of trust value for Face Link took 1.049041748046875e-05s
INFO | --- Analysis for Face_Link took 2.698254108428955s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4189746379852295s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0005381107330322266s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 119.39665794372559s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9584484100341797s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.45288372039795s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.194301843643188s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.17686581611633s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.5302445888519287s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3388943672180176s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.909695386886597s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.178450345993042s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.49919676780700684s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.149671792984s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21488571166992188s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3711974620819092s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9687047004699707s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.48638105392456055s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19907045364379883s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2517671585083008s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.478012323379517s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.361701965332031e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18852782249450684s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19469332695007324s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5352466106414795s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.40045690536499023s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.54042387008667s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.49295973777770996s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22637486457824707s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 152.07587122917175s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2252507209777832s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19782447814941406s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5688121318817139s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 40.117363929748535s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.654693603515625s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.553027629852295s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21565032005310059s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 86.15507411956787s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.156270503997803s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 36.3787739276886s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3141803741455078s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 87.10038089752197s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6855220794677734s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5819010734558105s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2459547519683838s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.489610433578491s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5128614902496338s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.02094101905822754s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for FADN_(2019) took 2272.894200563431s
Availability | SPARQL endpoint availability check for FAMEData took 4.2438507080078125e-05s
Availability | VoID file availability check for FAMEData took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for FAMEData took 0.28654909133911133s
Reputation | Calculation of the PageRank for FAMEData took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for FAMEData took 2.9087066650390625e-05s
Believability | Calculation of trust value for FAMEData took 1.049041748046875e-05s
INFO | --- Analysis for famedata took 7.247023582458496s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.100799560546875e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0007596015930175781s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.3870058059692383s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02093052864074707s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00010466575622558594s
Believability | Calculation of trust value for FAO geopolitical ontology took 9.059906005859375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 561.6937546730042s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.10828232765197754s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.28515028953552246s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.022623538970947266s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.870529174804688e-05s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for fao-linked-data took 2.798780918121338s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 8.7738037109375e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.29560089111328125s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.02106618881225586s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.123283386230469e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for FAO_species took 2.6822195053100586s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.591808080673218s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.30162525177001953s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.6253204345703125e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.0013580322265625e-05s
INFO | --- Analysis for farmbio-chembl took 65.20621085166931s
Availability | SPARQL endpoint availability check for I4.0-Onto took 8.535385131835938e-05s
Availability | VoID file availability check for I4.0-Onto took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.2873404026031494s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020693540573120117s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 2.9802322387695312e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.049041748046875e-05s
INFO | --- Analysis for fatimazahra took 2.612438201904297s
Availability | SPARQL endpoint availability check for FHIR STU3 took 8.797645568847656e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.28727102279663086s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.021303415298461914s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.0994415283203125e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.0251998901367188e-05s
INFO | --- Analysis for FHIR_STU3 took 3.085761070251465s
Availability | SPARQL endpoint availability check for FiESTA took 4.2438507080078125e-05s
Availability | VoID file availability check for FiESTA took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for FiESTA took 0.3127284049987793s
Reputation | Calculation of the PageRank for FiESTA took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.9577484130859375e-05s
Believability | Calculation of trust value for FiESTA took 9.5367431640625e-06s
INFO | --- Analysis for fiesta took 12.938597679138184s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 8.916854858398438e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.2933778762817383s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.021083593368530273s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.123283386230469e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.6266088485717773s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.2438507080078125e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2722659111022949s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 6.794929504394531e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 9.059906005859375e-06s
INFO | --- Analysis for finnish-municipalities took 3.8780739307403564s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.21798276901245117s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0004520416259765625s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 116.66149067878723s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.956068754196167s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 9.080286502838135s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.052019596099854s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.2377667427063s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.1114296913146973s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.21046996116638184s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 8.762667179107666s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.18140339851379395s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.21512937545776367s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.244615316391s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.21680927276611328s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 1.3237967491149902s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.40114688873291016s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.20939397811889648s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.2205498218536377s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.25661396980285645s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.384371280670166s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 7.2479248046875e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.20670557022094727s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.20835113525390625s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.49042773246765137s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4285576343536377s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 3.5740668773651123s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.504753589630127s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.22485566139221191s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 152.7077341079712s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.1995382308959961s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.21152472496032715s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.18543028831481934s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 36.727996826171875s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.658334493637085s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.5910167694091797s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.19942116737365723s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 86.06467795372009s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.20152235031128s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 32.86414194107056s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.3667852878570557s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 87.25243616104126s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.696040153503418s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.6741812229156494s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.19148468971252441s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 19.790772199630737s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.6985113620758057s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.02163529396057129s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 2.86102294921875e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.933906555175781e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 9.059906005859375e-06s
INFO | --- Analysis for Fishery_Stock_Dataset took 2270.3784170150757s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.6253204345703125e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.3087751865386963s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.021367788314819336s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.296966552734375e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.2636184692382812e-05s
INFO | --- Analysis for fishes-of-texas took 3.2153143882751465s
Availability | SPARQL endpoint availability check for flickr? wrappr took 8.702278137207031e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.2843019962310791s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.02098870277404785s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.274482727050781e-05s
Believability | Calculation of trust value for flickr? wrappr took 1.239776611328125e-05s
INFO | --- Analysis for flickr-wrappr took 3.516488552093506s
Availability | SPARQL endpoint availability check for Future land use simulation model took 8.821487426757812e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.31006836891174316s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.021003246307373047s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.838539123535156e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.0967254638671875e-05s
INFO | --- Analysis for FLUS took 127.70454955101013s
Availability | SPARQL endpoint availability check for Flybase took 1.2071006298065186s
Availability | VoID file availability check for Flybase took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Flybase took 0.2776951789855957s
Reputation | Calculation of the PageRank for Flybase took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for Flybase took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.600120544433594e-05s
Believability | Calculation of trust value for Flybase took 1.0251998901367188e-05s
INFO | --- Analysis for flybase took 5.79302453994751s
Availability | SPARQL endpoint availability check for Flyted took 0.8907101154327393s
Availability | VoID file availability check for Flyted took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Flyted took 0.2749757766723633s
Reputation | Calculation of the PageRank for Flyted took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for Flyted took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Flyted took 2.9802322387695312e-05s
Believability | Calculation of trust value for Flyted took 1.2159347534179688e-05s
INFO | --- Analysis for flyted took 5.622282981872559s
Availability | SPARQL endpoint availability check for Foodista took 1.5950415134429932s
Availability | VoID file availability check for Foodista took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for Foodista took 0.33447861671447754s
Reputation | Calculation of the PageRank for Foodista took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Foodista took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Foodista took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.9325485229492188e-05s
Believability | Calculation of trust value for Foodista took 1.2159347534179688e-05s
INFO | --- Analysis for foodista took 10.950412034988403s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.06245589256286621s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.3124532699584961s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02202320098876953s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0010616779327392578s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 8.7738037109375e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1682510375976562e-05s
INFO | --- Analysis for foodpedia took 2.716750144958496s
Availability | SPARQL endpoint availability check for FrameBase schema took 8.726119995117188e-05s
Availability | VoID file availability check for FrameBase schema took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.3288137912750244s
Reputation | Calculation of the PageRank for FrameBase schema took 0.021065473556518555s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.57763671875e-05s
Believability | Calculation of trust value for FrameBase schema took 1.239776611328125e-05s
INFO | --- Analysis for framebase-schema took 3.4490835666656494s
Availability | SPARQL endpoint availability check for Framester took 0.0001010894775390625s
Availability | VoID file availability check for Framester took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Framester took 0.3272073268890381s
Reputation | Calculation of the PageRank for Framester took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for Framester took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Framester took 7.176399230957031e-05s
Believability | Calculation of trust value for Framester took 7.152557373046875e-06s
INFO | --- Analysis for framester took 4.191529989242554s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.07149696350097656s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2773106098175049s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.021671295166015625s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 0.0001087188720703125s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for frb-linked-data took 2.9150660037994385s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 0.00010061264038085938s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 0.3147847652435303s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.0002715587615966797s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.2874603271484375e-05s
INFO | --- Analysis for freebase took 4.341398477554321s
Availability | SPARQL endpoint availability check for Freeyork took 9.846687316894531e-05s
Availability | VoID file availability check for Freeyork took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2879936695098877s
Reputation | Calculation of the PageRank for Freeyork took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010347366333007812s
Believability | Calculation of trust value for Freeyork took 1.1920928955078125e-05s
INFO | --- Analysis for freeyork-org took 3.2441840171813965s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7609925270080566s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.29508256912231445s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.2479248046875e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 9.298324584960938e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.705789804458618s
Availability | SPARQL endpoint availability check for DailyMed took 0.7215535640716553s
Availability | VoID file availability check for DailyMed took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for DailyMed took 0.27783727645874023s
Reputation | Calculation of the PageRank for DailyMed took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.512901306152344e-05s
Believability | Calculation of trust value for DailyMed took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-dailymed took 5.89781379699707s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.70450758934021s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.27810001373291016s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.559226989746094e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.1205673217773438e-05s
INFO | --- Analysis for fu-berlin-dblp took 4.632445573806763s
Availability | SPARQL endpoint availability check for Diseasome took 0.7179226875305176s
Availability | VoID file availability check for Diseasome took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Diseasome took 0.2765462398529053s
Reputation | Calculation of the PageRank for Diseasome took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.0001068115234375s
Believability | Calculation of trust value for Diseasome took 1.0013580322265625e-05s
INFO | --- Analysis for fu-berlin-diseasome took 5.741249084472656s
Availability | SPARQL endpoint availability check for DrugBank took 0.7368626594543457s
Availability | VoID file availability check for DrugBank took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2736971378326416s
Reputation | Calculation of the PageRank for DrugBank took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011491775512695312s
Believability | Calculation of trust value for DrugBank took 8.821487426757812e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.854439973831177s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.6925861835479736s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.29473090171813965s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.123283386230469e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 4.641222238540649s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6993310451507568s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.3120114803314209s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.2479248046875e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 9.775161743164062e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.739492416381836s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.7070755958557129s
Availability | VoID file availability check for European Employment Services (EURES) took 0.00040984153747558594s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.29150843620300293s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.462501525878906e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.9604644775390625e-06s
INFO | --- Analysis for fu-berlin-eures took 4.663404941558838s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6801748275756836s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2946944236755371s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 0.00010037422180175781s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.179780006408691s
Availability | SPARQL endpoint availability check for MediCare took 0.7174732685089111s
Availability | VoID file availability check for MediCare took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for MediCare took 0.27831602096557617s
Reputation | Calculation of the PageRank for MediCare took 0.02076125144958496s
Interlinking | Calculation of Degree of Connection for MediCare took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.482269287109375e-05s
Believability | Calculation of trust value for MediCare took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-medicare took 8.03819465637207s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.712165355682373s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.3190455436706543s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.43865966796875e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.812204599380493s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.720120906829834s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.3264734745025635s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.202957153320312e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.3113021850585938e-05s
INFO | --- Analysis for fu-berlin-sider took 5.255354642868042s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.7112321853637695s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2684059143066406s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.2479248046875e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.521552801132202s
Availability | SPARQL endpoint availability check for fvdb took 4.315376281738281e-05s
Availability | VoID file availability check for fvdb took 0.0003209114074707031s
Completeness | Calculation of interlinking completeness for fvdb took 0.30068016052246094s
Reputation | Calculation of the PageRank for fvdb took 0.021205902099609375s
Interlinking | Calculation of Degree of Connection for fvdb took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.170967102050781e-05s
Believability | Calculation of trust value for fvdb took 8.106231689453125e-06s
INFO | --- Analysis for fv took 12.64046025276184s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 5.125999450683594e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.28149914741516113s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0010068416595458984s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.7670135498046875e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 7.152557373046875e-06s
INFO | --- Analysis for GACS took 3.2007217407226562s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.267692565917969e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.26828932762145996s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020437002182006836s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 3.814697265625e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 6.67572021484375e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.375255584716797s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 8.535385131835938e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.29558873176574707s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.965896606445312e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 5.9604644775390625e-06s
INFO | --- Analysis for garnicaplywood took 3.5150485038757324s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.172325134277344e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.2797091007232666s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.021738529205322266s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.274482727050781e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.0251998901367188e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 10.151283264160156s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.43361687660217285s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.30324649810791016s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.02152729034423828s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.322166442871094e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for gemet took 5.303305625915527s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.458427429199219e-05s
Availability | VoID file availability check for gemet-annotated took 0.0007548332214355469s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.2913973331451416s
Reputation | Calculation of the PageRank for gemet-annotated took 0.021245241165161133s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.9577484130859375e-05s
Believability | Calculation of trust value for gemet-annotated took 1.3828277587890625e-05s
INFO | --- Analysis for gemet-annotated took 3.2813899517059326s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.8459503650665283s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00041604042053222656s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2969672679901123s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.553794860839844e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.1920928955078125e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.494271993637085s
Availability | SPARQL endpoint availability check for Super Ontology took 0.959848165512085s
Availability | VoID file availability check for Super Ontology took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2693929672241211s
Reputation | Calculation of the PageRank for Super Ontology took 0.020983219146728516s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Super Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 4.758600473403931s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.267692565917969e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.3194308280944824s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020785808563232422s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.218650817871094e-05s
Believability | Calculation of trust value for Geographic detector model took 1.3589859008789062e-05s
INFO | --- Analysis for GeoDetector took 19.722611904144287s
Availability | SPARQL endpoint availability check for geodomainwn took 8.749961853027344e-05s
Availability | VoID file availability check for geodomainwn took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.2986476421356201s
Reputation | Calculation of the PageRank for geodomainwn took 0.020856380462646484s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.76837158203125e-05s
Believability | Calculation of trust value for geodomainwn took 1.0728836059570312e-05s
INFO | --- Analysis for geodomainwn took 7.193110466003418s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.3392181396484375e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.3297460079193115s
Reputation | Calculation of the PageRank for GeoEcuador took 0.020998477935791016s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.699562072753906e-05s
Believability | Calculation of trust value for GeoEcuador took 1.2874603271484375e-05s
INFO | --- Analysis for geoecuador took 12.763540029525757s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.207716941833496s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0007851123809814453s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.30254554748535156s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.021099328994750977s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.866455078125e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.1444091796875e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 48.9396333694458s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.5200085639953613s
Availability | VoID file availability check for GeoLinkedData took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.2862820625305176s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.702278137207031e-05s
Believability | Calculation of trust value for GeoLinkedData took 5.0067901611328125e-06s
INFO | --- Analysis for geolinkeddata took 4.46707558631897s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.18636655807495117s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0006005764007568359s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.921376705169678s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.3835735321044922s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.15343475341796875s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.442039966583252s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.2135775089263916s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.17441701889038086s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.20676589012145996s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.10070419311523438s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.11433911323547363s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.07609391212463379s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.1145009994506836s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.8495566844940186s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.10792970657348633s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.11799144744873047s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.14480328559875488s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.09944796562194824s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.06891632080078125s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10648441314697266s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.317171335220337s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 7.557868957519531e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06961941719055176s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06891012191772461s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.10740160942077637s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.07038760185241699s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.0625307559967041s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1516892910003662s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16920900344848633s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.3459525108337402s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 0.7799727916717529s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.1075601577758789s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.0666494369506836s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06868982315063477s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.30556392669677734s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.00738525390625s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.2343761920928955s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.06233787536621094s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.21726608276367188s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5174355506896973s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.2113354206085205s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.5121595859527588s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.6864900588989258s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.17948460578918457s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.07601237297058105s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.1424064636230469s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.2777693271636963s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 7.843971252441406e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 0.4988367557525635s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 113.05037689208984s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 8.869171142578125e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.30961036682128906s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020647525787353516s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004596710205078125s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.4066696166992188e-05s
INFO | --- Analysis for geonames-semantic-web took 3.6288928985595703s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.172325134277344e-05s
Availability | VoID file availability check for Geospatial World  took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.2892920970916748s
Reputation | Calculation of the PageRank for Geospatial World  took 0.022366762161254883s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010323524475097656s
Believability | Calculation of trust value for Geospatial World  took 1.0251998901367188e-05s
INFO | --- Analysis for geospatialworld-net took 3.2489075660705566s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5565793514251709s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.3023219108581543s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.021045923233032227s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013399124145507812s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.0728836059570312e-05s
INFO | --- Analysis for geospecies took 6.035823345184326s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.57763671875e-05s
Availability | VoID file availability check for GeoWordNet took 0.0009453296661376953s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2838282585144043s
Reputation | Calculation of the PageRank for GeoWordNet took 0.022210121154785156s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 4.887580871582031e-05s
Believability | Calculation of trust value for GeoWordNet took 1.2874603271484375e-05s
INFO | --- Analysis for geowordnet took 8.111523628234863s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.08052778244018555s
Availability | VoID file availability check for German labor law thesaurus took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.31900668144226074s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.796287536621094e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 2.8872358798980713s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.410743713378906e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.2657163143157959s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02098870277404785s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.00543212890625e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.0728836059570312e-05s
INFO | --- Analysis for germlex took 3.0429182052612305s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.3532276153564453s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2868056297302246s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020679950714111328s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.702278137207031e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.049041748046875e-05s
INFO | --- Analysis for gesis-thesoz took 5.27105975151062s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.9899470806121826s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.28773951530456543s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.02075505256652832s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0009276866912841797s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 8.916854858398438e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for getty-aat took 17.05723285675049s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.3514463901519775s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.31520724296569824s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.125999450683594e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.0728836059570312e-05s
INFO | --- Analysis for getty-tgn took 13.464648962020874s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 6.648555040359497s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0007948875427246094s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.28678464889526367s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 2.9087066650390625e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 1.049041748046875e-05s
INFO | --- Analysis for gipuzkoademografia took 30.332210540771484s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 9.202957153320312e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.3255012035369873s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.1948089599609375e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.3113021850585938e-05s
INFO | --- Analysis for glastonbury-2011 took 5.815512657165527s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.2438507080078125e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0008687973022460938s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.3142092227935791s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0009675025939941406s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 6.127357482910156e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.2636184692382812e-05s
INFO | --- Analysis for global-hunger-index-2011 took 3.555969715118408s
Availability | SPARQL endpoint availability check for Glottolog took 8.749961853027344e-05s
Availability | VoID file availability check for Glottolog took 0.00030922889709472656s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2918698787689209s
Reputation | Calculation of the PageRank for Glottolog took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.0067901611328125e-05s
Believability | Calculation of trust value for Glottolog took 1.0967254638671875e-05s
INFO | --- Analysis for glottolog took 6.4322404861450195s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.863739013671875e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0009229183197021484s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.44257116317749023s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.02121448516845703s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00011110305786132812s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.0251998901367188e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 510.8503818511963s
Availability | SPARQL endpoint availability check for 1121 took 4.2438507080078125e-05s
Availability | VoID file availability check for 1121 took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for 1121 took 0.2800254821777344s
Reputation | Calculation of the PageRank for 1121 took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for 1121 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for 1121 took 2.9087066650390625e-05s
Believability | Calculation of trust value for 1121 took 6.67572021484375e-06s
INFO | --- Analysis for God_ took 3.5475881099700928s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 8.988380432128906e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2908437252044678s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.02082204818725586s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.054473876953125e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.33514404296875e-05s
INFO | --- Analysis for gold took 4.279560804367065s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 8.821487426757812e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.3047313690185547s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.508827209472656e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.0251998901367188e-05s
INFO | --- Analysis for googleart-wrapper took 2.9708993434906006s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.1042478084564209s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.3070981502532959s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02106308937072754s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.1948089599609375e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.1920928955078125e-05s
INFO | --- Analysis for govagribus-denmark took 35.08678317070007s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.4696543216705322s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.31171417236328125s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.022473573684692383s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.630752563476562e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 24.201447010040283s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 11.553773880004883s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0008018016815185547s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.31151413917541504s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 9.298324584960938e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 9.298324584960938e-06s
INFO | --- Analysis for govtrack took 95.69252371788025s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 5.221366882324219e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.32875776290893555s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.021910667419433594s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.7220458984375e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.0013580322265625e-05s
INFO | --- Analysis for greek-administrative-geography took 2.8328702449798584s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.2088758945465088s
Availability | VoID file availability check for Greek Wordnet took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.2755148410797119s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.021403074264526367s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 3.8623809814453125e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.2159347534179688e-05s
INFO | --- Analysis for greek-wordnet took 2.8827741146087646s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2606813907623291s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0013933181762695312s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 12.702203273773193s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.6156225204467773s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.9357337951660156s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 1.6157023906707764s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 1.745903730392456s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.4869849681854248s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.14897584915161133s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12405920028686523s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13312554359436035s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12971115112304688s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.47017812728881836s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12418079376220703s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.23923707008361816s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2497851848602295s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1305100917816162s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11565518379211426s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12257742881774902s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.89473032951355s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 0.00011444091796875s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11449646949768066s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11463570594787598s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1295785903930664s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12138676643371582s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1212766170501709s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.25071167945861816s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.25141239166259766s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 7.641391754150391s
Interoperability | New vocabularies check for Greek prisons releases Jan 2018 - Dec 2023 took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1304798126220703s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.11182832717895508s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.1203773021697998s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 2.346653461456299s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.2891237735748291s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.761518478393555s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12153959274291992s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.185727834701538s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 2.855464220046997s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.2319691181182861s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.4088053703308105s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.8124759197235107s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11289763450622559s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 4878.023820400238s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.7277791500091553s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.021716594696044922s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.7404556274414062e-05s
Interoperability | Check the re-using of existing vocabs for Greek prisons releases Jan 2018 - Dec 2023 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 1.2159347534179688e-05s
INFO | --- Analysis for greek_prisons_releases took 4957.5590534210205s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.7801609039306641s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.3101234436035156s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02068305015563965s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.295608520507812e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.1205673217773438e-05s
INFO | --- Analysis for greekchildrensartmuseum took 4.745508432388306s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.2438507080078125e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0003311634063720703s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.2867741584777832s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 9.441375732421875e-05s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 7.3388001918792725s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 2.3170111179351807s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.29891419410705566s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020224571228027344s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.363059997558594e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 5.9604644775390625e-06s
INFO | --- Analysis for grrp took 5.128451824188232s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.2678391933441162s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.28761887550354004s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02214336395263672s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.341934204101562e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 8.821487426757812e-06s
INFO | --- Analysis for grrt took 4.062262535095215s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1035809516906738s
Availability | VoID file availability check for Geological Timescale took 0.0005903244018554688s
Extra | Recovery of all triples for Geological Timescale took 2.8753085136413574s
Performance | Total latancy measurement for Geological Timescale took 6.020517587661743s
Amount of data | Number of triples check for Geological Timescale took 1.041311502456665s
Interoperability | New terms check for Geological Timescale took 3.2629971504211426s
Versatility | Languages check for Geological Timescale took 1.102457046508789s
Interpretability | Number of blank nodes check for Geological Timescale took 1.027393102645874s
Security | Check HTTPS for Geological Timescale took 0.9619522094726562s
Interpretability | RDF structures check for Geological Timescale took 2.1357171535491943s
Versatility | Serialization formats check for Geological Timescale took 1.989781141281128s
Availability | RDF dump link check for Geological Timescale took 1.8405697345733643s
License | MR license check for Geological Timescale took 0.997509241104126s
License | HR license check for Geological Timescale took 1.0532341003417969s
Amount of data | Number of property check for Geological Timescale took 1.0005943775177002s
Understandability | Number of label check for Geological Timescale took 1.0398926734924316s
Understandability | URI regex check for Geological Timescale took 2.9980239868164062s
Understandability | Vocabs check for Geological Timescale took 1.005356788635254s
Verifiability | Authors check for Geological Timescale took 1.002711534500122s
Verifiability | Publishers check for Geological Timescale took 0.9776651859283447s
Performance | Throughput check for Geological Timescale took 13.900736570358276s
Amount of data | Check the number of entities for Geological Timescale took 0.019101619720458984s
Verifiability | Contribs. check for Geological Timescale took 1.0524342060089111s
Interlinking | sameAs chians check for Geological Timescale took 0.9811384677886963s
Interlinking | skos check for Geological Timescale took 0.9632997512817383s
Interlinking | skos check for Geological Timescale took 2.112157106399536s
Timeliness | dataset update frequency check for Geological Timescale took 1.0333168506622314s
Currency | Creation date check for Geological Timescale took 7.1957807540893555s
Currency | Modification date check for Geological Timescale took 2.0546975135803223s
Rep.Conc. | URIs length for Geological Timescale took 2.132676601409912s
Interoperability | New vocabularies check for Geological Timescale took 1.786010503768921s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.41866087913513184s
Accuracy | Check Functional Property for Geological Timescale took 1.0273358821868896s
Accuracy | Check Inverse Functional Property for Geological Timescale took 2.5026092529296875s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.3592479228973389s
Accuracy | Check White space in annotation for Geological Timescale took 0.015549421310424805s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07381296157836914s
Consistency | Disjoint class check for Geological Timescale took 1.0293447971343994s
Consistency | Check Misplaced properties for Geological Timescale took 2.0282042026519775s
Consistency | Misplaced classes for Geological Timescale took 1.1102161407470703s
Consistency | Check Ontology hijacking for Geological Timescale took 1.6781058311462402s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.2318334579467773s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.2470297813415527s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.0498809814453125s
Conciseness | Check Intensional conciseness for Geological Timescale took 1.012026309967041s
Security | Sign check for Geological Timescale took 1.0189013481140137s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.7874834537506104s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.27745652198791504s
Reputation | Calculation of the PageRank for Geological Timescale took 0.021376848220825195s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.343292236328125e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 1.494701862335205s
Believability | Calculation of trust value for Geological Timescale took 1.3589859008789062e-05s
INFO | --- Analysis for GTS took 144.31349635124207s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2873537540435791s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02116107940673828s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.049041748046875e-05s
INFO | --- Analysis for GTS-ont took 2.919851779937744s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.57763671875e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.29300737380981445s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020844697952270508s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 2.86102294921875e-05s
Believability | Calculation of trust value for GUTSTOK  took 6.4373016357421875e-06s
INFO | --- Analysis for Guillaume_Forget took 2.6740880012512207s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.267692565917969e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0003757476806640625s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.3887791633605957s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02092885971069336s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.532669067382812e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.1205673217773438e-05s
INFO | --- Analysis for gutenberg took 188.10627055168152s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.267692565917969e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007672309875488281s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.28320932388305664s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02091217041015625s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.3855438232421875e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.3828277587890625e-05s
INFO | --- Analysis for gwa-ili took 5.334482908248901s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 8.487701416015625e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.29932570457458496s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.020861148834228516s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 2.86102294921875e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 1.0251998901367188e-05s
INFO | --- Analysis for GWR took 20.254527807235718s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.1961669921875e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.30935072898864746s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.021198272705078125s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 2.9087066650390625e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.0967254638671875e-05s
INFO | --- Analysis for HASM took 23.165635585784912s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.221099615097046s
Availability | VoID file availability check for HealthCare Ontology took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.28749680519104004s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.02169346809387207s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.4332275390625e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for HealthCare_Ontology took 6.304347276687622s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 9.059906005859375e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.30430150032043457s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.021518945693969727s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 5.817413330078125e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 9.775161743164062e-06s
INFO | --- Analysis for heartfailure took 3.3453903198242188s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.828038692474365s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.000774383544921875s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.3272831439971924s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.62396240234375e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.2874603271484375e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 120.52803993225098s
Availability | SPARQL endpoint availability check for Hedatuz took 0.24134182929992676s
Availability | VoID file availability check for Hedatuz took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.27942585945129395s
Reputation | Calculation of the PageRank for Hedatuz took 0.021790027618408203s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0009646415710449219s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 5.4836273193359375e-05s
Believability | Calculation of trust value for Hedatuz took 1.1920928955078125e-05s
INFO | --- Analysis for hedatuz took 3.2080211639404297s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.12172675132751465s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2927405834197998s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020629405975341797s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012183189392089844s
Believability | Calculation of trust value for Hellenic Fire Brigade took 8.344650268554688e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.853776693344116s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.02296137809753418s
Availability | VoID file availability check for Hellenic Police took 0.00041365623474121094s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.3015463352203369s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020462512969970703s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012159347534179688s
Believability | Calculation of trust value for Hellenic Police took 8.106231689453125e-06s
INFO | --- Analysis for hellenic-police took 2.7570242881774902s
Availability | SPARQL endpoint availability check for Hermos took 4.291534423828125e-05s
Availability | VoID file availability check for Hermos took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Hermos took 0.2750527858734131s
Reputation | Calculation of the PageRank for Hermos took 0.020931005477905273s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.123283386230469e-05s
Believability | Calculation of trust value for Hermos took 1.1205673217773438e-05s
INFO | --- Analysis for Hermos took 3.2759921550750732s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 8.320808410644531e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.267139196395874s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.457069396972656e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 5.0067901611328125e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.620054244995117s
Availability | SPARQL endpoint availability check for HITO took 0.4006476402282715s
Availability | VoID file availability check for HITO took 0.0005679130554199219s
Extra | Recovery of all triples for HITO took 1.8075850009918213s
Performance | Total latancy measurement for HITO took 0.9539980888366699s
Amount of data | Number of triples check for HITO took 0.2011575698852539s
Interoperability | New terms check for HITO took 1.4894263744354248s
Versatility | Languages check for HITO took 0.22044157981872559s
Interpretability | Number of blank nodes check for HITO took 0.17796993255615234s
Interpretability | RDF structures check for HITO took 0.19970393180847168s
Versatility | Serialization formats check for HITO took 0.19898366928100586s
Availability | RDF dump link check for HITO took 0.1976466178894043s
License | MR license check for HITO took 0.2020888328552246s
License | HR license check for HITO took 0.20105648040771484s
Amount of data | Number of property check for HITO took 0.18225741386413574s
Understandability | Number of label check for HITO took 0.20157766342163086s
Understandability | URI regex check for HITO took 10.287347555160522s
Understandability | Vocabs check for HITO took 0.1906604766845703s
Verifiability | Authors check for HITO took 0.18659043312072754s
Verifiability | Publishers check for HITO took 0.19885849952697754s
Verifiability | Contribs. check for HITO took 10.083814859390259s
Interlinking | sameAs chians check for HITO took 0.19385385513305664s
Interlinking | skos check for HITO took 0.19388103485107422s
Interlinking | skos check for HITO took 0.19748902320861816s
Timeliness | dataset update frequency check for HITO took 0.18654322624206543s
Currency | Creation date check for HITO took 0.3854689598083496s
Currency | Modification date check for HITO took 0.3644077777862549s
Rep.Conc. | URIs length for HITO took 1.0890367031097412s
Interoperability | New vocabularies check for HITO took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.1796553134918213s
Accuracy | Check Functional Property for HITO took 0.18856239318847656s
Accuracy | Check Inverse Functional Property for HITO took 0.1797194480895996s
Accuracy | Check Empty annotation labels for HITO took 0.5671911239624023s
Accuracy | Check White space in annotation for HITO took 0.013259649276733398s
Accuracy | Check Datatype consistency for HITO took 0.07431697845458984s
Consistency | Disjoint class check for HITO took 0.19739723205566406s
Consistency | Check Misplaced properties for HITO took 0.4845085144042969s
Consistency | Misplaced classes for HITO took 0.3471236228942871s
Consistency | Check Ontology hijacking for HITO took 1.7801198959350586s
Consistency | Check Invalid usage of undefined classes for HITO took 1.270172357559204s
Consistency | Check Invalid usage of undefined properties for HITO took 1.5227978229522705s
Conciseness | Check Extensional conciseness for HITO took 0.06218099594116211s
Conciseness | Check Intensional conciseness for HITO took 0.2023477554321289s
Security | Sign check for HITO took 0.19269251823425293s
Availability | Check URIs Dereferenciability for HITO took 2223.874210834503s
Completeness | Calculation of interlinking completeness for HITO took 0.5866906642913818s
Reputation | Calculation of the PageRank for HITO took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for HITO took 6.222724914550781e-05s
Interlinking | Calculation of Centrality for HITO took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for HITO took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.430511474609375e-06s
Believability | Calculation of trust value for HITO took 1.3113021850585938e-05s
INFO | --- Analysis for hito took 2326.5643022060394s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 12.878380298614502s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0007698535919189453s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.3086843490600586s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 2.7418136596679688e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.1205673217773438e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 42.85833191871643s
Availability | SPARQL endpoint availability check for gseg took 8.988380432128906e-05s
Availability | VoID file availability check for gseg took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for gseg took 0.2658205032348633s
Reputation | Calculation of the PageRank for gseg took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for gseg took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for gseg took 2.8371810913085938e-05s
Believability | Calculation of trust value for gseg took 2.8133392333984375e-05s
INFO | --- Analysis for hongse took 3.0740089416503906s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.5006062984466553s
Availability | VoID file availability check for COURAGE Dataset took 0.0007340908050537109s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.2815525531768799s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.02076101303100586s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 5.685389518737793s
Availability | SPARQL endpoint availability check for RoadTrb took 4.4345855712890625e-05s
Availability | VoID file availability check for RoadTrb took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.3099493980407715s
Reputation | Calculation of the PageRank for RoadTrb took 0.021230220794677734s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.0040740966796875e-05s
Believability | Calculation of trust value for RoadTrb took 1.1682510375976562e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.7105774879455566s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.26902270317077637s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 42.800477266311646s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 8.749961853027344e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.2871236801147461s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.0279159545898438e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.1920928955078125e-05s
INFO | --- Analysis for http:pakistan.com took 2.749415397644043s
Availability | SPARQL endpoint availability check for CEDICT took 8.821487426757812e-05s
Availability | VoID file availability check for CEDICT took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for CEDICT took 0.28710460662841797s
Reputation | Calculation of the PageRank for CEDICT took 0.02213740348815918s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.000997304916381836s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.910064697265625e-05s
Believability | Calculation of trust value for CEDICT took 1.239776611328125e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.230685472488403s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.4974889755249023s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2990844249725342s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020769357681274414s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.556510925292969e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2874603271484375e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 4.912433385848999s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 9.489059448242188e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.2791271209716797s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.021141767501831055s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.0994415283203125e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.33514404296875e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 3.414884567260742s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.363059997558594e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.33890295028686523s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.022237777709960938s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 2.86102294921875e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.3113021850585938e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.7602109909057617s
Availability | SPARQL endpoint availability check for Soccer Dataset took 5.650520324707031e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.2859649658203125s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.8371810913085938e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.33514404296875e-05s
INFO | --- Analysis for http:www.msm.com took 2.667036533355713s
Availability | SPARQL endpoint availability check for Game Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Game Ontology took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.27419519424438477s
Reputation | Calculation of the PageRank for Game Ontology took 0.021538972854614258s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for Game Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 3.26051664352417s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.988380432128906e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2878999710083008s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 2.765655517578125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0251998901367188e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.3955986499786377s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.410743713378906e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.32878971099853516s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.021089553833007812s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.123283386230469e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2874603271484375e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.7510993480682373s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.4345855712890625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2925102710723877s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.457069396972656e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2636184692382812e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.6937246322631836s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.749961853027344e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.29346632957458496s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020812034606933594s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0279159545898438e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2636184692382812e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.7132558822631836s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00010395050048828125s
Availability | VoID file availability check for Indian Biodiversity took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2890772819519043s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9802322387695312e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2874603271484375e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.6368582248687744s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.560585021972656e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3207051753997803s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.170967102050781e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2636184692382812e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 4.107010126113892s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.410743713378906e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2875068187713623s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.0212862491607666s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7418136596679688e-05s
Believability | Calculation of trust value for Indian Biodiversity took 9.059906005859375e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.77268123626709s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.00011515617370605469s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.30258798599243164s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.02104926109313965s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.075599670410156e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.2874603271484375e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.080944776535034s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.0431578159332275s
Availability | VoID file availability check for Bookkeeping took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.30460429191589355s
Reputation | Calculation of the PageRank for Bookkeeping took 0.021638154983520508s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bookkeeping took 1.3113021850585938e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 4.37919020652771s
Availability | SPARQL endpoint availability check for Legal Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Legal Ontology took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.30930566787719727s
Reputation | Calculation of the PageRank for Legal Ontology took 0.021018505096435547s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for Legal Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 3.332049608230591s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 9.608268737792969e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.27155399322509766s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.748603820800781e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 8.58306884765625e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 3.021446704864502s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 8.845329284667969e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.31512975692749023s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.075599670410156e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.0728836059570312e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 3.0166707038879395s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.6376345157623291s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.32535552978515625s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.000993490219116211s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00012063980102539062s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.1682510375976562e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 3.265117883682251s
Availability | SPARQL endpoint availability check for IATE RDF took 4.315376281738281e-05s
Availability | VoID file availability check for IATE RDF took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.2993643283843994s
Reputation | Calculation of the PageRank for IATE RDF took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for IATE RDF took 1.2159347534179688e-05s
INFO | --- Analysis for iate-rdf took 2.9227206707000732s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.373571157455444s
Availability | VoID file availability check for IATI as Linked Data took 0.0008313655853271484s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.3126246929168701s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.177757263183594e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for iati-as-linked-data took 14.319582462310791s
Availability | SPARQL endpoint availability check for ICANE took 0.367112398147583s
Availability | VoID file availability check for ICANE took 0.0008571147918701172s
Completeness | Calculation of interlinking completeness for ICANE took 0.2982978820800781s
Reputation | Calculation of the PageRank for ICANE took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for ICANE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.320808410644531e-05s
Believability | Calculation of trust value for ICANE took 9.059906005859375e-06s
INFO | --- Analysis for icane took 3.961752414703369s
Availability | SPARQL endpoint availability check for ichoose took 0.18520450592041016s
Availability | VoID file availability check for ichoose took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for ichoose took 0.2983839511871338s
Reputation | Calculation of the PageRank for ichoose took 0.021027565002441406s
Interlinking | Calculation of Degree of Connection for ichoose took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.295608520507812e-05s
Believability | Calculation of trust value for ichoose took 1.2636184692382812e-05s
INFO | --- Analysis for ichoose took 42.72043800354004s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 1.1214747428894043s
Availability | VoID file availability check for The Iconology Dataset took 0.0007560253143310547s
Extra | Recovery of all triples for The Iconology Dataset took 3.8520731925964355s
Performance | Total latancy measurement for The Iconology Dataset took 0.4920170307159424s
Amount of data | Number of triples check for The Iconology Dataset took 0.20108485221862793s
Interoperability | New terms check for The Iconology Dataset took 1.405883550643921s
Versatility | Languages check for The Iconology Dataset took 0.5774049758911133s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.2360365390777588s
Interpretability | RDF structures check for The Iconology Dataset took 0.11602950096130371s
Versatility | Serialization formats check for The Iconology Dataset took 0.10383176803588867s
Availability | RDF dump link check for The Iconology Dataset took 0.09135723114013672s
License | MR license check for The Iconology Dataset took 0.10439682006835938s
License | HR license check for The Iconology Dataset took 0.2946503162384033s
Amount of data | Number of property check for The Iconology Dataset took 0.10131978988647461s
Understandability | Number of label check for The Iconology Dataset took 0.15248560905456543s
Understandability | URI regex check for The Iconology Dataset took 0.1676480770111084s
Understandability | Vocabs check for The Iconology Dataset took 0.09155011177062988s
Verifiability | Authors check for The Iconology Dataset took 0.09720921516418457s
Verifiability | Publishers check for The Iconology Dataset took 0.09847736358642578s
Performance | Throughput check for The Iconology Dataset took 10.497282028198242s
Amount of data | Check the number of entities for The Iconology Dataset took 0.0004298686981201172s
Verifiability | Contribs. check for The Iconology Dataset took 0.08924603462219238s
Interlinking | sameAs chians check for The Iconology Dataset took 0.08801865577697754s
Interlinking | skos check for The Iconology Dataset took 0.09102106094360352s
Interlinking | skos check for The Iconology Dataset took 0.09012889862060547s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.08877992630004883s
Currency | Creation date check for The Iconology Dataset took 0.18137836456298828s
Currency | Modification date check for The Iconology Dataset took 0.1872868537902832s
Rep.Conc. | URIs length for The Iconology Dataset took 1.2153198719024658s
Interoperability | New vocabularies check for The Iconology Dataset took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08179521560668945s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.27416467666625977s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016122817993164062s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.4281313419342041s
Consistency | Disjoint class check for The Iconology Dataset took 0.0807645320892334s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.14851093292236328s
Consistency | Misplaced classes for The Iconology Dataset took 0.8697264194488525s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.5945351123809814s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.2805867195129395s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.3694331645965576s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.29934024810791016s
Security | Sign check for The Iconology Dataset took 0.08530926704406738s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2554.644725561142s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.7689919471740723s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.020958900451660156s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.5735626220703125e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for The Iconology Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for iconology-dataset took 2613.1796357631683s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.220008850097656e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2785196304321289s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.772445678710938e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.0967254638671875e-05s
INFO | --- Analysis for idreffr took 3.7985801696777344s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.6717038154602051s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.28783607482910156s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.8160552978515625e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.2636184692382812e-05s
INFO | --- Analysis for ids took 3.741851806640625s
Availability | SPARQL endpoint availability check for ietflang took 8.893013000488281e-05s
Availability | VoID file availability check for ietflang took 0.0008909702301025391s
Completeness | Calculation of interlinking completeness for ietflang took 0.44608068466186523s
Reputation | Calculation of the PageRank for ietflang took 0.02088642120361328s
Interlinking | Calculation of Degree of Connection for ietflang took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for ietflang took 5.269050598144531e-05s
Believability | Calculation of trust value for ietflang took 1.1682510375976562e-05s
INFO | --- Analysis for ietflang took 14.641389846801758s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.6287415027618408s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.28038811683654785s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 4.1961669921875e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for IGVLL took 4.286947250366211s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.47690391540527344s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0005521774291992188s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.4351298809051514s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9220988750457764s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.18952250480651855s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.4799604415893555s
Versatility | Languages check for 3LGM² IHE Ontology took 0.20890593528747559s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.17918181419372559s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.25020313262939453s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.21074795722961426s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.20902061462402344s
License | MR license check for 3LGM² IHE Ontology took 0.1931300163269043s
License | HR license check for 3LGM² IHE Ontology took 0.2234048843383789s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.1769711971282959s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.2195742130279541s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.40691161155700684s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.1912081241607666s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.20375847816467285s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.18229126930236816s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.390975952148438e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.18342161178588867s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.20180320739746094s
Interlinking | skos check for 3LGM² IHE Ontology took 0.20351028442382812s
Interlinking | skos check for 3LGM² IHE Ontology took 0.1699357032775879s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.19433808326721191s
Currency | Creation date check for 3LGM² IHE Ontology took 0.3736555576324463s
Currency | Modification date check for 3LGM² IHE Ontology took 0.3923189640045166s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.7746186256408691s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.2102513313293457s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.18081426620483398s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.20685887336730957s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.35144829750061035s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0036597251892089844s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.05254244804382324s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.20093512535095215s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.46006298065185547s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.5519764423370361s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.2706375122070312s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.4936468601226807s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.02974534034729004s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.1929922103881836s
Security | Sign check for 3LGM² IHE Ontology took 0.17322683334350586s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 412.3178572654724s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.39717841148376465s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.02114582061767578s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 4.38690185546875e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.430511474609375e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.049041748046875e-05s
INFO | --- Analysis for IHE took 468.22899866104126s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.881845235824585s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.000759124755859375s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 7.207763671875s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 9.150907754898071s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 17.214504718780518s
Interoperability | New terms check for Test Site, LOD Lab 317 took 8.299195051193237s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.80855345726013s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.9528577327728271s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.2203330993652344s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 2.1420786380767822s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.909494161605835s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.8498046398162842s
License | MR license check for Test Site, LOD Lab 317 took 1.8551759719848633s
License | HR license check for Test Site, LOD Lab 317 took 2.18658709526062s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.865612268447876s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.9711503982543945s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.642530918121338s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.8447818756103516s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.94533109664917s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.8383119106292725s
Performance | Throughput check for Test Site, LOD Lab 317 took 18.11579394340515s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 6.985664367675781e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.841426134109497s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.8295438289642334s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.8845653533935547s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.84517240524292s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.8952553272247314s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.724867582321167s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.6830101013183594s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 33.06249785423279s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.9032883644104004s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.8392136096954346s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.843456506729126s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 3.7123687267303467s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.0308380126953125s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.029296398162841797s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.8560492992401123s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 23.66045331954956s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 2.2137086391448975s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 5.007578134536743s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.2740137577056885s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 23.0371196269989s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.032050132751464844s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.456289529800415s
Security | Sign check for Test Site, LOD Lab 317 took 1.840601921081543s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 9.336348533630371s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.3748195171356201s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.021218061447143555s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 4.553794860839844e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.430511474609375e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.2636184692382812e-05s
INFO | --- Analysis for iislod-test took 561.8518109321594s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 0.0001163482666015625s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.00067138671875s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.2890889644622803s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.02201676368713379s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.6716461181640625e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.2874603271484375e-05s
INFO | --- Analysis for ILUSOC took 21.308947324752808s
Availability | SPARQL endpoint availability check for im@sparql took 7.396699666976929s
Availability | VoID file availability check for im@sparql took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for im@sparql took 0.2875840663909912s
Reputation | Calculation of the PageRank for im@sparql took 0.020661115646362305s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for im@sparql took 0.00011539459228515625s
Believability | Calculation of trust value for im@sparql took 9.775161743164062e-06s
INFO | --- Analysis for im@sparql took 14.671683311462402s
Availability | SPARQL endpoint availability check for imagery bailingniao took 0.000102996826171875s
Availability | VoID file availability check for imagery bailingniao took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.27524852752685547s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.02115464210510254s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0008356571197509766s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.5762786865234375e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.1444091796875e-05s
INFO | --- Analysis for imagery_bailingniao took 3.540450096130371s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.0937039852142334s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006089210510253906s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 20.969408988952637s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.4062154293060303s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.982034921646118s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.3922154903411865s
Versatility | Languages check for Imagesnippets Image Descriptions took 20.182249546051025s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.715978622436523s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.651710033416748s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7152178287506104s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.734158992767334s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7167341709136963s
License | MR license check for Imagesnippets Image Descriptions took 0.719703197479248s
License | HR license check for Imagesnippets Image Descriptions took 30.705795288085938s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7352170944213867s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.5659642219543457s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.41117525100708s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.708345890045166s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7367753982543945s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7046647071838379s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.52458643913269s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 6.961822509765625e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7070889472961426s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.6940736770629883s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7291533946990967s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6751818656921387s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.6894707679748535s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.4262964725494385s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.4124598503112793s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 33.253886699676514s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.6960136890411377s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6953601837158203s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7041049003601074s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 11.34538722038269s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.16528582572937s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.26890230178833s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7047460079193115s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.971171617507935s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 5.03111457824707s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.4211008548736572s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.548810720443726s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.77728271484375s
Security | Sign check for Imagesnippets Image Descriptions took 0.7152423858642578s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 11.179685592651367s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.33423376083374023s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.1920928955078125e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.2159347534179688e-05s
INFO | --- Analysis for imagesnippets took 372.054395198822s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.08546710014343262s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.2841310501098633s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.988380432128906e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for imf-linked-data took 2.8852195739746094s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 8.535385131835938e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.2878756523132324s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.0967254638671875e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 1.049041748046875e-05s
INFO | --- Analysis for Imtiaz took 2.580507755279541s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.267692565917969e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2973966598510742s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020905494689941406s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 2.7418136596679688e-05s
Believability | Calculation of trust value for Royalty Free Music took 5.4836273193359375e-06s
INFO | --- Analysis for inaudio.org took 4.15034294128418s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.5049667358398438s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.29733848571777344s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.021619081497192383s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.4809112548828125e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.049041748046875e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 4.169044017791748s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.00010204315185546875s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2877349853515625s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010609626770019531s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 1.1444091796875e-05s
INFO | --- Analysis for ineverycrea took 13.663919448852539s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.416175842285156e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0012278556823730469s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.3087019920349121s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.012222290039062e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.1205673217773438e-05s
INFO | --- Analysis for ineverycrea-argentina took 7.510307788848877s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 271.7325885295868s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.44156742095947266s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02202153205871582s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.152557373046875e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for influence-tracker-dataset took 565.3748977184296s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.220008850097656e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2733156681060791s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.7179718017578125e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 1.2636184692382812e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 2.592848777770996s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.267692565917969e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00092315673828125s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.3120713233947754s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02071523666381836s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.822845458984375e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for interactivemaps-gnoss took 9.08595895767212s
Availability | SPARQL endpoint availability check for intervalue took 0.15413379669189453s
Availability | VoID file availability check for intervalue took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for intervalue took 0.28660130500793457s
Reputation | Calculation of the PageRank for intervalue took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for intervalue took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for intervalue took 7.677078247070312e-05s
Believability | Calculation of trust value for intervalue took 1.1920928955078125e-05s
INFO | --- Analysis for intervalue took 2.7831602096557617s
Availability | SPARQL endpoint availability check for Inztrow took 4.172325134277344e-05s
Availability | VoID file availability check for Inztrow took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for Inztrow took 0.28648805618286133s
Reputation | Calculation of the PageRank for Inztrow took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.86102294921875e-05s
Believability | Calculation of trust value for Inztrow took 1.239776611328125e-05s
INFO | --- Analysis for Inztrow took 4.115338087081909s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.3062708377838135s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.022827625274658203s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 5.0067901611328125e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for ipbes took 3.9561266899108887s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 8.463859558105469e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.28604984283447266s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020946741104125977s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.601478576660156e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.0251998901367188e-05s
INFO | --- Analysis for iptc-newscodes took 3.2860493659973145s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.3105251789093018s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.3108494281768799s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.34600830078125e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.0013580322265625e-05s
INFO | --- Analysis for iserve took 9.06445598602295s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.064512968063354s
Availability | VoID file availability check for ISIC V4 took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.3104736804962158s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020796537399291992s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.315376281738281e-05s
Believability | Calculation of trust value for ISIC V4 took 8.821487426757812e-06s
INFO | --- Analysis for isic-v4 took 115.15125298500061s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.267692565917969e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.27524876594543457s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.021182537078857422s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.128715515136719e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 8.821487426757812e-06s
INFO | --- Analysis for isil-dbpedia took 4.392848014831543s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 9.1552734375e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.28840112686157227s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.02100205421447754s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.6716461181640625e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 9.5367431640625e-06s
INFO | --- Analysis for iso-639-oasis took 3.452998161315918s
Availability | SPARQL endpoint availability check for ISOcat took 4.6253204345703125e-05s
Availability | VoID file availability check for ISOcat took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for ISOcat took 0.28676795959472656s
Reputation | Calculation of the PageRank for ISOcat took 0.02125072479248047s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.008148193359375e-05s
Believability | Calculation of trust value for ISOcat took 1.1920928955078125e-05s
INFO | --- Analysis for isocat took 7.7175514698028564s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 8.392333984375e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.2810661792755127s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.361701965332031e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.1444091796875e-05s
INFO | --- Analysis for isocat-metadata took 4.952892541885376s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13166189193725586s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006079673767089844s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.78206205368042s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28164219856262207s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15215396881103516s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8575172424316406s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.75903654098511s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09133005142211914s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.031487464904785156s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10956907272338867s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10559511184692383s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09322786331176758s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14330077171325684s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.73645758628845s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09389257431030273s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3325810432434082s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3119676113128662s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13700485229492188s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13679051399230957s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09136223793029785s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.434183597564697s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.7670135498046875e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1337580680847168s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20228886604309082s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.42420291900634766s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3877077102661133s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13929009437561035s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18622207641601562s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09479260444641113s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 12.863474130630493s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09066176414489746s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10799908638000488s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09447908401489258s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.781406879425049s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.30542850494384766s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2648189067840576s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0904083251953125s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.01997709274292s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9260530471801758s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8032288551330566s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.312453269958496s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.134751319885254s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2911534309387207s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09798526763916016s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10504961013793945s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.718450546264648s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.30443906784057617s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.021184682846069336s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.870529174804688e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.384185791015625e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3828277587890625e-05s
INFO | --- Analysis for ispra-lod-place took 442.4357600212097s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.05104374885559082s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0003235340118408203s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.321720361709595s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.29965758323669434s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.14818263053894043s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.9033899307250977s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 91.14579129219055s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.09160113334655762s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.03187060356140137s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.117156982421875s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.10525321960449219s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.09530782699584961s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.1524667739868164s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 90.83078336715698s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.09326815605163574s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.1789395809173584s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.2877042293548584s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.12889838218688965s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.13546228408813477s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.0914769172668457s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.347651958465576s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 8.797645568847656e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.1440291404724121s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.20969891548156738s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4589400291442871s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4267613887786865s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.14291739463806152s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.18300461769104004s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.09088587760925293s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 12.909905433654785s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.08974003791809082s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.10085129737854004s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.09365463256835938s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.8284096717834473s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.30989861488342285s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.27114057540893555s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.08766484260559082s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 8.911953210830688s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9243035316467285s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.9495952129364014s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.3203833103179932s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.217203140258789s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.29695987701416016s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.09775853157043457s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.10492897033691406s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.241820812225342s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.3764052391052246s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.02188587188720703s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.267692565917969e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.9073486328125e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.1682510375976562e-05s
INFO | --- Analysis for ispra-lod-ron took 441.16654205322266s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.7400617599487305s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.28628993034362793s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020990848541259766s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.655952453613281e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 9.775161743164062e-06s
INFO | --- Analysis for issa-agritrop took 5.105907201766968s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.76837158203125e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.27187275886535645s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020895004272460938s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.123283386230469e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 9.5367431640625e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.506747007369995s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 8.821487426757812e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.29750633239746094s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02266979217529297s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.075599670410156e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.3828277587890625e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 3.791694164276123s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 8.821487426757812e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.28722214698791504s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.02168560028076172s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 2.9802322387695312e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 9.5367431640625e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 2.844094753265381s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.3211863040924072s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.2832348346710205s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.022005319595336914s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.678436279296875e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 8.58306884765625e-06s
INFO | --- Analysis for istat-immigration took 3.974738597869873s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.4963674545288086s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0008139610290527344s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2815423011779785s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.021062612533569336s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.0994415283203125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 8.58306884765625e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.3902738094329834s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.237067699432373s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.28691530227661133s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.021471023559570312s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.486343383789062e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.049041748046875e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 3.8596556186676025s
Availability | SPARQL endpoint availability check for IWN took 4.649162292480469e-05s
Availability | VoID file availability check for IWN took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for IWN took 0.28526854515075684s
Reputation | Calculation of the PageRank for IWN took 0.021109580993652344s
Interlinking | Calculation of Degree of Connection for IWN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for IWN took 3.8623809814453125e-05s
Believability | Calculation of trust value for IWN took 1.1444091796875e-05s
INFO | --- Analysis for iwn took 6.0614824295043945s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.712418794631958s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.29744601249694824s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020856380462646484s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.079673767089844e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.0013580322265625e-05s
INFO | --- Analysis for jamendo-dbtune took 10.110883235931396s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 7.891654968261719e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.28503894805908203s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.76837158203125e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.668769598007202s
Availability | SPARQL endpoint availability check for JEL Classification took 4.363059997558594e-05s
Availability | VoID file availability check for JEL Classification took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2887537479400635s
Reputation | Calculation of the PageRank for JEL Classification took 0.021496057510375977s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.075599670410156e-05s
Believability | Calculation of trust value for JEL Classification took 1.0013580322265625e-05s
INFO | --- Analysis for jel-classification took 4.791244745254517s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.1736598014831543s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.2772860527038574s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020869731903076172s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.2874603271484375e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 6.772996664047241s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.8825263977051s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.29149770736694336s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.021623611450195312s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.390975952148438e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.049041748046875e-05s
INFO | --- Analysis for jita took 542.8027319908142s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.068254470825195s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.34430813789367676s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.021570920944213867s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.273124694824219e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.33514404296875e-05s
INFO | --- Analysis for john-goodwins-family-tree took 63.32678437232971s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.1484832763671875e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2829105854034424s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.02108478546142578s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.457069396972656e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 1.5497207641601562e-05s
INFO | --- Analysis for jp-cos took 4.819084882736206s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 0.00011897087097167969s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.2721576690673828s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.02152228355407715s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0009665489196777344s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.601478576660156e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.2636184692382812e-05s
INFO | --- Analysis for jp-textbook took 4.6398515701293945s
Availability | SPARQL endpoint availability check for JRC-Names took 8.535385131835938e-05s
Availability | VoID file availability check for JRC-Names took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.29351806640625s
Reputation | Calculation of the PageRank for JRC-Names took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.218650817871094e-05s
Believability | Calculation of trust value for JRC-Names took 1.1444091796875e-05s
INFO | --- Analysis for jrc-names-ec took 5.024799585342407s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 0.9552676677703857s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.27950453758239746s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020941972732543945s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0008413791656494141s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.723403930664062e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 7.867813110351562e-06s
INFO | --- Analysis for jrc-names-mlode took 3.7289609909057617s
Availability | SPARQL endpoint availability check for JudaicaLink took 8.797645568847656e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.31076622009277344s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020589590072631836s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 9.942054748535156e-05s
Believability | Calculation of trust value for JudaicaLink took 1.239776611328125e-05s
INFO | --- Analysis for judaicalink took 5.734115839004517s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06782865524291992s
Availability | VoID file availability check for Kallikratis municipalities took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.27463245391845703s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.02188706398010254s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 8.916854858398438e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 5.0067901611328125e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.8270459175109863s
Availability | SPARQL endpoint availability check for EU Soccer League took 8.630752563476562e-05s
Availability | VoID file availability check for EU Soccer League took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2775123119354248s
Reputation | Calculation of the PageRank for EU Soccer League took 0.02154684066772461s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.52587890625e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0010466575622558594s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.886222839355469e-05s
Believability | Calculation of trust value for EU Soccer League took 1.1920928955078125e-05s
INFO | --- Analysis for KG:Course_Submission took 4.812185287475586s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 6.866455078125e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.29526543617248535s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.020937442779541016s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.1444091796875e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.3589859008789062e-05s
INFO | --- Analysis for KING took 3.0912811756134033s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 8.7738037109375e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.26676154136657715s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.127357482910156e-05s
Believability | Calculation of trust value for Klappstuhlclub took 9.298324584960938e-06s
INFO | --- Analysis for klappstuhlclub took 12.838684797286987s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.81629753112793s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.2786743640899658s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.02154088020324707s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 5.793571472167969e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.2636184692382812e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.569196701049805s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.458427429199219e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.3145632743835449s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.7894973754882812e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.2159347534179688e-05s
INFO | --- Analysis for KnowledgeFusion took 2.6936867237091064s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 8.630752563476562e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.28690338134765625s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.175041198730469e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.049041748046875e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.501249551773071s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.393692016601562e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.2942495346069336s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.7179718017578125e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.1444091796875e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.6038424968719482s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.172325134277344e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.2663257122039795s
Reputation | Calculation of the PageRank for Informatics Studies took 0.021908998489379883s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.765655517578125e-05s
Believability | Calculation of trust value for Informatics Studies took 1.0967254638671875e-05s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.3139967918395996s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.0676732063293457s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.31700730323791504s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.695487976074219e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 1.049041748046875e-05s
INFO | --- Analysis for kupkb took 9.777393341064453s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 7.4653236865997314s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.3023064136505127s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.033348083496094e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 3.7670135498046875e-05s
INFO | --- Analysis for l3s-dblp took 41.86142420768738s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.17449450492859s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.311248779296875s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.02099466323852539s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.318092346191406e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for lak-dataset took 66.71189737319946s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.23288536071777344s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005793571472167969s
Extra | Recovery of all triples for  Language Name Authority List  took 207.92658042907715s
Performance | Total latancy measurement for  Language Name Authority List  took 0.5937800407409668s
Amount of data | Number of triples check for  Language Name Authority List  took 107.06350660324097s
Interoperability | New terms check for  Language Name Authority List  took 58.082266092300415s
Versatility | Languages check for  Language Name Authority List  took 300.0167007446289s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 60.010985136032104s
Security | Check HTTPS for  Language Name Authority List  took 0.3647487163543701s
Interpretability | RDF structures check for  Language Name Authority List  took 0.3073558807373047s
Versatility | Serialization formats check for  Language Name Authority List  took 4.418492078781128s
Availability | RDF dump link check for  Language Name Authority List  took 0.2298569679260254s
License | MR license check for  Language Name Authority List  took 0.38365721702575684s
License | HR license check for  Language Name Authority List  took 300.05852460861206s
Amount of data | Number of property check for  Language Name Authority List  took 0.17872047424316406s
Understandability | Number of label check for  Language Name Authority List  took 1.7679927349090576s
Understandability | URI regex check for  Language Name Authority List  took 0.37676405906677246s
Understandability | Vocabs check for  Language Name Authority List  took 0.10227560997009277s
Verifiability | Authors check for  Language Name Authority List  took 0.2550678253173828s
Verifiability | Publishers check for  Language Name Authority List  took 0.20580101013183594s
Performance | Throughput check for  Language Name Authority List  took 10.717446327209473s
Amount of data | Check the number of entities for  Language Name Authority List  took 0.0001068115234375s
Verifiability | Contribs. check for  Language Name Authority List  took 0.11491560935974121s
Interlinking | sameAs chians check for  Language Name Authority List  took 8.590540409088135s
Interlinking | skos check for  Language Name Authority List  took 0.36171865463256836s
Interlinking | skos check for  Language Name Authority List  took 0.3287391662597656s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.32828211784362793s
Currency | Creation date check for  Language Name Authority List  took 0.5369036197662354s
Currency | Modification date check for  Language Name Authority List  took 0.16146564483642578s
Rep.Conc. | URIs length for  Language Name Authority List  took 407.33304047584534s
Interoperability | New vocabularies check for  Language Name Authority List  took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.189528226852417s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.1999197006225586s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.16344761848449707s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 38.61411380767822s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.0198910236358643s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.607576370239258s
Consistency | Disjoint class check for  Language Name Authority List  took 0.16969060897827148s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.38601183891296s
Consistency | Misplaced classes for  Language Name Authority List  took 8.383888006210327s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 37.73023962974548s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.7853584289550781s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.38516640663147s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 2.9790937900543213s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.3870680332183838s
Security | Sign check for  Language Name Authority List  took 0.3965260982513428s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 11.300071954727173s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.8157675266265869s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021305322647094727s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.059906005859375e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.1205673217773438e-05s
INFO | --- Analysis for language-authority-list took 14908.851579904556s
Availability | SPARQL endpoint availability check for Lark took 384.1989896297455s
Availability | VoID file availability check for Lark took 0.0010175704956054688s
Completeness | Calculation of interlinking completeness for Lark took 0.3571035861968994s
Reputation | Calculation of the PageRank for Lark took 0.021115541458129883s
Interlinking | Calculation of Degree of Connection for Lark took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Lark took 6.651878356933594e-05s
Believability | Calculation of trust value for Lark took 1.0251998901367188e-05s
INFO | --- Analysis for LARK took 1675.8051362037659s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.6423690319061279s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.29009222984313965s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.02196478843688965s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for LASLA took 4.7364113330841064s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.5899097919464111s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.30064892768859863s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020862817764282227s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 4.029273986816406e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 4.3439085483551025s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.5772984027862549s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.3078923225402832s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.1444091796875e-05s
INFO | --- Analysis for LatinAffectus took 4.5259315967559814s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.6137592792510986s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0007507801055908203s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.3048405647277832s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.020612001419067383s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.124641418457031e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.3113021850585938e-05s
INFO | --- Analysis for LatinWordnetLiLa took 4.731815814971924s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 8.7738037109375e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2978792190551758s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011658668518066406s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.1682510375976562e-05s
INFO | --- Analysis for lcsh took 7.661362409591675s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 8.797645568847656e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.3303718566894531s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.106231689453125e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.1205673217773438e-05s
INFO | --- Analysis for lcsubjects took 3.538602590560913s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.861336469650269s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.32858943939208984s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020537853240966797s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0009698867797851562s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 5.221366882324219e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.2159347534179688e-05s
INFO | --- Analysis for ldt@library took 35.26311111450195s
Availability | SPARQL endpoint availability check for U ime Legije took 9.179115295410156e-05s
Availability | VoID file availability check for U ime Legije took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.28925657272338867s
Reputation | Calculation of the PageRank for U ime Legije took 0.022423267364501953s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.314018249511719e-05s
Believability | Calculation of trust value for U ime Legije took 1.1920928955078125e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 2.7324819564819336s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.5049655437469482s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.2943735122680664s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 6.937980651855469e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.1444091796875e-05s
INFO | --- Analysis for LemmaBank took 4.895779132843018s
Availability | SPARQL endpoint availability check for lemonUby took 8.869171142578125e-05s
Availability | VoID file availability check for lemonUby took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2985382080078125s
Reputation | Calculation of the PageRank for lemonUby took 0.02148604393005371s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.52587890625e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for lemonUby took 7.224082946777344e-05s
Believability | Calculation of trust value for lemonUby took 1.049041748046875e-05s
INFO | --- Analysis for lemonuby took 3.4376800060272217s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.863739013671875e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.32013607025146484s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.457069396972656e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.049041748046875e-05s
INFO | --- Analysis for lemonwiktionary took 4.192110538482666s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.5057032108306885s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.2869260311126709s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02119755744934082s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for LewisShort took 4.197267293930054s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.2332234382629395s
Availability | VoID file availability check for LEXIN-RDF took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.32639002799987793s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.0224301815032959s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 2.86102294921875e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.239776611328125e-05s
INFO | --- Analysis for lexin-rdf took 6.207195520401001s
Availability | SPARQL endpoint availability check for lexinfo took 4.172325134277344e-05s
Availability | VoID file availability check for lexinfo took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for lexinfo took 0.28835296630859375s
Reputation | Calculation of the PageRank for lexinfo took 0.020442485809326172s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.440017700195312e-05s
Believability | Calculation of trust value for lexinfo took 1.0728836059570312e-05s
INFO | --- Analysis for lexinfo took 3.1722218990325928s
Availability | SPARQL endpoint availability check for Lexvo took 8.535385131835938e-05s
Availability | VoID file availability check for Lexvo took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Lexvo took 0.28717732429504395s
Reputation | Calculation of the PageRank for Lexvo took 0.021055936813354492s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00016689300537109375s
Believability | Calculation of trust value for Lexvo took 1.0013580322265625e-05s
INFO | --- Analysis for lexvo took 3.225470781326294s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.076957702636719e-05s
Availability | VoID file availability check for Lexvo.org took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.29747843742370605s
Reputation | Calculation of the PageRank for Lexvo.org took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 6.985664367675781e-05s
Believability | Calculation of trust value for Lexvo.org took 1.0251998901367188e-05s
INFO | --- Analysis for lexvo-org took 2.9032950401306152s
Availability | SPARQL endpoint availability check for LIBRIS took 0.44693517684936523s
Availability | VoID file availability check for LIBRIS took 0.0006222724914550781s
Extra | Recovery of all triples for LIBRIS took 7.25879693031311s
Performance | Total latancy measurement for LIBRIS took 0.7434229850769043s
Amount of data | Number of triples check for LIBRIS took 22.025076389312744s
Interoperability | New terms check for LIBRIS took 38.68353748321533s
Versatility | Languages check for LIBRIS took 0.21749305725097656s
Interpretability | Number of blank nodes check for LIBRIS took 300.0685062408447s
Security | Check HTTPS for LIBRIS took 0.3415255546569824s
Interpretability | RDF structures check for LIBRIS took 0.23829388618469238s
Versatility | Serialization formats check for LIBRIS took 0.21478724479675293s
Availability | RDF dump link check for LIBRIS took 0.13402056694030762s
License | MR license check for LIBRIS took 0.14458084106445312s
License | HR license check for LIBRIS took 0.1861715316772461s
Amount of data | Number of property check for LIBRIS took 0.210601806640625s
Understandability | Number of label check for LIBRIS took 0.21942877769470215s
Understandability | URI regex check for LIBRIS took 0.30027079582214355s
Understandability | Vocabs check for LIBRIS took 0.12706899642944336s
Verifiability | Authors check for LIBRIS took 0.1355886459350586s
Verifiability | Publishers check for LIBRIS took 0.13327288627624512s
Performance | Throughput check for LIBRIS took 10.813410520553589s
Amount of data | Check the number of entities for LIBRIS took 0.00014138221740722656s
Verifiability | Contribs. check for LIBRIS took 0.13447237014770508s
Interlinking | sameAs chians check for LIBRIS took 0.1435537338256836s
Interlinking | skos check for LIBRIS took 0.13832783699035645s
Interlinking | skos check for LIBRIS took 0.14216208457946777s
Timeliness | dataset update frequency check for LIBRIS took 0.13825392723083496s
Currency | Creation date check for LIBRIS took 0.34609007835388184s
Currency | Modification date check for LIBRIS took 0.6313419342041016s
Rep.Conc. | URIs length for LIBRIS took 147.99126410484314s
Interoperability | New vocabularies check for LIBRIS took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.1986551284790039s
Accuracy | Check Functional Property for LIBRIS took 0.20365333557128906s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.1326303482055664s
Accuracy | Check Datatype consistency for LIBRIS took 0.2661552429199219s
Consistency | Disjoint class check for LIBRIS took 0.21421504020690918s
Consistency | Check Misplaced properties for LIBRIS took 60.427605390548706s
Consistency | Misplaced classes for LIBRIS took 1.144946575164795s
Consistency | Check Ontology hijacking for LIBRIS took 3.514925241470337s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.238025188446045s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 61.62658762931824s
Conciseness | Check Extensional conciseness for LIBRIS took 0.27470850944519043s
Conciseness | Check Intensional conciseness for LIBRIS took 0.42284274101257324s
Security | Sign check for LIBRIS took 0.14081668853759766s
Availability | Check URIs Dereferenciability for LIBRIS took 9.513029336929321s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.40940046310424805s
Reputation | Calculation of the PageRank for LIBRIS took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 8.940696716308594e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 9.5367431640625e-07s
Believability | Calculation of trust value for LIBRIS took 7.62939453125e-06s
INFO | --- Analysis for libris took 1150.2346234321594s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06554913520812988s
Availability | VoID file availability check for Public Library of Veroia took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.32435154914855957s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.021283626556396484s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.843971252441406e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.2636184692382812e-05s
INFO | --- Analysis for libver took 3.9321513175964355s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.1311798095703125s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.3394629955291748s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.034706115722656e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 9.059906005859375e-06s
INFO | --- Analysis for lichfield-spending took 3.0077176094055176s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 0.00010037422180175781s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.31685376167297363s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02214956283569336s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.239776611328125e-05s
INFO | --- Analysis for lime took 15.235649108886719s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00011157989501953125s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.4600968360900879s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.30856895446777344s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010752677917480469s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.2159347534179688e-05s
INFO | --- Analysis for lingvoj took 12.946780443191528s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 9.179115295410156e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.2875206470489502s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.43865966796875e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.2874603271484375e-05s
INFO | --- Analysis for linked-crunchbase took 15.082083463668823s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.36739039421081543s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2879753112792969s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.021106243133544922s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.653236389160156e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1444091796875e-05s
INFO | --- Analysis for linked-drugs took 7.3762617111206055s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 0.00010251998901367188s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.2860274314880371s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.083747863769531e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 9.059906005859375e-06s
INFO | --- Analysis for linked-edgar took 4.5088677406311035s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 8.893013000488281e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.288771390914917s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.021542072296142578s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.465217590332031e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.2159347534179688e-05s
INFO | --- Analysis for linked-eurostat took 4.015852212905884s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.482269287109375e-05s
Availability | VoID file availability check for linked hypernyms took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.29955339431762695s
Reputation | Calculation of the PageRank for linked hypernyms took 0.021859407424926758s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 6.937980651855469e-05s
Believability | Calculation of trust value for linked hypernyms took 7.867813110351562e-06s
INFO | --- Analysis for linked-hypernyms took 3.5605781078338623s
Availability | SPARQL endpoint availability check for Linked Life Data took 223.31776881217957s
Availability | VoID file availability check for Linked Life Data took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.8652381896972656s
Reputation | Calculation of the PageRank for Linked Life Data took 0.021366119384765625s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.744529724121094e-05s
Believability | Calculation of trust value for Linked Life Data took 1.1682510375976562e-05s
INFO | --- Analysis for linked-life-data took 689.2727057933807s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.423189640045166s
Availability | VoID file availability check for Linked Logainm took 0.0005457401275634766s
Extra | Recovery of all triples for Linked Logainm took 1.7522387504577637s
Performance | Total latancy measurement for Linked Logainm took 0.5983202457427979s
Amount of data | Number of triples check for Linked Logainm took 0.26171255111694336s
Interoperability | New terms check for Linked Logainm took 1.427325963973999s
Versatility | Languages check for Linked Logainm took 1.351912021636963s
Interpretability | Number of blank nodes check for Linked Logainm took 0.15520715713500977s
Security | Check HTTPS for Linked Logainm took 0.46674680709838867s
Interpretability | RDF structures check for Linked Logainm took 0.25749993324279785s
Versatility | Serialization formats check for Linked Logainm took 0.1560049057006836s
Availability | RDF dump link check for Linked Logainm took 0.1131138801574707s
License | MR license check for Linked Logainm took 0.1280367374420166s
License | HR license check for Linked Logainm took 0.12044811248779297s
Amount of data | Number of property check for Linked Logainm took 0.15168547630310059s
Understandability | Number of label check for Linked Logainm took 0.20089173316955566s
Understandability | URI regex check for Linked Logainm took 0.23056602478027344s
Understandability | Vocabs check for Linked Logainm took 0.11411380767822266s
Verifiability | Authors check for Linked Logainm took 0.14451098442077637s
Verifiability | Publishers check for Linked Logainm took 0.11503386497497559s
Performance | Throughput check for Linked Logainm took 12.248130559921265s
Amount of data | Check the number of entities for Linked Logainm took 7.343292236328125e-05s
Verifiability | Contribs. check for Linked Logainm took 0.11568951606750488s
Interlinking | sameAs chians check for Linked Logainm took 0.20744109153747559s
Interlinking | skos check for Linked Logainm took 0.15630531311035156s
Interlinking | skos check for Linked Logainm took 0.10466599464416504s
Timeliness | dataset update frequency check for Linked Logainm took 0.12250065803527832s
Currency | Creation date check for Linked Logainm took 0.26880955696105957s
Currency | Modification date check for Linked Logainm took 0.26494336128234863s
Rep.Conc. | URIs length for Linked Logainm took 0.8984951972961426s
Interoperability | New vocabularies check for Linked Logainm took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.13407373428344727s
Accuracy | Check Functional Property for Linked Logainm took 0.21899867057800293s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.18155980110168457s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.5172054767608643s
Accuracy | Check White space in annotation for Linked Logainm took 0.024411439895629883s
Accuracy | Check Datatype consistency for Linked Logainm took 0.027643442153930664s
Consistency | Disjoint class check for Linked Logainm took 0.17717933654785156s
Consistency | Check Misplaced properties for Linked Logainm took 0.32233262062072754s
Consistency | Misplaced classes for Linked Logainm took 0.27369213104248047s
Consistency | Check Ontology hijacking for Linked Logainm took 1.7442903518676758s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.2267956733703613s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.806565284729004s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.032051801681518555s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.190643310546875s
Security | Sign check for Linked Logainm took 0.1154325008392334s
Availability | Check URIs Dereferenciability for Linked Logainm took 1090.942087173462s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.4038090705871582s
Reputation | Calculation of the PageRank for Linked Logainm took 0.02140021324157715s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.344650268554688e-05s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 1.1920928955078125e-06s
Believability | Calculation of trust value for Linked Logainm took 1.1444091796875e-05s
INFO | --- Analysis for linked-logainm took 1150.263418674469s
Availability | SPARQL endpoint availability check for Linked NUTS took 8.678436279296875e-05s
Availability | VoID file availability check for Linked NUTS took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.28124189376831055s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020418882369995117s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 4.863739013671875e-05s
Believability | Calculation of trust value for Linked NUTS took 8.821487426757812e-06s
INFO | --- Analysis for linked-nuts took 2.9215071201324463s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.657008409500122s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.299893856048584s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.409385681152344e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 9.059906005859375e-06s
INFO | --- Analysis for linked-open-camera took 4.62107253074646s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.933171033859253s
Availability | VoID file availability check for Linked Open Commerce took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2981104850769043s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.02057194709777832s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 2.8848648071289062e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.3113021850585938e-05s
INFO | --- Analysis for linked-open-commerce took 16.402055025100708s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 0.6082220077514648s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.3244314193725586s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 9.775161743164062e-05s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.3113021850585938e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 3.5750207901000977s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 8.678436279296875e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.3486800193786621s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.02199411392211914s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.58306884765625e-05s
Believability | Calculation of trust value for Linked Open Numbers took 1.33514404296875e-05s
INFO | --- Analysis for linked-open-numbers took 3.232783079147339s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 8.940696716308594e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.3210489749908447s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020813941955566406s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.123283386230469e-05s
Believability | Calculation of trust value for Linked Open Piracy took 9.5367431640625e-06s
INFO | --- Analysis for linked-open-piracy took 7.607456684112549s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 1.802137851715088s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0012745857238769531s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 56.58852171897888s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 1.1420960426330566s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 1.8313171863555908s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 2.0734078884124756s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 12.933895349502563s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 1.6210145950317383s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 0.25443601608276367s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 0.21761035919189453s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 0.9027962684631348s
License | MR license check for Linked Open Vocabularies (LOV) took 0.1915135383605957s
License | HR license check for Linked Open Vocabularies (LOV) took 44.74421262741089s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 0.32311582565307617s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 0.7202069759368896s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 0.4344449043273926s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 0.20151019096374512s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 0.21326375007629395s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 0.21797609329223633s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 11.447352886199951s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 0.9503653049468994s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 0.2183232307434082s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 0.21480917930603027s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.19667863845825195s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.1968066692352295s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 0.196014404296875s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 1.380549669265747s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 0.20292973518371582s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 23.270344495773315s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 14.934877395629883s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 0.25713372230529785s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 0.19250941276550293s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.18416762351989746s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 6.341994285583496s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6806998252868652s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.747177839279175s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 0.3890085220336914s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 6.768534183502197s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 0.22333335876464844s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 5.988605737686157s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.3825881481170654s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.820544481277466s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 2.896467685699463s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.42121243476867676s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 5596.397111654282s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.6702141761779785s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.02193593978881836s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 6.937980651855469e-05s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 17.780322551727295s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 6601.729516506195s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 8.7738037109375e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.30562400817871094s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.021109580993652344s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 4.315376281738281e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 9.5367431640625e-06s
INFO | --- Analysis for linked-periodicals took 2.876157760620117s
Availability | SPARQL endpoint availability check for Linked Index took 8.869171142578125e-05s
Availability | VoID file availability check for Linked Index took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for Linked Index took 0.29039430618286133s
Reputation | Calculation of the PageRank for Linked Index took 0.02088785171508789s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Linked Index took 7.891654968261719e-05s
Believability | Calculation of trust value for Linked Index took 1.0967254638671875e-05s
INFO | --- Analysis for linked-stockindex took 3.500688314437866s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 6.326594591140747s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.28946781158447266s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.7670135498046875e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.1682510375976562e-05s
INFO | --- Analysis for linked-structured-product-labels took 21.096303462982178s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.31923818588256836s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.26857542991638184s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.3828277587890625e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 3.084961175918579s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.211597204208374s
Availability | VoID file availability check for Linked TCGA took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.29001879692077637s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02093219757080078s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.036064147949219e-05s
Believability | Calculation of trust value for Linked TCGA took 1.0251998901367188e-05s
INFO | --- Analysis for linked-tcga took 63.20448613166809s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.09140133857727051s
Availability | VoID file availability check for Linked User Feedback took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.3194594383239746s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.743171691894531e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.1444091796875e-05s
INFO | --- Analysis for linked-user-feedback took 2.8492419719696045s
Availability | SPARQL endpoint availability check for USPTO Patent data took 0.0001266002655029297s
Availability | VoID file availability check for USPTO Patent data took 0.0013654232025146484s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.32675838470458984s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.02236151695251465s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 8.130073547363281e-05s
Believability | Calculation of trust value for USPTO Patent data took 1.2636184692382812e-05s
INFO | --- Analysis for linked-uspto-patent-data took 53.613123655319214s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.19704222679138184s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.29653215408325195s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.022289514541625977s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.361701965332031e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.1682510375976562e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 3.2525014877319336s
Availability | SPARQL endpoint availability check for LinkedCT took 1.371885061264038s
Availability | VoID file availability check for LinkedCT took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.3329601287841797s
Reputation | Calculation of the PageRank for LinkedCT took 0.0211331844329834s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00010037422180175781s
Believability | Calculation of trust value for LinkedCT took 1.0251998901367188e-05s
INFO | --- Analysis for linkedct took 5.1893603801727295s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.15317130088806152s
Availability | VoID file availability check for LinkedGeoData took 0.0008764266967773438s
Extra | Recovery of all triples for LinkedGeoData took 6.671842813491821s
Performance | Total latancy measurement for LinkedGeoData took 0.6506993770599365s
Amount of data | Number of triples check for LinkedGeoData took 53.41665244102478s
Interoperability | New terms check for LinkedGeoData took 90.73187685012817s
Versatility | Languages check for LinkedGeoData took 180.37478113174438s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.20475530624389648s
Security | Check HTTPS for LinkedGeoData took 0.3096179962158203s
Interpretability | RDF structures check for LinkedGeoData took 0.1545250415802002s
Versatility | Serialization formats check for LinkedGeoData took 0.1412496566772461s
Availability | RDF dump link check for LinkedGeoData took 0.12320852279663086s
License | MR license check for LinkedGeoData took 0.12464332580566406s
License | HR license check for LinkedGeoData took 90.21737623214722s
Amount of data | Number of property check for LinkedGeoData took 0.15963959693908691s
Understandability | Number of label check for LinkedGeoData took 0.9812445640563965s
Understandability | URI regex check for LinkedGeoData took 0.2826263904571533s
Understandability | Vocabs check for LinkedGeoData took 0.13866209983825684s
Verifiability | Authors check for LinkedGeoData took 0.11831521987915039s
Verifiability | Publishers check for LinkedGeoData took 0.13009023666381836s
Performance | Throughput check for LinkedGeoData took 10.527964115142822s
Amount of data | Check the number of entities for LinkedGeoData took 0.0657491683959961s
Verifiability | Contribs. check for LinkedGeoData took 0.1386711597442627s
Interlinking | sameAs chians check for LinkedGeoData took 0.18413281440734863s
Interlinking | skos check for LinkedGeoData took 0.14884400367736816s
Interlinking | skos check for LinkedGeoData took 0.12188124656677246s
Timeliness | dataset update frequency check for LinkedGeoData took 0.11350798606872559s
Currency | Creation date check for LinkedGeoData took 0.28448915481567383s
Currency | Modification date check for LinkedGeoData took 0.26639366149902344s
Rep.Conc. | URIs length for LinkedGeoData took 272.5206582546234s
Interoperability | New vocabularies check for LinkedGeoData took 13.56103777885437s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.15142512321472168s
Accuracy | Check Functional Property for LinkedGeoData took 0.15094280242919922s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.12621617317199707s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.6494965553283691s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15794014930725098s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13643455505371094s
Consistency | Disjoint class check for LinkedGeoData took 0.13787198066711426s
Consistency | Check Misplaced properties for LinkedGeoData took 180.98074984550476s
Consistency | Misplaced classes for LinkedGeoData took 0.6328315734863281s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.5152735710144043s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.2913007736206055s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 181.68941235542297s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.1517486572265625s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.2994048595428467s
Security | Sign check for LinkedGeoData took 0.15375995635986328s
Availability | Check URIs Dereferenciability for LinkedGeoData took 11.176605939865112s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.5834708213806152s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021082401275634766s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 6.246566772460938e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00014209747314453125s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 13.170989513397217s
Believability | Calculation of trust value for LinkedGeoData took 1.1682510375976562e-05s
INFO | --- Analysis for linkedgeodata took 2310.1141381263733s
Availability | SPARQL endpoint availability check for LinkedLCCN took 0.9587459564208984s
Availability | VoID file availability check for LinkedLCCN took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.29735541343688965s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 9.894371032714844e-05s
Believability | Calculation of trust value for LinkedLCCN took 1.2636184692382812e-05s
INFO | --- Analysis for linkedlccn took 17.794880390167236s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 8.440017700195312e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.2962512969970703s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.021181583404541016s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.4332275390625e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.1682510375976562e-05s
INFO | --- Analysis for linkedmarkmail took 2.9019200801849365s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.5843448638916s
Availability | VoID file availability check for Linked Movie DataBase took 0.0007414817810058594s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.32237911224365234s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.021478652954101562s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00014257431030273438s
Believability | Calculation of trust value for Linked Movie DataBase took 1.1920928955078125e-05s
INFO | --- Analysis for linkedmdb took 133.58776473999023s
Availability | SPARQL endpoint availability check for LinkedSpending took 0.510117769241333s
Availability | VoID file availability check for LinkedSpending took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for LinkedSpending took 0.3344149589538574s
Reputation | Calculation of the PageRank for LinkedSpending took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for LinkedSpending took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LinkedSpending took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for LinkedSpending took 6.937980651855469e-05s
Believability | Calculation of trust value for LinkedSpending took 1.0251998901367188e-05s
INFO | --- Analysis for linkedspending took 4.36756443977356s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.07292366027832031s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.324718713760376s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02160811424255371s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00011229515075683594s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.2159347534179688e-05s
INFO | --- Analysis for linklion took 2.940443992614746s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 600.4345965385437s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.3132002353668213s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 7.05718994140625e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.316734313964844e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 1214.9878075122833s
Availability | SPARQL endpoint availability check for lobid-organisations took 0.9353034496307373s
Availability | VoID file availability check for lobid-organisations took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.30933094024658203s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.107589721679688e-05s
Believability | Calculation of trust value for lobid-organisations took 7.62939453125e-06s
INFO | --- Analysis for lobid-organisations took 5.773764133453369s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.7378072738647461s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.28890347480773926s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010228157043457031s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.2874603271484375e-05s
INFO | --- Analysis for lobid-resources took 7.345780849456787s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.649162292480469e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.28848838806152344s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.02048492431640625s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 6.937980651855469e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.2874603271484375e-05s
INFO | --- Analysis for loc took 7.454568862915039s
Availability | SPARQL endpoint availability check for Location Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Location Ontology took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.266538143157959s
Reputation | Calculation of the PageRank for Location Ontology took 0.02097320556640625s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for Location Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Location_Ontology took 4.047194480895996s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 8.893013000488281e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.27724170684814453s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020743846893310547s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 4.076957702636719e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 7.3909759521484375e-06s
INFO | --- Analysis for locv took 34.24045372009277s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.72438645362854s
Availability | VoID file availability check for LOD-a-lot took 0.0008492469787597656s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.301084041595459s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 2.9087066650390625e-05s
Believability | Calculation of trust value for LOD-a-lot took 5.0067901611328125e-06s
INFO | --- Analysis for lod-a-lot took 14.173075914382935s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 8.749961853027344e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2782289981842041s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020870447158813477s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.678436279296875e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.239776611328125e-05s
INFO | --- Analysis for lod2-project-wiki took 3.9604623317718506s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.622973918914795s
Availability | VoID file availability check for LODAC BDLS took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.30376625061035156s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 6.771087646484375e-05s
Believability | Calculation of trust value for LODAC BDLS took 9.5367431640625e-06s
INFO | --- Analysis for lodac-bdls took 13.871427774429321s
Availability | SPARQL endpoint availability check for lofd took 0.1292867660522461s
Availability | VoID file availability check for lofd took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for lofd took 0.30794572830200195s
Reputation | Calculation of the PageRank for lofd took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for lofd took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lofd took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for lofd took 2.956390380859375e-05s
Believability | Calculation of trust value for lofd took 1.239776611328125e-05s
INFO | --- Analysis for lofd took 2.796023368835449s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.7667167186737s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.2906327247619629s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.02074909210205078s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 2.8371810913085938e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 4.9591064453125e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 1.0013580322265625e-05s
INFO | --- Analysis for loius took 585.8769221305847s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.6786730289459229s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.2961132526397705s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.626678466796875e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.0067901611328125e-06s
INFO | --- Analysis for london-gazette took 4.238556146621704s
Availability | SPARQL endpoint availability check for Weather Stations took 9.369850158691406e-05s
Availability | VoID file availability check for Weather Stations took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.29821157455444336s
Reputation | Calculation of the PageRank for Weather Stations took 0.022477149963378906s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0009560585021972656s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 9.369850158691406e-05s
Believability | Calculation of trust value for Weather Stations took 1.2159347534179688e-05s
INFO | --- Analysis for los_metar took 9.333348751068115s
Availability | SPARQL endpoint availability check for Lotico took 0.5688540935516357s
Availability | VoID file availability check for Lotico took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for Lotico took 0.28796958923339844s
Reputation | Calculation of the PageRank for Lotico took 0.02081465721130371s
Interlinking | Calculation of Degree of Connection for Lotico took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lotico took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.368492126464844e-05s
Believability | Calculation of trust value for Lotico took 1.3113021850585938e-05s
INFO | --- Analysis for lotico took 4.855072021484375s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.30802130699157715s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0006062984466552734s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.7549707889556885s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.90677809715271s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.21590161323547363s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.5636789798736572s
Versatility | Languages check for Lower Layer Super Output Areas took 0.4052548408508301s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.183286428451538s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.11418008804321289s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.20213699340820312s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.21221399307250977s
Availability | RDF dump link check for Lower Layer Super Output Areas took 62.58544588088989s
License | MR license check for Lower Layer Super Output Areas took 0.15099740028381348s
License | HR license check for Lower Layer Super Output Areas took 30.23566746711731s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.16228485107421875s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.2114553451538086s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.6427621841430664s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.1970961093902588s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.21407246589660645s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.20704913139343262s
Performance | Throughput check for Lower Layer Super Output Areas took 11.387587785720825s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 3.123283386230469e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.6426191329956055s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.13745522499084473s
Interlinking | skos check for Lower Layer Super Output Areas took 0.1389014720916748s
Interlinking | skos check for Lower Layer Super Output Areas took 0.11896634101867676s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.14628839492797852s
Currency | Creation date check for Lower Layer Super Output Areas took 0.3578770160675049s
Currency | Modification date check for Lower Layer Super Output Areas took 0.1349031925201416s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.7198283672332764s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.13888931274414062s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.19993901252746582s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.13319897651672363s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.19809246063232422s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 1.3892319202423096s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 1.0977015495300293s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.5031657218933105s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.00016689300537109375s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.45038890838623047s
Security | Sign check for Lower Layer Super Output Areas took 0.12432479858398438s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.2903616428375244s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.886222839355469e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 9.5367431640625e-07s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.1444091796875e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 280.69334626197815s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5272703170776367s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.00048470497131347656s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 108.22195529937744s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9553537368774414s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.34148120880127s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.147401332855225s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.25792932510376s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.383946180343628s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.34510064125061035s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.317599534988403s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.41341328620910645s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.782355785369873s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.24346113204956s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2173168659210205s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.924597978591919s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1812844276428223s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.628570556640625s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23207616806030273s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.25873589515686035s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.100405216217041s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 6.842613220214844e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2173442840576172s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19307184219360352s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5051515102386475s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.41851377487182617s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.1885669231414795s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.49809861183166504s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23085260391235352s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 160.5851011276245s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21666169166564941s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5145540237426758s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5300586223602295s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 31.799007415771484s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.652141809463501s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.551487684249878s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.17789435386657715s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 86.71634602546692s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.342283964157104s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 30.09541130065918s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3756403923034668s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 87.52233695983887s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.707019567489624s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5473151206970215s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.5289788246154785s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.15087103843689s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5191001892089844s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.021313190460205078s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for LPIS_(Poland) took 2270.7964346408844s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19667553901672363s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0006339550018310547s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 120.1548535823822s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0025737285614014s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.22326111793518s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.02151894569397s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.25200486183167s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.8365287780761719s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1837296485900879s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.113550662994385s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3959767818450928s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21157193183898926s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2461724281311s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21432876586914062s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3021247386932373s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.39298343658447266s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21267437934875488s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.17997121810913086s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.26416444778442383s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.102668762207031s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.630752563476562e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18117833137512207s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18559622764587402s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.47928619384765625s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.43296217918395996s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.367242813110352s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5218734741210938s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.23699212074279785s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 155.56788516044617s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19262170791625977s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1817619800567627s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21369004249572754s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 37.88744378089905s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6515262126922607s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6241817474365234s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2583179473876953s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 85.92302584648132s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.287840604782104s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 40.222392320632935s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3172380924224854s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.83570098876953s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7478091716766357s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.6020767688751221s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1829681396484375s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.03605580329895s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5372858047485352s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.02146601676940918s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.5299530029296875e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2281.877381801605s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.291534423828125e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.2930750846862793s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 2.6941299438476562e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.3113021850585938e-05s
INFO | --- Analysis for lremap-auth took 3.323160409927368s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.267692565917969e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.27605676651000977s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0009469985961914062s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.1948089599609375e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.1682510375976562e-05s
INFO | --- Analysis for lremap-conf took 2.850447177886963s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 9.608268737792969e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.299959659576416s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020512104034423828s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 2.7179718017578125e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.2636184692382812e-05s
INFO | --- Analysis for lremap-ri took 2.9250545501708984s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 8.940696716308594e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.2865457534790039s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 2.8371810913085938e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.0728836059570312e-05s
INFO | --- Analysis for lremap-sub took 2.8720810413360596s
Availability | SPARQL endpoint availability check for LSQ took 4.458427429199219e-05s
Availability | VoID file availability check for LSQ took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for LSQ took 0.28807950019836426s
Reputation | Calculation of the PageRank for LSQ took 0.02174973487854004s
Interlinking | Calculation of Degree of Connection for LSQ took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LSQ took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.6941299438476562e-05s
Believability | Calculation of trust value for LSQ took 1.2159347534179688e-05s
INFO | --- Analysis for lsq took 3.841733932495117s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6123104095458984s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.30242395401000977s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for LucaniPharsalia took 4.368605136871338s
Availability | SPARQL endpoint availability check for Linked rules took 9.1552734375e-05s
Availability | VoID file availability check for Linked rules took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2857332229614258s
Reputation | Calculation of the PageRank for Linked rules took 0.021162748336791992s
Interlinking | Calculation of Degree of Connection for Linked rules took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked rules took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Linked rules took 2.8848648071289062e-05s
Believability | Calculation of trust value for Linked rules took 1.2159347534179688e-05s
INFO | --- Analysis for Luminaires_senlis took 2.647423505783081s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.131579637527466s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.295274019241333s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 2.7894973754882812e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for makg took 63.499464988708496s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.220008850097656e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.3131554126739502s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.02090930938720703s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.647804260253906e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 6.198883056640625e-06s
INFO | --- Analysis for manchester-university-reading-lists took 5.307888984680176s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 0.00010943412780761719s
Availability | VoID file availability check for engineering equipment ontology took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.3028414249420166s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.022345304489135742s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for engineering equipment ontology took 9.775161743164062e-06s
INFO | --- Analysis for manish took 2.592965841293335s
Availability | SPARQL endpoint availability check for MARC Codes List took 8.940696716308594e-05s
Availability | VoID file availability check for MARC Codes List took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.29187822341918945s
Reputation | Calculation of the PageRank for MARC Codes List took 0.021924257278442383s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.0001201629638671875s
Believability | Calculation of trust value for MARC Codes List took 1.33514404296875e-05s
INFO | --- Analysis for marc-codes took 14.866601943969727s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 8.58306884765625e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.29693174362182617s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.886222839355469e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.5020370483398438e-05s
INFO | --- Analysis for masc took 6.1925835609436035s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.363059997558594e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.3532283306121826s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.02073359489440918s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.695487976074219e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.3113021850585938e-05s
INFO | --- Analysis for masc-bn-nif took 2.7989490032196045s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.1387345790863037s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.2945261001586914s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.021050691604614258s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.765655517578125e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 1.239776611328125e-05s
INFO | --- Analysis for massobservationarchivecatalogue took 3.9309909343719482s
Availability | SPARQL endpoint availability check for medline took 8.559226989746094e-05s
Availability | VoID file availability check for medline took 0.00037479400634765625s
Completeness | Calculation of interlinking completeness for medline took 0.2910032272338867s
Reputation | Calculation of the PageRank for medline took 0.021302461624145508s
Interlinking | Calculation of Degree of Connection for medline took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for medline took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for medline took 3.4332275390625e-05s
Believability | Calculation of trust value for medline took 1.2874603271484375e-05s
INFO | --- Analysis for medline took 8.799584865570068s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.8268053531646729s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.3056659698486328s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.437301635742188e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.1444091796875e-05s
INFO | --- Analysis for meducator took 14.26411509513855s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 0.00012826919555664062s
Availability | VoID file availability check for MetaShare metadata model took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.30387067794799805s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.022466182708740234s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 6.747245788574219e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.1920928955078125e-05s
INFO | --- Analysis for metashare took 2.646352767944336s
Availability | SPARQL endpoint availability check for MExiCo took 4.1961669921875e-05s
Availability | VoID file availability check for MExiCo took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for MExiCo took 0.2793748378753662s
Reputation | Calculation of the PageRank for MExiCo took 0.020558595657348633s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.267692565917969e-05s
Believability | Calculation of trust value for MExiCo took 1.1920928955078125e-05s
INFO | --- Analysis for mexico took 22.748682260513306s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.0256850719451904s
Availability | VoID file availability check for Coronavirus dataset took 0.00037169456481933594s
Extra | Recovery of all triples for Coronavirus dataset took 6.053750038146973s
Performance | Total latancy measurement for Coronavirus dataset took 2.4680335521698s
Amount of data | Number of triples check for Coronavirus dataset took 1.1821367740631104s
Interoperability | New terms check for Coronavirus dataset took 2.5853288173675537s
Versatility | Languages check for Coronavirus dataset took 60.50955557823181s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.847564458847046s
Interpretability | RDF structures check for Coronavirus dataset took 0.5546953678131104s
Versatility | Serialization formats check for Coronavirus dataset took 0.5493652820587158s
Availability | RDF dump link check for Coronavirus dataset took 0.4901297092437744s
License | MR license check for Coronavirus dataset took 0.5539286136627197s
License | HR license check for Coronavirus dataset took 42.86685585975647s
Amount of data | Number of property check for Coronavirus dataset took 0.5390872955322266s
Understandability | Number of label check for Coronavirus dataset took 1.3875608444213867s
Understandability | URI regex check for Coronavirus dataset took 0.9927325248718262s
Understandability | Vocabs check for Coronavirus dataset took 0.49793219566345215s
Verifiability | Authors check for Coronavirus dataset took 0.5474631786346436s
Verifiability | Publishers check for Coronavirus dataset took 0.4959697723388672s
Performance | Throughput check for Coronavirus dataset took 14.204529285430908s
Amount of data | Check the number of entities for Coronavirus dataset took 7.200241088867188e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.48749876022338867s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5430014133453369s
Interlinking | skos check for Coronavirus dataset took 0.529296875s
Interlinking | skos check for Coronavirus dataset took 0.49988532066345215s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5045385360717773s
Currency | Creation date check for Coronavirus dataset took 1.0150172710418701s
Currency | Modification date check for Coronavirus dataset took 1.0134644508361816s
Rep.Conc. | URIs length for Coronavirus dataset took 8.292094945907593s
Interoperability | New vocabularies check for Coronavirus dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5159077644348145s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7187256813049316s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.736473560333252s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.112459182739258s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022237062454223633s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.027583837509155273s
Consistency | Disjoint class check for Coronavirus dataset took 1.0225098133087158s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.465235710144043s
Consistency | Misplaced classes for Coronavirus dataset took 0.6198413372039795s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.429203987121582s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.273646593093872s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 7.06474232673645s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03212761878967285s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5363175868988037s
Security | Sign check for Coronavirus dataset took 0.5366065502166748s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3128.1985533237457s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.7601263523101807s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021386146545410156s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 0.00011038780212402344s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.33514404296875e-05s
INFO | --- Analysis for micro-coronavirus took 3364.4095525741577s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0001201629638671875s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.3309648036956787s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010347366333007812s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.775161743164062e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 5.5241639614105225s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 8.893013000488281e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.3121664524078369s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.021010637283325195s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011277198791503906s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.0013580322265625e-05s
INFO | --- Analysis for mismuseos-gnoss took 5.111975431442261s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.09771227836608887s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.28870463371276855s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.022125959396362305s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.887580871582031e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.2874603271484375e-05s
INFO | --- Analysis for mlsa took 3.1848561763763428s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.506111145019531e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.30117154121398926s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.647804260253906e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 1.3113021850585938e-05s
INFO | --- Analysis for model took 40.48632597923279s
Availability | SPARQL endpoint availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 4.363059997558594e-05s
Availability | VoID file availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.29174304008483887s
Reputation | Calculation of the PageRank for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.021055936813354492s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 3.123283386230469e-05s
Believability | Calculation of trust value for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.239776611328125e-05s
INFO | --- Analysis for model1 took 26.077388763427734s
Availability | SPARQL endpoint availability check for MORElab took 1.0587518215179443s
Availability | VoID file availability check for MORElab took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for MORElab took 0.29868149757385254s
Reputation | Calculation of the PageRank for MORElab took 0.02086019515991211s
Interlinking | Calculation of Degree of Connection for MORElab took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MORElab took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for MORElab took 9.846687316894531e-05s
Believability | Calculation of trust value for MORElab took 1.2159347534179688e-05s
INFO | --- Analysis for morelab took 5.096858263015747s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 2.1027791500091553s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0008134841918945312s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.28775620460510254s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.022432565689086914s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.797645568847656e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.049041748046875e-05s
INFO | --- Analysis for msc took 16.984110355377197s
Availability | SPARQL endpoint availability check for Multext-East took 4.673004150390625e-05s
Availability | VoID file availability check for Multext-East took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Multext-East took 0.28508734703063965s
Reputation | Calculation of the PageRank for Multext-East took 0.021543264389038086s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Multext-East took 4.935264587402344e-05s
Believability | Calculation of trust value for Multext-East took 1.33514404296875e-05s
INFO | --- Analysis for multext-east took 2.6069250106811523s
Availability | SPARQL endpoint availability check for Multimedia Lab took 8.749961853027344e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.2899513244628906s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.021107196807861328s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.337860107421875e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.1205673217773438e-05s
INFO | --- Analysis for multimedia-lab took 2.723437786102295s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.702988862991333s
Availability | VoID file availability check for Muninn World War I took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.29941296577453613s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.058547973632812e-05s
Believability | Calculation of trust value for Muninn World War I took 1.1444091796875e-05s
INFO | --- Analysis for muninn-world-war-i took 11.228385925292969s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 8.726119995117188e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.30093908309936523s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.02109670639038086s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011181831359863281s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.3113021850585938e-05s
INFO | --- Analysis for museosespania-gnoss took 72.48820066452026s
Availability | SPARQL endpoint availability check for Italian Museums took 1.864698886871338s
Availability | VoID file availability check for Italian Museums took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.2823662757873535s
Reputation | Calculation of the PageRank for Italian Museums took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 7.62939453125e-05s
Believability | Calculation of trust value for Italian Museums took 5.245208740234375e-06s
INFO | --- Analysis for museums-in-italy took 4.525334596633911s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7622189521789551s
Availability | VoID file availability check for Muziekweb took 0.0006499290466308594s
Extra | Recovery of all triples for Muziekweb took 1.4454855918884277s
Performance | Total latancy measurement for Muziekweb took 1.6257905960083008s
Amount of data | Number of triples check for Muziekweb took 0.40563368797302246s
Interoperability | New terms check for Muziekweb took 1.6632163524627686s
Versatility | Languages check for Muziekweb took 54.48421907424927s
Interpretability | Number of blank nodes check for Muziekweb took 0.33716368675231934s
Interpretability | RDF structures check for Muziekweb took 0.7929220199584961s
Versatility | Serialization formats check for Muziekweb took 0.32384800910949707s
Availability | RDF dump link check for Muziekweb took 0.30380892753601074s
License | MR license check for Muziekweb took 0.34786128997802734s
License | HR license check for Muziekweb took 11.42597770690918s
Amount of data | Number of property check for Muziekweb took 0.3374514579772949s
Understandability | Number of label check for Muziekweb took 0.41895031929016113s
Understandability | URI regex check for Muziekweb took 0.6114060878753662s
Understandability | Vocabs check for Muziekweb took 0.3117544651031494s
Verifiability | Authors check for Muziekweb took 0.33861660957336426s
Verifiability | Publishers check for Muziekweb took 0.33235621452331543s
Performance | Throughput check for Muziekweb took 12.160760164260864s
Amount of data | Check the number of entities for Muziekweb took 6.818771362304688e-05s
Verifiability | Contribs. check for Muziekweb took 0.3302903175354004s
Interlinking | sameAs chians check for Muziekweb took 0.3243367671966553s
Interlinking | skos check for Muziekweb took 0.4153594970703125s
Interlinking | skos check for Muziekweb took 0.3155539035797119s
Timeliness | dataset update frequency check for Muziekweb took 0.3403892517089844s
Currency | Creation date check for Muziekweb took 0.8850119113922119s
Currency | Modification date check for Muziekweb took 0.9701817035675049s
Rep.Conc. | URIs length for Muziekweb took 1.8862462043762207s
Interoperability | New vocabularies check for Muziekweb took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.3192911148071289s
Accuracy | Check Empty annotation labels for Muziekweb took 0.9015111923217773s
Accuracy | Check White space in annotation for Muziekweb took 0.027491331100463867s
Accuracy | Check Datatype consistency for Muziekweb took 0.028420209884643555s
Consistency | Disjoint class check for Muziekweb took 0.5447952747344971s
Consistency | Check Misplaced properties for Muziekweb took 1.179276466369629s
Consistency | Check Ontology hijacking for Muziekweb took 2.0872139930725098s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.2248508930206299s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.6655247211456299s
Conciseness | Check Extensional conciseness for Muziekweb took 0.033031463623046875s
Conciseness | Check Intensional conciseness for Muziekweb took 0.32232093811035156s
Security | Sign check for Muziekweb took 0.3054232597351074s
Availability | Check URIs Dereferenciability for Muziekweb took 2073.6230883598328s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.5127213001251221s
Reputation | Calculation of the PageRank for Muziekweb took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for Muziekweb took 7.319450378417969e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 0.00010657310485839844s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.9073486328125e-06s
Believability | Calculation of trust value for Muziekweb took 1.2636184692382812e-05s
INFO | --- Analysis for muziekweb took 2202.629103422165s
Availability | SPARQL endpoint availability check for myExperiment took 0.6245207786560059s
Availability | VoID file availability check for myExperiment took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for myExperiment took 0.2803316116333008s
Reputation | Calculation of the PageRank for myExperiment took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for myExperiment took 9.608268737792969e-05s
Believability | Calculation of trust value for myExperiment took 1.2159347534179688e-05s
INFO | --- Analysis for my-experiment took 4.633474826812744s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.06726646423339844s
Availability | VoID file availability check for My Family Lineage took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.2984011173248291s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020784378051757812s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.440017700195312e-05s
Believability | Calculation of trust value for My Family Lineage took 1.049041748046875e-05s
INFO | --- Analysis for my-family-lineage took 3.890738010406494s
Availability | SPARQL endpoint availability check for My ontology test took 1.1580424308776855s
Availability | VoID file availability check for My ontology test took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for My ontology test took 0.28742074966430664s
Reputation | Calculation of the PageRank for My ontology test took 0.022383451461791992s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for My ontology test took 2.9325485229492188e-05s
Believability | Calculation of trust value for My ontology test took 1.0251998901367188e-05s
INFO | --- Analysis for myontologytest took 3.853105068206787s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 8.916854858398438e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.2769627571105957s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 9.822845458984375e-05s
Believability | Calculation of trust value for myopenlink dataspaces took 1.049041748046875e-05s
INFO | --- Analysis for myopenlink-dataspaces took 3.177072286605835s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 8.378113031387329s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.2755320072174072s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.604194641113281e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for n-lex-as-linked-data took 21.43921732902527s
Availability | SPARQL endpoint availability check for NAICS 2007 took 26.20562243461609s
Availability | VoID file availability check for NAICS 2007 took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.293165922164917s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 3.6716461181640625e-05s
Believability | Calculation of trust value for NAICS 2007 took 9.298324584960938e-06s
INFO | --- Analysis for naics-2007 took 124.83347249031067s
Availability | SPARQL endpoint availability check for NAICS 2012 took 26.02089262008667s
Availability | VoID file availability check for NAICS 2012 took 0.0007543563842773438s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.2836728096008301s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.020937204360961914s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.435943603515625e-05s
Believability | Calculation of trust value for NAICS 2012 took 9.059906005859375e-06s
INFO | --- Analysis for naics-2012 took 124.43528628349304s
Availability | SPARQL endpoint availability check for Usernames  took 4.220008850097656e-05s
Availability | VoID file availability check for Usernames  took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Usernames  took 0.28753137588500977s
Reputation | Calculation of the PageRank for Usernames  took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.5762786865234375e-05s
Believability | Calculation of trust value for Usernames  took 1.1920928955078125e-05s
INFO | --- Analysis for Names took 2.878811836242676s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.1814980506896973s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0011937618255615234s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 0.9472653865814209s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 4.189523220062256s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.603579998016357s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 14.4368314743042s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.31416988372802734s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.824690341949463s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.3012814521789551s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.7643358707427979s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.780555009841919s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.32168006896972656s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.773547887802124s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.72400903701782s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.824347734451294s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.574120283126831s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.7257418632507324s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.3369154930114746s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.7778325080871582s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.8313109874725342s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.117904663085938s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.678436279296875e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.7817103862762451s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.45178818702697754s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 2.079277515411377s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.0118887424468994s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.32760024070739746s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.0125691890716553s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7237043380737305s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.844735860824585s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.3271961212158203s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.32235097885131836s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.33688783645629883s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.3397080898284912s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007317066192626953s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.001062154769897461s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.8202176094055176s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.6662535667419434s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3549351692199707s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.654205083847046s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.2852120399475098s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.6145803928375244s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.000698089599609375s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.3204684257507324s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 5.090418815612793s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.3026747703552246s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.437301635742188e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 8.821487426757812e-06s
INFO | --- Analysis for national-diet-library-authorities took 236.4840793609619s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.3324735164642334s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006196498870849609s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.3985753059387207s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 3.286064863204956s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.513412237167358s
Interoperability | New terms check for National Diet Library of Japan subject headings took 22.275967121124268s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.3621847629547119s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.333252429962158s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.3037850856781006s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.3260066509246826s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.3541128635406494s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.3490912914276123s
License | MR license check for National Diet Library of Japan subject headings took 0.780362606048584s
License | HR license check for National Diet Library of Japan subject headings took 91.75114631652832s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8337082862854004s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.326139450073242s
Understandability | URI regex check for National Diet Library of Japan subject headings took 1.1107041835784912s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.8188385963439941s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3386240005493164s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.8144502639770508s
Performance | Throughput check for National Diet Library of Japan subject headings took 13.01390290260315s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.7738037109375e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.7772750854492188s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.42471957206726074s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.3040847778320312s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.0348913669586182s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.36342549324035645s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.4338288307189941s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.6591427326202393s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.6476461887359619s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.3272745609283447s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.8035843372344971s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.8214294910430908s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.596311092376709s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007174015045166016s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010881423950195312s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.3390378952026367s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.6449120044708252s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.33221983909606934s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.6031358242034912s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.2465064525604248s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.5629870891571045s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006465911865234375s
Security | Sign check for National Diet Library of Japan subject headings took 0.33678507804870605s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 5.27548623085022s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.38733911514282227s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.52587890625e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 1.0728836059570312e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 238.89905905723572s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.1053402423858643s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.001386404037475586s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.29039883613586426s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.553794860839844e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 1.1920928955078125e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 5.7303307056427s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.267692565917969e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2876896858215332s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020878076553344727s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.604194641113281e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.4066696166992188e-05s
INFO | --- Analysis for Naturopathy took 3.7240335941314697s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.3921778202056885s
Availability | VoID file availability check for COVID-19 Data took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.2785956859588623s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.02241230010986328s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 2.7179718017578125e-05s
Believability | Calculation of trust value for COVID-19 Data took 1.1444091796875e-05s
INFO | --- Analysis for NCMI-COVID-19 took 7.440297603607178s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.4082159996032715s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.2878291606903076s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020780086517333984s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.2636184692382812e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 1.1920928955078125e-05s
INFO | --- Analysis for NCMICOVID-19 took 6.450612783432007s
Availability | SPARQL endpoint availability check for Near took 0.00010704994201660156s
Availability | VoID file availability check for Near took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for Near took 0.27906250953674316s
Reputation | Calculation of the PageRank for Near took 0.021217823028564453s
Interlinking | Calculation of Degree of Connection for Near took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Near took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Near took 9.179115295410156e-05s
Believability | Calculation of trust value for Near took 1.1682510375976562e-05s
INFO | --- Analysis for near took 9.93145203590393s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 8.797645568847656e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.3015162944793701s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.02195000648498535s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 2.9802322387695312e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.2159347534179688e-05s
INFO | --- Analysis for neurolex-wiki took 2.6393377780914307s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 8.392333984375e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.29279065132141113s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.022059202194213867s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.3392181396484375e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.2159347534179688e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 4.756494045257568s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 0.00022220611572265625s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.27810192108154297s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.021227598190307617s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.866455078125e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.1444091796875e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.269098520278931s
Availability | SPARQL endpoint availability check for neXtProt took 1.7485089302062988s
Availability | VoID file availability check for neXtProt took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for neXtProt took 0.2760889530181885s
Reputation | Calculation of the PageRank for neXtProt took 0.02250194549560547s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.814697265625e-05s
Believability | Calculation of trust value for neXtProt took 1.3113021850585938e-05s
INFO | --- Analysis for nextprot took 5.021186590194702s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 8.726119995117188e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.48945045471191406s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.022118568420410156s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 3.4332275390625e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00011491775512695312s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1205673217773438e-05s
INFO | --- Analysis for nextweb-gnoss took 212.31248092651367s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 8.606910705566406e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.2884500026702881s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.02112412452697754s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 7.963180541992188e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 8.821487426757812e-06s
INFO | --- Analysis for nhs-jargon took 3.1514952182769775s
Availability | SPARQL endpoint availability check for NIT Patna took 8.535385131835938e-05s
Availability | VoID file availability check for NIT Patna took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.29654693603515625s
Reputation | Calculation of the PageRank for NIT Patna took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.985664367675781e-05s
Believability | Calculation of trust value for NIT Patna took 1.1444091796875e-05s
INFO | --- Analysis for NITP took 3.5797412395477295s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 0.0001087188720703125s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2864096164703369s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020624160766601562s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.4809112548828125e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for nlr-dataset-mod took 4.125086784362793s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.6046278476715088s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.27373480796813965s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020682811737060547s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for NLW took 4.341730356216431s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.3359158039093018s
Availability | VoID file availability check for Nobel Prizes took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.274080753326416s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.250640869140625e-05s
Believability | Calculation of trust value for Nobel Prizes took 1.0251998901367188e-05s
INFO | --- Analysis for nobelprizes took 9.135893821716309s
Availability | SPARQL endpoint availability check for NoiPA took 0.2556192874908447s
Availability | VoID file availability check for NoiPA took 0.0005009174346923828s
Extra | Recovery of all triples for NoiPA took 1.5016400814056396s
Performance | Total latancy measurement for NoiPA took 0.6645543575286865s
Amount of data | Number of triples check for NoiPA took 6.057729721069336s
Interoperability | New terms check for NoiPA took 2.842339038848877s
Versatility | Languages check for NoiPA took 60.16280794143677s
Interpretability | Number of blank nodes check for NoiPA took 0.15274691581726074s
Interpretability | RDF structures check for NoiPA took 0.5481722354888916s
Versatility | Serialization formats check for NoiPA took 0.3417820930480957s
Availability | RDF dump link check for NoiPA took 0.1322944164276123s
License | MR license check for NoiPA took 0.6120483875274658s
License | HR license check for NoiPA took 60.1095244884491s
Amount of data | Number of property check for NoiPA took 0.14324712753295898s
Understandability | Number of label check for NoiPA took 1.17457914352417s
Understandability | URI regex check for NoiPA took 0.4250948429107666s
Understandability | Vocabs check for NoiPA took 0.25406646728515625s
Verifiability | Authors check for NoiPA took 0.37438058853149414s
Verifiability | Publishers check for NoiPA took 0.26949214935302734s
Performance | Throughput check for NoiPA took 10.523005962371826s
Amount of data | Check the number of entities for NoiPA took 0.00011134147644042969s
Verifiability | Contribs. check for NoiPA took 0.2204761505126953s
Interlinking | sameAs chians check for NoiPA took 0.17824983596801758s
Interlinking | skos check for NoiPA took 0.5176386833190918s
Interlinking | skos check for NoiPA took 0.13393211364746094s
Timeliness | dataset update frequency check for NoiPA took 0.29840922355651855s
Currency | Creation date check for NoiPA took 0.489778995513916s
Currency | Modification date check for NoiPA took 0.30075502395629883s
Rep.Conc. | URIs length for NoiPA took 18.78885841369629s
Interoperability | New vocabularies check for NoiPA took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.1337873935699463s
Accuracy | Check Functional Property for NoiPA took 0.19885587692260742s
Accuracy | Check Inverse Functional Property for NoiPA took 0.19614768028259277s
Accuracy | Check Empty annotation labels for NoiPA took 0.45087528228759766s
Accuracy | Check White space in annotation for NoiPA took 0.0260467529296875s
Accuracy | Check Datatype consistency for NoiPA took 0.027466535568237305s
Consistency | Disjoint class check for NoiPA took 0.14958405494689941s
Consistency | Check Misplaced properties for NoiPA took 16.858768224716187s
Consistency | Misplaced classes for NoiPA took 0.2115616798400879s
Consistency | Check Ontology hijacking for NoiPA took 1.6192631721496582s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.223238229751587s
Consistency | Check Invalid usage of undefined properties for NoiPA took 17.956814527511597s
Conciseness | Check Extensional conciseness for NoiPA took 0.03392744064331055s
Conciseness | Check Intensional conciseness for NoiPA took 0.18919610977172852s
Security | Sign check for NoiPA took 0.10769391059875488s
Availability | Check URIs Dereferenciability for NoiPA took 11.029963254928589s
Completeness | Calculation of interlinking completeness for NoiPA took 0.5788624286651611s
Reputation | Calculation of the PageRank for NoiPA took 0.023310422897338867s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for NoiPA took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.6689300537109375e-06s
Believability | Calculation of trust value for NoiPA took 1.33514404296875e-05s
INFO | --- Analysis for NoiPA took 518.6850326061249s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 1.146252155303955s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.30835628509521484s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02091670036315918s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.34600830078125e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.33514404296875e-05s
INFO | --- Analysis for nom took 8.635609865188599s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 27.424160480499268s
Availability | VoID file availability check for Nomenclator Asturias took 0.0007517337799072266s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2794206142425537s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.021487712860107422s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.58306884765625e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 8.58306884765625e-06s
INFO | --- Analysis for nomenclator-asturias took 139.25124764442444s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.5174353122711182s
Availability | VoID file availability check for Nomisma.org  took 0.0006911754608154297s
Extra | Recovery of all triples for Nomisma.org  took 300.0962529182434s
Performance | Total latancy measurement for Nomisma.org  took 2.202439546585083s
Amount of data | Number of triples check for Nomisma.org  took 46.64484143257141s
Interoperability | New terms check for Nomisma.org  took 10.785062074661255s
Versatility | Languages check for Nomisma.org  took 222.26435804367065s
Interpretability | Number of blank nodes check for Nomisma.org  took 83.64187479019165s
Security | Check HTTPS for Nomisma.org  took 0.8576948642730713s
Interpretability | RDF structures check for Nomisma.org  took 0.37201809883117676s
Versatility | Serialization formats check for Nomisma.org  took 0.4256734848022461s
Availability | RDF dump link check for Nomisma.org  took 2111.321689605713s
License | MR license check for Nomisma.org  took 0.39039111137390137s
License | HR license check for Nomisma.org  took 64.03321194648743s
Amount of data | Number of property check for Nomisma.org  took 0.39066171646118164s
Understandability | Number of label check for Nomisma.org  took 15.345515489578247s
Understandability | URI regex check for Nomisma.org  took 1.0823824405670166s
Understandability | Vocabs check for Nomisma.org  took 0.46604299545288086s
Verifiability | Authors check for Nomisma.org  took 0.365997314453125s
Verifiability | Publishers check for Nomisma.org  took 0.39211249351501465s
Performance | Throughput check for Nomisma.org  took 11.50640606880188s
Amount of data | Check the number of entities for Nomisma.org  took 9.775161743164062e-05s
Verifiability | Contribs. check for Nomisma.org  took 1.5805928707122803s
Interlinking | sameAs chians check for Nomisma.org  took 1.3293101787567139s
Interlinking | skos check for Nomisma.org  took 27.47979497909546s
Interlinking | skos check for Nomisma.org  took 10.49008584022522s
Timeliness | dataset update frequency check for Nomisma.org  took 0.3690452575683594s
Currency | Creation date check for Nomisma.org  took 0.7869586944580078s
Currency | Modification date check for Nomisma.org  took 0.703632116317749s
Rep.Conc. | URIs length for Nomisma.org  took 405.10752296447754s
Interoperability | New vocabularies check for Nomisma.org  took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.44077086448669434s
Accuracy | Check Functional Property for Nomisma.org  took 0.3560066223144531s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3619060516357422s
Accuracy | Check Empty annotation labels for Nomisma.org  took 301.7702405452728s
Accuracy | Check White space in annotation for Nomisma.org  took 2.696310043334961s
Consistency | Disjoint class check for Nomisma.org  took 0.382601261138916s
Consistency | Check Misplaced properties for Nomisma.org  took 27.65056037902832s
Consistency | Check Ontology hijacking for Nomisma.org  took 327.089106798172s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 47.92928409576416s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.0001666545867919922s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.4544367790222168s
Security | Sign check for Nomisma.org  took 0.37077999114990234s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1970.5106518268585s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.6759810447692871s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.02163076400756836s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 7.700920104980469e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.9073486328125e-06s
Believability | Calculation of trust value for Nomisma.org  took 6.4373016357421875e-06s
INFO | --- Analysis for nomisma_org took 8120.053437948227s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.3698573112487793s
Availability | VoID file availability check for Curriculum Vitae took 0.0005130767822265625s
Extra | Recovery of all triples for Curriculum Vitae took 0.6118447780609131s
Performance | Total latancy measurement for Curriculum Vitae took 0.8921771049499512s
Amount of data | Number of triples check for Curriculum Vitae took 0.2306346893310547s
Interoperability | New terms check for Curriculum Vitae took 1.4731330871582031s
Versatility | Languages check for Curriculum Vitae took 0.2501959800720215s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.22871875762939453s
Interpretability | RDF structures check for Curriculum Vitae took 0.25747060775756836s
Versatility | Serialization formats check for Curriculum Vitae took 0.2652723789215088s
Availability | RDF dump link check for Curriculum Vitae took 0.12217497825622559s
License | MR license check for Curriculum Vitae took 0.13541889190673828s
License | HR license check for Curriculum Vitae took 0.13309359550476074s
Amount of data | Number of property check for Curriculum Vitae took 0.23947882652282715s
Understandability | Number of label check for Curriculum Vitae took 0.2474076747894287s
Understandability | URI regex check for Curriculum Vitae took 0.36496806144714355s
Understandability | Vocabs check for Curriculum Vitae took 0.1525566577911377s
Verifiability | Authors check for Curriculum Vitae took 0.13567757606506348s
Verifiability | Publishers check for Curriculum Vitae took 0.11638307571411133s
Performance | Throughput check for Curriculum Vitae took 10.998725175857544s
Amount of data | Check the number of entities for Curriculum Vitae took 0.00010752677917480469s
Verifiability | Contribs. check for Curriculum Vitae took 0.11719179153442383s
Interlinking | sameAs chians check for Curriculum Vitae took 0.11745214462280273s
Interlinking | skos check for Curriculum Vitae took 0.11631536483764648s
Interlinking | skos check for Curriculum Vitae took 0.21558427810668945s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.13140106201171875s
Currency | Creation date check for Curriculum Vitae took 0.24661707878112793s
Currency | Modification date check for Curriculum Vitae took 0.2350296974182129s
Rep.Conc. | URIs length for Curriculum Vitae took 0.3074028491973877s
Interoperability | New vocabularies check for Curriculum Vitae took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.12056469917297363s
Accuracy | Check Functional Property for Curriculum Vitae took 0.13584375381469727s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.11871218681335449s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.13747906684875488s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.00010395050048828125s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0038394927978515625s
Consistency | Disjoint class check for Curriculum Vitae took 0.23195409774780273s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.2658383846282959s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.3794219493865967s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.2385427951812744s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.3685393333435059s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0014853477478027344s
Security | Sign check for Curriculum Vitae took 0.11303448677062988s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 18.95163345336914s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.293475866317749s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.021559476852416992s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 2.8371810913085938e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.1920928955078125e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.1444091796875e-05s
INFO | --- Analysis for Nordine_Bittich took 56.86513924598694s
Availability | SPARQL endpoint availability check for NorPark took 1.0575873851776123s
Availability | VoID file availability check for NorPark took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for NorPark took 0.2864806652069092s
Reputation | Calculation of the PageRank for NorPark took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for NorPark took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.076957702636719e-05s
Believability | Calculation of trust value for NorPark took 1.2159347534179688e-05s
INFO | --- Analysis for norpark took 3.7454943656921387s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.01563405990600586s
Availability | VoID file availability check for Parking Dataset took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.28393983840942383s
Reputation | Calculation of the PageRank for Parking Dataset took 0.021215200424194336s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.363059997558594e-05s
Believability | Calculation of trust value for Parking Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for norpark2 took 2.703543186187744s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 5.461716175079346s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.00048542022705078125s
Extra | Recovery of all triples for Norway fishery stocks dataset took 114.53719305992126s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.9760451316833496s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.24335765838623s
Interoperability | New terms check for Norway fishery stocks dataset took 14.611445665359497s
Versatility | Languages check for Norway fishery stocks dataset took 300.22504329681396s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 1.889650583267212s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.3090634346008301s
Versatility | Serialization formats check for Norway fishery stocks dataset took 9.843179702758789s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.2222919464111328s
License | MR license check for Norway fishery stocks dataset took 0.24340176582336426s
License | HR license check for Norway fishery stocks dataset took 300.189448595047s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.21026921272277832s
Understandability | Number of label check for Norway fishery stocks dataset took 1.5017774105072021s
Understandability | URI regex check for Norway fishery stocks dataset took 0.39488697052001953s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.18485164642333984s
Verifiability | Authors check for Norway fishery stocks dataset took 0.1966869831085205s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.24815130233764648s
Performance | Throughput check for Norway fishery stocks dataset took 10.901675939559937s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 7.033348083496094e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.20248651504516602s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.22048592567443848s
Interlinking | skos check for Norway fishery stocks dataset took 0.47193288803100586s
Interlinking | skos check for Norway fishery stocks dataset took 0.421036958694458s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 4.484547853469849s
Currency | Creation date check for Norway fishery stocks dataset took 0.45763635635375977s
Currency | Modification date check for Norway fishery stocks dataset took 0.23230648040771484s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 156.08098101615906s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.20041465759277344s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.20808053016662598s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.18265056610107422s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 30.621166944503784s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.652414083480835s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.5978400707244873s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.19896578788757324s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 86.07385325431824s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.16145920753479s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 29.756213426589966s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.3142380714416504s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 87.81756114959717s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.6936912536621094s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5275003910064697s
Security | Sign check for Norway fishery stocks dataset took 0.8066585063934326s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 10.211752891540527s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.37120556831359863s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.02122640609741211s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.1444091796875e-05s
INFO | --- Analysis for Norway_Fishery_ took 2258.000062942505s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.3373713493347168s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.27263379096984863s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.0206606388092041s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.673004150390625e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.1920928955078125e-05s
INFO | --- Analysis for norwegian-geo-divisions took 6.463931083679199s
Availability | SPARQL endpoint availability check for NITP took 4.4345855712890625e-05s
Availability | VoID file availability check for NITP took 0.00040650367736816406s
Completeness | Calculation of interlinking completeness for NITP took 0.2911968231201172s
Reputation | Calculation of the PageRank for NITP took 0.021048784255981445s
Interlinking | Calculation of Degree of Connection for NITP took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for NITP took 6.461143493652344e-05s
Believability | Calculation of trust value for NITP took 7.62939453125e-06s
INFO | --- Analysis for notIdentifier took 3.154496908187866s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.172325134277344e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.2721712589263916s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.266334533691406e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 7.62939453125e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.883094310760498s
Availability | SPARQL endpoint availability check for NPM took 4.267692565917969e-05s
Availability | VoID file availability check for NPM took 0.0003800392150878906s
Completeness | Calculation of interlinking completeness for NPM took 0.2773451805114746s
Reputation | Calculation of the PageRank for NPM took 0.0207669734954834s
Interlinking | Calculation of Degree of Connection for NPM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for NPM took 3.1948089599609375e-05s
Believability | Calculation of trust value for NPM took 7.867813110351562e-06s
INFO | --- Analysis for npm took 3.4031383991241455s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.025166749954223633s
Availability | VoID file availability check for NTNU special collections took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.2750418186187744s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.6743621826171875e-05s
Believability | Calculation of trust value for NTNU special collections took 6.198883056640625e-06s
INFO | --- Analysis for ntnusc took 5.406703948974609s
Availability | SPARQL endpoint availability check for links took 8.893013000488281e-05s
Availability | VoID file availability check for links took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for links took 0.3074159622192383s
Reputation | Calculation of the PageRank for links took 0.02262258529663086s
Interlinking | Calculation of Degree of Connection for links took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for links took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for links took 1.239776611328125e-05s
Believability | Calculation of trust value for links took 1.0013580322265625e-05s
INFO | --- Analysis for nugmyanmar took 2.609415292739868s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 9.560585021972656e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2882857322692871s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.751319885253906e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 8.58306884765625e-06s
INFO | --- Analysis for nuts-geovocab took 2.6291236877441406s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.39415812492370605s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.275604248046875s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020838022232055664s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.699562072753906e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.049041748046875e-05s
INFO | --- Analysis for nvd took 4.165348052978516s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.792109489440918s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.2867598533630371s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.021828889846801758s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.058547973632812e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.3113021850585938e-05s
INFO | --- Analysis for nvs took 9.121909856796265s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 8.726119995117188e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.29083847999572754s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.022254467010498047s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0001800060272216797s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for nytimes-linked-open-data took 2.705423593521118s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.5891919136047363s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006494522094726562s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.4103732109069824s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.9630742073059082s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 4.047552585601807s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.7356698513031006s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 58.229931354522705s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.602891445159912s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.26316094398498535s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.4350554943084717s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.5086421966552734s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.47785019874572754s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.6254703998565674s
License | HR license check for Italian Chamber of Deputies - official dataset took 58.21971583366394s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.34478235244750977s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.9417741298675537s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.9087140560150146s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.4400029182434082s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.4775125980377197s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.38846373558044434s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 11.28872537612915s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 7.557868957519531e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.41826415061950684s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.37527966499328613s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.4053990840911865s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3633103370666504s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.4727349281311035s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.8081753253936768s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.39025402069091797s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 16.741234064102173s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.4018886089324951s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.3844752311706543s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.37443995475769043s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.8854742050170898s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.03022027015686035s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.029578447341918945s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.3880150318145752s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.666322946548462s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.43900489807128906s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 1.919386386871338s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.265166997909546s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.517500162124634s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03272104263305664s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.4277970790863037s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.32822155952453613s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 9.989201068878174s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.3857440948486328s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.0001049041748046875s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.33514404296875e-05s
INFO | --- Analysis for ocd took 404.407399892807s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 8.893013000488281e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.2900094985961914s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020142078399658203s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.933906555175781e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.2636184692382812e-05s
INFO | --- Analysis for oceandrilling-borehole took 3.734557628631592s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 3.259293556213379s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.27545595169067383s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.02131962776184082s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0010216236114501953s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 9.655952453613281e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.3113021850585938e-05s
INFO | --- Analysis for oceandrilling-codices took 9.065378904342651s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 2.588101625442505s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.2971527576446533s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.0279159545898438e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.1920928955078125e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 7.051081657409668s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 2.9744648933410645s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.2770099639892578s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.457069396972656e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.1444091796875e-05s
INFO | --- Analysis for oceandrilling-forams took 7.814799070358276s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 2.582641839981079s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.28888821601867676s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.0040740966796875e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-janus took 7.461930751800537s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 12.443762063980103s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.2955441474914551s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.170967102050781e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.2636184692382812e-05s
INFO | --- Analysis for oceandrilling-janusamp took 17.574408054351807s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.6558830738067627s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2757992744445801s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.022686004638671875s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.147125244140625e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 5.245208740234375e-06s
INFO | --- Analysis for oceandrilling-ldeo took 7.793425798416138s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 9.226799011230469e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2804994583129883s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.3882598876953125e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 5.4836273193359375e-06s
INFO | --- Analysis for oclc-fast took 8.428802967071533s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 5.841255187988281e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.2789931297302246s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.021422624588012695s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.218650817871094e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 8.58306884765625e-06s
INFO | --- Analysis for odc-imd-environment-score took 5.530897617340088s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.22211194038391113s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0005507469177246094s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 1.177567958831787s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 0.8879451751708984s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.1375870704650879s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 2.052794933319092s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.3766961097717285s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 30.24880862236023s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.0998387336730957s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.14086174964904785s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.22039556503295898s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 51.760315895080566s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.16333413124084473s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.17358160018921s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.22033929824829102s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.14915752410888672s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.3477308750152588s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.12495994567871094s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.13991379737854004s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.13811898231506348s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 11.177423238754272s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 0.00010943412780761719s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.21104931831359863s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.22494173049926758s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.14032578468322754s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.19666361808776855s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.1330580711364746s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.4288632869720459s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.14155817031860352s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.5032413005828857s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.15637731552124023s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.21022391319274902s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.21085619926452637s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.22761297225952148s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.5093445777893066s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 1.1222069263458252s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.5846967697143555s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.0001678466796875s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.3106679916381836s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.15289950370788574s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.32678937911987305s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02102208137512207s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.6689300537109375e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 9.298324584960938e-06s
INFO | --- Analysis for odc-lsoa took 268.9724078178406s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.09122371673583984s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.28676795959472656s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020931005477905273s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.107589721679688e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for oecd-linked-data took 2.731198310852051s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.24259376525879s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.2806730270385742s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.6253204345703125e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.4066696166992188e-05s
INFO | --- Analysis for ogolod took 103.12314558029175s
Availability | SPARQL endpoint availability check for OLAC Metadata took 8.821487426757812e-05s
Availability | VoID file availability check for OLAC Metadata took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.2960371971130371s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.02194523811340332s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.267692565917969e-05s
Believability | Calculation of trust value for OLAC Metadata took 1.2159347534179688e-05s
INFO | --- Analysis for olac took 27.89160704612732s
Availability | SPARQL endpoint availability check for OLiA took 4.076957702636719e-05s
Availability | VoID file availability check for OLiA took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for OLiA took 0.281679630279541s
Reputation | Calculation of the PageRank for OLiA took 0.02132701873779297s
Interlinking | Calculation of Degree of Connection for OLiA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012135505676269531s
Believability | Calculation of trust value for OLiA took 1.239776611328125e-05s
INFO | --- Analysis for olia took 15.341373920440674s
Availability | SPARQL endpoint availability check for OLiA Discourse took 8.344650268554688e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0008528232574462891s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.2980997562408447s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.02087855339050293s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.1961669921875e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.239776611328125e-05s
INFO | --- Analysis for olia-discourse took 7.276015281677246s
Availability | SPARQL endpoint availability check for Open Land Use took 0.18487143516540527s
Availability | VoID file availability check for Open Land Use took 0.0005018711090087891s
Extra | Recovery of all triples for Open Land Use took 121.3710458278656s
Performance | Total latancy measurement for Open Land Use took 1.0003588199615479s
Amount of data | Number of triples check for Open Land Use took 9.00085711479187s
Interoperability | New terms check for Open Land Use took 13.98329496383667s
Versatility | Languages check for Open Land Use took 300.18865990638733s
Interpretability | Number of blank nodes check for Open Land Use took 1.993515968322754s
Interpretability | RDF structures check for Open Land Use took 0.21553754806518555s
Versatility | Serialization formats check for Open Land Use took 8.218221426010132s
Availability | RDF dump link check for Open Land Use took 0.2028181552886963s
License | MR license check for Open Land Use took 0.19466185569763184s
License | HR license check for Open Land Use took 300.16062092781067s
Amount of data | Number of property check for Open Land Use took 0.1854994297027588s
Understandability | Number of label check for Open Land Use took 1.186237096786499s
Understandability | URI regex check for Open Land Use took 0.4027426242828369s
Understandability | Vocabs check for Open Land Use took 0.20172786712646484s
Verifiability | Authors check for Open Land Use took 0.22658133506774902s
Verifiability | Publishers check for Open Land Use took 0.24847698211669922s
Performance | Throughput check for Open Land Use took 11.400671005249023s
Amount of data | Check the number of entities for Open Land Use took 5.7220458984375e-05s
Verifiability | Contribs. check for Open Land Use took 0.20258808135986328s
Interlinking | sameAs chians check for Open Land Use took 0.20544219017028809s
Interlinking | skos check for Open Land Use took 0.5006439685821533s
Interlinking | skos check for Open Land Use took 0.42908787727355957s
Timeliness | dataset update frequency check for Open Land Use took 3.3195884227752686s
Currency | Creation date check for Open Land Use took 0.5092511177062988s
Currency | Modification date check for Open Land Use took 0.2745978832244873s
Rep.Conc. | URIs length for Open Land Use took 154.80870985984802s
Interoperability | New vocabularies check for Open Land Use took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.21796369552612305s
Accuracy | Check Functional Property for Open Land Use took 0.19729900360107422s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.2234058380126953s
Accuracy | Check Empty annotation labels for Open Land Use took 37.58622765541077s
Accuracy | Check White space in annotation for Open Land Use took 2.637416362762451s
Accuracy | Check Datatype consistency for Open Land Use took 2.569106340408325s
Consistency | Disjoint class check for Open Land Use took 0.21631574630737305s
Consistency | Check Misplaced properties for Open Land Use took 86.11573362350464s
Consistency | Misplaced classes for Open Land Use took 8.274384021759033s
Consistency | Check Ontology hijacking for Open Land Use took 31.223576307296753s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.3831868171691895s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 86.97899889945984s
Conciseness | Check Extensional conciseness for Open Land Use took 2.7010016441345215s
Conciseness | Check Intensional conciseness for Open Land Use took 0.6104516983032227s
Security | Sign check for Open Land Use took 0.20935273170471191s
Availability | Check URIs Dereferenciability for Open Land Use took 8.97666072845459s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.6324751377105713s
Reputation | Calculation of the PageRank for Open Land Use took 0.021364450454711914s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 4.291534423828125e-06s
Believability | Calculation of trust value for Open Land Use took 1.049041748046875e-05s
INFO | --- Analysis for OLU took 2255.6693031787872s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.6528079509735107s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.2804293632507324s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.022565364837646484s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-als took 3.664128303527832s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2645118236541748s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.28415918350219727s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.022766590118408203s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 4.291534423828125e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-arb took 3.306966543197632s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2571408748626709s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.001220703125s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.3306894302368164s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-bul took 3.2856245040893555s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.25698161125183105s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2854151725769043s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.021052122116088867s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
INFO | --- Analysis for omwn-cow took 3.260596990585327s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2468245029449463s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.28685736656188965s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020896196365356445s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-cwn took 3.217209577560425s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.26769161224365234s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.287372350692749s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-dan took 3.257200241088867s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.2632713317871094s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.27828288078308105s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.021958112716674805s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-ell took 3.2870428562164307s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2767064571380615s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0002086162567138672s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.28497862815856934s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.021158456802368164s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-eng took 3.319398880004883s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.28796815872192383s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.32039332389831543s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.02133321762084961s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-fas took 3.2318453788757324s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.26888298988342285s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.28365278244018555s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-fin took 3.180450916290283s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.23092174530029297s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2740800380706787s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020912885665893555s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-fra took 3.1867241859436035s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.25702667236328125s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.27225255966186523s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020768404006958008s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-heb took 3.214840888977051s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2419123649597168s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.00042176246643066406s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.34029388427734375s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.020771026611328125s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-hrv took 3.2338640689849854s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.23981285095214844s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0002079010009765625s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2690887451171875s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.021671772003173828s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 4.76837158203125e-06s
INFO | --- Analysis for omwn-isl took 3.2221243381500244s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.22272586822509766s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.27870869636535645s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0221555233001709s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 4.0531158447265625e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-ita took 3.199319362640381s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.254425048828125s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.28635406494140625s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020842552185058594s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 5.7220458984375e-06s
INFO | --- Analysis for omwn-iwn took 3.2368829250335693s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.23139595985412598s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0002048015594482422s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.273958683013916s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.021570444107055664s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-jpn took 3.1689674854278564s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2666432857513428s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.27797770500183105s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.021280288696289062s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.4066696166992188e-05s
INFO | --- Analysis for omwn-mcr took 3.2657296657562256s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2240300178527832s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.27423596382141113s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
INFO | --- Analysis for omwn-msa took 3.116201639175415s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.2391972541809082s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.27779364585876465s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.020781517028808594s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 5.4836273193359375e-06s
INFO | --- Analysis for omwn-nld took 3.1981422901153564s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.26258015632629395s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.3045988082885742s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
INFO | --- Analysis for omwn-nor took 3.2710464000701904s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.24529576301574707s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2828080654144287s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.022258281707763672s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
INFO | --- Analysis for omwn-pol took 3.1780192852020264s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2702317237854004s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.29935145378112793s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-por took 3.2353322505950928s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2523961067199707s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0004277229309082031s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.291248083114624s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 4.76837158203125e-06s
INFO | --- Analysis for omwn-ron took 3.2248523235321045s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2254934310913086s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2741880416870117s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.02118539810180664s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-slk took 3.2258706092834473s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2663917541503906s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.284564733505249s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-slv took 3.2887141704559326s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.24234771728515625s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2958254814147949s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.021067380905151367s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-swe took 3.2077579498291016s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.29102301597595215s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2863044738769531s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.02087092399597168s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-tha took 3.3699605464935303s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.081883668899536s
Availability | VoID file availability check for OntoBeef Domain took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.28317737579345703s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.021168947219848633s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 5.3882598876953125e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.1444091796875e-05s
INFO | --- Analysis for ontobeef-domain took 27.425346612930298s
Availability | SPARQL endpoint availability check for Ontos News Portal took 8.749961853027344e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.2948951721191406s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.02313828468322754s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.083747863769531e-05s
Believability | Calculation of trust value for Ontos News Portal took 1.1682510375976562e-05s
INFO | --- Analysis for ontos-news-portal took 4.508257150650024s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.291534423828125e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.2824232578277588s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 2.9802322387695312e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 7.867813110351562e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.667116403579712s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.315376281738281e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.27886486053466797s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.022013425827026367s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.838539123535156e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 6.67572021484375e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 13.216421842575073s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 8.535385131835938e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.30127811431884766s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.6253204345703125e-05s
Believability | Calculation of trust value for Open Data Euskadi took 8.821487426757812e-06s
INFO | --- Analysis for open-data-euskadi took 9.116820096969604s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 9.822845458984375e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.2956697940826416s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010013580322265625s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 1.1682510375976562e-05s
INFO | --- Analysis for open-data-risp took 7.919776439666748s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.1799778938293457s
Availability | VoID file availability check for Open Data Thesaurus took 0.0006389617919921875s
Extra | Recovery of all triples for Open Data Thesaurus took 1.0817160606384277s
Performance | Total latancy measurement for Open Data Thesaurus took 0.4406445026397705s
Amount of data | Number of triples check for Open Data Thesaurus took 0.10494446754455566s
Interoperability | New terms check for Open Data Thesaurus took 1.3234984874725342s
Versatility | Languages check for Open Data Thesaurus took 0.113494873046875s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.11154460906982422s
Security | Check HTTPS for Open Data Thesaurus took 0.34047961235046387s
Interpretability | RDF structures check for Open Data Thesaurus took 0.11237311363220215s
Versatility | Serialization formats check for Open Data Thesaurus took 0.10570287704467773s
Availability | RDF dump link check for Open Data Thesaurus took 1.1217358112335205s
License | MR license check for Open Data Thesaurus took 0.11834430694580078s
License | HR license check for Open Data Thesaurus took 0.09033012390136719s
Amount of data | Number of property check for Open Data Thesaurus took 0.11044931411743164s
Understandability | Number of label check for Open Data Thesaurus took 0.11988663673400879s
Understandability | URI regex check for Open Data Thesaurus took 0.17334747314453125s
Understandability | Vocabs check for Open Data Thesaurus took 0.1172783374786377s
Verifiability | Authors check for Open Data Thesaurus took 0.12040209770202637s
Verifiability | Publishers check for Open Data Thesaurus took 0.10340261459350586s
Performance | Throughput check for Open Data Thesaurus took 10.50500774383545s
Amount of data | Check the number of entities for Open Data Thesaurus took 0.00017976760864257812s
Verifiability | Contribs. check for Open Data Thesaurus took 0.11119341850280762s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.10350489616394043s
Interlinking | skos check for Open Data Thesaurus took 0.11086869239807129s
Interlinking | skos check for Open Data Thesaurus took 0.08643269538879395s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.0813603401184082s
Currency | Creation date check for Open Data Thesaurus took 0.18688416481018066s
Currency | Modification date check for Open Data Thesaurus took 0.1919727325439453s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.43932008743286133s
Interoperability | New vocabularies check for Open Data Thesaurus took 8.28646183013916s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.11953401565551758s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.08704447746276855s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.07963705062866211s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.16568470001220703s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0012176036834716797s
Consistency | Disjoint class check for Open Data Thesaurus took 0.0887608528137207s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.1792433261871338s
Consistency | Misplaced classes for Open Data Thesaurus took 0.07916116714477539s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.3811390399932861s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.3325183391571045s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00016117095947265625s
Security | Sign check for Open Data Thesaurus took 0.07704973220825195s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.29877281188964844s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020158052444458008s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0006809234619140625s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.677078247070312e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 11.13197112083435s
Believability | Calculation of trust value for Open Data Thesaurus took 1.5735626220703125e-05s
INFO | --- Analysis for open-data-thesaurus took 94.38428401947021s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.315376281738281e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.2918844223022461s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.02101731300354004s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 7.43865966796875e-05s
Believability | Calculation of trust value for Open Election Data Project took 8.58306884765625e-06s
INFO | --- Analysis for open-election-data-project took 42.68564748764038s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.953615427017212s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.2871849536895752s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.344650268554688e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 8.58306884765625e-06s
INFO | --- Analysis for open-energy-info-wiki took 19.19646978378296s
Availability | SPARQL endpoint availability check for Open Library took 4.4345855712890625e-05s
Availability | VoID file availability check for Open Library took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for Open Library took 0.2904531955718994s
Reputation | Calculation of the PageRank for Open Library took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for Open Library took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.699562072753906e-05s
Believability | Calculation of trust value for Open Library took 1.1682510375976562e-05s
INFO | --- Analysis for open-library took 9.17860722541809s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.21559667587280273s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0004646778106689453s
Extra | Recovery of all triples for Open Land Use @PSNC took 123.13621616363525s
Performance | Total latancy measurement for Open Land Use @PSNC took 1.0695104598999023s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.024767875671387s
Interoperability | New terms check for Open Land Use @PSNC took 14.050549983978271s
Versatility | Languages check for Open Land Use @PSNC took 300.2601933479309s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 1.8274657726287842s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.18346166610717773s
Versatility | Serialization formats check for Open Land Use @PSNC took 10.372735261917114s
Availability | RDF dump link check for Open Land Use @PSNC took 0.2049238681793213s
License | MR license check for Open Land Use @PSNC took 0.18477511405944824s
License | HR license check for Open Land Use @PSNC took 300.23408794403076s
Amount of data | Number of property check for Open Land Use @PSNC took 0.1970665454864502s
Understandability | Number of label check for Open Land Use @PSNC took 1.4497525691986084s
Understandability | URI regex check for Open Land Use @PSNC took 0.5295722484588623s
Understandability | Vocabs check for Open Land Use @PSNC took 0.195753812789917s
Verifiability | Authors check for Open Land Use @PSNC took 0.21946501731872559s
Verifiability | Publishers check for Open Land Use @PSNC took 0.25504112243652344s
Performance | Throughput check for Open Land Use @PSNC took 11.622543811798096s
Amount of data | Check the number of entities for Open Land Use @PSNC took 8.082389831542969e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.20357203483581543s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.1978130340576172s
Interlinking | skos check for Open Land Use @PSNC took 0.5170698165893555s
Interlinking | skos check for Open Land Use @PSNC took 0.45419788360595703s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 4.457216739654541s
Currency | Creation date check for Open Land Use @PSNC took 0.4889092445373535s
Currency | Modification date check for Open Land Use @PSNC took 0.24164772033691406s
Rep.Conc. | URIs length for Open Land Use @PSNC took 145.2260491847992s
Interoperability | New vocabularies check for Open Land Use @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.19559955596923828s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.20214080810546875s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.18866634368896484s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 41.018985748291016s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.6499762535095215s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.550443172454834s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.21614551544189453s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 86.41375207901001s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.264315366744995s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 36.44989371299744s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.320577621459961s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 86.32158088684082s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.671100378036499s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.5523989200592041s
Security | Sign check for Open Land Use @PSNC took 0.19505929946899414s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 10.042003870010376s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.5108098983764648s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.02158379554748535s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for Open_Land_Use took 2260.6015799045563s
Availability | SPARQL endpoint availability check for flyatlas took 1.1508734226226807s
Availability | VoID file availability check for flyatlas took 0.0006797313690185547s
Completeness | Calculation of interlinking completeness for flyatlas took 0.3055245876312256s
Reputation | Calculation of the PageRank for flyatlas took 0.020839452743530273s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.504753112792969e-05s
Believability | Calculation of trust value for flyatlas took 1.3113021850585938e-05s
INFO | --- Analysis for openbiomed-flyatlas took 5.416245222091675s
Availability | SPARQL endpoint availability check for OpenCalais took 0.00010919570922851562s
Availability | VoID file availability check for OpenCalais took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.29025912284851074s
Reputation | Calculation of the PageRank for OpenCalais took 0.021056652069091797s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010800361633300781s
Believability | Calculation of trust value for OpenCalais took 1.1920928955078125e-05s
INFO | --- Analysis for opencalais took 6.207901477813721s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 8.606910705566406e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.29718852043151855s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.02147817611694336s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.963180541992188e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 9.775161743164062e-06s
INFO | --- Analysis for opencorporates took 2.9614861011505127s
Availability | SPARQL endpoint availability check for OpenCyc took 9.465217590332031e-05s
Availability | VoID file availability check for OpenCyc took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2854177951812744s
Reputation | Calculation of the PageRank for OpenCyc took 0.02189016342163086s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010418891906738281s
Believability | Calculation of trust value for OpenCyc took 7.3909759521484375e-06s
INFO | --- Analysis for opencyc took 2.691659688949585s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.30034852027893066s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020799636840820312s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.4809112548828125e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 4.434303522109985s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 9.846687316894531e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.27607107162475586s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.2898504734039307s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.28960323333740234s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.024182796478271484s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0011692047119140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.3511838912963867s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.2828333377838135s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020401716232299805s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.6136820316314697s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2904646396636963s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.784721612930298s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.3006114959716797s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.022617578506469727s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 4.0869340896606445s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0007288455963134766s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.3011343479156494s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 4.2254838943481445s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2788093090057373s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.6287989616394043s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 8.702278137207031e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.2779972553253174s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.021092891693115234s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.430511474609375e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.7366044521331787s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 8.535385131835938e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2875044345855713s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020893096923828125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 4.3839497566223145s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 8.487701416015625e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.273317813873291s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020659446716308594s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 9.775161743164062e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 3.4618821144104004s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 5.7220458984375e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.2652313709259033s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.021265268325805664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 4.4667229652404785s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 9.226799011230469e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.28589582443237305s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 9.298324584960938e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 3.4371533393859863s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 0.0001232624053955078s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.27785205841064453s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02219843864440918s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.6027395725250244s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 9.393692016601562e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.28435349464416504s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 3.5194520950317383s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 8.630752563476562e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0008463859558105469s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.29021477699279785s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020874500274658203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0009570121765136719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 5.221366882324219e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 3.5544800758361816s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.00011754035949707031s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.30298447608947754s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020909547805786133s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.65314507484436s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 8.916854858398438e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.3226735591888428s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.342949867248535s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 8.797645568847656e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.3045470714569092s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.022819995880126953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.66459321975708s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 8.869171142578125e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2961852550506592s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.02152562141418457s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.382300615310669s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 8.916854858398438e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.29541659355163574s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.7404556274414062e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.4271018505096436s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0007355213165283203s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.28849220275878906s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 4.184271574020386s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 8.940696716308594e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0008413791656494141s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.316303014755249s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.071687459945679s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 8.726119995117188e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.27554821968078613s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.021081924438476562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.365762710571289s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 8.535385131835938e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.27553653717041016s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.021884441375732422s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.934154510498047s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.00010251998901367188s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0008974075317382812s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.29116368293762207s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020812511444091797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.274305105209351s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.678436279296875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007913112640380859s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.29276037216186523s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.021031618118286133s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 5.245208740234375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 3.819906711578369s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.28632569313049316s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0224761962890625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.3139848709106445s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 9.131431579589844e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007839202880859375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.2892146110534668s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.02086329460144043s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.316734313964844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 3.215874433517456s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.2880401611328125s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020850419998168945s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 6.8134942054748535s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.294081449508667s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.021320581436157227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.81850004196167s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 8.96453857421875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.29683995246887207s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.02176380157470703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 5.230974912643433s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.696846008300781e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2776951789855957s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.021503686904907227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 3.64461612701416s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.2749142646789551s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.5418012142181396s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00012969970703125s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.28482747077941895s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.021181583404541016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.5958497524261475s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.32552027702331543s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.021025896072387695s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 4.098782539367676s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 9.202957153320312e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.283388614654541s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.7007358074188232s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.2987349033355713s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 4.280136823654175s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 5.650520324707031e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2893974781036377s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020852088928222656s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 3.3697686195373535s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.845329284667969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2924003601074219s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.021070003509521484s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.540661811828613s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.2870471477508545s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.2155559062957764s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 8.58306884765625e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.30974841117858887s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.022290945053100586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.1886987686157227s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 8.630752563476562e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0003483295440673828s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.3340742588043213s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 3.7720017433166504s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 3.834503412246704s
Availability | VoID file availability check for Open Data of Ecuador took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.29622817039489746s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.726119995117188e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.2636184692382812e-05s
INFO | --- Analysis for opendataec took 10.528160095214844s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.869171142578125e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.28895044326782227s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 6.437441349029541s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 8.7738037109375e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2746305465698242s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.021023273468017578s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.239776611328125e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.907404899597168s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 8.869171142578125e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.28713274002075195s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.02088761329650879s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.626542329788208s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.2859196662902832s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.497549533843994s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.00040149688720703125s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.30939459800720215s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.021794795989990234s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0008707046508789062s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.982948303222656e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.686769723892212s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.482269287109375e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.27663660049438477s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.0729570388793945s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 5.841255187988281e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.28578662872314453s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.6425282955169678s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 8.487701416015625e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.28821301460266113s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.021843433380126953s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 5.412101745605469e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.649590492248535s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 0.00010967254638671875s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.2762167453765869s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.0251998901367188e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.6047351360321045s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.46852993965149s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.3038053512573242s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020944595336914062s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.719329833984375e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.239776611328125e-05s
INFO | --- Analysis for openlink-lod-cache took 63.45406627655029s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 8.749961853027344e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.3823997974395752s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.020989179611206055s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.274482727050781e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 6.4373016357421875e-06s
INFO | --- Analysis for openlinksw-dataspaces took 3.1410257816314697s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.267692565917969e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.29319238662719727s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020725011825561523s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 0.00011396408081054688s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 8.344650268554688e-06s
INFO | --- Analysis for openlylocal took 16.056199073791504s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.3878424167633057s
Availability | VoID file availability check for OpenMobileNetwork took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.28588223457336426s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.020817279815673828s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.367134094238281e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.0728836059570312e-05s
INFO | --- Analysis for openmobilenetwork took 4.9348390102386475s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.9879894256591797s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.00040841102600097656s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.28647303581237793s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02191329002380371s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.894371032714844e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 6.123137950897217s
Availability | SPARQL endpoint availability check for oreilly took 8.559226989746094e-05s
Availability | VoID file availability check for oreilly took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for oreilly took 0.2881135940551758s
Reputation | Calculation of the PageRank for oreilly took 0.022228002548217773s
Interlinking | Calculation of Degree of Connection for oreilly took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for oreilly took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.863739013671875e-05s
Believability | Calculation of trust value for oreilly took 1.2159347534179688e-05s
INFO | --- Analysis for oreilly took 4.935993909835815s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.378340244293213s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.3149681091308594s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.02132725715637207s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 4.1961669921875e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.1682510375976562e-05s
INFO | --- Analysis for Organchem-Data took 7.427863836288452s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.05380678176879883s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2882707118988037s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.02238631248474121s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.081031799316406e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for organic-edunet took 9.165764331817627s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.3727426528930664s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0004918575286865234s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 5.797294855117798s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.6383216381072998s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.14892292022705078s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.6370964050292969s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 5.317673206329346s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.13240694999694824s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.3908686637878418s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.12869906425476074s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.1310570240020752s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.1529383659362793s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.4370501041412354s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.13625383377075195s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.1516423225402832s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.30483102798461914s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.12224555015563965s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.15145277976989746s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.15064024925231934s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.673651218414307s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 0.00010895729064941406s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.1336045265197754s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.14639711380004883s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.16402316093444824s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.16414570808410645s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.1644880771636963s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.36294984817504883s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.6465442180633545s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 4.004651784896851s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.1466693878173828s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.22013378143310547s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.1734776496887207s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.5986175537109375s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.28798770904541016s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2658834457397461s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.28223252296447754s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.29829740524292s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.9584801197052002s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.32688307762146s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.3063395023345947s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.1579599380493164s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.2801821231842041s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.15963101387023926s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.1490933895111084s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2078.2035672664642s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.4763004779815674s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.022051095962524414s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 6.628036499023438e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.7404556274414062e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 2.6226043701171875e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.1682510375976562e-05s
INFO | --- Analysis for orkg took 2312.0748841762543s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.006901502609253s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.27967190742492676s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.022909164428710938s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 9.250640869140625e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.239776611328125e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 29.996360301971436s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.5453755855560303s
Availability | VoID file availability check for OSM Semantic Network took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.27871108055114746s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.6716461181640625e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.0013580322265625e-05s
INFO | --- Analysis for osm-semantic-network took 8.454009771347046s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.3342432975769043s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00054931640625s
Extra | Recovery of all triples for Open Transport Map @PSNC took 115.18608617782593s
Performance | Total latancy measurement for Open Transport Map @PSNC took 6.102049112319946s
Amount of data | Number of triples check for Open Transport Map @PSNC took 9.25094223022461s
Interoperability | New terms check for Open Transport Map @PSNC took 14.07619595527649s
Versatility | Languages check for Open Transport Map @PSNC took 300.2113938331604s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 1.7706477642059326s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.22968649864196777s
Versatility | Serialization formats check for Open Transport Map @PSNC took 8.66106915473938s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.30079054832458496s
License | MR license check for Open Transport Map @PSNC took 0.21268463134765625s
License | HR license check for Open Transport Map @PSNC took 300.177170753479s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.200941801071167s
Understandability | Number of label check for Open Transport Map @PSNC took 1.3686776161193848s
Understandability | URI regex check for Open Transport Map @PSNC took 0.6596550941467285s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.2079148292541504s
Verifiability | Authors check for Open Transport Map @PSNC took 0.21027779579162598s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.2685811519622803s
Performance | Throughput check for Open Transport Map @PSNC took 11.749167442321777s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 8.96453857421875e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.19767212867736816s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.19472718238830566s
Interlinking | skos check for Open Transport Map @PSNC took 0.43617963790893555s
Interlinking | skos check for Open Transport Map @PSNC took 0.4203643798828125s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 5.202047824859619s
Currency | Creation date check for Open Transport Map @PSNC took 0.513134241104126s
Currency | Modification date check for Open Transport Map @PSNC took 0.23759031295776367s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 151.95785760879517s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.18201804161071777s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.18135547637939453s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.20791220664978027s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 40.36301827430725s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.640549898147583s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.5813612937927246s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.21450114250183105s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 86.28076696395874s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.218087911605835s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 32.51095199584961s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.314723253250122s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 86.56863784790039s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.7122442722320557s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.5502569675445557s
Security | Sign check for Open Transport Map @PSNC took 0.21131205558776855s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 10.36986756324768s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.48888635635375977s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.022247791290283203s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0010690689086914062s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for OTM took 2284.029435634613s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 21.71014404296875s
Availability | VoID file availability check for Pali English Lexicon took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.2994363307952881s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.02119302749633789s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.3855438232421875e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.0728836059570312e-05s
INFO | --- Analysis for pali-english-lexicon took 55.29369807243347s
Availability | SPARQL endpoint availability check for PanLex took 1.794079303741455s
Availability | VoID file availability check for PanLex took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for PanLex took 0.28844594955444336s
Reputation | Calculation of the PageRank for PanLex took 0.02054619789123535s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.200241088867188e-05s
Believability | Calculation of trust value for PanLex took 1.4066696166992188e-05s
INFO | --- Analysis for panlex took 4.445469379425049s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.5299530029296875e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.28515076637268066s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.021767377853393555s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 4.220008850097656e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.239776611328125e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.502335071563721s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.030860185623168945s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.2742021083831787s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.6253204345703125e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 1.0251998901367188e-05s
INFO | --- Analysis for patents-data-gov-uk took 2.6645824909210205s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.7206878662109375e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.2829091548919678s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.695487976074219e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.1682510375976562e-05s
INFO | --- Analysis for pdev-lemon took 4.031865358352661s
Availability | SPARQL endpoint availability check for pdevlemon took 8.606910705566406e-05s
Availability | VoID file availability check for pdevlemon took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.3008439540863037s
Reputation | Calculation of the PageRank for pdevlemon took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.0994415283203125e-05s
Believability | Calculation of trust value for pdevlemon took 1.239776611328125e-05s
INFO | --- Analysis for pdevlemon took 3.3909504413604736s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 8.749961853027344e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008666515350341797s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.29677462577819824s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.021007776260375977s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.52587890625e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.463859558105469e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.0728836059570312e-05s
INFO | --- Analysis for periodo took 18.802966833114624s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.100799560546875e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.34624648094177246s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020973682403564453s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00038361549377441406s
Believability | Calculation of trust value for Personal_Homepages took 1.0728836059570312e-05s
INFO | --- Analysis for personal-homepages took 3.1289148330688477s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.57763671875e-05s
Availability | VoID file availability check for Ontology of University People took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.28826069831848145s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020743846893310547s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.0994415283203125e-05s
Believability | Calculation of trust value for Ontology of University People took 1.1682510375976562e-05s
INFO | --- Analysis for PersonOnto took 2.5453951358795166s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.517233371734619s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.30063295364379883s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.022901058197021484s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3113021850585938e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3589859008789062e-05s
INFO | --- Analysis for PFKHS took 8.0083646774292s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.4728946685791016s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.28780126571655273s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.021045446395874023s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1682510375976562e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2159347534179688e-05s
INFO | --- Analysis for PFRPPH took 8.317224502563477s
Availability | SPARQL endpoint availability check for PGxLOD took 0.40441155433654785s
Availability | VoID file availability check for PGxLOD took 0.0007259845733642578s
Extra | Recovery of all triples for PGxLOD took 1.9088542461395264s
Performance | Total latancy measurement for PGxLOD took 0.8275723457336426s
Amount of data | Number of triples check for PGxLOD took 0.8265857696533203s
Interoperability | New terms check for PGxLOD took 1.943530797958374s
Versatility | Languages check for PGxLOD took 60.23010492324829s
Interpretability | Number of blank nodes check for PGxLOD took 1.5724401473999023s
Interpretability | RDF structures check for PGxLOD took 0.3906593322753906s
Versatility | Serialization formats check for PGxLOD took 0.1922624111175537s
Availability | RDF dump link check for PGxLOD took 15.612114191055298s
License | MR license check for PGxLOD took 0.18199706077575684s
License | HR license check for PGxLOD took 60.2383394241333s
Amount of data | Number of property check for PGxLOD took 0.15521240234375s
Understandability | Number of label check for PGxLOD took 0.9469904899597168s
Understandability | URI regex check for PGxLOD took 0.32256150245666504s
Understandability | Vocabs check for PGxLOD took 0.18457460403442383s
Verifiability | Authors check for PGxLOD took 0.17143988609313965s
Verifiability | Publishers check for PGxLOD took 0.16586923599243164s
Performance | Throughput check for PGxLOD took 10.734805822372437s
Amount of data | Check the number of entities for PGxLOD took 0.11813592910766602s
Verifiability | Contribs. check for PGxLOD took 0.15537095069885254s
Interlinking | sameAs chians check for PGxLOD took 0.27779221534729004s
Interlinking | skos check for PGxLOD took 0.20224452018737793s
Interlinking | skos check for PGxLOD took 0.18398833274841309s
Timeliness | dataset update frequency check for PGxLOD took 0.17267775535583496s
Currency | Creation date check for PGxLOD took 0.31986308097839355s
Currency | Modification date check for PGxLOD took 0.3084909915924072s
Rep.Conc. | URIs length for PGxLOD took 7.032677888870239s
Interoperability | New vocabularies check for PGxLOD took 85.04054856300354s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.16495871543884277s
Accuracy | Check Functional Property for PGxLOD took 0.18069124221801758s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.19495868682861328s
Accuracy | Check Empty annotation labels for PGxLOD took 0.7624642848968506s
Accuracy | Check White space in annotation for PGxLOD took 0.036832571029663086s
Accuracy | Check Datatype consistency for PGxLOD took 0.02762293815612793s
Consistency | Disjoint class check for PGxLOD took 0.17784953117370605s
Consistency | Check Misplaced properties for PGxLOD took 6.679917573928833s
Consistency | Misplaced classes for PGxLOD took 0.30278944969177246s
Consistency | Check Ontology hijacking for PGxLOD took 1.8862967491149902s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.2235221862792969s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.810534238815308s
Conciseness | Check Extensional conciseness for PGxLOD took 0.032421112060546875s
Conciseness | Check Intensional conciseness for PGxLOD took 0.24152183532714844s
Security | Sign check for PGxLOD took 0.17854762077331543s
Availability | Check URIs Dereferenciability for PGxLOD took 2218.6395978927612s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.4983651638031006s
Reputation | Calculation of the PageRank for PGxLOD took 0.021263599395751953s
Interlinking | Calculation of Degree of Connection for PGxLOD took 0.00010013580322265625s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for PGxLOD took 60.09640574455261s
Believability | Calculation of trust value for PGxLOD took 1.1682510375976562e-05s
INFO | --- Analysis for PGxLOD took 3610.3821444511414s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0452628135681152s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007925033569335938s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.28020429611206055s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.021007537841796875s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 5.53131103515625e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.2636184692382812e-05s
INFO | --- Analysis for phoible took 4.754587888717651s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 8.845329284667969e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0009868144989013672s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.3147094249725342s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.021240949630737305s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.743171691894531e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.3113021850585938e-05s
INFO | --- Analysis for PISM took 26.76531744003296s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 7.557868957519531e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2933027744293213s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.02128744125366211s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0008966922760009766s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 0.00011467933654785156s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.1205673217773438e-05s
INFO | --- Analysis for planetdata-project-wiki took 2.628906726837158s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.226698398590088s
Availability | VoID file availability check for digitized plant specimen took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.3042271137237549s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.02085566520690918s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.271766662597656e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.5974044799804688e-05s
INFO | --- Analysis for plant-specimen took 3.860912799835205s
Availability | SPARQL endpoint availability check for Pleiades took 9.036064147949219e-05s
Availability | VoID file availability check for Pleiades took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Pleiades took 0.2916402816772461s
Reputation | Calculation of the PageRank for Pleiades took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.606910705566406e-05s
Believability | Calculation of trust value for Pleiades took 1.2636184692382812e-05s
INFO | --- Analysis for pleiades took 12.941161155700684s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 8.797645568847656e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0008437633514404297s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.28794169425964355s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.409385681152344e-05s
Believability | Calculation of trust value for podorozhnyk.com took 1.1682510375976562e-05s
INFO | --- Analysis for podorozhnyk took 3.2504804134368896s
Availability | SPARQL endpoint availability check for Poképédia took 5.245208740234375e-05s
Availability | VoID file availability check for Poképédia took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Poképédia took 0.3156256675720215s
Reputation | Calculation of the PageRank for Poképédia took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.486343383789062e-05s
Believability | Calculation of trust value for Poképédia took 1.3113021850585938e-05s
INFO | --- Analysis for pokepedia-fr took 2.8530311584472656s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 9.202957153320312e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.28876447677612305s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.724761962890625e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.33514404296875e-05s
INFO | --- Analysis for polymath-virtual-library took 5.866377115249634s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2669641971588135s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0005829334259033203s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 11.022383689880371s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.5807414054870605s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.436861515045166s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.5694143772125244s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2297723293304443s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.3812680244445801s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11468219757080078s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1144564151763916s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12794232368469238s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12108731269836426s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.592526912689209s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1227865219116211s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.15735173225402832s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.25694918632507324s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1144723892211914s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1145012378692627s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1212465763092041s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.776671648025513s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.104873657226562e-05s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12839555740356445s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12905144691467285s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12817931175231934s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12067413330078125s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12857437133789062s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2571892738342285s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.26766204833984375s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.480508089065552s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12595653533935547s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12683868408203125s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1127936840057373s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.1260926723480225s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.19274115562438965s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.818211317062378s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12891554832458496s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.846372127532959s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.532304525375366s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.292487621307373s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.1151602268218994s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.4428586959838867s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11989021301269531s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4858.370989322662s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.6943178176879883s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.02150106430053711s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4.1484832763671875e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.7642974853515625e-05s
Interoperability | Check the re-using of existing vocabs for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.049041748046875e-05s
INFO | --- Analysis for portuguese_prisons_releases took 5109.585897922516s
Availability | SPARQL endpoint availability check for prefix.cc took 8.702278137207031e-05s
Availability | VoID file availability check for prefix.cc took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.29011058807373047s
Reputation | Calculation of the PageRank for prefix.cc took 0.023079633712768555s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.00115966796875s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 5.221366882324219e-05s
Believability | Calculation of trust value for prefix.cc took 1.2636184692382812e-05s
INFO | --- Analysis for prefix-cc took 3.476876735687256s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.4962878227233887s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2748892307281494s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.744529724121094e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.0013580322265625e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 7.28460955619812s
Availability | SPARQL endpoint availability check for PreLex took 7.4529807567596436s
Availability | VoID file availability check for PreLex took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for PreLex took 0.27655458450317383s
Reputation | Calculation of the PageRank for PreLex took 0.020847797393798828s
Interlinking | Calculation of Degree of Connection for PreLex took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.82012939453125e-05s
Believability | Calculation of trust value for PreLex took 1.3589859008789062e-05s
INFO | --- Analysis for prelex took 21.01260805130005s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.20705246925354s
Availability | VoID file availability check for Prelinger Archives took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.30028772354125977s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.170967102050781e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.239776611328125e-05s
INFO | --- Analysis for prelinger_archives took 12.072884559631348s
Availability | SPARQL endpoint availability check for PreMOn took 0.4989511966705322s
Availability | VoID file availability check for PreMOn took 0.0008697509765625s
Completeness | Calculation of interlinking completeness for PreMOn took 0.28752851486206055s
Reputation | Calculation of the PageRank for PreMOn took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for PreMOn took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PreMOn took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for PreMOn took 5.125999450683594e-05s
Believability | Calculation of trust value for PreMOn took 1.0251998901367188e-05s
INFO | --- Analysis for premon took 5.333692312240601s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 8.702278137207031e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.2841212749481201s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.021036148071289062s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.650520324707031e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 9.775161743164062e-06s
INFO | --- Analysis for princeton-library-findingaids took 3.7794885635375977s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.6201164722442627s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006470680236816406s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.30959343910217285s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.049041748046875e-05s
INFO | --- Analysis for PrinParLat took 4.689069747924805s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.3655693531036377s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.2841367721557617s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.653236389160156e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 9.775161743164062e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.357860565185547s
Availability | SPARQL endpoint availability check for Prior Panel took 8.511543273925781e-05s
Availability | VoID file availability check for Prior Panel took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.2960062026977539s
Reputation | Calculation of the PageRank for Prior Panel took 0.020795583724975586s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.361701965332031e-05s
Believability | Calculation of trust value for Prior Panel took 9.775161743164062e-06s
INFO | --- Analysis for Prior_Panel took 2.5824241638183594s
Availability | SPARQL endpoint availability check for ProductDB took 0.7421040534973145s
Availability | VoID file availability check for ProductDB took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for ProductDB took 0.27432799339294434s
Reputation | Calculation of the PageRank for ProductDB took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.081031799316406e-05s
Believability | Calculation of trust value for ProductDB took 9.298324584960938e-06s
INFO | --- Analysis for productdb took 3.900233745574951s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.28771233558654785s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.367134094238281e-05s
Believability | Calculation of trust value for Product Types Ontology took 9.775161743164062e-06s
INFO | --- Analysis for productontology took 3.5585944652557373s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 8.749961853027344e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.2872796058654785s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.021131277084350586s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010776519775390625s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 9.298324584960938e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 6.572805166244507s
Availability | SPARQL endpoint availability check for provenanceweb took 0.0447688102722168s
Availability | VoID file availability check for provenanceweb took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.2915949821472168s
Reputation | Calculation of the PageRank for provenanceweb took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.001004934310913086s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 9.226799011230469e-05s
Believability | Calculation of trust value for provenanceweb took 1.2874603271484375e-05s
INFO | --- Analysis for provenanceweb took 47.67904090881348s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 8.749961853027344e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.28836798667907715s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00010228157043457031s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.2636184692382812e-05s
INFO | --- Analysis for proyectoapadrina took 6.688260078430176s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.55282974243164s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008563995361328125s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.289628267288208s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.021260738372802734s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 5.0067901611328125e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 9.298324584960938e-06s
INFO | --- Analysis for pscs-catalogue took 123.99261450767517s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.172325134277344e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.2842545509338379s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.021099090576171875s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.82012939453125e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.0967254638671875e-05s
INFO | --- Analysis for psh-subject-headings took 3.0737571716308594s
Availability | SPARQL endpoint availability check for Depression took 0.5142965316772461s
Availability | VoID file availability check for Depression took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for Depression took 0.2824537754058838s
Reputation | Calculation of the PageRank for Depression took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for Depression took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Depression took 3.075599670410156e-05s
Believability | Calculation of trust value for Depression took 1.1682510375976562e-05s
INFO | --- Analysis for Psychology took 3.1391210556030273s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.267692565917969e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.28904175758361816s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for PubChem RDF took 1.0728836059570312e-05s
INFO | --- Analysis for PubChem_RDF took 5.725963592529297s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 60.04844379425049s
Availability | VoID file availability check for Public Spending in Greece took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.3407776355743408s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.02153754234313965s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 9.465217590332031e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.1920928955078125e-05s
INFO | --- Analysis for public-spending-in-greece took 147.43098497390747s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.2029585838317871s
Availability | VoID file availability check for Publications Office Authority tables took 0.0006489753723144531s
Extra | Recovery of all triples for Publications Office Authority tables took 221.25505089759827s
Performance | Total latancy measurement for Publications Office Authority tables took 0.5903842449188232s
Amount of data | Number of triples check for Publications Office Authority tables took 49.52561140060425s
Interoperability | New terms check for Publications Office Authority tables took 62.34022903442383s
Versatility | Languages check for Publications Office Authority tables took 300.1174199581146s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 16.746842861175537s
Security | Check HTTPS for Publications Office Authority tables took 0.33031606674194336s
Interpretability | RDF structures check for Publications Office Authority tables took 0.33716249465942383s
Versatility | Serialization formats check for Publications Office Authority tables took 3.5532338619232178s
Availability | RDF dump link check for Publications Office Authority tables took 0.2830221652984619s
License | MR license check for Publications Office Authority tables took 0.3790879249572754s
License | HR license check for Publications Office Authority tables took 300.0561776161194s
Amount of data | Number of property check for Publications Office Authority tables took 0.20343518257141113s
Understandability | Number of label check for Publications Office Authority tables took 1.7198224067687988s
Understandability | URI regex check for Publications Office Authority tables took 0.41633105278015137s
Understandability | Vocabs check for Publications Office Authority tables took 0.09169411659240723s
Verifiability | Authors check for Publications Office Authority tables took 0.11759448051452637s
Verifiability | Publishers check for Publications Office Authority tables took 0.2507023811340332s
Performance | Throughput check for Publications Office Authority tables took 10.303642511367798s
Amount of data | Check the number of entities for Publications Office Authority tables took 7.343292236328125e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.1680622100830078s
Interlinking | sameAs chians check for Publications Office Authority tables took 6.651885032653809s
Interlinking | skos check for Publications Office Authority tables took 0.33072710037231445s
Interlinking | skos check for Publications Office Authority tables took 0.13262152671813965s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.2872457504272461s
Currency | Creation date check for Publications Office Authority tables took 0.7149040699005127s
Currency | Modification date check for Publications Office Authority tables took 0.17363381385803223s
Rep.Conc. | URIs length for Publications Office Authority tables took 411.45288372039795s
Interoperability | New vocabularies check for Publications Office Authority tables took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.16150236129760742s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.24470210075378418s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.14925575256347656s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 38.11634421348572s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.0341131687164307s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.552614688873291s
Consistency | Disjoint class check for Publications Office Authority tables took 0.13502287864685059s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.4127480983734s
Consistency | Misplaced classes for Publications Office Authority tables took 8.18441367149353s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 40.167481422424316s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.77117919921875s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.466504573822s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.0130951404571533s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.38625121116638184s
Security | Sign check for Publications Office Authority tables took 0.2764601707458496s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 11.220679759979248s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.740786075592041s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.021235942840576172s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.9073486328125e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 9.5367431640625e-06s
INFO | --- Analysis for publications_office_authority_tables took 14540.205800294876s
Availability | SPARQL endpoint availability check for QBOAirbase took 8.630752563476562e-05s
Availability | VoID file availability check for QBOAirbase took 0.0008313655853271484s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.29709291458129883s
Reputation | Calculation of the PageRank for QBOAirbase took 0.025332212448120117s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.557868957519531e-05s
Believability | Calculation of trust value for QBOAirbase took 1.2636184692382812e-05s
INFO | --- Analysis for qboairbase took 137.70804619789124s
Availability | SPARQL endpoint availability check for Qualité de l'air took 8.893013000488281e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.29361987113952637s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.021024227142333984s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.0279159545898438e-05s
Believability | Calculation of trust value for Qualité de l'air took 8.106231689453125e-06s
INFO | --- Analysis for Qualité_de_l'air took 2.9939801692962646s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.38690185546875e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.29360365867614746s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.504753112792969e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 7.62939453125e-06s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 52.61676645278931s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.6239941120147705s
Availability | VoID file availability check for Querolus in LiLa took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.27765679359436035s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.02078700065612793s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.4809112548828125e-05s
Believability | Calculation of trust value for Querolus in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for Querolus took 4.253748178482056s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.5686728954315186s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0003819465637207031s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 28.780295848846436s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7024857997894287s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.0274264812469482s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.9699256420135498s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.888152599334717s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.4253993034362793s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13756918907165527s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1565847396850586s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14482474327087402s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1458747386932373s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15981340408325195s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.16022038459777832s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15975236892700195s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.29944276809692383s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14434266090393066s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13525676727294922s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1578357219696045s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.696778535842896s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 8.726119995117188e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13916993141174316s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14352154731750488s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14446568489074707s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14362502098083496s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14484786987304688s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.30164194107055664s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.29356932640075684s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 26.835793256759644s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15331768989562988s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12905192375183105s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14105820655822754s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15654897689819336s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.170967102050781e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.0603110790252686s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14610743522644043s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.120807647705078s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.848964214324951s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.368903398513794s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.546562910079956s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.7842326164245605s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15130186080932617s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.789694786071777s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.29642295837402344s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.02097177505493164s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.7697296142578125e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.6689300537109375e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1920928955078125e-05s
INFO | --- Analysis for racai-legalnero took 163.33777260780334s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 0.00010085105895996094s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0004036426544189453s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.29425835609436035s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 2.8848648071289062e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.2636184692382812e-05s
INFO | --- Analysis for racai-llod-corola-we took 2.941007137298584s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.15618085861206055s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0006542205810546875s
Extra | Recovery of all triples for PARSEME-Ro corpus took 30.69506072998047s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.7347180843353271s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.864421606063843s
Interoperability | New terms check for PARSEME-Ro corpus took 2.125086784362793s
Versatility | Languages check for PARSEME-Ro corpus took 17.800959825515747s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.4176552295684814s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.15306544303894043s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.1314530372619629s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.15192079544067383s
License | MR license check for PARSEME-Ro corpus took 0.14322662353515625s
License | HR license check for PARSEME-Ro corpus took 10.153798818588257s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.140183687210083s
Understandability | Number of label check for PARSEME-Ro corpus took 0.20295166969299316s
Understandability | URI regex check for PARSEME-Ro corpus took 0.2822756767272949s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.13051271438598633s
Verifiability | Authors check for PARSEME-Ro corpus took 0.14099788665771484s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.14215612411499023s
Performance | Throughput check for PARSEME-Ro corpus took 10.926045894622803s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 0.00012350082397460938s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.154266357421875s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.15372610092163086s
Interlinking | skos check for PARSEME-Ro corpus took 0.13214731216430664s
Interlinking | skos check for PARSEME-Ro corpus took 0.14259624481201172s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.14297771453857422s
Currency | Creation date check for PARSEME-Ro corpus took 0.287564754486084s
Currency | Modification date check for PARSEME-Ro corpus took 0.2962331771850586s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 78.7016658782959s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.14310312271118164s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.1422727108001709s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.14170360565185547s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 1.9821219444274902s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.23065757751464844s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 3.9115488529205322s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.13501524925231934s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 11.194535732269287s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 28.910979509353638s
Consistency | Check Invalid usage of undefined classes for PARSEME-Ro corpus took 1.5467867851257324s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 12.818843841552734s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 2.772158145904541s
Security | Sign check for PARSEME-Ro corpus took 0.15190863609313965s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.457777500152588s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.3562304973602295s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.021426916122436523s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0008876323699951172s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 2.86102294921875e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.1444091796875e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 278.1788721084595s
Availability | SPARQL endpoint availability check for RoLEX took 0.1316828727722168s
Availability | VoID file availability check for RoLEX took 0.0005433559417724609s
Extra | Recovery of all triples for RoLEX took 34.20717644691467s
Performance | Total latancy measurement for RoLEX took 0.7375493049621582s
Amount of data | Number of triples check for RoLEX took 1.609741449356079s
Interoperability | New terms check for RoLEX took 1.663599967956543s
Versatility | Languages check for RoLEX took 4.186218976974487s
Interpretability | Number of blank nodes check for RoLEX took 1.0769729614257812s
Interpretability | RDF structures check for RoLEX took 0.14437103271484375s
Versatility | Serialization formats check for RoLEX took 0.15466618537902832s
Availability | RDF dump link check for RoLEX took 0.1325531005859375s
License | MR license check for RoLEX took 0.14321541786193848s
License | HR license check for RoLEX took 0.1546182632446289s
Amount of data | Number of property check for RoLEX took 0.152846097946167s
Understandability | Number of label check for RoLEX took 0.1583404541015625s
Understandability | URI regex check for RoLEX took 0.296708345413208s
Understandability | Vocabs check for RoLEX took 0.13161182403564453s
Verifiability | Authors check for RoLEX took 0.14345359802246094s
Verifiability | Publishers check for RoLEX took 0.13059592247009277s
Performance | Throughput check for RoLEX took 10.89456820487976s
Amount of data | Check the number of entities for RoLEX took 6.937980651855469e-05s
Verifiability | Contribs. check for RoLEX took 0.14270520210266113s
Interlinking | sameAs chians check for RoLEX took 0.13117313385009766s
Interlinking | skos check for RoLEX took 0.13155245780944824s
Interlinking | skos check for RoLEX took 0.14245843887329102s
Timeliness | dataset update frequency check for RoLEX took 0.1433546543121338s
Currency | Creation date check for RoLEX took 0.2850792407989502s
Currency | Modification date check for RoLEX took 0.28627729415893555s
Rep.Conc. | URIs length for RoLEX took 52.50346255302429s
Interoperability | New vocabularies check for RoLEX took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.14083027839660645s
Accuracy | Check Functional Property for RoLEX took 0.1356823444366455s
Accuracy | Check Inverse Functional Property for RoLEX took 0.14161348342895508s
Accuracy | Check Datatype consistency for RoLEX took 3.9971024990081787s
Consistency | Disjoint class check for RoLEX took 0.14486217498779297s
Consistency | Check Misplaced properties for RoLEX took 2.535956859588623s
Consistency | Check Ontology hijacking for RoLEX took 8.325540542602539s
Consistency | Check Invalid usage of undefined classes for RoLEX took 1.828986644744873s
Consistency | Check Invalid usage of undefined properties for RoLEX took 3.7909605503082275s
Conciseness | Check Extensional conciseness for RoLEX took 3.002269983291626s
Security | Sign check for RoLEX took 0.13192319869995117s
Availability | Check URIs Dereferenciability for RoLEX took 7.320697069168091s
Completeness | Calculation of interlinking completeness for RoLEX took 0.43824338912963867s
Reputation | Calculation of the PageRank for RoLEX took 0.02094101905822754s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for RoLEX took 2.9802322387695312e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 1.430511474609375e-06s
Believability | Calculation of trust value for RoLEX took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-rolex took 169.5138247013092s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 9.179115295410156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2978525161743164s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020781278610229492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.0517578125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.0728836059570312e-05s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.867788076400757s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.315376281738281e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.2877194881439209s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.022140979766845703s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.2901763916015625e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 4.5299530029296875e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.78485369682312s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.3392181396484375e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.28481101989746094s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 2.9325485229492188e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 5.245208740234375e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.757017135620117s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.315376281738281e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0010352134704589844s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.2738325595855713s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 2.956390380859375e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.239776611328125e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.9060354232788086s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.1485004425048828s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.00036334991455078125s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 9.470206260681152s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.7304625511169434s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.3151867389678955s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.4422087669372559s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.6507489681243896s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.28328943252563477s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.15477991104125977s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.15429425239562988s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.15626001358032227s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.1459522247314453s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.14881610870361328s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.1304006576538086s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.14946579933166504s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.2825038433074951s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.14251446723937988s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.14537549018859863s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.131270170211792s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 10.749891996383667s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 0.00010943412780761719s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.14299321174621582s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.15598344802856445s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.1430373191833496s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.14406704902648926s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.14347171783447266s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.2860233783721924s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.2871556282043457s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.509352684020996s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.1526787281036377s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.14284610748291016s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.14244532585144043s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.39029717445373535s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009571552276611328s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.2307376861572266s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.15196943283081055s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.49896812438964844s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.033682107925415s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.2773022651672363s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.6514782905578613s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.8281030654907227s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.13950276374816895s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 7.245352268218994s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.3095834255218506s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020995616912841797s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 3.0994415283203125e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 1.6689300537109375e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.049041748046875e-05s
INFO | --- Analysis for racai-llod-rtasc took 63.349533796310425s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.15498614311218262s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0005791187286376953s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 33.407081604003906s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.6922745704650879s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.124969482421875s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.4643118381500244s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.4257826805114746s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.8309531211853027s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.14354681968688965s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.14312410354614258s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.14114856719970703s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.14229631423950195s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.5012452602386475s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.13074874877929688s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.14789748191833496s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.27522754669189453s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.1433424949645996s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.14530634880065918s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.14455151557922363s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 11.026416063308716s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 6.985664367675781e-05s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.15366053581237793s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.14127779006958008s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.15401291847229004s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.15301203727722168s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.15291261672973633s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.28567981719970703s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.2844886779785156s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.218709707260132s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.12902569770812988s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.14028263092041016s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.1518101692199707s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.7241671085357666s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.019369125366210938s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 4.01031231880188s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.15387845039367676s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.6770215034484863s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.503780841827393s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.3176047801971436s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.763216018676758s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 2.900106430053711s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.1278517246246338s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 1564.6659750938416s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.5167460441589355s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.0211181640625s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 6.127357482910156e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 1.6689300537109375e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.1205673217773438e-05s
INFO | --- Analysis for racai-llod-simonero took 1667.3378279209137s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.12725567817687988s
Availability | VoID file availability check for Rådata nå! took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2868521213531494s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020970582962036133s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.130073547363281e-05s
Believability | Calculation of trust value for Rådata nå! took 1.1920928955078125e-05s
INFO | --- Analysis for radatana took 4.581629753112793s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 8.749961853027344e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.29975414276123047s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.02134418487548828s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.910064697265625e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.0251998901367188e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 17.72202706336975s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 13.293543577194214s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.2999446392059326s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02213883399963379s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.337860107421875e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.0728836059570312e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 28.399312019348145s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 392.82498931884766s
Availability | VoID file availability check for Polish LGU financial statements took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.3084433078765869s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 4.267692565917969e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 6.9141387939453125e-06s
INFO | --- Analysis for Rb_PL_LGU took 665.7583701610565s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 9.131431579589844e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.30008721351623535s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.021347999572753906s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.559226989746094e-05s
Believability | Calculation of trust value for RDF Book Mashup took 9.5367431640625e-06s
INFO | --- Analysis for rdf-book-mashup took 3.6229476928710938s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 8.749961853027344e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.2984778881072998s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.022294282913208008s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010156631469726562s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 1.239776611328125e-05s
INFO | --- Analysis for rdfize-lastfm took 2.7464160919189453s
Availability | SPARQL endpoint availability check for RDFLicense took 260.9140028953552s
Availability | VoID file availability check for RDFLicense took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.31338000297546387s
Reputation | Calculation of the PageRank for RDFLicense took 0.02164483070373535s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.7670135498046875e-05s
Believability | Calculation of trust value for RDFLicense took 1.0251998901367188e-05s
INFO | --- Analysis for rdflicense took 535.9240627288818s
Availability | SPARQL endpoint availability check for RDFohloh took 8.749961853027344e-05s
Availability | VoID file availability check for RDFohloh took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.2913520336151123s
Reputation | Calculation of the PageRank for RDFohloh took 0.021082639694213867s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.1552734375e-05s
Believability | Calculation of trust value for RDFohloh took 9.5367431640625e-06s
INFO | --- Analysis for rdfohloh took 6.8831727504730225s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.7009732723236084s
Availability | VoID file availability check for Reactome RDF took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.28548264503479004s
Reputation | Calculation of the PageRank for Reactome RDF took 0.022027969360351562s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for Reactome RDF took 1.049041748046875e-05s
INFO | --- Analysis for reactome-rdf took 4.071344375610352s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.11583757400512695s
Availability | VoID file availability check for Rechtspraak.nl took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.2902872562408447s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.021303653717041016s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 0.00010323524475097656s
Believability | Calculation of trust value for Rechtspraak.nl took 1.0013580322265625e-05s
INFO | --- Analysis for rechtspraak took 2.8128559589385986s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 8.702278137207031e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2894477844238281s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.020833969116210938s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.96453857421875e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.1920928955078125e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 6.253314733505249s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.03258490562438965s
Availability | VoID file availability check for reference.data.gov.uk took 0.0013248920440673828s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2880537509918213s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00014972686767578125s
Believability | Calculation of trust value for reference.data.gov.uk took 8.58306884765625e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.675539255142212s
Availability | SPARQL endpoint availability check for RELD took 0.5813248157501221s
Availability | VoID file availability check for RELD took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for RELD took 0.3453526496887207s
Reputation | Calculation of the PageRank for RELD took 0.021974802017211914s
Interlinking | Calculation of Degree of Connection for RELD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for RELD took 2.765655517578125e-05s
Believability | Calculation of trust value for RELD took 1.0728836059570312e-05s
INFO | --- Analysis for RELD took 13.59955883026123s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.17926287651062012s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.000568389892578125s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.0183088779449463s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.3948531150817871s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.3097846508026123s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.6608788967132568s
Versatility | Languages check for Repository for Linked Open Archival Data took 18.798389673233032s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 12.395822286605835s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.19936323165893555s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.2336423397064209s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.23884320259094238s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.14636707305908203s
License | MR license check for Repository for Linked Open Archival Data took 0.340801477432251s
License | HR license check for Repository for Linked Open Archival Data took 8.593597412109375s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.11888527870178223s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.7893941402435303s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.3786633014678955s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.11193633079528809s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.13911890983581543s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.1842951774597168s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.575166702270508s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 3.314018249511719e-05s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.057227373123168945s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.10602211952209473s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.19412589073181152s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.07141971588134766s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.22908401489257812s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.14960479736328125s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.15914154052734375s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.929880380630493s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.10913991928100586s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.11565256118774414s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.09845232963562012s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.4023129940032959s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.0281069278717041s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.0278623104095459s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.19449496269226074s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 2.0571558475494385s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.22013497352600098s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.523888349533081s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.2672624588012695s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.1281299591064453s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.03825068473815918s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.14358091354370117s
Security | Sign check for Repository for Linked Open Archival Data took 0.393435001373291s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 969.9330775737762s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.5421009063720703s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.02141857147216797s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 0.0001513957977294922s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.6689300537109375e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.1205673217773438e-05s
INFO | --- Analysis for reload took 1109.8589887619019s
Availability | SPARQL endpoint availability check for Land use merced dataset took 8.58306884765625e-05s
Availability | VoID file availability check for Land use merced dataset took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.288707971572876s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 2.7894973754882812e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.0728836059570312e-05s
INFO | --- Analysis for remote_Sensing took 3.2821974754333496s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.7503082752227783s
Availability | VoID file availability check for Renewable Energy Generators took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.26987338066101074s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.3392181396484375e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 8.58306884765625e-06s
INFO | --- Analysis for renewable_energy_generators took 10.960854053497314s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.03977847099304199s
Availability | VoID file availability check for research.data.gov.uk took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.31677865982055664s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.022914409637451172s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.417533874511719e-05s
Believability | Calculation of trust value for research.data.gov.uk took 9.059906005859375e-06s
INFO | --- Analysis for research-data-gov-uk took 2.790994882583618s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 8.368492126464844e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.2875838279724121s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 7.867813110351562e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 1.0728836059570312e-05s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 4.302359104156494s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.05886435508728027s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.2864396572113037s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.02213454246520996s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.0279159545898438e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.1444091796875e-05s
INFO | --- Analysis for revistas_turismo took 2.8286690711975098s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.2836427688598633s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2942690849304199s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00010991096496582031s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.1444091796875e-05s
INFO | --- Analysis for revyu took 2.918577194213867s
Availability | SPARQL endpoint availability check for sdafsadf took 0.3442678451538086s
Availability | VoID file availability check for sdafsadf took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.29761576652526855s
Reputation | Calculation of the PageRank for sdafsadf took 0.020863056182861328s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.075599670410156e-05s
Believability | Calculation of trust value for sdafsadf took 1.430511474609375e-05s
INFO | --- Analysis for rgsdfg took 3.4775912761688232s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 8.559226989746094e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007524490356445312s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.302471399307251s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.9591064453125e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 8.106231689453125e-06s
INFO | --- Analysis for riese took 22.877673864364624s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.3712277412414551s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0006384849548339844s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 25.13016414642334s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.47259521484375s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 52.75895309448242s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 1.9868688583374023s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 152.01887345314026s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 48.703017234802246s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.23020219802856445s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.17863798141479492s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.14921021461486816s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.09423422813415527s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.13458871841430664s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.01676392555237s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 0.1474456787109375s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 11.602893590927124s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.24444317817687988s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.11233997344970703s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.10152697563171387s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.10824799537658691s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.589697122573853s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 7.987022399902344e-05s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.11497068405151367s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.314061164855957s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.17086267471313477s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.14061355590820312s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.11927461624145508s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.23548126220703125s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.23285126686096191s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 78.47096729278564s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.15161418914794922s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 0.11892485618591309s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.12224245071411133s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 11.200857877731323s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.3647401332855225s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.74924635887146s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.09752678871154785s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 47.07637286186218s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 5.679650783538818s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.2839431762695312s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 47.12227940559387s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.694199562072754s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.11322355270385742s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 1.599353551864624s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.4257376194000244s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.021382808685302734s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 5.4836273193359375e-05s
Interoperability | Check the re-using of existing vocabs for Répertoire International des Sources Musicales - RISM took 2.1457672119140625e-06s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 1.0251998901367188e-05s
INFO | --- Analysis for rism took 1026.42165184021s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.09819507598876953s
Availability | VoID file availability check for RISM Authority data took 0.0006434917449951172s
Extra | Recovery of all triples for RISM Authority data took 23.589186906814575s
Performance | Total latancy measurement for RISM Authority data took 0.49817657470703125s
Amount of data | Number of triples check for RISM Authority data took 52.49423170089722s
Interoperability | New terms check for RISM Authority data took 1.8430571556091309s
Versatility | Languages check for RISM Authority data took 160.8557481765747s
Interpretability | Number of blank nodes check for RISM Authority data took 52.49924659729004s
Security | Check HTTPS for RISM Authority data took 0.1426389217376709s
Interpretability | RDF structures check for RISM Authority data took 0.14066457748413086s
Versatility | Serialization formats check for RISM Authority data took 0.12356209754943848s
Availability | RDF dump link check for RISM Authority data took 0.09066128730773926s
License | MR license check for RISM Authority data took 0.08423995971679688s
License | HR license check for RISM Authority data took 300.03953647613525s
Amount of data | Number of property check for RISM Authority data took 0.12441396713256836s
Understandability | Number of label check for RISM Authority data took 6.785333633422852s
Understandability | URI regex check for RISM Authority data took 0.23169875144958496s
Understandability | Vocabs check for RISM Authority data took 0.09088301658630371s
Verifiability | Authors check for RISM Authority data took 0.0968935489654541s
Verifiability | Publishers check for RISM Authority data took 0.09767985343933105s
Performance | Throughput check for RISM Authority data took 10.601794481277466s
Amount of data | Check the number of entities for RISM Authority data took 8.082389831542969e-05s
Verifiability | Contribs. check for RISM Authority data took 0.09414458274841309s
Interlinking | sameAs chians check for RISM Authority data took 1.509880781173706s
Interlinking | skos check for RISM Authority data took 0.13687467575073242s
Interlinking | skos check for RISM Authority data took 0.09856748580932617s
Timeliness | dataset update frequency check for RISM Authority data took 0.10930180549621582s
Currency | Creation date check for RISM Authority data took 0.225006103515625s
Currency | Modification date check for RISM Authority data took 0.21577239036560059s
Rep.Conc. | URIs length for RISM Authority data took 75.36858773231506s
Interoperability | New vocabularies check for RISM Authority data took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.15259289741516113s
Accuracy | Check Functional Property for RISM Authority data took 0.1334679126739502s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.10920190811157227s
Accuracy | Check Empty annotation labels for RISM Authority data took 17.2184054851532s
Accuracy | Check White space in annotation for RISM Authority data took 2.3713059425354004s
Accuracy | Check Datatype consistency for RISM Authority data took 3.7959070205688477s
Consistency | Disjoint class check for RISM Authority data took 0.10781669616699219s
Consistency | Check Misplaced properties for RISM Authority data took 47.30403232574463s
Consistency | Check Ontology hijacking for RISM Authority data took 4.7794671058654785s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.2921006679534912s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 45.47876739501953s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.802509069442749s
Security | Sign check for RISM Authority data took 0.09648919105529785s
Availability | Check URIs Dereferenciability for RISM Authority data took 1.4553813934326172s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.6229736804962158s
Reputation | Calculation of the PageRank for RISM Authority data took 0.021113157272338867s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for RISM Authority data took 1.9073486328125e-06s
Believability | Calculation of trust value for RISM Authority data took 8.344650268554688e-06s
INFO | --- Analysis for rism-authorities took 1236.3165328502655s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 8.869171142578125e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2978808879852295s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.3113021850585938e-05s
INFO | --- Analysis for rk took 2.6275460720062256s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.06103181838989258s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.2880821228027344s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.021390438079833984s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002319812774658203s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-acm took 2.77897310256958s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.02659749984741211s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.28031015396118164s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00013399124145507812s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.643913984298706s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.02727198600769043s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.31581974029541016s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.0001964569091796875s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 2.750328540802002s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0284116268157959s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.277756929397583s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.02307724952697754s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0008335113525390625s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00018525123596191406s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-cordis took 2.647038698196411s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.04275202751159668s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.2762463092803955s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.023077726364135742s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00015306472778320312s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-courseware took 2.7087128162384033s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.02624797821044922s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.28703856468200684s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.981590270996094e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-crime took 2.6899349689483643s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0316462516784668s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2972126007080078s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0009906291961669922s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00013303756713867188s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 2.6173014640808105s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.042357683181762695s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.2769296169281006s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0009365081787109375s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.936622619628906e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 2.0503997802734375e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.6781160831451416s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.027317285537719727s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.2799794673919678s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00022459030151367188s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-dblp took 2.6920793056488037s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.05233883857727051s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.3010251522064209s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.081031799316406e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.720492124557495s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.3614475727081299s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2976109981536865s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.021067142486572266s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.083747863769531e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-deploy took 4.210961580276489s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.02686905860900879s
Availability | VoID file availability check for digitaleconomy took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.287672758102417s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 2.8133392333984375e-05s
Believability | Calculation of trust value for digitaleconomy took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.735771894454956s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.026582717895507812s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.3078601360321045s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014328956604003906s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-dotac took 2.750120162963867s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.028593063354492188s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2922680377960205s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02080535888671875s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.458427429199219e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-ecs took 3.229308843612671s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.03738212585449219s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.2653841972351074s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00017690658569335938s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.745791435241699s
Availability | SPARQL endpoint availability check for epsrc took 0.026105165481567383s
Availability | VoID file availability check for epsrc took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for epsrc took 0.286395788192749s
Reputation | Calculation of the PageRank for epsrc took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for epsrc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.4836273193359375e-05s
Believability | Calculation of trust value for epsrc took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 2.6621346473693848s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.042231082916259766s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.2971038818359375s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.021640539169311523s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.249282836914062e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-era took 2.722346067428589s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.0413358211517334s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.28496313095092773s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010251998901367188s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 2.741201400756836s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.33965349197387695s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.2972266674041748s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020858049392700195s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.918212890625e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-ft took 4.156969308853149s
Availability | SPARQL endpoint availability check for fun took 0.026685237884521484s
Availability | VoID file availability check for fun took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for fun took 0.2868359088897705s
Reputation | Calculation of the PageRank for fun took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for fun took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for fun took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for fun took 6.747245788574219e-05s
Believability | Calculation of trust value for fun took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-fun took 2.640604019165039s
Availability | SPARQL endpoint availability check for gdlc took 0.027420997619628906s
Availability | VoID file availability check for gdlc took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for gdlc took 0.27582383155822754s
Reputation | Calculation of the PageRank for gdlc took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.341934204101562e-05s
Believability | Calculation of trust value for gdlc took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 2.637990713119507s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.02791905403137207s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.2984304428100586s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011610984802246094s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.6928951740264893s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.02712392807006836s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2789430618286133s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001361370086669922s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.6894969940185547s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02318716049194336s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.28508591651916504s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02097797393798828s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0001342296600341797s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.6381824016571045s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.03374052047729492s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.30084729194641113s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.151199340820312e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-italy took 2.703606367111206s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.03187870979309082s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.00032401084899902344s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.27306294441223145s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.390975952148438e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.658465623855591s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.04171562194824219s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.27297329902648926s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.02137613296508789s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.1961669921875e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 2.727443218231201s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.03644371032714844s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.28815770149230957s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.021971702575683594s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00015735626220703125s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.7143781185150146s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.027174711227416992s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.2755317687988281s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020773649215698242s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.0001423358917236328s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-laas took 2.6553831100463867s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0338749885559082s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.3129451274871826s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.020287513732910156s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.175041198730469e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.726803779602051s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.04405808448791504s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.28679871559143066s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015401840209960938s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.693434476852417s
Availability | SPARQL endpoint availability check for notube took 0.026195049285888672s
Availability | VoID file availability check for notube took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for notube took 0.26424169540405273s
Reputation | Calculation of the PageRank for notube took 0.026830673217773438s
Interlinking | Calculation of Degree of Connection for notube took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for notube took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for notube took 4.982948303222656e-05s
Believability | Calculation of trust value for notube took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.6936912536621094s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.03963875770568848s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.2985055446624756s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.0001285076141357422s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-nsf took 2.7252118587493896s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.02635502815246582s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.27414751052856445s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0001518726348876953s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-oai took 2.6088812351226807s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.03687334060668945s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.3015720844268799s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.022836923599243164s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0010175704956054688s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 0.00011610984802246094s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-os took 2.746030569076538s
Availability | SPARQL endpoint availability check for photos took 0.02768421173095703s
Availability | VoID file availability check for photos took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for photos took 0.3003723621368408s
Reputation | Calculation of the PageRank for photos took 0.02071356773376465s
Interlinking | Calculation of Degree of Connection for photos took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for photos took 0.0009801387786865234s
Interlinking | Calculation of Clustering coefficient for photos took 8.916854858398438e-05s
Believability | Calculation of trust value for photos took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.6889572143554688s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.037232160568237305s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.00032520294189453125s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.292433500289917s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.021615028381347656s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011205673217773438s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-pisa took 2.7084085941314697s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.04581737518310547s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.28946852684020996s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.021405696868896484s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00018930435180664062s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.7421913146972656s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.034210920333862305s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.3043229579925537s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0008795261383056641s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00019073486328125s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-resex took 2.872312068939209s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.06165957450866699s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.00048828125s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.4490323066711426s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.021806716918945312s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.202957153320312e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-risks took 4.254331111907959s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0632021427154541s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.4935436248779297s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.02245926856994629s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.000125885009765625s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-roma took 4.1468634605407715s
Availability | SPARQL endpoint availability check for roni took 0.04024767875671387s
Availability | VoID file availability check for roni took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for roni took 0.3036031723022461s
Reputation | Calculation of the PageRank for roni took 0.020987510681152344s
Interlinking | Calculation of Degree of Connection for roni took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for roni took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for roni took 3.0994415283203125e-05s
Believability | Calculation of trust value for roni took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-roni took 3.0642812252044678s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.027878522872924805s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.3172318935394287s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0210416316986084s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002143383026123047s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.7539286613464355s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.041056156158447266s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00041675567626953125s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.30292487144470215s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.02243947982788086s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010561943054199219s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-ulm took 2.725329875946045s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.0406346321105957s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.3030967712402344s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.02133941650390625s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.560585021972656e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-unlocode took 2.7744393348693848s
Availability | SPARQL endpoint availability check for webconf took 0.025804758071899414s
Availability | VoID file availability check for webconf took 0.0003743171691894531s
Completeness | Calculation of interlinking completeness for webconf took 0.3003113269805908s
Reputation | Calculation of the PageRank for webconf took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for webconf took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010037422180175781s
Believability | Calculation of trust value for webconf took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-webconf took 22.741056442260742s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.03964734077453613s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.27527928352355957s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.02277684211730957s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.176399230957031e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-webscience took 2.6701481342315674s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.04080367088317871s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.29848337173461914s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.02178502082824707s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00020241737365722656s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-wiki took 2.7091660499572754s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.04003548622131348s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.29770803451538086s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.021367788314819336s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.250640869140625e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-wordnet took 2.6951794624328613s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.3023402690887451s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0005145072937011719s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 39.46119689941406s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.43955063819885254s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.4522454738616943s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.617760419845581s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 4.407867431640625s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.2418038845062256s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.08967041969299316s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.08816146850585938s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.08570981025695801s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.09407925605773926s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.0949099063873291s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.08514547348022461s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.1009979248046875s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.17086148262023926s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.0788884162902832s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.09466671943664551s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.0946192741394043s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.47001838684082s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 8.225440979003906e-05s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.1218876838684082s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.09413027763366699s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.07999300956726074s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.09364938735961914s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.09547185897827148s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.1819155216217041s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.15980982780456543s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 19.163127660751343s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.11436581611633301s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.1065526008605957s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.08076763153076172s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.819826364517212s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.08775877952575684s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 2.950491428375244s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 5.818185329437256s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.3739714622497559s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.047502517700195s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 2.981682300567627s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.07793784141540527s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 1.1170222759246826s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.3259158134460449s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02116084098815918s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 7.748603820800781e-05s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 2.1457672119140625e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.1682510375976562e-05s
INFO | --- Analysis for roceeh-road took 124.38177013397217s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 8.7738037109375e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.29137492179870605s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 4.124641418457031e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.1920928955078125e-05s
INFO | --- Analysis for ROSHANI took 5.134097576141357s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.3392181396484375e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.2905702590942383s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.2901763916015625e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 1.1444091796875e-05s
INFO | --- Analysis for ROSHANI_SAHU took 2.6714577674865723s
Availability | SPARQL endpoint availability check for x took 8.559226989746094e-05s
Availability | VoID file availability check for x took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for x took 0.3071298599243164s
Reputation | Calculation of the PageRank for x took 0.023723363876342773s
Interlinking | Calculation of Degree of Connection for x took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for x took 0.002250194549560547s
Interlinking | Calculation of Clustering coefficient for x took 6.532669067382812e-05s
Believability | Calculation of trust value for x took 9.775161743164062e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.6264913082122803s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 9.059906005859375e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.3020906448364258s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.022000789642333984s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 0.00010156631469726562s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 1.0728836059570312e-05s
INFO | --- Analysis for rss-500-nif-ner-corpus took 4.595155239105225s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.57763671875e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.3088812828063965s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.021180391311645508s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.43865966796875e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 8.106231689453125e-06s
INFO | --- Analysis for rubentaelman took 3.104900598526001s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.267692565917969e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.29058003425598145s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.273124694824219e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 7.867813110351562e-06s
INFO | --- Analysis for rubenverborgh took 3.1996803283691406s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 391.7349350452423s
Availability | VoID file availability check for Russian Universities Specialities took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.3341093063354492s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.02113199234008789s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.220008850097656e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 9.5367431640625e-06s
INFO | --- Analysis for russian-universities-specialities took 676.9874632358551s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.052397012710571s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.27620816230773926s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 2.9325485229492188e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 1.049041748046875e-05s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 8.77872085571289s
Availability | SPARQL endpoint availability check for SALDO-RDF took 0.9790802001953125s
Availability | VoID file availability check for SALDO-RDF took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.3011171817779541s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.022665739059448242s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.4332275390625e-05s
Believability | Calculation of trust value for SALDO-RDF took 1.0251998901367188e-05s
INFO | --- Analysis for saldo-rdf took 5.846261262893677s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6397333145141602s
Availability | VoID file availability check for SALDOM-RDF took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2777731418609619s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.021067142486572266s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for SALDOM-RDF took 1.3113021850585938e-05s
INFO | --- Analysis for saldom-rdf took 4.998788595199585s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 8.678436279296875e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2895188331604004s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02153325080871582s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0009951591491699219s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00012445449829101562s
Believability | Calculation of trust value for Salzburgerland DE took 1.239776611328125e-05s
INFO | --- Analysis for salzburgerland-com-de took 3.2708115577697754s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 0.00011110305786132812s
Availability | VoID file availability check for Salzburgerland EN took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.2902491092681885s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00010514259338378906s
Believability | Calculation of trust value for Salzburgerland EN took 1.239776611328125e-05s
INFO | --- Analysis for salzburgerland-com-en took 3.085430860519409s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.3392181396484375e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.00048828125s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.2992384433746338s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.02119159698486328s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010704994201660156s
Believability | Calculation of trust value for Salzburgerland IT took 9.5367431640625e-06s
INFO | --- Analysis for salzburgerland-com-it took 3.3233370780944824s
Availability | SPARQL endpoint availability check for sandrart.net took 0.00016450881958007812s
Availability | VoID file availability check for sandrart.net took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.28627848625183105s
Reputation | Calculation of the PageRank for sandrart.net took 0.021405458450317383s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.818771362304688e-05s
Believability | Calculation of trust value for sandrart.net took 9.775161743164062e-06s
INFO | --- Analysis for sandrart-net took 4.30091404914856s
Availability | SPARQL endpoint availability check for Taxons  took 0.24488472938537598s
Availability | VoID file availability check for Taxons  took 0.0011296272277832031s
Extra | Recovery of all triples for Taxons  took 19.26569151878357s
Performance | Total latancy measurement for Taxons  took 0.4478001594543457s
Amount of data | Number of triples check for Taxons  took 1.9340975284576416s
Interoperability | New terms check for Taxons  took 1.7726225852966309s
Versatility | Languages check for Taxons  took 43.773382902145386s
Interpretability | Number of blank nodes check for Taxons  took 1.049746036529541s
Security | Check HTTPS for Taxons  took 0.1907634735107422s
Interpretability | RDF structures check for Taxons  took 1.2776358127593994s
Versatility | Serialization formats check for Taxons  took 0.5503251552581787s
Availability | RDF dump link check for Taxons  took 0.317781925201416s
License | MR license check for Taxons  took 2.0057857036590576s
License | HR license check for Taxons  took 2.084859609603882s
Amount of data | Number of property check for Taxons  took 0.12347269058227539s
Understandability | Number of label check for Taxons  took 3.432737112045288s
Understandability | URI regex check for Taxons  took 0.9746639728546143s
Understandability | Vocabs check for Taxons  took 0.2699100971221924s
Verifiability | Authors check for Taxons  took 0.09951424598693848s
Verifiability | Publishers check for Taxons  took 0.08020377159118652s
Performance | Throughput check for Taxons  took 10.463824033737183s
Amount of data | Check the number of entities for Taxons  took 7.390975952148438e-05s
Verifiability | Contribs. check for Taxons  took 0.08147144317626953s
Interlinking | sameAs chians check for Taxons  took 0.15316462516784668s
Interlinking | skos check for Taxons  took 0.17100811004638672s
Interlinking | skos check for Taxons  took 0.08124351501464844s
Timeliness | dataset update frequency check for Taxons  took 0.5922701358795166s
Currency | Creation date check for Taxons  took 0.20009875297546387s
Currency | Modification date check for Taxons  took 0.2014484405517578s
Rep.Conc. | URIs length for Taxons  took 7.609026908874512s
Interoperability | New vocabularies check for Taxons  took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.10425782203674316s
Accuracy | Check Functional Property for Taxons  took 0.6356513500213623s
Accuracy | Check Inverse Functional Property for Taxons  took 0.46568751335144043s
Accuracy | Check Empty annotation labels for Taxons  took 3.9404959678649902s
Accuracy | Check White space in annotation for Taxons  took 0.30209875106811523s
Accuracy | Check Datatype consistency for Taxons  took 0.2637913227081299s
Consistency | Disjoint class check for Taxons  took 0.12452840805053711s
Consistency | Check Misplaced properties for Taxons  took 4.0359861850738525s
Consistency | Misplaced classes for Taxons  took 0.9518210887908936s
Consistency | Check Ontology hijacking for Taxons  took 4.135117053985596s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.271787166595459s
Consistency | Check Invalid usage of undefined properties for Taxons  took 11.318521976470947s
Conciseness | Check Extensional conciseness for Taxons  took 0.2824716567993164s
Security | Sign check for Taxons  took 10.003444194793701s
Availability | Check URIs Dereferenciability for Taxons  took 1757.2444384098053s
Completeness | Calculation of interlinking completeness for Taxons  took 0.5045723915100098s
Reputation | Calculation of the PageRank for Taxons  took 0.021821975708007812s
Interlinking | Calculation of Degree of Connection for Taxons  took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Taxons  took 0.00013136863708496094s
Interoperability | Check the re-using of existing vocabs for Taxons  took 5.7220458984375e-06s
Believability | Calculation of trust value for Taxons  took 1.049041748046875e-05s
INFO | --- Analysis for sandre took 1971.5284371376038s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.6316859722137451s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.3021557331085205s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 2.9325485229492188e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.0013580322265625e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 7.473633050918579s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 260.7464611530304s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0008192062377929688s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.2953965663909912s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.022556304931640625s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.00543212890625e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for santillana_guide_dataset took 664.4763247966766s
Availability | SPARQL endpoint availability check for SATAR test  took 9.059906005859375e-05s
Availability | VoID file availability check for SATAR test  took 0.00035190582275390625s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.28780341148376465s
Reputation | Calculation of the PageRank for SATAR test  took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 2.86102294921875e-05s
Believability | Calculation of trust value for SATAR test  took 6.4373016357421875e-06s
INFO | --- Analysis for SATAR_test took 5.433928728103638s
Availability | SPARQL endpoint availability check for SCBG Data took 21.50008511543274s
Availability | VoID file availability check for SCBG Data took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.302276611328125s
Reputation | Calculation of the PageRank for SCBG Data took 0.02178502082824707s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 9.059906005859375e-05s
Believability | Calculation of trust value for SCBG Data took 1.1444091796875e-05s
INFO | --- Analysis for SCBG-Data took 54.39183187484741s
Availability | SPARQL endpoint availability check for Schemantra took 4.363059997558594e-05s
Availability | VoID file availability check for Schemantra took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Schemantra took 0.31087327003479004s
Reputation | Calculation of the PageRank for Schemantra took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Schemantra took 2.9087066650390625e-05s
Believability | Calculation of trust value for Schemantra took 7.867813110351562e-06s
INFO | --- Analysis for Schemantra took 2.620561122894287s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.4060840606689453s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0003707408905029297s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.2954123020172119s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.02081751823425293s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.504753112792969e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 7.3909759521484375e-06s
INFO | --- Analysis for schemapedia took 4.346883058547974s
Availability | SPARQL endpoint availability check for Scholarometer took 4.2438507080078125e-05s
Availability | VoID file availability check for Scholarometer took 0.00041294097900390625s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.28976917266845703s
Reputation | Calculation of the PageRank for Scholarometer took 0.020662546157836914s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.58306884765625e-05s
Believability | Calculation of trust value for Scholarometer took 7.867813110351562e-06s
INFO | --- Analysis for scholarometer took 8.02008318901062s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.315376281738281e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0003559589385986328s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.2801032066345215s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.0517578125e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 5.0067901611328125e-06s
INFO | --- Analysis for scoreboard took 4.580928325653076s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.172325134277344e-05s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.2897655963897705s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020682096481323242s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.075599670410156e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 7.3909759521484375e-06s
INFO | --- Analysis for SDDEC took 27.58007001876831s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.076957702636719e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.29693150520324707s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.0279159545898438e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 8.106231689453125e-06s
INFO | --- Analysis for SDG took 3.479703426361084s
Availability | SPARQL endpoint availability check for sears.com took 8.535385131835938e-05s
Availability | VoID file availability check for sears.com took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for sears.com took 0.30069589614868164s
Reputation | Calculation of the PageRank for sears.com took 0.02053046226501465s
Interlinking | Calculation of Degree of Connection for sears.com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.580352783203125e-05s
Believability | Calculation of trust value for sears.com took 1.239776611328125e-05s
INFO | --- Analysis for sears took 5.569799900054932s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.09817671775817871s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.2923316955566406s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.022052764892578125s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 7.843971252441406e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.821487426757812e-06s
INFO | --- Analysis for sec-rdfabout took 44.37313747406006s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.73414397239685s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0007498264312744141s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.2856462001800537s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.02259230613708496s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.249282836914062e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for secold took 168.05265164375305s
Availability | SPARQL endpoint availability check for semanlink took 8.296966552734375e-05s
Availability | VoID file availability check for semanlink took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for semanlink took 0.30040550231933594s
Reputation | Calculation of the PageRank for semanlink took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00014066696166992188s
Believability | Calculation of trust value for semanlink took 1.0013580322265625e-05s
INFO | --- Analysis for semanlink took 3.768425703048706s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.168290376663208s
Availability | VoID file availability check for Semantic Universe Data took 0.00042510032653808594s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.274446964263916s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.075599670410156e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.2874603271484375e-05s
INFO | --- Analysis for semantic-universe took 3.0744338035583496s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.66946530342102s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.29145288467407227s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011754035949707031s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.239776611328125e-05s
INFO | --- Analysis for semantic-web-dog-food took 83.66186428070068s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 9.131431579589844e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.2894744873046875s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.076957702636719e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.0967254638671875e-05s
INFO | --- Analysis for semantic-web-grundlagen took 3.154921054840088s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 0.00011467933654785156s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.2754385471343994s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.02037811279296875s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 7.82012939453125e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 9.5367431640625e-06s
INFO | --- Analysis for semantic-xbrl took 3.603163242340088s
Availability | SPARQL endpoint availability check for Semantic Quran took 7.0388734340667725s
Availability | VoID file availability check for Semantic Quran took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Semantic Quran took 0.27292799949645996s
Reputation | Calculation of the PageRank for Semantic Quran took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for Semantic Quran took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Quran took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Semantic Quran took 6.651878356933594e-05s
Believability | Calculation of trust value for Semantic Quran took 1.1444091796875e-05s
INFO | --- Analysis for semanticquran took 16.873945951461792s
Availability | SPARQL endpoint availability check for SemanticTweet took 8.845329284667969e-05s
Availability | VoID file availability check for SemanticTweet took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.2755861282348633s
Reputation | Calculation of the PageRank for SemanticTweet took 0.022977590560913086s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.1021575927734375e-05s
Believability | Calculation of trust value for SemanticTweet took 1.049041748046875e-05s
INFO | --- Analysis for semantictweet took 2.776926040649414s
Availability | SPARQL endpoint availability check for semanticweb.org took 8.845329284667969e-05s
Availability | VoID file availability check for semanticweb.org took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.2815687656402588s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02198934555053711s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.534027099609375e-05s
Believability | Calculation of trust value for semanticweb.org took 1.0251998901367188e-05s
INFO | --- Analysis for semanticweb-org took 22.84523320198059s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.06822824478149414s
Availability | VoID file availability check for Semantic CrunchBase took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.282346248626709s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.246566772460938e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.2636184692382812e-05s
INFO | --- Analysis for semsol-crunchbase took 2.6997790336608887s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.258638858795166s
Availability | VoID file availability check for SentimentWortschatz took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.30382609367370605s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 3.8623809814453125e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.1682510375976562e-05s
INFO | --- Analysis for sentiws took 4.669929027557373s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.07211947441101s
Availability | VoID file availability check for seoul-bike-data took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.2941598892211914s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.020504236221313477s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 2.765655517578125e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.049041748046875e-05s
INFO | --- Analysis for seoul-bike-data took 72.84841442108154s
Availability | SPARQL endpoint availability check for Serendipity took 4.262369871139526s
Availability | VoID file availability check for Serendipity took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for Serendipity took 0.2791574001312256s
Reputation | Calculation of the PageRank for Serendipity took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Serendipity took 6.651878356933594e-05s
Believability | Calculation of trust value for Serendipity took 1.2636184692382812e-05s
INFO | --- Analysis for serendipity took 10.835445165634155s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 0.00010704994201660156s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.29904723167419434s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02208256721496582s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.0517578125e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.2159347534179688e-05s
INFO | --- Analysis for Sherry_Wine took 2.7992208003997803s
Availability | SPARQL endpoint availability check for Sherry Wine took 8.630752563476562e-05s
Availability | VoID file availability check for Sherry Wine took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.2729644775390625s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.8371810913085938e-05s
Believability | Calculation of trust value for Sherry Wine took 1.239776611328125e-05s
INFO | --- Analysis for Sherry_Wine_ took 2.5623931884765625s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.19476866722106934s
Availability | VoID file availability check for Shoah victims? names took 0.2232191562652588s
Extra | Recovery of all triples for Shoah victims? names took 1.1918613910675049s
Performance | Total latancy measurement for Shoah victims? names took 0.3800497055053711s
Amount of data | Number of triples check for Shoah victims? names took 1.474522352218628s
Interoperability | New terms check for Shoah victims? names took 1.7134606838226318s
Versatility | Languages check for Shoah victims? names took 17.751392364501953s
Interpretability | Number of blank nodes check for Shoah victims? names took 10.524820804595947s
Security | Check HTTPS for Shoah victims? names took 0.21001601219177246s
Interpretability | RDF structures check for Shoah victims? names took 0.22542905807495117s
Versatility | Serialization formats check for Shoah victims? names took 0.2877464294433594s
Availability | RDF dump link check for Shoah victims? names took 0.12517976760864258s
License | MR license check for Shoah victims? names took 0.2924795150756836s
License | HR license check for Shoah victims? names took 7.9587721824646s
Amount of data | Number of property check for Shoah victims? names took 0.12558412551879883s
Understandability | Number of label check for Shoah victims? names took 0.8476312160491943s
Understandability | URI regex check for Shoah victims? names took 0.36087799072265625s
Understandability | Vocabs check for Shoah victims? names took 0.09686875343322754s
Verifiability | Authors check for Shoah victims? names took 0.12479829788208008s
Verifiability | Publishers check for Shoah victims? names took 0.16147613525390625s
Performance | Throughput check for Shoah victims? names took 10.504865884780884s
Amount of data | Check the number of entities for Shoah victims? names took 7.319450378417969e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.08940386772155762s
Interlinking | sameAs chians check for Shoah victims? names took 0.1202850341796875s
Interlinking | skos check for Shoah victims? names took 0.21165180206298828s
Interlinking | skos check for Shoah victims? names took 0.0673065185546875s
Timeliness | dataset update frequency check for Shoah victims? names took 0.18366765975952148s
Currency | Creation date check for Shoah victims? names took 0.209181547164917s
Currency | Modification date check for Shoah victims? names took 0.23125982284545898s
Rep.Conc. | URIs length for Shoah victims? names took 2.5321784019470215s
Interoperability | New vocabularies check for Shoah victims? names took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.10855603218078613s
Accuracy | Check Functional Property for Shoah victims? names took 0.10764408111572266s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.05541229248046875s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.3862264156341553s
Accuracy | Check White space in annotation for Shoah victims? names took 0.02774834632873535s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.02837538719177246s
Consistency | Disjoint class check for Shoah victims? names took 0.1727769374847412s
Consistency | Check Misplaced properties for Shoah victims? names took 2.0044310092926025s
Consistency | Misplaced classes for Shoah victims? names took 0.21517229080200195s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.5626792907714844s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.281653642654419s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.11018705368042s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.03288602828979492s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.13620567321777344s
Security | Sign check for Shoah victims? names took 0.3714792728424072s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1026.9117925167084s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.4414641857147217s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.022983312606811523s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 3.528594970703125e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.6689300537109375e-06s
Believability | Calculation of trust value for Shoah victims? names took 1.3113021850585938e-05s
INFO | --- Analysis for shoah-victims-names took 1156.0560598373413s
Availability | SPARQL endpoint availability check for Person took 8.916854858398438e-05s
Availability | VoID file availability check for Person took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Person took 0.30162596702575684s
Reputation | Calculation of the PageRank for Person took 0.020948410034179688s
Interlinking | Calculation of Degree of Connection for Person took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Person took 0.000993967056274414s
Interlinking | Calculation of Clustering coefficient for Person took 4.0531158447265625e-05s
Believability | Calculation of trust value for Person took 1.1444091796875e-05s
INFO | --- Analysis for Shripriya_Dubey took 2.6809656620025635s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 8.702278137207031e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.29044365882873535s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.020833730697631836s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 1.0728836059570312e-05s
INFO | --- Analysis for Shutterstock took 2.6733131408691406s
Availability | SPARQL endpoint availability check for SIMPLE took 4.267692565917969e-05s
Availability | VoID file availability check for SIMPLE took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.30434441566467285s
Reputation | Calculation of the PageRank for SIMPLE took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.506111145019531e-05s
Believability | Calculation of trust value for SIMPLE took 1.0728836059570312e-05s
INFO | --- Analysis for simple took 8.367926597595215s
Availability | SPARQL endpoint availability check for SITC-V4 took 26.194578170776367s
Availability | VoID file availability check for SITC-V4 took 0.0007574558258056641s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.34439516067504883s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02252197265625s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.6716461181640625e-05s
Believability | Calculation of trust value for SITC-V4 took 1.3113021850585938e-05s
INFO | --- Analysis for sitc-v4 took 125.22454452514648s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 8.797645568847656e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.3001582622528076s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020795822143554688s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 5.030632019042969e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.1682510375976562e-05s
INFO | --- Analysis for sli_galnet_rdf took 12.921043872833252s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 0.00010609626770019531s
Availability | VoID file availability check for Slideshare2RDF Server took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.3137381076812744s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.02063441276550293s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.0517578125e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.1444091796875e-05s
INFO | --- Analysis for slideshare2rdf took 2.714766025543213s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.5235133171081543s
Availability | VoID file availability check for Linked Stage Graph took 0.0004684925079345703s
Extra | Recovery of all triples for Linked Stage Graph took 2.0013303756713867s
Performance | Total latancy measurement for Linked Stage Graph took 1.3315680027008057s
Amount of data | Number of triples check for Linked Stage Graph took 0.30008554458618164s
Interoperability | New terms check for Linked Stage Graph took 1.5827932357788086s
Versatility | Languages check for Linked Stage Graph took 0.737929105758667s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.28076887130737305s
Security | Check HTTPS for Linked Stage Graph took 0.16729402542114258s
Interpretability | RDF structures check for Linked Stage Graph took 0.5352330207824707s
Versatility | Serialization formats check for Linked Stage Graph took 0.3450639247894287s
Availability | RDF dump link check for Linked Stage Graph took 0.23739886283874512s
License | MR license check for Linked Stage Graph took 0.5178217887878418s
License | HR license check for Linked Stage Graph took 1.8136241436004639s
Amount of data | Number of property check for Linked Stage Graph took 0.2485053539276123s
Understandability | Number of label check for Linked Stage Graph took 0.9586954116821289s
Understandability | URI regex check for Linked Stage Graph took 0.7370684146881104s
Understandability | Vocabs check for Linked Stage Graph took 0.3533303737640381s
Verifiability | Authors check for Linked Stage Graph took 0.28639698028564453s
Verifiability | Publishers check for Linked Stage Graph took 0.2598459720611572s
Performance | Throughput check for Linked Stage Graph took 10.456095218658447s
Amount of data | Check the number of entities for Linked Stage Graph took 7.2479248046875e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.27388668060302734s
Interlinking | sameAs chians check for Linked Stage Graph took 0.36290407180786133s
Interlinking | skos check for Linked Stage Graph took 0.34021615982055664s
Interlinking | skos check for Linked Stage Graph took 0.252685546875s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.4212360382080078s
Currency | Creation date check for Linked Stage Graph took 0.5130267143249512s
Currency | Modification date check for Linked Stage Graph took 0.5232417583465576s
Rep.Conc. | URIs length for Linked Stage Graph took 1.5942645072937012s
Interoperability | New vocabularies check for Linked Stage Graph took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.24960994720458984s
Accuracy | Check Functional Property for Linked Stage Graph took 0.5218257904052734s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.4953763484954834s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 1.5286829471588135s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.023504018783569336s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.02799224853515625s
Consistency | Disjoint class check for Linked Stage Graph took 0.2654993534088135s
Consistency | Check Misplaced properties for Linked Stage Graph took 1.1567676067352295s
Consistency | Misplaced classes for Linked Stage Graph took 0.6951456069946289s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.1243526935577393s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.2790074348449707s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.8201286792755127s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.026335954666137695s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.7594280242919922s
Security | Sign check for Linked Stage Graph took 0.6613094806671143s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 1050.3648159503937s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.3743116855621338s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.021287918090820312s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 6.413459777832031e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.1920928955078125e-05s
INFO | --- Analysis for slod took 1121.4155905246735s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.6230001449584961s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0004897117614746094s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 123.67564940452576s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 1.0053892135620117s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 9.25955057144165s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 13.984252691268921s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.1739869117737s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.1333746910095215s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.3652956485748291s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 9.140512943267822s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.2758493423461914s
License | MR license check for Smart Points Of Interest @PSNC took 0.5931038856506348s
License | HR license check for Smart Points Of Interest @PSNC took 300.2344431877136s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.23627543449401855s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.107913017272949s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 1.0781705379486084s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.48505330085754395s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.21699094772338867s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.26722192764282227s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.161648035049438s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 7.152557373046875e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.1901841163635254s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.1839745044708252s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.5181553363800049s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.45295143127441406s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 6.003558397293091s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.5127413272857666s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.25890660285949707s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 161.27445244789124s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.18921136856079102s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.46081018447875977s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.1961078643798828s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 42.82305097579956s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.6278011798858643s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.5377044677734375s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.2614598274230957s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 86.38977336883545s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.238868236541748s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 36.629881143569946s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.3289580345153809s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 88.97355222702026s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7225234508514404s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.5419139862060547s
Security | Sign check for Smart Points Of Interest @PSNC took 0.8627643585205078s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 9.291620016098022s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.7074196338653564s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.020812511444091797s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 6.508827209472656e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00010442733764648438s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for Smart_POI_dataset took 2298.3530371189117s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.160869121551514s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.00054931640625s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.3014838695526123s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.02188706398010254s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.695487976074219e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.0251998901367188e-05s
INFO | --- Analysis for smartlink took 13.253588199615479s
Availability | SPARQL endpoint availability check for SNIK took 0.4747462272644043s
Availability | VoID file availability check for SNIK took 0.0006024837493896484s
Extra | Recovery of all triples for SNIK took 3.5470175743103027s
Performance | Total latancy measurement for SNIK took 0.97894287109375s
Amount of data | Number of triples check for SNIK took 0.2036724090576172s
Interoperability | New terms check for SNIK took 1.4565563201904297s
Versatility | Languages check for SNIK took 0.22586512565612793s
Interpretability | Number of blank nodes check for SNIK took 0.20015883445739746s
Interpretability | RDF structures check for SNIK took 0.22783160209655762s
Versatility | Serialization formats check for SNIK took 0.2244563102722168s
Availability | RDF dump link check for SNIK took 0.1923375129699707s
License | MR license check for SNIK took 0.23481273651123047s
License | HR license check for SNIK took 0.2173938751220703s
Amount of data | Number of property check for SNIK took 0.21653246879577637s
Understandability | Number of label check for SNIK took 0.24998259544372559s
Understandability | URI regex check for SNIK took 0.4124641418457031s
Understandability | Vocabs check for SNIK took 0.18547892570495605s
Verifiability | Authors check for SNIK took 0.19369196891784668s
Verifiability | Publishers check for SNIK took 0.17821097373962402s
Amount of data | Check the number of entities for SNIK took 8.20159912109375e-05s
Verifiability | Contribs. check for SNIK took 0.18478608131408691s
Interlinking | sameAs chians check for SNIK took 0.21731972694396973s
Interlinking | skos check for SNIK took 0.23459219932556152s
Interlinking | skos check for SNIK took 0.19263505935668945s
Timeliness | dataset update frequency check for SNIK took 0.21811294555664062s
Currency | Creation date check for SNIK took 0.3982970714569092s
Currency | Modification date check for SNIK took 0.4078958034515381s
Rep.Conc. | URIs length for SNIK took 1.478243350982666s
Interoperability | New vocabularies check for SNIK took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.1787717342376709s
Accuracy | Check Functional Property for SNIK took 0.1953580379486084s
Accuracy | Check Inverse Functional Property for SNIK took 0.20327520370483398s
Accuracy | Check Empty annotation labels for SNIK took 0.6561553478240967s
Accuracy | Check White space in annotation for SNIK took 0.02678966522216797s
Accuracy | Check Datatype consistency for SNIK took 0.21549773216247559s
Consistency | Disjoint class check for SNIK took 0.17406940460205078s
Consistency | Check Misplaced properties for SNIK took 0.6711254119873047s
Consistency | Misplaced classes for SNIK took 0.7015781402587891s
Consistency | Check Ontology hijacking for SNIK took 1.795485019683838s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.2604386806488037s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.514380931854248s
Conciseness | Check Extensional conciseness for SNIK took 0.1508646011352539s
Conciseness | Check Intensional conciseness for SNIK took 0.34647178649902344s
Security | Sign check for SNIK took 0.19700264930725098s
Availability | Check URIs Dereferenciability for SNIK took 2024.318119764328s
Completeness | Calculation of interlinking completeness for SNIK took 0.5214300155639648s
Reputation | Calculation of the PageRank for SNIK took 0.02136850357055664s
Interlinking | Calculation of Degree of Connection for SNIK took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for SNIK took 8.106231689453125e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.6689300537109375e-06s
Believability | Calculation of trust value for SNIK took 1.239776611328125e-05s
INFO | --- Analysis for snik took 2098.606794834137s
Availability | SPARQL endpoint availability check for SocialLink took 1.1603307723999023s
Availability | VoID file availability check for SocialLink took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for SocialLink took 0.2923600673675537s
Reputation | Calculation of the PageRank for SocialLink took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.843971252441406e-05s
Believability | Calculation of trust value for SocialLink took 1.0967254638671875e-05s
INFO | --- Analysis for SocialLink took 5.629514932632446s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 4.172325134277344e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0004100799560546875s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.2875823974609375s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 2.9087066650390625e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.2636184692382812e-05s
INFO | --- Analysis for SocialRoles took 10.218446493148804s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.22867655754089355s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0006570816040039062s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 15.200683832168579s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.4851353168487549s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.18743443489074707s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.4838428497314453s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.29561758041381836s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.17818236351013184s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.30443501472473145s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.1246640682220459s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.12216734886169434s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.7447881698608398s
License | MR license check for Social Semantic Web Thesaurus took 0.11905670166015625s
License | HR license check for Social Semantic Web Thesaurus took 0.10212373733520508s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.13026738166809082s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.1301126480102539s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.18740105628967285s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.1266040802001953s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.11125779151916504s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.1187586784362793s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.491955757141113s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 7.200241088867188e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.11903214454650879s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.1258234977722168s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.12831664085388184s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.08065986633300781s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.09605717658996582s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.17175674438476562s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.21691513061523438s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.4168915748596191s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 0.7037601470947266s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.1251695156097412s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.09436345100402832s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.08747172355651855s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.4758460521697998s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012304306030273438s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.07825994491577148s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.2776072025299072s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.09850192070007324s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.006945848464966s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.3912854194641113s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00013303756713867188s
Security | Sign check for Social Semantic Web Thesaurus took 0.08689141273498535s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 106.40684628486633s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.2987251281738281s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020505905151367188s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006682872772216797s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.775161743164062e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 0.4418058395385742s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 293.905396938324s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3469278812408447s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.000499725341796875s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 110.00573587417603s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.02061128616333s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.105109453201294s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.213866710662842s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.25590348243713s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.039121150970459s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1947338581085205s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.944721221923828s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18061542510986328s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1808469295501709s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2311019897461s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19100117683410645s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.4369566440582275s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.6067273616790771s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.22753620147705078s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21612548828125s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.26760339736938477s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.485041379928589s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.462501525878906e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21946978569030762s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21229004859924316s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4528522491455078s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.41619229316711426s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.0491533279418945s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5144705772399902s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2401597499847412s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 152.4490361213684s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.2649765014648438e-05s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19617438316345215s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18484735488891602s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1788797378540039s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 39.39483690261841s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6479954719543457s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.639131784439087s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.24125099182128906s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 86.07897138595581s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.362107992172241s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 30.152283430099487s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.381209135055542s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 86.78993487358093s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6941215991973877s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5465273857116699s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5253732204437256s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.064682483673096s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.6239540576934814s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.021628618240356445s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.124641418457031e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.0531158447265625e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for Soil_maps took 2261.1837656497955s
Availability | SPARQL endpoint availability check for terrorrist ontology took 9.751319885253906e-05s
Availability | VoID file availability check for terrorrist ontology took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.27729129791259766s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.021361112594604492s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 8.535385131835938e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.719329833984375e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.0967254638671875e-05s
INFO | --- Analysis for somya_omer took 2.5836610794067383s
Availability | SPARQL endpoint availability check for Sonclubcx took 0.00024390220642089844s
Availability | VoID file availability check for Sonclubcx took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.3003103733062744s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.2636184692382812e-05s
Believability | Calculation of trust value for Sonclubcx took 1.0967254638671875e-05s
INFO | --- Analysis for sonclubcx took 3.939220666885376s
Availability | SPARQL endpoint availability check for SORS took 4.696846008300781e-05s
Availability | VoID file availability check for SORS took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for SORS took 0.4452095031738281s
Reputation | Calculation of the PageRank for SORS took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for SORS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for SORS took 4.839897155761719e-05s
Believability | Calculation of trust value for SORS took 1.0013580322265625e-05s
INFO | --- Analysis for sors took 13.445703268051147s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 8.726119995117188e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.307326078414917s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.1552734375e-05s
Believability | Calculation of trust value for southampton-ac-uk took 1.239776611328125e-05s
INFO | --- Analysis for southampton-ac-uk took 3.8807625770568848s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.2942087650299072s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.3216385841369629s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02155160903930664s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.647804260253906e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 1.3589859008789062e-05s
INFO | --- Analysis for southampton-ac-uk-apps took 10.934455394744873s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 8.893013000488281e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.2922980785369873s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020973682403564453s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.34600830078125e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.0251998901367188e-05s
INFO | --- Analysis for southampton-ecs-eprints took 2.924196243286133s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5185239315032959s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0005221366882324219s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 161.49888920783997s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.2018001079559326s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.127347946166992s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.014756679534912s
Versatility | Languages check for Spanish Linguistic Datasets took 44.55670881271362s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.240661859512329s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.14557504653930664s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.29074788093566895s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.2987706661224365s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.28241539001464844s
License | MR license check for Spanish Linguistic Datasets took 0.29915881156921387s
License | HR license check for Spanish Linguistic Datasets took 0.3667948246002197s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.2844429016113281s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.3448758125305176s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5881469249725342s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.288973331451416s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.302156925201416s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.314403772354126s
Performance | Throughput check for Spanish Linguistic Datasets took 11.227074384689331s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 7.033348083496094e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.5325634479522705s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.32079553604125977s
Interlinking | skos check for Spanish Linguistic Datasets took 0.30243825912475586s
Interlinking | skos check for Spanish Linguistic Datasets took 0.21552562713623047s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.28133249282836914s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5874392986297607s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5755996704101562s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 58.04070854187012s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.5500669479370117s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.28486204147338867s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.2839338779449463s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9416770935058594s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010159969329833984s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.5856869220733643s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.30644917488098145s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.671288251876831s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.310713529586792s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 45.67691659927368s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.496427297592163s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.745877504348755s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.8564412593841553s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.30013608932495117s
Security | Sign check for Spanish Linguistic Datasets took 0.28549981117248535s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 9.737217903137207s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.37514615058898926s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021387815475463867s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.4332275390625e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.1457672119140625e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.239776611328125e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 413.4007480144501s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.04554343223571777s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2861058712005615s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.8160552978515625e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 7.867813110351562e-06s
INFO | --- Analysis for sparql-endpoint-status took 2.614088773727417s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 8.797645568847656e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.2904677391052246s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.021190404891967773s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 0.00010347366333007812s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.2874603271484375e-05s
INFO | --- Analysis for springernaturescigraph took 3.5556836128234863s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.267692565917969e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.29950833320617676s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.023762226104736328s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0013260841369628906s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.410743713378906e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.2159347534179688e-05s
INFO | --- Analysis for srcmf took 7.447347402572632s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.3375849723815918s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0005459785461425781s
Extra | Recovery of all triples for Lexicon of Syntactic and Semantic Framework took 1.293808937072754s
Performance | Total latancy measurement for Lexicon of Syntactic and Semantic Framework took 0.8057291507720947s
Amount of data | Number of triples check for Lexicon of Syntactic and Semantic Framework took 0.15969467163085938s
Interoperability | New terms check for Lexicon of Syntactic and Semantic Framework took 1.3892507553100586s
Versatility | Languages check for Lexicon of Syntactic and Semantic Framework took 0.16576576232910156s
Interpretability | Number of blank nodes check for Lexicon of Syntactic and Semantic Framework took 0.17472290992736816s
Security | Check HTTPS for Lexicon of Syntactic and Semantic Framework took 0.10165143013000488s
Interpretability | RDF structures check for Lexicon of Syntactic and Semantic Framework took 0.14519929885864258s
Versatility | Serialization formats check for Lexicon of Syntactic and Semantic Framework took 0.1523725986480713s
Availability | RDF dump link check for Lexicon of Syntactic and Semantic Framework took 0.14275884628295898s
License | MR license check for Lexicon of Syntactic and Semantic Framework took 0.13991427421569824s
License | HR license check for Lexicon of Syntactic and Semantic Framework took 0.15103387832641602s
Amount of data | Number of property check for Lexicon of Syntactic and Semantic Framework took 0.1448206901550293s
Understandability | Number of label check for Lexicon of Syntactic and Semantic Framework took 0.1706373691558838s
Understandability | URI regex check for Lexicon of Syntactic and Semantic Framework took 0.29276061058044434s
Understandability | Vocabs check for Lexicon of Syntactic and Semantic Framework took 0.1313621997833252s
Verifiability | Authors check for Lexicon of Syntactic and Semantic Framework took 0.15935087203979492s
Verifiability | Publishers check for Lexicon of Syntactic and Semantic Framework took 0.1506950855255127s
Performance | Throughput check for Lexicon of Syntactic and Semantic Framework took 10.79423999786377s
Amount of data | Check the number of entities for Lexicon of Syntactic and Semantic Framework took 7.05718994140625e-05s
Verifiability | Contribs. check for Lexicon of Syntactic and Semantic Framework took 0.15107941627502441s
Interlinking | sameAs chians check for Lexicon of Syntactic and Semantic Framework took 0.1437389850616455s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.14984774589538574s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.16236376762390137s
Timeliness | dataset update frequency check for Lexicon of Syntactic and Semantic Framework took 0.1453845500946045s
Currency | Creation date check for Lexicon of Syntactic and Semantic Framework took 0.2913999557495117s
Currency | Modification date check for Lexicon of Syntactic and Semantic Framework took 0.3171994686126709s
Rep.Conc. | URIs length for Lexicon of Syntactic and Semantic Framework took 0.4482743740081787s
Interoperability | New vocabularies check for Lexicon of Syntactic and Semantic Framework took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Lexicon of Syntactic and Semantic Framework took 0.1499793529510498s
Accuracy | Check Functional Property for Lexicon of Syntactic and Semantic Framework took 0.14387035369873047s
Accuracy | Check Inverse Functional Property for Lexicon of Syntactic and Semantic Framework took 0.16997742652893066s
Accuracy | Check Empty annotation labels for Lexicon of Syntactic and Semantic Framework took 0.15927600860595703s
Accuracy | Check White space in annotation for Lexicon of Syntactic and Semantic Framework took 0.0003485679626464844s
Accuracy | Check Datatype consistency for Lexicon of Syntactic and Semantic Framework took 0.037073612213134766s
Consistency | Disjoint class check for Lexicon of Syntactic and Semantic Framework took 0.15048599243164062s
Consistency | Check Misplaced properties for Lexicon of Syntactic and Semantic Framework took 0.30654096603393555s
Consistency | Misplaced classes for Lexicon of Syntactic and Semantic Framework took 0.21936607360839844s
Consistency | Check Ontology hijacking for Lexicon of Syntactic and Semantic Framework took 1.4598934650421143s
Consistency | Check Invalid usage of undefined classes for Lexicon of Syntactic and Semantic Framework took 1.2717466354370117s
Consistency | Check Invalid usage of undefined properties for Lexicon of Syntactic and Semantic Framework took 1.4334845542907715s
Conciseness | Check Extensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.021831035614013672s
Conciseness | Check Intensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.14810681343078613s
Security | Sign check for Lexicon of Syntactic and Semantic Framework took 0.1376960277557373s
Availability | Check URIs Dereferenciability for Lexicon of Syntactic and Semantic Framework took 340.3704786300659s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.3692042827606201s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.021495580673217773s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Lexicon of Syntactic and Semantic Framework took 1.9073486328125e-06s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 7.867813110351562e-06s
INFO | --- Analysis for ssf took 380.9317967891693s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.553794860839844e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0003743171691894531s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.3039588928222656s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020879268646240234s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.5762786865234375e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 6.9141387939453125e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.9607224464416504s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.2438507080078125e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.2717444896697998s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.021113872528076172s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.361701965332031e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 5.0067901611328125e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 3.0401272773742676s
Availability | SPARQL endpoint availability check for Stammbuch took 9.965896606445312e-05s
Availability | VoID file availability check for Stammbuch took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2991220951080322s
Reputation | Calculation of the PageRank for Stammbuch took 0.02112102508544922s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.0517578125e-05s
Believability | Calculation of trust value for Stammbuch took 7.3909759521484375e-06s
INFO | --- Analysis for Stammbuch took 2.5352864265441895s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.3955047130584717s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.28473472595214844s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.021025896072387695s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010395050048828125s
Believability | Calculation of trust value for statistics.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for statistics-data-gov-uk took 4.82653284072876s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0003848075866699219s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.27300500869750977s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.021051883697509766s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010585784912109375s
Believability | Calculation of trust value for statusnet-1w6-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-1w6-org took 4.286321640014648s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.27131175994873047s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020915746688842773s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.127357482910156e-05s
Believability | Calculation of trust value for statusnet-20100-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-20100-org took 2.75057315826416s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.27541160583496094s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02074599266052246s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.890296936035156e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 3.0115275382995605s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.28211259841918945s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.02096724510192871s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 8.630752563476562e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.5743629932403564s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 8.344650268554688e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.3116297721862793s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.02088165283203125s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.560585021972656e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.767759323120117s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 5.7220458984375e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.27786993980407715s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.020786046981811523s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011014938354492188s
Believability | Calculation of trust value for statusnet-bka-li took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-bka-li took 12.666196346282959s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.27942371368408203s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.020915508270263672s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.838539123535156e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.3724169731140137s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.27882933616638184s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.02100515365600586s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.030632019042969e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ced117-net took 4.373427867889404s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.2969624996185303s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.1975250244140625e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.7487385272979736s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.28977036476135254s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020916461944580078s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011372566223144531s
Believability | Calculation of trust value for statusnet-chromic-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.6724131107330322s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.00037670135498046875s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2761673927307129s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020799875259399414s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.843971252441406e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 5.958633184432983s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2772383689880371s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.459785461425781e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.608977794647217s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 6.29425048828125e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.31052160263061523s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.985664367675781e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.241750955581665s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0004017353057861328s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.2772700786590576s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010156631469726562s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.6750974655151367s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 8.988380432128906e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.2788822650909424s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.02082538604736328s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.60487699508667s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 8.296966552734375e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0003612041473388672s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.304948091506958s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020993471145629883s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.14984130859375e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.92228627204895s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.28642702102661133s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.021114110946655273s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.961822509765625e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-dtdns-net took 22.581504583358765s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.28617143630981445s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.02073979377746582s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.910064697265625e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.604816436767578s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 7.724761962890625e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0004222393035888672s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.25972604751586914s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.414817810058594e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-exdc-net took 2.6322333812713623s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.00032448768615722656s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.29053211212158203s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.02117013931274414s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.417533874511719e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-fcac-com took 2.9894649982452393s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.00040221214294433594s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.28941893577575684s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.02089548110961914s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 3.302643060684204s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.26954221725463867s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00021076202392578125s
Believability | Calculation of trust value for statusnet-fragdev-com took 2.6464462280273438e-05s
INFO | --- Analysis for statusnet-fragdev-com took 3.572373867034912s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.2818009853363037s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.02082657814025879s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.7967936992645264s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 8.058547973632812e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.2660508155822754s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.02106475830078125s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010752677917480469s
Believability | Calculation of trust value for statusnet-gegeweb-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.6099131107330322s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 7.390975952148438e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0003864765167236328s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.32782626152038574s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.021072864532470703s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0008478164672851562s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 7.557868957519531e-05s
Believability | Calculation of trust value for statusnet-glou-org took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-glou-org took 2.664689064025879s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.3010845184326172s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012540817260742188s
Believability | Calculation of trust value for statusnet-gomertronic-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.6095175743103027s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 5.1975250244140625e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0003147125244140625s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.3163168430328369s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020877838134765625s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00011348724365234375s
Believability | Calculation of trust value for statusnet-hackerposse-com took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-hackerposse-com took 3.116955041885376s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.30961132049560547s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.02154064178466797s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 3.0040740966796875e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.863739013671875e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-hii-co-il took 3.922624349594116s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.28986501693725586s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.021253585815429688s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0008759498596191406s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 0.00010180473327636719s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 2.8391261100769043s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 8.869171142578125e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.2952849864959717s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.022698640823364258s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 8.177757263183594e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 2.6419010162353516s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 9.083747863769531e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0002994537353515625s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.309281587600708s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020916223526000977s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.100799560546875e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.814300298690796s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.2822229862213135s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02104330062866211s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.5471031665802s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2786061763763428s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.02083444595336914s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.0001385211944580078s
Believability | Calculation of trust value for statusnet-jonkman-ca took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 22.543469667434692s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 7.915496826171875e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2831566333770752s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020852088928222656s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.489059448242188e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 7.62939453125e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.6875667572021484s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.3107273578643799s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.02102041244506836s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.1975250244140625e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.6088147163391113s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2702507972717285s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.02215266227722168s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.8623809814453125e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 3.4005677700042725s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 7.677078247070312e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.31165480613708496s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020964622497558594s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.685757875442505s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 5.7697296142578125e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.29086875915527344s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020891427993774414s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.707568645477295s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.00038623809814453125s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.28153395652770996s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020924806594848633s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.8558924198150635s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.26975440979003906s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.512901306152344e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 3.2431344985961914s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.27923154830932617s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020753860473632812s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.000152587890625s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.5418295860290527s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 7.724761962890625e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.28847765922546387s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.020819902420043945s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.9207797050476074s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.3002452850341797s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.703636169433594e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 2.677119731903076s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 9.083747863769531e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2894470691680908s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.022081375122070312s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.6059203147888184s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.30701160430908203s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.0001533031463623047s
Believability | Calculation of trust value for statusnet-macno-org took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-macno-org took 2.783665895462036s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.28124356269836426s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.6744556427001953s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0007305145263671875s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.29331517219543457s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.916854858398438e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-maymay-net took 42.07297134399414s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 0.00011301040649414062s
Availability | VoID file availability check for statusnet-morphtown-de took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2814033031463623s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020884275436401367s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00016045570373535156s
Believability | Calculation of trust value for statusnet-morphtown-de took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-morphtown-de took 2.622972249984741s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 8.702278137207031e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.28618931770324707s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.021085500717163086s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.00010418891906738281s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 2.644045352935791s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 8.487701416015625e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.27965664863586426s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-mulestable-net took 2.712556838989258s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 0.00010204315185546875s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.2745051383972168s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.02121257781982422s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-my-status-tk took 2.809037923812866s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 0.00011014938354492188s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.28600072860717773s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.02120375633239746s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00011086463928222656s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.6552627086639404s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2620432376861572s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.022218704223632812s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.888938903808594e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.842034101486206s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.39589977264404297s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.022295475006103516s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-otbm-fr took 2.8280019760131836s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.9114227294921875e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.28545093536376953s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 9.012222290039062e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.6639204025268555s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2889389991760254s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.022776126861572266s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 5.030632019042969e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-panda-id-au took 3.228856325149536s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2899174690246582s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.02091073989868164s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.584426879882812e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-piana-eu took 2.7028934955596924s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.30694127082824707s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.02104473114013672s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.748603820800781e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 2.7664527893066406s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 0.00010132789611816406s
Availability | VoID file availability check for statusnet-postblue-info took 0.0011610984802246094s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.27655577659606934s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.021894454956054688s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0010280609130859375s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00027108192443847656s
Believability | Calculation of trust value for statusnet-postblue-info took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-postblue-info took 2.8292362689971924s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.30321836471557617s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.02092885971069336s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.414817810058594e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-progval-net took 7.686537504196167s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 8.702278137207031e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.277512788772583s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.0209805965423584s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011205673217773438s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-qdnx-org took 3.2206873893737793s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.34275245666503906s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 8.273124694824219e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-qth-fr took 3.5247809886932373s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 9.083747863769531e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.2918205261230469s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020832300186157227s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.0002193450927734375s
Believability | Calculation of trust value for statusnet-quitter-se took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-quitter-se took 16.870227336883545s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.29975461959838867s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010371208190917969s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.8196256160736084s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.31510257720947266s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.021524667739868164s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-recit-org took 13.22232699394226s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 0.00011301040649414062s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.29287123680114746s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.02123880386352539s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001475811004638672s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-russwurm-org took 22.623858213424683s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.3068561553955078s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.02094578742980957s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.58306884765625e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-samnoble-org took 4.998346328735352s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2990274429321289s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.845329284667969e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-schiessle-org took 2.9408979415893555s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 8.702278137207031e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.28887081146240234s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 0.00010275840759277344s
Believability | Calculation of trust value for statusnet-scoffoni-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-scoffoni-net took 2.7268052101135254s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 9.179115295410156e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.297619104385376s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.02228069305419922s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 5.9604644775390625e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 2.6945013999938965s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.000579833984375s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.30837035179138184s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.271766662597656e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 3.4978201389312744s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 8.7738037109375e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0007655620574951172s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.29895901679992676s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.000209808349609375s
Believability | Calculation of trust value for statusnet-skilledtests-com took 2.1219253540039062e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 3.2652621269226074s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2749037742614746s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02094578742980957s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-somsants-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.626610517501831s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 9.751319885253906e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.30709075927734375s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00013518333435058594s
Believability | Calculation of trust value for statusnet-soucy-cc took 7.62939453125e-06s
INFO | --- Analysis for statusnet-soucy-cc took 4.316704034805298s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2780909538269043s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.021132946014404297s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.29425048828125e-05s
Believability | Calculation of trust value for statusnet-spip-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-spip-org took 3.646498203277588s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.28778791427612305s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.580352783203125e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-spraci-org took 5.537444829940796s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.2894105911254883s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.022413969039916992s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00014662742614746094s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 5.504714250564575s
Availability | SPARQL endpoint availability check for statusnet-status-net took 8.535385131835938e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.30665016174316406s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.0205385684967041s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022459030151367188s
Believability | Calculation of trust value for statusnet-status-net took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-status-net took 3.600625991821289s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 5.91278076171875e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.3025791645050049s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.022408008575439453s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.817413330078125e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.6424405574798584s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.27371764183044434s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020800113677978516s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.489059448242188e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.750070810317993s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.2759549617767334s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001251697540283203s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.9550323486328125e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 2.7656972408294678s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 0.00010752677917480469s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.26797986030578613s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.653236389160156e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-thornton2-com took 7.053268194198608s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.27907490730285645s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020757675170898438s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010657310485839844s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.897719144821167s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2849559783935547s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 3.3855438232421875e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.8160552978515625e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-tl1n-com took 3.753830671310425s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 8.678436279296875e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.28837084770202637s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020427703857421875s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.532669067382812e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.8969435691833496s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.00037407875061035156s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.28397631645202637s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.021036386489868164s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.9577484130859375e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 3.543468475341797s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 8.797645568847656e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.2977769374847412s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.8371810913085938e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for steak took 3.1761350631713867s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 8.416175842285156e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.2896244525909424s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020821571350097656s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.3882598876953125e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.0251998901367188e-05s
INFO | --- Analysis for stitch-rameau took 4.2435338497161865s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.8293578624725342s
Availability | VoID file availability check for Stone Tech Square took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.2995567321777344s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.021889925003051758s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.2636184692382812e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.3113021850585938e-05s
INFO | --- Analysis for stone-tech-square-data took 4.485093116760254s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.46281003952026367s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0006740093231201172s
Extra | Recovery of all triples for STW Thesaurus for Economics took 14.803550004959106s
Performance | Total latancy measurement for STW Thesaurus for Economics took 4.7406229972839355s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.9970235824584961s
Interoperability | New terms check for STW Thesaurus for Economics took 1.5705482959747314s
Versatility | Languages check for STW Thesaurus for Economics took 1.5869617462158203s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5428884029388428s
Security | Check HTTPS for STW Thesaurus for Economics took 0.16675806045532227s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.23988604545593262s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.2653045654296875s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.24577569961547852s
License | MR license check for STW Thesaurus for Economics took 0.24751710891723633s
License | HR license check for STW Thesaurus for Economics took 2.5137832164764404s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.2348475456237793s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6549727916717529s
Understandability | URI regex check for STW Thesaurus for Economics took 0.49892187118530273s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.25786757469177246s
Verifiability | Authors check for STW Thesaurus for Economics took 0.24842119216918945s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.24861812591552734s
Performance | Throughput check for STW Thesaurus for Economics took 11.020518779754639s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.68453049659729s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2814507484436035s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.22825169563293457s
Interlinking | skos check for STW Thesaurus for Economics took 0.3540024757385254s
Interlinking | skos check for STW Thesaurus for Economics took 0.284808874130249s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.23746514320373535s
Currency | Creation date check for STW Thesaurus for Economics took 0.49503016471862793s
Currency | Modification date check for STW Thesaurus for Economics took 0.5009810924530029s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 8.172273874282837s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 11.822075605392456s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2797269821166992s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2890646457672119s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.2586536407470703s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 6.523447275161743s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.021683692932129s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.2897255420684814s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.25603437423706055s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.467526912689209s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.716594934463501s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.2720966339111328s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.243159294128418s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6130213737487793s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.27396559715270996s
Security | Sign check for STW Thesaurus for Economics took 0.26001715660095215s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2854.27983045578s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.7771556377410889s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.021866798400878906s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 6.961822509765625e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00016832351684570312s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 11.924281120300293s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.1920928955078125e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 3058.8880836963654s
Availability | SPARQL endpoint availability check for SudershanTech took 9.703636169433594e-05s
Availability | VoID file availability check for SudershanTech took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.27443528175354004s
Reputation | Calculation of the PageRank for SudershanTech took 0.02108931541442871s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.0994415283203125e-05s
Believability | Calculation of trust value for SudershanTech took 1.1205673217773438e-05s
INFO | --- Analysis for SudershanTech took 2.5642435550689697s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.8766090869903564s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.2874605655670166s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.020616769790649414s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.649162292480469e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.1444091796875e-05s
INFO | --- Analysis for sudocfr took 7.4943037033081055s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0160043239593506s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006692409515380859s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 24.717094659805298s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.7414608001708984s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.6937294006347656s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.9005067348480225s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.141490936279297s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.2493557929992676s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5434825420379639s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5474452972412109s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5490918159484863s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5497751235961914s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 8.90979814529419s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.5971882343292236s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.6701273918151855s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.1179399490356445s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5453636646270752s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5499951839447021s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5499179363250732s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.954113721847534s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 6.985664367675781e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5463917255401611s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5566089153289795s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6448342800140381s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5944066047668457s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5756733417510986s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.1056089401245117s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.1113991737365723s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 42.18561291694641s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5575320720672607s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5422337055206299s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5424244403839111s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 3.0841526985168457s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.37341856956481934s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5819635391235352s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 32.49637961387634s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.272006034851074s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.4618580341339s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 21.810965061187744s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.9998278617858887s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.734675645828247s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5681121349334717s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4371.884687900543s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.6536984443664551s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 2.7179718017578125e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 9.1552734375e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 1.9073486328125e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.3589859008789062e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 7879.485987663269s
Availability | SPARQL endpoint availability check for Surge Radio took 9.655952453613281e-05s
Availability | VoID file availability check for Surge Radio took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.2889714241027832s
Reputation | Calculation of the PageRank for Surge Radio took 0.02219676971435547s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.344650268554688e-05s
Believability | Calculation of trust value for Surge Radio took 1.1682510375976562e-05s
INFO | --- Analysis for surge-radio took 3.6900510787963867s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 9.34600830078125e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.28095197677612305s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0008072853088378906s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.409385681152344e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.1444091796875e-05s
INFO | --- Analysis for SWAT took 99.01540064811707s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 9.059906005859375e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.45362210273742676s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.2997913360595703s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.021256685256958008s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.866455078125e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.239776611328125e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 5.91586971282959s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.169071912765503s
Availability | VoID file availability check for SweFN-RDF took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.28821301460266113s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.02089381217956543s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.4066696166992188e-05s
INFO | --- Analysis for swefn-rdf took 5.9245617389678955s
Availability | SPARQL endpoint availability check for SwetoDblp took 6.031990051269531e-05s
Availability | VoID file availability check for SwetoDblp took 0.0008652210235595703s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.28997349739074707s
Reputation | Calculation of the PageRank for SwetoDblp took 0.021962881088256836s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 5.340576171875e-05s
Believability | Calculation of trust value for SwetoDblp took 9.5367431640625e-06s
INFO | --- Analysis for sweto-dblp took 22.93117356300354s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.42455410957336426s
Availability | VoID file availability check for Swift Vocabulary took 0.0006573200225830078s
Extra | Recovery of all triples for Swift Vocabulary took 2.046832799911499s
Performance | Total latancy measurement for Swift Vocabulary took 0.9820036888122559s
Amount of data | Number of triples check for Swift Vocabulary took 0.17063474655151367s
Interoperability | New terms check for Swift Vocabulary took 1.4625585079193115s
Versatility | Languages check for Swift Vocabulary took 0.15137982368469238s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.2062830924987793s
Interpretability | RDF structures check for Swift Vocabulary took 0.21527385711669922s
Versatility | Serialization formats check for Swift Vocabulary took 0.21073555946350098s
Availability | RDF dump link check for Swift Vocabulary took 0.20780229568481445s
License | MR license check for Swift Vocabulary took 0.1756124496459961s
License | HR license check for Swift Vocabulary took 0.16296768188476562s
Amount of data | Number of property check for Swift Vocabulary took 0.17317986488342285s
Understandability | Number of label check for Swift Vocabulary took 0.17595219612121582s
Understandability | URI regex check for Swift Vocabulary took 0.3888254165649414s
Understandability | Vocabs check for Swift Vocabulary took 0.22847580909729004s
Verifiability | Authors check for Swift Vocabulary took 0.22755670547485352s
Verifiability | Publishers check for Swift Vocabulary took 0.18936920166015625s
Performance | Throughput check for Swift Vocabulary took 10.747253656387329s
Amount of data | Check the number of entities for Swift Vocabulary took 6.794929504394531e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.20767855644226074s
Interlinking | sameAs chians check for Swift Vocabulary took 0.20548152923583984s
Interlinking | skos check for Swift Vocabulary took 0.20660924911499023s
Interlinking | skos check for Swift Vocabulary took 0.20756316184997559s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.20755624771118164s
Currency | Creation date check for Swift Vocabulary took 0.4395599365234375s
Currency | Modification date check for Swift Vocabulary took 0.42149996757507324s
Rep.Conc. | URIs length for Swift Vocabulary took 0.885570764541626s
Interoperability | New vocabularies check for Swift Vocabulary took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.18856239318847656s
Accuracy | Check Functional Property for Swift Vocabulary took 0.1892993450164795s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.20668768882751465s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.3060760498046875s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.00254058837890625s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03588700294494629s
Consistency | Disjoint class check for Swift Vocabulary took 0.22485804557800293s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.4763965606689453s
Consistency | Misplaced classes for Swift Vocabulary took 0.2767353057861328s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.569521427154541s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.2839999198913574s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.450253963470459s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.02606797218322754s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.1520061492919922s
Security | Sign check for Swift Vocabulary took 0.16941022872924805s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 937.8210887908936s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.624129056930542s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.021763086318969727s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 7.939338684082031e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 1.9073486328125e-06s
Believability | Calculation of trust value for Swift Vocabulary took 1.1444091796875e-05s
INFO | --- Analysis for Swift took 984.1667349338531s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.363059997558594e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.28804540634155273s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.075599670410156e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.0728836059570312e-05s
INFO | --- Analysis for symptoms-in-chinese took 53.0857834815979s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.5495705604553223s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0006916522979736328s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.4852333068847656s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.8997757434844971s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 34.77489352226257s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 18.677950859069824s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.1806943416595459s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.4015653133392334s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.1213521957397461s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.6560914516448975s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.3024790287017822s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.1837918758392334s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.36058568954467773s
License | HR license check for National Digital Data Archive of Hungary (partial) took 53.57876110076904s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.46579861640930176s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 32.64194107055664s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.36538219451904297s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.2419276237487793s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.17835330963134766s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.17706656455993652s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.374934673309326s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 8.392333984375e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.692840814590454s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.8013226985931396s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.670487642288208s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.6649067401885986s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.7019195556640625s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.3593828678131104s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 3.1754183769226074s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 62.08231544494629s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.17231297492980957s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.19007253646850586s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.17561602592468262s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2359781265258789s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.002672910690307617s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0028274059295654297s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.16628003120422363s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 44.220855474472046s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2751026153564453s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.592966079711914s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.2982902526855469s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.458239793777466s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.001992464065551758s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.44513440132141113s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.17365431785583496s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 9.477444887161255s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.39130568504333496s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.02230548858642578s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.916854858398438e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.430511474609375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 1.2159347534179688e-05s
INFO | --- Analysis for sztaki-lod took 530.2711699008942s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 8.96453857421875e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.30332112312316895s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.021135568618774414s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.2159347534179688e-05s
INFO | --- Analysis for t4gm-info took 3.067656993865967s
Availability | SPARQL endpoint availability check for tags2con delicious took 8.654594421386719e-05s
Availability | VoID file availability check for tags2con delicious took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.3103444576263428s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020873308181762695s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.100799560546875e-05s
Believability | Calculation of trust value for tags2con delicious took 1.1444091796875e-05s
INFO | --- Analysis for tags2con-delicious took 44.93843460083008s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 262.50751972198486s
Availability | VoID file availability check for Taiwan geographic names took 0.000820159912109375s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.3374018669128418s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.021224498748779297s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 6.937980651855469e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.1975250244140625e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.0728836059570312e-05s
INFO | --- Analysis for taiwan-geographic-names took 666.5230059623718s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 9.918212890625e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.38379359245300293s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.021953821182250977s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.226799011230469e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.3589859008789062e-05s
INFO | --- Analysis for talis-openlibrary took 4.312394857406616s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.8716919422149658s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.2916443347930908s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020946264266967773s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00011873245239257812s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.2636184692382812e-05s
INFO | --- Analysis for taxonconcept took 13.247714281082153s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 9.1552734375e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.29176878929138184s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.022623062133789062s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.726119995117188e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.2874603271484375e-05s
INFO | --- Analysis for taxonconcept-assets took 3.209033966064453s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 8.511543273925781e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.2824685573577881s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02093195915222168s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.269050598144531e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.3589859008789062e-05s
INFO | --- Analysis for taxonconcept-occurences took 2.9858810901641846s
Availability | SPARQL endpoint availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 21.22147297859192s
Availability | VoID file availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.2940027713775635s
Reputation | Calculation of the PageRank for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 5.412101745605469e-05s
Believability | Calculation of trust value for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.239776611328125e-05s
INFO | --- Analysis for taxref-ld took 75.2830536365509s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.56636095046997s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0005967617034912109s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.287611722946167s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.02096700668334961s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.838539123535156e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.1205673217773438e-05s
INFO | --- Analysis for tcga took 541.00546002388s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3486819267272949s
Availability | VoID file availability check for TCGA Roadmap took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.27617335319519043s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.021724224090576172s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.486343383789062e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.0251998901367188e-05s
INFO | --- Analysis for tcga-roadmap took 6.295384407043457s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 2.13242244720459s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.33443737030029297s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.0211336612701416s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010895729064941406s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.239776611328125e-05s
INFO | --- Analysis for tcmgenedit_dataset took 143.06614470481873s
Availability | SPARQL endpoint availability check for TDS took 8.749961853027344e-05s
Availability | VoID file availability check for TDS took 0.000843048095703125s
Completeness | Calculation of interlinking completeness for TDS took 0.2876424789428711s
Reputation | Calculation of the PageRank for TDS took 0.020700931549072266s
Interlinking | Calculation of Degree of Connection for TDS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for TDS took 3.886222839355469e-05s
Believability | Calculation of trust value for TDS took 7.867813110351562e-06s
INFO | --- Analysis for tds took 4.947050333023071s
Availability | SPARQL endpoint availability check for TEKORD took 8.606910705566406e-05s
Availability | VoID file availability check for TEKORD took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for TEKORD took 0.30081677436828613s
Reputation | Calculation of the PageRank for TEKORD took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.4345855712890625e-05s
Believability | Calculation of trust value for TEKORD took 1.2159347534179688e-05s
INFO | --- Analysis for tekord took 5.290060520172119s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 3.176391124725342s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.286696195602417s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.021454572677612305s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00010585784912109375s
Believability | Calculation of trust value for Telegraphis Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for telegraphis took 9.469023942947388s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 8.940696716308594e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.3014225959777832s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.021157026290893555s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.295608520507812e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.3113021850585938e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 13.695186614990234s
Availability | SPARQL endpoint availability check for Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Ontology took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Ontology took 0.28827857971191406s
Reputation | Calculation of the PageRank for Ontology took 0.020772218704223633s
Interlinking | Calculation of Degree of Connection for Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.218650817871094e-05s
Believability | Calculation of trust value for Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for Terrorist_attack took 3.194164276123047s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.506111145019531e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.2720057964324951s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020893335342407227s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.695487976074219e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.3113021850585938e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 2.572399377822876s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.3392181396484375e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.2741367816925049s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.020827054977416992s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.170967102050781e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.0967254638671875e-05s
INFO | --- Analysis for Tesla_Deaths took 3.595608949661255s
Availability | SPARQL endpoint availability check for test took 4.315376281738281e-05s
Availability | VoID file availability check for test took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for test took 0.28495073318481445s
Reputation | Calculation of the PageRank for test took 0.021017789840698242s
Interlinking | Calculation of Degree of Connection for test took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for test took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for test took 3.123283386230469e-05s
Believability | Calculation of trust value for test took 1.2636184692382812e-05s
INFO | --- Analysis for test took 2.5654373168945312s
Availability | SPARQL endpoint availability check for Test took 4.315376281738281e-05s
Availability | VoID file availability check for Test took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Test took 0.2752068042755127s
Reputation | Calculation of the PageRank for Test took 0.021322011947631836s
Interlinking | Calculation of Degree of Connection for Test took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Test took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Test took 3.24249267578125e-05s
Believability | Calculation of trust value for Test took 1.1920928955078125e-05s
INFO | --- Analysis for Test took 2.5836472511291504s
Availability | SPARQL endpoint availability check for test-svu took 20.202213764190674s
Availability | VoID file availability check for test-svu took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for test-svu took 0.308840274810791s
Reputation | Calculation of the PageRank for test-svu took 0.022368907928466797s
Interlinking | Calculation of Degree of Connection for test-svu took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for test-svu took 2.9325485229492188e-05s
Believability | Calculation of trust value for test-svu took 7.62939453125e-06s
INFO | --- Analysis for test-svu took 52.8782103061676s
Availability | SPARQL endpoint availability check for Test took 9.942054748535156e-05s
Availability | VoID file availability check for Test took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Test took 0.2869222164154053s
Reputation | Calculation of the PageRank for Test took 0.02092432975769043s
Interlinking | Calculation of Degree of Connection for Test took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Test took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Test took 3.314018249511719e-05s
Believability | Calculation of trust value for Test took 1.4543533325195312e-05s
INFO | --- Analysis for Test_ took 2.614766836166382s
Availability | SPARQL endpoint availability check for xxxxx took 260.5125255584717s
Availability | VoID file availability check for xxxxx took 0.0008344650268554688s
Completeness | Calculation of interlinking completeness for xxxxx took 0.4237055778503418s
Reputation | Calculation of the PageRank for xxxxx took 0.02208113670349121s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for xxxxx took 5.5789947509765625e-05s
Believability | Calculation of trust value for xxxxx took 7.62939453125e-06s
INFO | --- Analysis for testee took 795.6019556522369s
Availability | SPARQL endpoint availability check for tharawat magazine took 8.702278137207031e-05s
Availability | VoID file availability check for tharawat magazine took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.287278413772583s
Reputation | Calculation of the PageRank for tharawat magazine took 0.021427154541015625s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00011658668518066406s
Believability | Calculation of trust value for tharawat magazine took 1.2636184692382812e-05s
INFO | --- Analysis for tharawat-magazine-com took 3.260937452316284s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.5151879787445068s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.2850804328918457s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.021043062210083008s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.0517578125e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.1444091796875e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 7.886833906173706s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 3.3145999908447266s
Availability | VoID file availability check for The European Library Open Dataset took 0.0006816387176513672s
Extra | Recovery of all triples for The European Library Open Dataset took 4.920985460281372s
Performance | Total latancy measurement for The European Library Open Dataset took 15.99277639389038s
Amount of data | Number of triples check for The European Library Open Dataset took 64.04927396774292s
Interoperability | New terms check for The European Library Open Dataset took 60.122223138809204s
Versatility | Languages check for The European Library Open Dataset took 3.1829581260681152s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.201451539993286s
Interpretability | RDF structures check for The European Library Open Dataset took 3.2040140628814697s
Versatility | Serialization formats check for The European Library Open Dataset took 3.2038416862487793s
Availability | RDF dump link check for The European Library Open Dataset took 3.197019577026367s
License | MR license check for The European Library Open Dataset took 3.209096908569336s
License | HR license check for The European Library Open Dataset took 3.1962027549743652s
Amount of data | Number of property check for The European Library Open Dataset took 3.1990134716033936s
Understandability | Number of label check for The European Library Open Dataset took 3.718404531478882s
Understandability | URI regex check for The European Library Open Dataset took 6.390597105026245s
Understandability | Vocabs check for The European Library Open Dataset took 3.200416326522827s
Verifiability | Authors check for The European Library Open Dataset took 3.2014553546905518s
Verifiability | Publishers check for The European Library Open Dataset took 3.19866681098938s
Performance | Throughput check for The European Library Open Dataset took 31.965474367141724s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.2479248046875e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.212000846862793s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.3043828010559082s
Interlinking | skos check for The European Library Open Dataset took 3.2855963706970215s
Interlinking | skos check for The European Library Open Dataset took 3.2334163188934326s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.225511074066162s
Currency | Creation date check for The European Library Open Dataset took 6.395985841751099s
Currency | Modification date check for The European Library Open Dataset took 6.3983776569366455s
Rep.Conc. | URIs length for The European Library Open Dataset took 123.72360944747925s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 3.1819112300872803s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.492692470550537s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.026226520538330078s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.027493715286254883s
Consistency | Disjoint class check for The European Library Open Dataset took 3.205737352371216s
Consistency | Check Misplaced properties for The European Library Open Dataset took 67.75875401496887s
Consistency | Misplaced classes for The European Library Open Dataset took 2.53633975982666s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.848761558532715s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.2851850986480713s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 65.03862142562866s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.033068180084228516s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 3.2062151432037354s
Security | Sign check for The European Library Open Dataset took 3.198580503463745s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 10.978270530700684s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.5031599998474121s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.021212339401245117s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.580352783203125e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for the-european-library-open-dataset took 910.1112639904022s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.05522847175598s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.2765984535217285s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.021788597106933594s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.000102996826171875s
Believability | Calculation of trust value for The Eurostat Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for the-eurostat-linked-data took 242.95558285713196s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.2438507080078125e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.00036525726318359375s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.2758345603942871s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.021810054779052734s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.367134094238281e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.3828277587890625e-05s
INFO | --- Analysis for the-living-lod-cloud took 43.38213276863098s
Availability | SPARQL endpoint availability check for The View From took 4.594666004180908s
Availability | VoID file availability check for The View From took 0.0003006458282470703s
Completeness | Calculation of interlinking completeness for The View From took 0.2747178077697754s
Reputation | Calculation of the PageRank for The View From took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for The View From took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for The View From took 8.106231689453125e-05s
Believability | Calculation of trust value for The View From took 1.239776611328125e-05s
INFO | --- Analysis for the-view-from took 10.034070491790771s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.469226360321045s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2856404781341553s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020932674407958984s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.7670135498046875e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 9.5367431640625e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.24502658843994s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.073355436325073s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0007944107055664062s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.28955578804016113s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.02080821990966797s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.814697265625e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.2636184692382812e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 102.9629852771759s
Availability | SPARQL endpoint availability check for The Content Wrangler took 5.459785461425781e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.28098249435424805s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.0212857723236084s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 9.846687316894531e-05s
Believability | Calculation of trust value for The Content Wrangler took 1.239776611328125e-05s
INFO | --- Analysis for thecontentwrangler-com took 3.0789546966552734s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.220008850097656e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.2753303050994873s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 2.6941299438476562e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 1.1920928955078125e-05s
INFO | --- Analysis for thesaurus-datenwissen took 2.6422948837280273s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.5790219306945801s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.3033297061920166s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.200241088867188e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.0967254638671875e-05s
INFO | --- Analysis for thesaurus-w took 4.126481056213379s
Availability | SPARQL endpoint availability check for theses.fr took 0.00012969970703125s
Availability | VoID file availability check for theses.fr took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for theses.fr took 0.27431750297546387s
Reputation | Calculation of the PageRank for theses.fr took 0.02146172523498535s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.673004150390625e-05s
Believability | Calculation of trust value for theses.fr took 1.0013580322265625e-05s
INFO | --- Analysis for thesesfr took 5.006648063659668s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.124641418457031e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.2934873104095459s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.02093029022216797s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.2901763916015625e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.1205673217773438e-05s
INFO | --- Analysis for Thinkphile took 2.61224627494812s
Availability | SPARQL endpoint availability check for ThIST took 264.8236651420593s
Availability | VoID file availability check for ThIST took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for ThIST took 0.2888646125793457s
Reputation | Calculation of the PageRank for ThIST took 0.0227205753326416s
Interlinking | Calculation of Degree of Connection for ThIST took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.107589721679688e-05s
Believability | Calculation of trust value for ThIST took 1.0967254638671875e-05s
INFO | --- Analysis for thist took 563.0260248184204s
Availability | SPARQL endpoint availability check for TIP took 40.037444829940796s
Availability | VoID file availability check for TIP took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for TIP took 0.295269250869751s
Reputation | Calculation of the PageRank for TIP took 0.020947933197021484s
Interlinking | Calculation of Degree of Connection for TIP took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011038780212402344s
Believability | Calculation of trust value for TIP took 1.0967254638671875e-05s
INFO | --- Analysis for tip took 102.80847716331482s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 8.869171142578125e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0007936954498291016s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.28553128242492676s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.02086496353149414s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.6716461181640625e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.0251998901367188e-05s
INFO | --- Analysis for TOPMODEL took 27.344141006469727s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.439652919769287s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.2744143009185791s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.0219271183013916s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.600120544433594e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.0728836059570312e-05s
INFO | --- Analysis for TP-data took 7.446157217025757s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.3402702808380127s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.28705453872680664s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.022836685180664062s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.363059997558594e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for traditional-korean-medicine took 3.5412254333496094s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.22453832626342773s
Availability | VoID file availability check for Traffic Scotland took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.2867310047149658s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.021010160446166992s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.4332275390625e-05s
Believability | Calculation of trust value for Traffic Scotland took 9.298324584960938e-06s
INFO | --- Analysis for traffic-scotland took 2.8530569076538086s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.2539663314819336s
Availability | VoID file availability check for Transparency International Linked Data took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.2844977378845215s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.021139144897460938s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010633468627929688s
Believability | Calculation of trust value for Transparency International Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for transparency-linked-data took 2.905967950820923s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.6733074188232422s
Availability | VoID file availability check for transport.data.gov.uk took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.2742342948913574s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.02104020118713379s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 8.96453857421875e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 9.5367431640625e-06s
INFO | --- Analysis for transport-data-gov-uk took 4.046137571334839s
Availability | SPARQL endpoint availability check for Trelios took 4.220008850097656e-05s
Availability | VoID file availability check for Trelios took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Trelios took 0.29949522018432617s
Reputation | Calculation of the PageRank for Trelios took 0.020825862884521484s
Interlinking | Calculation of Degree of Connection for Trelios took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Trelios took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.1682510375976562e-05s
Believability | Calculation of trust value for Trelios took 1.1920928955078125e-05s
INFO | --- Analysis for Trelios took 2.6195530891418457s
Availability | SPARQL endpoint availability check for Twarql took 10.536372661590576s
Availability | VoID file availability check for Twarql took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Twarql took 0.28975534439086914s
Reputation | Calculation of the PageRank for Twarql took 0.022512435913085938s
Interlinking | Calculation of Degree of Connection for Twarql took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Twarql took 7.605552673339844e-05s
Believability | Calculation of trust value for Twarql took 1.1920928955078125e-05s
INFO | --- Analysis for twarql took 13.142058372497559s
Availability | SPARQL endpoint availability check for TWC Data-gov took 8.7738037109375e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.29107046127319336s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020946502685546875s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.075599670410156e-05s
Believability | Calculation of trust value for TWC Data-gov took 8.58306884765625e-06s
INFO | --- Analysis for twc-data-gov took 12.937312841415405s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.13814687728881836s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.2921285629272461s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 2.956390380859375e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 8.58306884765625e-06s
INFO | --- Analysis for twc-healthdata took 13.74393081665039s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 3.9699318408966064s
Availability | VoID file availability check for Instance Hub (all) took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.3088111877441406s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.021028518676757812s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 7.82012939453125e-05s
Believability | Calculation of trust value for Instance Hub (all) took 7.867813110351562e-06s
INFO | --- Analysis for twc-hub took 79.62790012359619s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.12420058250427246s
Availability | VoID file availability check for IEEE VIS Source Data took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.3768889904022217s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.022417068481445312s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00010728836059570312s
Believability | Calculation of trust value for IEEE VIS Source Data took 1.0728836059570312e-05s
INFO | --- Analysis for twc-ieeevis took 129.7562711238861s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.1961669921875e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.28814196586608887s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.02234363555908203s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 8.368492126464844e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 8.344650268554688e-06s
INFO | --- Analysis for twc-logd took 2.6924943923950195s
Availability | SPARQL endpoint availability check for twc-opendap took 0.12547564506530762s
Availability | VoID file availability check for twc-opendap took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.2984473705291748s
Reputation | Calculation of the PageRank for twc-opendap took 0.021018266677856445s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 6.604194641113281e-05s
Believability | Calculation of trust value for twc-opendap took 1.0728836059570312e-05s
INFO | --- Analysis for twc-opendap took 51.894957304000854s
Availability | SPARQL endpoint availability check for typepad took 8.893013000488281e-05s
Availability | VoID file availability check for typepad took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for typepad took 0.2980465888977051s
Reputation | Calculation of the PageRank for typepad took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for typepad took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for typepad took 4.935264587402344e-05s
Believability | Calculation of trust value for typepad took 8.106231689453125e-06s
INFO | --- Analysis for typepad took 3.2556049823760986s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.9213104248046875s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.2897520065307617s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.02301025390625s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0009613037109375s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.696846008300781e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.2636184692382812e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 4.934004306793213s
Availability | SPARQL endpoint availability check for Uberblic.org took 5.160841703414917s
Availability | VoID file availability check for Uberblic.org took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.2922327518463135s
Reputation | Calculation of the PageRank for Uberblic.org took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010824203491210938s
Believability | Calculation of trust value for Uberblic.org took 1.2874603271484375e-05s
INFO | --- Analysis for uberblic took 12.63323426246643s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.6535406112670898s
Availability | VoID file availability check for UDante in LiLa took 0.0008218288421630859s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.27762937545776367s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.02129364013671875s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 4.1961669921875e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for UDante took 4.297433376312256s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 0.9869503974914551s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.27486419677734375s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.0218353271484375s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.239776611328125e-05s
INFO | --- Analysis for ufo took 4.868490934371948s
Availability | SPARQL endpoint availability check for Uganda Disasters took 6.4849853515625e-05s
Availability | VoID file availability check for Uganda Disasters took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.28879213333129883s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 4.982948303222656e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.239776611328125e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.637587547302246s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.047162532806396484s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.3096504211425781s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 9.679794311523438e-05s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for uis-linked-data took 2.6601946353912354s
Availability | SPARQL endpoint availability check for UK Legislation took 8.368492126464844e-05s
Availability | VoID file availability check for UK Legislation took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.29648661613464355s
Reputation | Calculation of the PageRank for UK Legislation took 0.022017717361450195s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.749961853027344e-05s
Believability | Calculation of trust value for UK Legislation took 9.059906005859375e-06s
INFO | --- Analysis for uk-legislation-api took 3.646179676055908s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.5299530029296875e-05s
Availability | VoID file availability check for UK Postcodes took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.27666783332824707s
Reputation | Calculation of the PageRank for UK Postcodes took 0.0211331844329834s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.745887756347656e-05s
Believability | Calculation of trust value for UK Postcodes took 1.239776611328125e-05s
INFO | --- Analysis for uk-postcodes took 22.588282108306885s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 8.702278137207031e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00040912628173828125s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.3048093318939209s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.02113175392150879s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0009860992431640625s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00014495849609375s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1205673217773438e-05s
INFO | --- Analysis for umbel took 7.179629564285278s
Availability | SPARQL endpoint availability check for German environmental thesaurus UMTHES took 8.440017700195312e-05s
Availability | VoID file availability check for German environmental thesaurus UMTHES took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for German environmental thesaurus UMTHES took 0.2881312370300293s
Reputation | Calculation of the PageRank for German environmental thesaurus UMTHES took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for German environmental thesaurus UMTHES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for German environmental thesaurus UMTHES took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for German environmental thesaurus UMTHES took 4.0531158447265625e-05s
Believability | Calculation of trust value for German environmental thesaurus UMTHES took 9.298324584960938e-06s
INFO | --- Analysis for umthes took 3.6680493354797363s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.639918327331543s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.2772543430328369s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.0994415283203125e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 9.5367431640625e-06s
INFO | --- Analysis for un-hazardous-numbers took 10.098698377609253s
Availability | SPARQL endpoint availability check for UniProt took 3.6048989295959473s
Availability | VoID file availability check for UniProt took 0.0005259513854980469s
Extra | Recovery of all triples for UniProt took 16.120938301086426s
Performance | Total latancy measurement for UniProt took 6.8948163986206055s
Amount of data | Number of triples check for UniProt took 0.6134295463562012s
Interoperability | New terms check for UniProt took 1.6545350551605225s
Versatility | Languages check for UniProt took 1.4606316089630127s
Interpretability | Number of blank nodes check for UniProt took 3.174625873565674s
Interpretability | RDF structures check for UniProt took 1.6063857078552246s
Versatility | Serialization formats check for UniProt took 2.2354211807250977s
Availability | RDF dump link check for UniProt took 0.43261122703552246s
License | MR license check for UniProt took 1.2184970378875732s
License | HR license check for UniProt took 300.09999108314514s
Amount of data | Number of property check for UniProt took 0.08198976516723633s
Understandability | Number of label check for UniProt took 49.454371213912964s
Understandability | URI regex check for UniProt took 0.8865363597869873s
Understandability | Vocabs check for UniProt took 1.0260405540466309s
Verifiability | Authors check for UniProt took 1.4120676517486572s
Verifiability | Publishers check for UniProt took 1.372908353805542s
Performance | Throughput check for UniProt took 34.22721219062805s
Amount of data | Check the number of entities for UniProt took 7.05718994140625e-05s
Verifiability | Contribs. check for UniProt took 0.6929841041564941s
Interlinking | sameAs chians check for UniProt took 0.4827141761779785s
Interlinking | skos check for UniProt took 1.1439208984375s
Interlinking | skos check for UniProt took 0.8524739742279053s
Timeliness | dataset update frequency check for UniProt took 1.2965590953826904s
Currency | Creation date check for UniProt took 1.4578149318695068s
Currency | Modification date check for UniProt took 1.6914756298065186s
Rep.Conc. | URIs length for UniProt took 122.00141477584839s
Interoperability | New vocabularies check for UniProt took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.37462353706359863s
Accuracy | Check Functional Property for UniProt took 0.34551000595092773s
Accuracy | Check Inverse Functional Property for UniProt took 0.3822596073150635s
Accuracy | Check Empty annotation labels for UniProt took 15.257469654083252s
Accuracy | Check White space in annotation for UniProt took 2.4750912189483643s
Accuracy | Check Datatype consistency for UniProt took 7.13431978225708s
Consistency | Disjoint class check for UniProt took 0.35564756393432617s
Consistency | Check Misplaced properties for UniProt took 2.4014055728912354s
Consistency | Check Ontology hijacking for UniProt took 8.323760986328125s
Consistency | Check Invalid usage of undefined classes for UniProt took 18598.13152575493s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.8729729652404785s
Conciseness | Check Extensional conciseness for UniProt took 2.6168150901794434s
Conciseness | Check Intensional conciseness for UniProt took 0.735457181930542s
Security | Sign check for UniProt took 1.248396873474121s
Availability | Check URIs Dereferenciability for UniProt took 4.490999698638916s
Completeness | Calculation of interlinking completeness for UniProt took 0.8063857555389404s
Reputation | Calculation of the PageRank for UniProt took 0.021162748336791992s
Interlinking | Calculation of Degree of Connection for UniProt took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProt took 1.049041748046875e-05s
INFO | --- Analysis for UniProt took 19621.515377998352s
Availability | SPARQL endpoint availability check for UniProt took 3.3783047199249268s
Availability | VoID file availability check for UniProt took 0.000732421875s
Extra | Recovery of all triples for UniProt took 17.55149531364441s
Performance | Total latancy measurement for UniProt took 7.5753889083862305s
Amount of data | Number of triples check for UniProt took 0.6504032611846924s
Versatility | Languages check for UniProt took 1.8658924102783203s
Interpretability | Number of blank nodes check for UniProt took 3.396028995513916s
Security | Check HTTPS for UniProt took 3.5395071506500244s
Interpretability | RDF structures check for UniProt took 0.19225668907165527s
Versatility | Serialization formats check for UniProt took 0.1880335807800293s
Availability | RDF dump link check for UniProt took 0.17149949073791504s
License | MR license check for UniProt took 0.16924071311950684s
License | HR license check for UniProt took 0.16881942749023438s
Amount of data | Number of property check for UniProt took 0.17021632194519043s
Understandability | Number of label check for UniProt took 0.1981644630432129s
Understandability | URI regex check for UniProt took 0.3471832275390625s
Understandability | Vocabs check for UniProt took 0.175370454788208s
Verifiability | Authors check for UniProt took 0.1575613021850586s
Verifiability | Publishers check for UniProt took 0.16852951049804688s
Performance | Throughput check for UniProt took 38.555633306503296s
Amount of data | Check the number of entities for UniProt took 0.00012230873107910156s
Verifiability | Contribs. check for UniProt took 0.22667407989501953s
Interlinking | sameAs chians check for UniProt took 0.16563057899475098s
Interlinking | skos check for UniProt took 0.19551849365234375s
Interlinking | skos check for UniProt took 0.13391685485839844s
Timeliness | dataset update frequency check for UniProt took 0.1854414939880371s
Currency | Creation date check for UniProt took 0.36839985847473145s
Currency | Modification date check for UniProt took 0.34341883659362793s
Rep.Conc. | URIs length for UniProt took 117.89724397659302s
Interoperability | New vocabularies check for UniProt took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.17893743515014648s
Accuracy | Check Datatype consistency for UniProt took 7.226086139678955s
Consistency | Disjoint class check for UniProt took 0.18131375312805176s
Consistency | Check Ontology hijacking for UniProt took 0.16565752029418945s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.5784740447998047s
Conciseness | Check Extensional conciseness for UniProt took 2.650773286819458s
Security | Sign check for UniProt took 0.1669750213623047s
Availability | Check URIs Dereferenciability for UniProt took 4.118290185928345s
Completeness | Calculation of interlinking completeness for UniProt took 0.3784065246582031s
Reputation | Calculation of the PageRank for UniProt took 0.02126789093017578s
Interlinking | Calculation of Degree of Connection for UniProt took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 7.152557373046875e-07s
Believability | Calculation of trust value for UniProt took 6.198883056640625e-06s
INFO | --- Analysis for uniprot took 755.2416830062866s
Availability | SPARQL endpoint availability check for uniprot-metadata took 7.081031799316406e-05s
Availability | VoID file availability check for uniprot-metadata took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.30680060386657715s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020964384078979492s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.079673767089844e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.239776611328125e-05s
INFO | --- Analysis for uniprot-metadata took 4.094494819641113s
Availability | SPARQL endpoint availability check for UniProtKB took 3.2020959854125977s
Availability | VoID file availability check for UniProtKB took 0.0005645751953125s
Extra | Recovery of all triples for UniProtKB took 18.193838357925415s
Performance | Total latancy measurement for UniProtKB took 6.851208448410034s
Amount of data | Number of triples check for UniProtKB took 0.5234503746032715s
Interoperability | New terms check for UniProtKB took 1.7655596733093262s
Versatility | Languages check for UniProtKB took 1.593308448791504s
Interpretability | Number of blank nodes check for UniProtKB took 3.1835005283355713s
Interpretability | RDF structures check for UniProtKB took 2.008615255355835s
Versatility | Serialization formats check for UniProtKB took 2.265740394592285s
Availability | RDF dump link check for UniProtKB took 0.2911999225616455s
License | MR license check for UniProtKB took 1.2369253635406494s
License | HR license check for UniProtKB took 300.11721634864807s
Amount of data | Number of property check for UniProtKB took 0.15265965461730957s
Understandability | Number of label check for UniProtKB took 51.82799506187439s
Understandability | URI regex check for UniProtKB took 0.8841431140899658s
Understandability | Vocabs check for UniProtKB took 0.7662539482116699s
Verifiability | Authors check for UniProtKB took 1.3775317668914795s
Verifiability | Publishers check for UniProtKB took 1.2290570735931396s
Performance | Throughput check for UniProtKB took 37.128321409225464s
Amount of data | Check the number of entities for UniProtKB took 9.1552734375e-05s
Verifiability | Contribs. check for UniProtKB took 0.710857629776001s
Interlinking | sameAs chians check for UniProtKB took 0.4905102252960205s
Interlinking | skos check for UniProtKB took 1.167588472366333s
Interlinking | skos check for UniProtKB took 0.8380491733551025s
Timeliness | dataset update frequency check for UniProtKB took 1.4472718238830566s
Currency | Creation date check for UniProtKB took 1.4526011943817139s
Currency | Modification date check for UniProtKB took 1.8234007358551025s
Rep.Conc. | URIs length for UniProtKB took 115.22436881065369s
Interoperability | New vocabularies check for UniProtKB took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.3728828430175781s
Accuracy | Check Functional Property for UniProtKB took 0.34799885749816895s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.3601226806640625s
Accuracy | Check Empty annotation labels for UniProtKB took 11.299792289733887s
Accuracy | Check White space in annotation for UniProtKB took 2.461561441421509s
Accuracy | Check Datatype consistency for UniProtKB took 7.141868352890015s
Consistency | Disjoint class check for UniProtKB took 0.4748358726501465s
Consistency | Check Misplaced properties for UniProtKB took 2.5408711433410645s
Consistency | Check Ontology hijacking for UniProtKB took 8.60251522064209s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 19719.53790640831s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 2.0104315280914307s
Conciseness | Check Extensional conciseness for UniProtKB took 2.6623849868774414s
Conciseness | Check Intensional conciseness for UniProtKB took 0.7583186626434326s
Security | Sign check for UniProtKB took 1.1870028972625732s
Availability | Check URIs Dereferenciability for UniProtKB took 4.454623460769653s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.8651628494262695s
Reputation | Calculation of the PageRank for UniProtKB took 0.021675825119018555s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProtKB took 7.867813110351562e-06s
INFO | --- Analysis for uniprotkb took 20742.897261857986s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 9.059906005859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.3096742630004883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.709168195724487s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.00011038780212402344s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.30915069580078125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0207517147064209s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 4.070898056030273s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 8.678436279296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.29199814796447754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.696846008300781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.502792358398438s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.3402895927429199s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.021541357040405273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.546088933944702s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.3127107620239258s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.504770755767822s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 8.630752563476562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0007593631744384766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.2649984359741211s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.02118659019470215s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.300880670547485s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 8.678436279296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.3199422359466553s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 4.437887907028198s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.3044865131378174s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.536892175674438s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.2914443016052246s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.022211074829101562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.384281396865845s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 8.7738037109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.3460240364074707s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.520458221435547s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 8.678436279296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.3426694869995117s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.022106170654296875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.383378982543945s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 8.559226989746094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0007967948913574219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.28180932998657227s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.021355867385864258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0009903907775878906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.792213439941406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.275530338287354s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.2893660068511963s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.251055955886841s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.2944762706756592s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.021173715591430664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.449251651763916s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.2999539375305176s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.022104978561401367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.52587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.29855751991272s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.2967336177825928s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.020731210708618164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.435768842697144s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0007932186126708984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.37502622604370117s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.02119755744934082s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.332093715667725s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 9.1552734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.32178497314453125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.021773099899291992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.214597702026367s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.3091919422149658s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.021723270416259766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.436424493789673s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.2859921455383301s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 4.079801321029663s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 8.726119995117188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0007696151733398438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.3452119827270508s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.02097177505493164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 13.305640459060669s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.27516889572143555s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.020847082138061523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.33113431930542s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0007877349853515625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.31819796562194824s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.020616531372070312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.520627498626709s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.3000352382659912s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.021029949188232422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 3.9129323959350586s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.3030228614807129s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.021101713180541992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 4.102953672409058s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 8.702278137207031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.3002743721008301s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.02139115333557129s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 4.139718294143677s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 8.511543273925781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.3249166011810303s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.02088189125061035s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 4.391905784606934s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 0.00016379356384277344s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.33327364921569824s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.02092885971069336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.41067361831665s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 8.654594421386719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0008382797241210938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.2762577533721924s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.674099445343018s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.649162292480469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.30983543395996094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.021184206008911133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 4.330023288726807s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.30031824111938477s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020746231079101562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.3952054977417s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 8.630752563476562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.32161927223205566s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.02079916000366211s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 5.245208740234375e-06s
INFO | --- Analysis for universal-dependencies-treebank-irish took 4.450714826583862s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.34207797050476074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.021975278854370117s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.393527030944824s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0007491111755371094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.2980082035064697s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.0208437442779541s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.609763145446777s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0007293224334716797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.3446922302246094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020722627639770508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 4.03668737411499s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 9.560585021972656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0008485317230224609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.30034303665161133s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020856857299804688s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.408305168151855s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 8.7738037109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.2766416072845459s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 3.9767682552337646s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.2923867702484131s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.272191047668457s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.29982948303222656s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.02106308937072754s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.312748670578003s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.3301064968109131s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.021516799926757812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.561650514602661s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 8.96453857421875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.40282607078552246s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020955324172973633s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.428008079528809s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 8.726119995117188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.3219718933105469s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.020865678787231445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.52792763710022s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.30648326873779297s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.02139878273010254s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 4.117142915725708s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 9.059906005859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.29682064056396484s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.468115091323853s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.3004438877105713s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 13.098104238510132s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 9.036064147949219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0007476806640625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.3467223644256592s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020936250686645508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.259192943572998s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0007627010345458984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.3086049556732178s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.367557525634766s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.96453857421875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.29920363426208496s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.02116227149963379s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0010857582092285156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 5.1021575927734375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.49422550201416s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.3042948246002197s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.417652368545532s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.2625160217285156s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.02084636688232422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 4.039260149002075s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0008349418640136719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.3038325309753418s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.02096843719482422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.658891439437866s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0007052421569824219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.3018300533294678s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.020914554595947266s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.57103180885315s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.34606194496154785s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.020968198776245117s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.506409406661987s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0007188320159912109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.29067349433898926s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.021668672561645508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.223592519760132s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 8.511543273925781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.2967844009399414s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.417187690734863s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.28623509407043457s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.021086454391479492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.382814407348633s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.3162527084350586s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.022728919982910156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 4.412943363189697s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 8.559226989746094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.2994515895843506s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 4.048237323760986s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 7.510185241699219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.3010866641998291s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.798732042312622s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.2999129295349121s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.02135157585144043s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.485912084579468s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 9.226799011230469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.2967832088470459s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.02098679542541504s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.501283168792725s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.2641024589538574s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.02088475227355957s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.400211572647095s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 8.654594421386719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.34093451499938965s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.0209043025970459s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 3.528594970703125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.583946943283081s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 9.489059448242188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.3173828125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.420691728591919s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.124641418457031e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.3236987590789795s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.270408630371094e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.0013580322265625e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.596727132797241s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 8.654594421386719e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.2642819881439209s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020427227020263672s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 4.673004150390625e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.0251998901367188e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 3.2441883087158203s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 8.821487426757812e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.30260729789733887s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.02155923843383789s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.719329833984375e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.33514404296875e-05s
INFO | --- Analysis for university-sussex-reading-lists took 3.062045097351074s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 10.259303331375122s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.2653617858886719s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.02351236343383789s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 6.794929504394531e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.2159347534179688e-05s
INFO | --- Analysis for unodc took 24.193344593048096s
Availability | SPARQL endpoint availability check for Super Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Super Ontology took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.3004446029663086s
Reputation | Calculation of the PageRank for Super Ontology took 0.020899057388305664s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 8.463859558105469e-05s
Believability | Calculation of trust value for Super Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for upper-ontology took 3.5947389602661133s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 1.186394214630127s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.284393310546875s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.409385681152344e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Upper_Ontology took 5.241714239120483s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 8.988380432128906e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.3036775588989258s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.1920928955078125e-05s
INFO | --- Analysis for Urban_Atlas_ took 2.7408316135406494s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.5981838703155518s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0005536079406738281s
Extra | Recovery of all triples for Urban Atlas dataset @PSNC took 99.53171634674072s
Performance | Total latancy measurement for Urban Atlas dataset @PSNC took 0.972287654876709s
Amount of data | Number of triples check for Urban Atlas dataset @PSNC took 9.291046857833862s
Interoperability | New terms check for Urban Atlas dataset @PSNC took 14.234423398971558s
Versatility | Languages check for Urban Atlas dataset @PSNC took 300.2473318576813s
Interpretability | Number of blank nodes check for Urban Atlas dataset @PSNC took 2.02779221534729s
Interpretability | RDF structures check for Urban Atlas dataset @PSNC took 0.3816566467285156s
Versatility | Serialization formats check for Urban Atlas dataset @PSNC took 8.391406774520874s
Availability | RDF dump link check for Urban Atlas dataset @PSNC took 0.36722278594970703s
License | MR license check for Urban Atlas dataset @PSNC took 0.6913836002349854s
License | HR license check for Urban Atlas dataset @PSNC took 300.219669342041s
Amount of data | Number of property check for Urban Atlas dataset @PSNC took 0.24318170547485352s
Understandability | Number of label check for Urban Atlas dataset @PSNC took 2.4903292655944824s
Understandability | URI regex check for Urban Atlas dataset @PSNC took 0.44627976417541504s
Understandability | Vocabs check for Urban Atlas dataset @PSNC took 0.6414036750793457s
Verifiability | Authors check for Urban Atlas dataset @PSNC took 0.21951723098754883s
Verifiability | Publishers check for Urban Atlas dataset @PSNC took 0.2348778247833252s
Performance | Throughput check for Urban Atlas dataset @PSNC took 11.631119966506958s
Amount of data | Check the number of entities for Urban Atlas dataset @PSNC took 7.128715515136719e-05s
Verifiability | Contribs. check for Urban Atlas dataset @PSNC took 0.20714998245239258s
Interlinking | sameAs chians check for Urban Atlas dataset @PSNC took 0.21276211738586426s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.5753462314605713s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.43613505363464355s
Timeliness | dataset update frequency check for Urban Atlas dataset @PSNC took 6.0791871547698975s
Currency | Creation date check for Urban Atlas dataset @PSNC took 0.4898974895477295s
Currency | Modification date check for Urban Atlas dataset @PSNC took 0.2661442756652832s
Rep.Conc. | URIs length for Urban Atlas dataset @PSNC took 152.4089925289154s
Interoperability | New vocabularies check for Urban Atlas dataset @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Urban Atlas dataset @PSNC took 0.22216057777404785s
Accuracy | Check Functional Property for Urban Atlas dataset @PSNC took 0.4269075393676758s
Accuracy | Check Inverse Functional Property for Urban Atlas dataset @PSNC took 0.1989433765411377s
Accuracy | Check Empty annotation labels for Urban Atlas dataset @PSNC took 34.15434169769287s
Accuracy | Check White space in annotation for Urban Atlas dataset @PSNC took 2.6394600868225098s
Accuracy | Check Datatype consistency for Urban Atlas dataset @PSNC took 2.6121292114257812s
Consistency | Disjoint class check for Urban Atlas dataset @PSNC took 0.21404576301574707s
Consistency | Check Misplaced properties for Urban Atlas dataset @PSNC took 85.74370050430298s
Consistency | Misplaced classes for Urban Atlas dataset @PSNC took 8.33344030380249s
Consistency | Check Ontology hijacking for Urban Atlas dataset @PSNC took 41.3453094959259s
Consistency | Check Invalid usage of undefined classes for Urban Atlas dataset @PSNC took 1.3793234825134277s
Consistency | Check Invalid usage of undefined properties for Urban Atlas dataset @PSNC took 86.9983594417572s
Conciseness | Check Extensional conciseness for Urban Atlas dataset @PSNC took 2.6721978187561035s
Conciseness | Check Intensional conciseness for Urban Atlas dataset @PSNC took 0.5907740592956543s
Security | Sign check for Urban Atlas dataset @PSNC took 0.3461313247680664s
Availability | Check URIs Dereferenciability for Urban Atlas dataset @PSNC took 10.121757984161377s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.5485227108001709s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.021359682083129883s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for Urban Atlas dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for Urban_Atlas_Dataset took 2259.5797193050385s
Availability | SPARQL endpoint availability check for URIBurner took 0.9636409282684326s
Availability | VoID file availability check for URIBurner took 0.0006015300750732422s
Extra | Recovery of all triples for URIBurner took 121.07477378845215s
Performance | Total latancy measurement for URIBurner took 2.7285618782043457s
Amount of data | Number of triples check for URIBurner took 3.6553537845611572s
Interoperability | New terms check for URIBurner took 37.67476010322571s
Versatility | Languages check for URIBurner took 122.80931043624878s
Interpretability | Number of blank nodes check for URIBurner took 1.8222227096557617s
Security | Check HTTPS for URIBurner took 0.8721201419830322s
Interpretability | RDF structures check for URIBurner took 2.3310651779174805s
Versatility | Serialization formats check for URIBurner took 6.599853515625s
Availability | RDF dump link check for URIBurner took 45.38022494316101s
License | MR license check for URIBurner took 1.2230284214019775s
License | HR license check for URIBurner took 121.44564628601074s
Amount of data | Number of property check for URIBurner took 0.8300158977508545s
Understandability | Number of label check for URIBurner took 3.7092361450195312s
Understandability | URI regex check for URIBurner took 1.3571228981018066s
Understandability | Vocabs check for URIBurner took 0.6280701160430908s
Verifiability | Authors check for URIBurner took 0.7479491233825684s
Verifiability | Publishers check for URIBurner took 0.6207776069641113s
Performance | Throughput check for URIBurner took 10.940139532089233s
Amount of data | Check the number of entities for URIBurner took 9.083747863769531e-05s
Verifiability | Contribs. check for URIBurner took 0.6362161636352539s
Interlinking | sameAs chians check for URIBurner took 1.2188935279846191s
Interlinking | skos check for URIBurner took 0.7551281452178955s
Interlinking | skos check for URIBurner took 0.5280487537384033s
Timeliness | dataset update frequency check for URIBurner took 1.035686731338501s
Currency | Creation date check for URIBurner took 3.2732784748077393s
Currency | Modification date check for URIBurner took 0.7447609901428223s
Rep.Conc. | URIs length for URIBurner took 112.35342931747437s
Interoperability | New vocabularies check for URIBurner took 111.8371696472168s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.6012139320373535s
Accuracy | Check Functional Property for URIBurner took 0.6061105728149414s
Accuracy | Check Inverse Functional Property for URIBurner took 0.5478816032409668s
Accuracy | Check Empty annotation labels for URIBurner took 57.84290933609009s
Accuracy | Check White space in annotation for URIBurner took 0.18541717529296875s
Consistency | Disjoint class check for URIBurner took 0.6140272617340088s
Consistency | Check Misplaced properties for URIBurner took 388.24474906921387s
Consistency | Misplaced classes for URIBurner took 57.7901291847229s
Consistency | Check Ontology hijacking for URIBurner took 56.79996371269226s
Consistency | Check Invalid usage of undefined properties for URIBurner took 58.06128215789795s
Conciseness | Check Extensional conciseness for URIBurner took 0.00020956993103027344s
Conciseness | Check Intensional conciseness for URIBurner took 110.21708965301514s
Security | Sign check for URIBurner took 0.8658576011657715s
Completeness | Calculation of interlinking completeness for URIBurner took 0.690866231918335s
Reputation | Calculation of the PageRank for URIBurner took 0.022921323776245117s
Interlinking | Calculation of Degree of Connection for URIBurner took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00010085105895996094s
Interoperability | Check the re-using of existing vocabs for URIBurner took 132.77303218841553s
Believability | Calculation of trust value for URIBurner took 1.33514404296875e-05s
INFO | --- Analysis for uriburner took 14782.333354473114s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.131431579589844e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.33618831634521484s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02123093605041504s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.719329833984375e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.049041748046875e-05s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.6876258850097656s
Availability | SPARQL endpoint availability check for Legija Stranaca took 8.7738037109375e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.27936697006225586s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.0517578125e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.3113021850585938e-05s
INFO | --- Analysis for Uros_Legija_Susa took 2.7491395473480225s
Availability | SPARQL endpoint availability check for Legija took 8.916854858398438e-05s
Availability | VoID file availability check for Legija took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Legija took 0.3179643154144287s
Reputation | Calculation of the PageRank for Legija took 0.021134614944458008s
Interlinking | Calculation of Degree of Connection for Legija took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Legija took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Legija took 3.147125244140625e-05s
Believability | Calculation of trust value for Legija took 1.239776611328125e-05s
INFO | --- Analysis for Uros_Susa took 2.7980451583862305s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.682969331741333s
Availability | VoID file availability check for USAGE review corpus took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.28396058082580566s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.021770000457763672s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.123283386230469e-05s
Believability | Calculation of trust value for USAGE review corpus took 9.059906005859375e-06s
INFO | --- Analysis for usage-review-corpus took 4.502896785736084s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 4.250450611114502s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.341933012008667s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.414817810058594e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for utpl-lod took 11.154048204421997s
Availability | SPARQL endpoint availability check for terrorist attack took 0.00022530555725097656s
Availability | VoID file availability check for terrorist attack took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.3469717502593994s
Reputation | Calculation of the PageRank for terrorist attack took 0.022319555282592773s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 2.9325485229492188e-05s
Believability | Calculation of trust value for terrorist attack took 1.2636184692382812e-05s
INFO | --- Analysis for varsha took 4.517277717590332s
Availability | SPARQL endpoint availability check for VA took 9.059906005859375e-05s
Availability | VoID file availability check for VA took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for VA took 0.27895069122314453s
Reputation | Calculation of the PageRank for VA took 0.021950960159301758s
Interlinking | Calculation of Degree of Connection for VA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VA took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for VA took 3.0279159545898438e-05s
Believability | Calculation of trust value for VA took 1.0728836059570312e-05s
INFO | --- Analysis for Vehicule_Autonome took 2.911515951156616s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.6728634834289551s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.3026702404022217s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.021183252334594727s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 1.3113021850585938e-05s
INFO | --- Analysis for VelezIndexTotiusArtis took 4.421237468719482s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.53898286819458s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.35134029388427734s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.021914243698120117s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 9.179115295410156e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.0728836059570312e-05s
INFO | --- Analysis for verrijktkoninkrijk took 15.393755674362183s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 8.893013000488281e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.3269491195678711s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.0207216739654541s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.000164031982421875s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.239776611328125e-05s
INFO | --- Analysis for viaf took 19.915767192840576s
Availability | SPARQL endpoint availability check for Vihar Exports took 4.4345855712890625e-05s
Availability | VoID file availability check for Vihar Exports took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.27445459365844727s
Reputation | Calculation of the PageRank for Vihar Exports took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 2.8133392333984375e-05s
Believability | Calculation of trust value for Vihar Exports took 1.049041748046875e-05s
INFO | --- Analysis for Vihar_Exports took 2.6595966815948486s
Availability | SPARQL endpoint availability check for VIVO took 4.291534423828125e-05s
Availability | VoID file availability check for VIVO took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for VIVO took 0.2999424934387207s
Reputation | Calculation of the PageRank for VIVO took 0.020943164825439453s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.723403930664062e-05s
Believability | Calculation of trust value for VIVO took 1.239776611328125e-05s
INFO | --- Analysis for vivo took 5.1923840045928955s
Availability | SPARQL endpoint availability check for VIVO Cornell took 8.7738037109375e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.2774794101715088s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.034706115722656e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.3589859008789062e-05s
INFO | --- Analysis for vivo-cornell-university took 6.2716896533966064s
Availability | SPARQL endpoint availability check for VIVO Indiana took 8.893013000488281e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2865176200866699s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.022216320037841797s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 9.250640869140625e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.33514404296875e-05s
INFO | --- Analysis for vivo-indiana-university took 3.32143497467041s
Availability | SPARQL endpoint availability check for VIVO Ponce took 7.534027099609375e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.29144906997680664s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.02050161361694336s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.075599670410156e-05s
Believability | Calculation of trust value for VIVO Ponce took 4.76837158203125e-06s
INFO | --- Analysis for vivo-ponce took 3.220430374145508s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 4.1961669921875e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.3022654056549072s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.020826339721679688s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.7670135498046875e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 1.3589859008789062e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 3.299450159072876s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.26302313804626465s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.021555185317993164s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.131431579589844e-05s
Believability | Calculation of trust value for VIVO University of Florida took 1.3589859008789062e-05s
INFO | --- Analysis for vivo-university-of-florida took 2.8634417057037354s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 8.20159912109375e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.3091120719909668s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.504753112792969e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 7.3909759521484375e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 3.0206713676452637s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.1484832763671875e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.30628538131713867s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.02175307273864746s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.4809112548828125e-05s
Believability | Calculation of trust value for VIVO WUSTL took 7.3909759521484375e-06s
INFO | --- Analysis for vivo-wustl took 3.1449763774871826s
Availability | SPARQL endpoint availability check for vivo2doi took 4.1961669921875e-05s
Availability | VoID file availability check for vivo2doi took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.3205862045288086s
Reputation | Calculation of the PageRank for vivo2doi took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.0531158447265625e-05s
Believability | Calculation of trust value for vivo2doi took 1.1682510375976562e-05s
INFO | --- Analysis for vivo2doi took 26.382086038589478s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 8.726119995117188e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.30169105529785156s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.628036499023438e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.1444091796875e-05s
INFO | --- Analysis for vu-wordnet took 15.387290716171265s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.14716100692749023s
Availability | VoID file availability check for vulnerapedia took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.2771008014678955s
Reputation | Calculation of the PageRank for vulnerapedia took 0.021879196166992188s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.413459777832031e-05s
Believability | Calculation of trust value for vulnerapedia took 1.239776611328125e-05s
INFO | --- Analysis for vulnerapedia took 3.2204809188842773s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 9.059906005859375e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.28578639030456543s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1920928955078125e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.3113021850585938e-05s
INFO | --- Analysis for VVASIAK took 2.685680627822876s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 8.678436279296875e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.27919459342956543s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 2.956390380859375e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.239776611328125e-05s
INFO | --- Analysis for Vyvasta took 2.682196617126465s
Availability | SPARQL endpoint availability check for W3C took 8.654594421386719e-05s
Availability | VoID file availability check for W3C took 0.0007772445678710938s
Completeness | Calculation of interlinking completeness for W3C took 0.28870344161987305s
Reputation | Calculation of the PageRank for W3C took 0.021182537078857422s
Interlinking | Calculation of Degree of Connection for W3C took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001354217529296875s
Believability | Calculation of trust value for W3C took 1.239776611328125e-05s
INFO | --- Analysis for w3c took 3.013045072555542s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 8.559226989746094e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.3331632614135742s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.020710468292236328s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00010848045349121094s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.1444091796875e-05s
INFO | --- Analysis for w3c-wordnet took 3.791619062423706s
Availability | SPARQL endpoint availability check for WarSampo took 0.3920104503631592s
Availability | VoID file availability check for WarSampo took 0.0008578300476074219s
Extra | Recovery of all triples for WarSampo took 25.151170253753662s
Performance | Total latancy measurement for WarSampo took 0.8194832801818848s
Amount of data | Number of triples check for WarSampo took 20.750678300857544s
Interoperability | New terms check for WarSampo took 4.118505001068115s
Versatility | Languages check for WarSampo took 53.2605345249176s
Interpretability | Number of blank nodes check for WarSampo took 18.198997974395752s
Security | Check HTTPS for WarSampo took 0.41080260276794434s
Interpretability | RDF structures check for WarSampo took 0.18006062507629395s
Versatility | Serialization formats check for WarSampo took 0.17854046821594238s
Availability | RDF dump link check for WarSampo took 0.7802534103393555s
License | MR license check for WarSampo took 0.1910533905029297s
License | HR license check for WarSampo took 49.68884539604187s
Amount of data | Number of property check for WarSampo took 0.18324565887451172s
Understandability | Number of label check for WarSampo took 9.408926248550415s
Understandability | URI regex check for WarSampo took 0.3555588722229004s
Understandability | Vocabs check for WarSampo took 0.17159366607666016s
Verifiability | Authors check for WarSampo took 0.19287753105163574s
Verifiability | Publishers check for WarSampo took 0.18513870239257812s
Performance | Throughput check for WarSampo took 11.196920394897461s
Amount of data | Check the number of entities for WarSampo took 15.250845670700073s
Verifiability | Contribs. check for WarSampo took 0.20295262336730957s
Interlinking | sameAs chians check for WarSampo took 0.2068331241607666s
Interlinking | skos check for WarSampo took 0.20510554313659668s
Interlinking | skos check for WarSampo took 0.1567401885986328s
Timeliness | dataset update frequency check for WarSampo took 0.17248797416687012s
Currency | Creation date check for WarSampo took 0.35596275329589844s
Currency | Modification date check for WarSampo took 0.37429213523864746s
Rep.Conc. | URIs length for WarSampo took 50.21762251853943s
Interoperability | New vocabularies check for WarSampo took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.17709875106811523s
Accuracy | Check Functional Property for WarSampo took 0.19002938270568848s
Accuracy | Check Inverse Functional Property for WarSampo took 0.16207337379455566s
Accuracy | Check Empty annotation labels for WarSampo took 10.828038454055786s
Accuracy | Check White space in annotation for WarSampo took 2.172161340713501s
Accuracy | Check Datatype consistency for WarSampo took 5.3970701694488525s
Consistency | Disjoint class check for WarSampo took 0.19651198387145996s
Consistency | Check Misplaced properties for WarSampo took 21.31128716468811s
Consistency | Check Ontology hijacking for WarSampo took 20.731913805007935s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.3877434730529785s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.6381940841674805s
Conciseness | Check Extensional conciseness for WarSampo took 2.7995433807373047s
Conciseness | Check Intensional conciseness for WarSampo took 0.2532482147216797s
Security | Sign check for WarSampo took 0.16435480117797852s
Availability | Check URIs Dereferenciability for WarSampo took 2.58589243888855s
Completeness | Calculation of interlinking completeness for WarSampo took 0.4005274772644043s
Reputation | Calculation of the PageRank for WarSampo took 0.021411895751953125s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.535385131835938e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for WarSampo took 1.1205673217773438e-05s
INFO | --- Analysis for warsampo took 960.9942393302917s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.418094158172607s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.2832674980163574s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.62939453125e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.1920928955078125e-05s
INFO | --- Analysis for wasabi took 55.26024651527405s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.7283267974853516s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.00046133995056152344s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 114.50097894668579s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 0.9838268756866455s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 9.236656188964844s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 14.12762713432312s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 300.20545172691345s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 2.019778251647949s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.19518303871154785s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 10.765198230743408s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.19590091705322266s
License | MR license check for FAO water areas classification as linked data @PSNC took 0.21015214920043945s
License | HR license check for FAO water areas classification as linked data @PSNC took 300.22554183006287s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.20785021781921387s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 1.225773572921753s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 0.41174793243408203s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.36188459396362305s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.23433828353881836s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.22133350372314453s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 11.407155275344849s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 8.535385131835938e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.20269083976745605s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.1997075080871582s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.4662749767303467s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.4188265800476074s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 5.431872606277466s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.5188069343566895s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.23684072494506836s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 144.04979133605957s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.20733857154846191s
Accuracy | Check Functional Property for FAO water areas classification as linked data @PSNC took 0.2090156078338623s
Accuracy | Check Inverse Functional Property for FAO water areas classification as linked data @PSNC took 0.21327853202819824s
Accuracy | Check Empty annotation labels for FAO water areas classification as linked data @PSNC took 35.81639909744263s
Accuracy | Check White space in annotation for FAO water areas classification as linked data @PSNC took 2.634554862976074s
Accuracy | Check Datatype consistency for FAO water areas classification as linked data @PSNC took 2.5772716999053955s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.20616722106933594s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 86.04584169387817s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 8.144560813903809s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 32.298417806625366s
Consistency | Check Invalid usage of undefined classes for FAO water areas classification as linked data @PSNC took 1.3192634582519531s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 86.33077764511108s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 2.676048517227173s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.5867154598236084s
Security | Sign check for FAO water areas classification as linked data @PSNC took 0.1767749786376953s
Availability | Check URIs Dereferenciability for FAO water areas classification as linked data @PSNC took 10.074248313903809s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.5632095336914062s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.020877838134765625s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 4.172325134277344e-05s
Interoperability | Check the re-using of existing vocabs for FAO water areas classification as linked data @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for Water_Areas_Classification took 2251.652933359146s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.1929471492767334s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.0005271434783935547s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 124.96118521690369s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 1.100175142288208s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 8.892189025878906s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 13.881084442138672s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 300.2399318218231s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 1.8119926452636719s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.17566967010498047s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 8.741153478622437s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.20748472213745117s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.20941948890686035s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 300.179758310318s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.21398663520812988s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 1.2316455841064453s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 0.40700244903564453s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.17656707763671875s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.20200610160827637s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.25036168098449707s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 11.446727275848389s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 8.0108642578125e-05s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.21052002906799316s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.21374201774597168s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.4032628536224365s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.4679889678955078s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 6.4061994552612305s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.5229034423828125s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.2293565273284912s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 152.27113032341003s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.37453341484069824s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.1939709186553955s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.1970381736755371s
Accuracy | Check Empty annotation labels for Water buffer dataset from Czech Republic @PSNC took 36.044848918914795s
Accuracy | Check White space in annotation for Water buffer dataset from Czech Republic @PSNC took 2.6480114459991455s
Accuracy | Check Datatype consistency for Water buffer dataset from Czech Republic @PSNC took 2.6634109020233154s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.2651796340942383s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 86.46042680740356s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 8.307919263839722s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 34.760252714157104s
Consistency | Check Invalid usage of undefined classes for Water buffer dataset from Czech Republic @PSNC took 1.3087241649627686s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 86.74974775314331s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 2.709392786026001s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.5653660297393799s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 0.19809699058532715s
Availability | Check URIs Dereferenciability for Water buffer dataset from Czech Republic @PSNC took 10.379359483718872s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.6668863296508789s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.021414756774902344s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for Water buffer dataset from Czech Republic @PSNC took 3.337860107421875e-06s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Water_Buffer took 2262.3644592761993s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.19446611404418945s
Availability | VoID file availability check for WebIsALOD took 0.0006208419799804688s
Extra | Recovery of all triples for WebIsALOD took 1.904980182647705s
Performance | Total latancy measurement for WebIsALOD took 0.43355274200439453s
Amount of data | Number of triples check for WebIsALOD took 27.691278219223022s
Interoperability | New terms check for WebIsALOD took 21.461918592453003s
Versatility | Languages check for WebIsALOD took 61.558337926864624s
Interpretability | Number of blank nodes check for WebIsALOD took 0.10551166534423828s
Interpretability | RDF structures check for WebIsALOD took 0.17029809951782227s
Versatility | Serialization formats check for WebIsALOD took 0.12185335159301758s
Availability | RDF dump link check for WebIsALOD took 1.4731268882751465s
License | MR license check for WebIsALOD took 0.10153484344482422s
License | HR license check for WebIsALOD took 14.349483489990234s
Amount of data | Number of property check for WebIsALOD took 1.5841028690338135s
Understandability | Number of label check for WebIsALOD took 0.3206794261932373s
Understandability | URI regex check for WebIsALOD took 0.18732357025146484s
Understandability | Vocabs check for WebIsALOD took 0.11607694625854492s
Verifiability | Authors check for WebIsALOD took 0.14128494262695312s
Verifiability | Publishers check for WebIsALOD took 0.11118602752685547s
Performance | Throughput check for WebIsALOD took 10.846078395843506s
Amount of data | Check the number of entities for WebIsALOD took 7.534027099609375e-05s
Verifiability | Contribs. check for WebIsALOD took 0.10779356956481934s
Interlinking | sameAs chians check for WebIsALOD took 0.1719515323638916s
Interlinking | skos check for WebIsALOD took 0.12505602836608887s
Interlinking | skos check for WebIsALOD took 0.0818939208984375s
Timeliness | dataset update frequency check for WebIsALOD took 0.10078549385070801s
Currency | Creation date check for WebIsALOD took 0.23633956909179688s
Currency | Modification date check for WebIsALOD took 0.21896910667419434s
Rep.Conc. | URIs length for WebIsALOD took 85.32468938827515s
Interoperability | New vocabularies check for WebIsALOD took 14.523278713226318s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 0.11463737487792969s
Accuracy | Check Functional Property for WebIsALOD took 0.12659573554992676s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.1102907657623291s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.44957709312438965s
Accuracy | Check White space in annotation for WebIsALOD took 0.030483722686767578s
Accuracy | Check Datatype consistency for WebIsALOD took 0.02817559242248535s
Consistency | Disjoint class check for WebIsALOD took 0.10549759864807129s
Consistency | Check Misplaced properties for WebIsALOD took 61.63627576828003s
Consistency | Misplaced classes for WebIsALOD took 0.2330000400543213s
Consistency | Check Ontology hijacking for WebIsALOD took 1.8490090370178223s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.4565794467926025s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 62.841453313827515s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.03126668930053711s
Conciseness | Check Intensional conciseness for WebIsALOD took 0.24591994285583496s
Security | Sign check for WebIsALOD took 0.13305449485778809s
Availability | Check URIs Dereferenciability for WebIsALOD took 19.71743416786194s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.41092705726623535s
Reputation | Calculation of the PageRank for WebIsALOD took 0.02093982696533203s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 8.96453857421875e-05s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 7.721294403076172s
Believability | Calculation of trust value for WebIsALOD took 1.0728836059570312e-05s
INFO | --- Analysis for webisalod took 576.4136908054352s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 9.512901306152344e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.3022472858428955s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 4.220008850097656e-05s
Believability | Calculation of trust value for webnmasunotraveler took 1.2159347534179688e-05s
INFO | --- Analysis for webnmasunotraveler took 2.94917368888855s
Availability | SPARQL endpoint availability check for Whisky Circle took 8.845329284667969e-05s
Availability | VoID file availability check for Whisky Circle took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.3137032985687256s
Reputation | Calculation of the PageRank for Whisky Circle took 0.021206140518188477s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.000110626220703125s
Believability | Calculation of trust value for Whisky Circle took 6.4373016357421875e-06s
INFO | --- Analysis for whisky-circle-info took 3.2039694786071777s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 14.446338891983032s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.3162872791290283s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for WHOnto took 33.07433319091797s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.2769324779510498s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.022241592407226562s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for whonto took 8.743627548217773s
Availability | SPARQL endpoint availability check for Wikidata took 0.9066569805145264s
Availability | VoID file availability check for Wikidata took 0.0005438327789306641s
Extra | Recovery of all triples for Wikidata took 53.420793771743774s
Performance | Total latancy measurement for Wikidata took 1.7237489223480225s
Amount of data | Number of triples check for Wikidata took 65.18919277191162s
Interoperability | New terms check for Wikidata took 2.3228423595428467s
Versatility | Languages check for Wikidata took 65.18214678764343s
Interpretability | Number of blank nodes check for Wikidata took 65.38193869590759s
Interpretability | RDF structures check for Wikidata took 0.40599894523620605s
Versatility | Serialization formats check for Wikidata took 0.18882274627685547s
Availability | RDF dump link check for Wikidata took 0.36035656929016113s
License | MR license check for Wikidata took 0.2621927261352539s
License | HR license check for Wikidata took 65.36200189590454s
Amount of data | Number of property check for Wikidata took 0.3852725028991699s
Understandability | Number of label check for Wikidata took 65.16846966743469s
Understandability | URI regex check for Wikidata took 0.5230052471160889s
Understandability | Vocabs check for Wikidata took 0.17196369171142578s
Verifiability | Authors check for Wikidata took 0.41529083251953125s
Verifiability | Publishers check for Wikidata took 0.3268909454345703s
Performance | Throughput check for Wikidata took 11.362065553665161s
Amount of data | Check the number of entities for Wikidata took 0.000118255615234375s
Verifiability | Contribs. check for Wikidata took 0.18580913543701172s
Interlinking | sameAs chians check for Wikidata took 24.00064206123352s
Interlinking | skos check for Wikidata took 0.2807469367980957s
Interlinking | skos check for Wikidata took 0.2046375274658203s
Timeliness | dataset update frequency check for Wikidata took 0.26509976387023926s
Currency | Creation date check for Wikidata took 0.7040541172027588s
Currency | Modification date check for Wikidata took 0.5842666625976562s
Rep.Conc. | URIs length for Wikidata took 60.06814670562744s
Interoperability | New vocabularies check for Wikidata took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Wikidata took 0.18138980865478516s
Accuracy | Check Empty annotation labels for Wikidata took 13.986431121826172s
Accuracy | Check White space in annotation for Wikidata took 2.6342520713806152s
Accuracy | Check Datatype consistency for Wikidata took 4.600478649139404s
Consistency | Disjoint class check for Wikidata took 0.24358105659484863s
Consistency | Check Misplaced properties for Wikidata took 1.3295118808746338s
Consistency | Misplaced classes for Wikidata took 8.750821828842163s
Consistency | Check Ontology hijacking for Wikidata took 18.993945598602295s
Consistency | Check Invalid usage of undefined classes for Wikidata took 1.3259413242340088s
Consistency | Check Invalid usage of undefined properties for Wikidata took 9.22750186920166s
Conciseness | Check Extensional conciseness for Wikidata took 2.780904531478882s
Security | Sign check for Wikidata took 0.16878557205200195s
Availability | Check URIs Dereferenciability for Wikidata took 9.499351263046265s
Completeness | Calculation of interlinking completeness for Wikidata took 0.5918130874633789s
Reputation | Calculation of the PageRank for Wikidata took 0.021389245986938477s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0002894401550292969s
Interoperability | Check the re-using of existing vocabs for Wikidata took 2.384185791015625e-06s
Believability | Calculation of trust value for Wikidata took 7.152557373046875e-06s
INFO | --- Analysis for wikidata took 815.7939505577087s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 4.76837158203125e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.27695226669311523s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 6.580352783203125e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.2636184692382812e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 2.760911464691162s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2899477481842041s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.3000216484069824s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.940696716308594e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.239776611328125e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.764618396759033s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2482268810272217s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.3193948268890381s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 2.8371810913085938e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.2159347534179688e-05s
INFO | --- Analysis for wl-kg took 4.19773006439209s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 9.179115295410156e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.32024359703063965s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.02276611328125s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 6.556510925292969e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.239776611328125e-05s
INFO | --- Analysis for wn-wiki-instances took 3.565998077392578s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.2737107276916504s
Availability | VoID file availability check for World Loanword Database took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.29706287384033203s
Reputation | Calculation of the PageRank for World Loanword Database took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 6.866455078125e-05s
Believability | Calculation of trust value for World Loanword Database took 1.239776611328125e-05s
INFO | --- Analysis for wold took 3.0711238384246826s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 7.462501525878906e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.30449748039245605s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 2.9802322387695312e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.2874603271484375e-05s
INFO | --- Analysis for woodtrick took 3.407940626144409s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.5257284641265869s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.00035881996154785156s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.2785613536834717s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.02083301544189453s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for WordFormationLatin took 4.300094366073608s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 8.797645568847656e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.30702662467956543s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010228157043457031s
Believability | Calculation of trust value for WordLift Blog EN took 1.1205673217773438e-05s
INFO | --- Analysis for wordlift-io-blog-en took 3.1363236904144287s
Availability | SPARQL endpoint availability check for WordLift IT took 4.2438507080078125e-05s
Availability | VoID file availability check for WordLift IT took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.3186225891113281s
Reputation | Calculation of the PageRank for WordLift IT took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00010395050048828125s
Believability | Calculation of trust value for WordLift IT took 1.1444091796875e-05s
INFO | --- Analysis for wordlift-io-blog-it took 3.211510419845581s
Availability | SPARQL endpoint availability check for WordNet-RDF took 8.654594421386719e-05s
Availability | VoID file availability check for WordNet-RDF took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.2760179042816162s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.020642995834350586s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 0.00011205673217773438s
Believability | Calculation of trust value for WordNet-RDF took 6.67572021484375e-06s
INFO | --- Analysis for wordnet-rdf took 2.687471389770508s
Availability | SPARQL endpoint availability check for wordpress took 9.107589721679688e-05s
Availability | VoID file availability check for wordpress took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for wordpress took 0.28998279571533203s
Reputation | Calculation of the PageRank for wordpress took 0.0211336612701416s
Interlinking | Calculation of Degree of Connection for wordpress took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.296966552734375e-05s
Believability | Calculation of trust value for wordpress took 1.239776611328125e-05s
INFO | --- Analysis for wordpress took 3.1251254081726074s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.09523582458496094s
Availability | VoID file availability check for World Bank Linked Data took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.275165319442749s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012254714965820312s
Believability | Calculation of trust value for World Bank Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for world-bank-linked-data took 2.8026795387268066s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 0.9388670921325684s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.30745434761047363s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.022387027740478516s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.177757263183594e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 1.239776611328125e-05s
INFO | --- Analysis for world-factbook-fu-berlin took 5.458946943283081s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 0.00012731552124023438s
Availability | VoID file availability check for World Wide Web Foundation took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.2993450164794922s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.225440979003906e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 9.5367431640625e-06s
INFO | --- Analysis for world-wide-web-foundation took 5.032285928726196s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.35422611236572266s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0005044937133789062s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 2.5970919132232666s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8027305603027344s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.23567461967468262s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.9414072036743164s
Versatility | Languages check for World War 1 as Linked Open Data took 0.3824779987335205s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.21953392028808594s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.38518285751342773s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.27772092819213867s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.2201099395751953s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.576697587966919s
License | MR license check for World War 1 as Linked Open Data took 0.19218111038208008s
License | HR license check for World War 1 as Linked Open Data took 1.577549934387207s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.18279409408569336s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.38097238540649414s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.38295435905456543s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.23266363143920898s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.18907475471496582s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.1911323070526123s
Performance | Throughput check for World War 1 as Linked Open Data took 11.019118785858154s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.0688941478729248s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.23064970970153809s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.56502366065979s
Interlinking | skos check for World War 1 as Linked Open Data took 0.18810105323791504s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1489732265472412s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.21464776992797852s
Currency | Creation date check for World War 1 as Linked Open Data took 0.37147045135498047s
Currency | Modification date check for World War 1 as Linked Open Data took 0.18623924255371094s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 2.0372202396392822s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 24.162848949432373s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.32094860076904297s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.18564391136169434s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.1686534881591797s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.122405767440796s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.049430131912231445s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.3146824836730957s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.2002265453338623s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.5829508304595947s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 1.9880709648132324s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.2804832458496094s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.533933162689209s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.18869972229003906s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 1.2508442401885986s
Security | Sign check for World War 1 as Linked Open Data took 0.1828300952911377s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 4.952128887176514s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.3145253658294678s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.020993709564208984s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 8.392333984375e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 27.62877321243286s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for ww1lod took 126.48917150497437s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.3235769271850586s
Availability | VoID file availability check for xLiD-Lexica took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.2974083423614502s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.02129673957824707s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 6.747245788574219e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.1920928955078125e-05s
INFO | --- Analysis for xlid-lexica took 4.414263725280762s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.410743713378906e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.26511144638061523s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.020682096481323242s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.838539123535156e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 1.239776611328125e-05s
INFO | --- Analysis for xwn took 2.907536029815674s
Availability | SPARQL endpoint availability check for xxx took 8.702278137207031e-05s
Availability | VoID file availability check for xxx took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for xxx took 0.28714728355407715s
Reputation | Calculation of the PageRank for xxx took 0.0218045711517334s
Interlinking | Calculation of Degree of Connection for xxx took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for xxx took 3.0279159545898438e-05s
Believability | Calculation of trust value for xxx took 1.3589859008789062e-05s
INFO | --- Analysis for xx took 2.6670005321502686s
Availability | SPARQL endpoint availability check for YAGO took 9.632110595703125e-05s
Availability | VoID file availability check for YAGO took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for YAGO took 0.2999417781829834s
Reputation | Calculation of the PageRank for YAGO took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for YAGO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.0001430511474609375s
Believability | Calculation of trust value for YAGO took 1.2636184692382812e-05s
INFO | --- Analysis for yago took 4.4872658252716064s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 2.7116997241973877s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.2999575138092041s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.020749568939208984s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.867813110351562e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.2636184692382812e-05s
INFO | --- Analysis for yahoo_geoplanet took 22.433096170425415s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.15405869483947754s
Availability | VoID file availability check for Yale Senselab took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.2976114749908447s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 2.6941299438476562e-05s
Believability | Calculation of trust value for Yale Senselab took 1.2874603271484375e-05s
INFO | --- Analysis for yale_senselab took 12.219346046447754s
Availability | SPARQL endpoint availability check for test-dapp-2 took 0.00010085105895996094s
Availability | VoID file availability check for test-dapp-2 took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.2753944396972656s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.022741079330444336s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 2.7418136596679688e-05s
Believability | Calculation of trust value for test-dapp-2 took 1.1682510375976562e-05s
INFO | --- Analysis for yordhis took 2.743605613708496s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.875192403793335s
Availability | VoID file availability check for Yovisto - academic video search took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.27740001678466797s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.842613220214844e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 8.821487426757812e-06s
INFO | --- Analysis for yovisto took 25.843789100646973s
Availability | SPARQL endpoint availability check for YSA - General Finnish Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for YSA - General Finnish Thesaurus took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for YSA - General Finnish Thesaurus took 0.2765519618988037s
Reputation | Calculation of the PageRank for YSA - General Finnish Thesaurus took 0.022029638290405273s
Interlinking | Calculation of Degree of Connection for YSA - General Finnish Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for YSA - General Finnish Thesaurus took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for YSA - General Finnish Thesaurus took 3.409385681152344e-05s
Believability | Calculation of trust value for YSA - General Finnish Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for ysa took 3.9643971920013428s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.2906813621520996s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.02104926109313965s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0010676383972167969s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 7.390975952148438e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 1.239776611328125e-05s
INFO | --- Analysis for yso took 4.4999940395355225s
Availability | SPARQL endpoint availability check for yso-fi-allars took 8.654594421386719e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.31851649284362793s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.0226132869720459s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.528594970703125e-05s
Believability | Calculation of trust value for yso-fi-allars took 1.3113021850585938e-05s
INFO | --- Analysis for yso-fi-allars took 3.3282837867736816s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 9.608268737792969e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.3228912353515625s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.021576642990112305s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.528594970703125e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.3113021850585938e-05s
INFO | --- Analysis for yso-fi-ysa took 3.3224263191223145s
Availability | SPARQL endpoint availability check for YSO places took 0.6461279392242432s
Availability | VoID file availability check for YSO places took 0.00041604042053222656s
Completeness | Calculation of interlinking completeness for YSO places took 0.3125424385070801s
Reputation | Calculation of the PageRank for YSO places took 0.020888328552246094s
Interlinking | Calculation of Degree of Connection for YSO places took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.0040740966796875e-05s
Believability | Calculation of trust value for YSO places took 1.049041748046875e-05s
INFO | --- Analysis for yso-paikat took 4.307276964187622s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.267692565917969e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0007801055908203125s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.3101785182952881s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.021583080291748047s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.552436828613281e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 9.775161743164062e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 6.422779083251953s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 9.059906005859375e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.31875014305114746s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.022394657135009766s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.4332275390625e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.33514404296875e-05s
INFO | --- Analysis for zaragoza_turruta took 2.888946294784546s
Availability | SPARQL endpoint availability check for ZBW Labs took 7.557868957519531e-05s
Availability | VoID file availability check for ZBW Labs took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.28160524368286133s
Reputation | Calculation of the PageRank for ZBW Labs took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 6.4849853515625e-05s
Believability | Calculation of trust value for ZBW Labs took 1.5497207641601562e-05s
INFO | --- Analysis for zbw-labs took 3.7408716678619385s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.16936993598937988s
Availability | VoID file availability check for 20th Century Press Archives took 0.0010519027709960938s
Extra | Recovery of all triples for 20th Century Press Archives took 40.67126798629761s
Performance | Total latancy measurement for 20th Century Press Archives took 3.2596166133880615s
Amount of data | Number of triples check for 20th Century Press Archives took 2.2815210819244385s
Interoperability | New terms check for 20th Century Press Archives took 1.942140817642212s
Versatility | Languages check for 20th Century Press Archives took 9.974092960357666s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 1.1966965198516846s
Interpretability | RDF structures check for 20th Century Press Archives took 0.21428775787353516s
Versatility | Serialization formats check for 20th Century Press Archives took 0.1582164764404297s
Availability | RDF dump link check for 20th Century Press Archives took 0.12495255470275879s
License | MR license check for 20th Century Press Archives took 0.17301654815673828s
License | HR license check for 20th Century Press Archives took 5.3617448806762695s
Amount of data | Number of property check for 20th Century Press Archives took 0.13700437545776367s
Understandability | Number of label check for 20th Century Press Archives took 0.5390911102294922s
Understandability | URI regex check for 20th Century Press Archives took 0.3186531066894531s
Understandability | Vocabs check for 20th Century Press Archives took 0.14139389991760254s
Verifiability | Authors check for 20th Century Press Archives took 0.14457440376281738s
Verifiability | Publishers check for 20th Century Press Archives took 0.13976812362670898s
Performance | Throughput check for 20th Century Press Archives took 11.011730670928955s
Amount of data | Check the number of entities for 20th Century Press Archives took 8.153915405273438e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.14133000373840332s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.13806819915771484s
Interlinking | skos check for 20th Century Press Archives took 0.18764042854309082s
Interlinking | skos check for 20th Century Press Archives took 0.20174074172973633s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.14099645614624023s
Currency | Creation date check for 20th Century Press Archives took 0.29712390899658203s
Currency | Modification date check for 20th Century Press Archives took 3.3514769077301025s
Rep.Conc. | URIs length for 20th Century Press Archives took 15.514375925064087s
Interoperability | New vocabularies check for 20th Century Press Archives took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.16267919540405273s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.151747465133667s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.17690253257751465s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 5.098017930984497s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8774161338806152s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.014723062515259s
Consistency | Disjoint class check for 20th Century Press Archives took 0.1782972812652588s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.2432034015655518s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.5407278537750244s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 6.892664909362793s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.5665159225463867s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.7170042991638184s
Security | Sign check for 20th Century Press Archives took 0.14671874046325684s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1042.1403806209564s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.6249473094940186s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.02105712890625s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 6.079673767089844e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00012159347534179688s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 2.1457672119140625e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.1444091796875e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1191.0090658664703s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.220008850097656e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0007832050323486328s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.2763545513153076s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.02094864845275879s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.553794860839844e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.2159347534179688e-05s
INFO | --- Analysis for zhishi-lemon took 24.825984239578247s
Availability | SPARQL endpoint availability check for Zhishi.me took 2.7284700870513916s
Availability | VoID file availability check for Zhishi.me took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.2741827964782715s
Reputation | Calculation of the PageRank for Zhishi.me took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 6.794929504394531e-05s
Believability | Calculation of trust value for Zhishi.me took 7.152557373046875e-06s
INFO | --- Analysis for zhishi-me took 8.03367018699646s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.3392181396484375e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.2908153533935547s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 6.031990051269531e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 7.62939453125e-06s
INFO | --- Analysis for zitgist-musicbrainz took 3.3382978439331055s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 4.363059997558594e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.2838895320892334s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 2.7418136596679688e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 7.867813110351562e-06s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.7873623371124268s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.3045985698699951s
Availability | VoID file availability check for performing-arts.ch took 0.0005240440368652344s
Extra | Recovery of all triples for performing-arts.ch took 18.333508729934692s
Performance | Total latancy measurement for performing-arts.ch took 0.7448067665100098s
Amount of data | Number of triples check for performing-arts.ch took 48.29732704162598s
Interoperability | New terms check for performing-arts.ch took 1.4668550491333008s
Versatility | Languages check for performing-arts.ch took 60.13093304634094s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.126930952072144s
Interpretability | RDF structures check for performing-arts.ch took 0.16327667236328125s
Versatility | Serialization formats check for performing-arts.ch took 0.16612482070922852s
Availability | RDF dump link check for performing-arts.ch took 0.16400527954101562s
License | MR license check for performing-arts.ch took 0.18555855751037598s
License | HR license check for performing-arts.ch took 39.84589624404907s
Amount of data | Number of property check for performing-arts.ch took 0.19203853607177734s
Understandability | Number of label check for performing-arts.ch took 2.635223865509033s
Understandability | URI regex check for performing-arts.ch took 0.2865607738494873s
Understandability | Vocabs check for performing-arts.ch took 0.16501712799072266s
Verifiability | Authors check for performing-arts.ch took 0.1647326946258545s
Verifiability | Publishers check for performing-arts.ch took 0.14304661750793457s
Performance | Throughput check for performing-arts.ch took 11.044315814971924s
Amount of data | Check the number of entities for performing-arts.ch took 7.295608520507812e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.1774756908416748s
Interlinking | sameAs chians check for performing-arts.ch took 0.8803496360778809s
Interlinking | skos check for performing-arts.ch took 0.17430543899536133s
Interlinking | skos check for performing-arts.ch took 0.1771221160888672s
Timeliness | dataset update frequency check for performing-arts.ch took 0.16280722618103027s
Currency | Creation date check for performing-arts.ch took 0.32733798027038574s
Currency | Modification date check for performing-arts.ch took 0.3484609127044678s
Rep.Conc. | URIs length for performing-arts.ch took 24.311216115951538s
Interoperability | New vocabularies check for performing-arts.ch took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.17009472846984863s
Accuracy | Check Functional Property for performing-arts.ch took 0.1581284999847412s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.1758265495300293s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.665735244750977s
Accuracy | Check White space in annotation for performing-arts.ch took 2.5067644119262695s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.821637868881226s
Consistency | Disjoint class check for performing-arts.ch took 0.15923166275024414s
Consistency | Check Misplaced properties for performing-arts.ch took 0.37949275970458984s
Consistency | Misplaced classes for performing-arts.ch took 8.362369298934937s
Consistency | Check Ontology hijacking for performing-arts.ch took 49.62016177177429s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 16318.034706830978s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.9247527122497559s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.8730666637420654s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.31185317039489746s
Security | Sign check for performing-arts.ch took 0.15501070022583008s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.629138708114624s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.794391393661499s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.021318674087524414s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.621246337890625e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 2.1457672119140625e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.239776611328125e-05s
INFO | --- Analysis for performing-arts.ch took 16992.140560150146s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.853459119796753s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.30213332176208496s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.02174973487854004s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.33514404296875e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for The-AA-Thesaurus took 9.696993350982666s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.6399757862091064s
Availability | VoID file availability check for MiMoTextBase took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.2892754077911377s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.3113021850585938e-05s
Believability | Calculation of trust value for MiMoTextBase took 1.1444091796875e-05s
INFO | --- Analysis for MiMoTextBase took 6.5340869426727295s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.5791287422180176s
Availability | VoID file availability check for National Library of Sweden took 0.0006031990051269531s
Extra | Recovery of all triples for National Library of Sweden took 7.702936410903931s
Performance | Total latancy measurement for National Library of Sweden took 1.006455898284912s
Amount of data | Number of triples check for National Library of Sweden took 21.489754915237427s
Interoperability | New terms check for National Library of Sweden took 15.507493257522583s
Versatility | Languages check for National Library of Sweden took 0.20565414428710938s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.2297043800354s
Interpretability | RDF structures check for National Library of Sweden took 0.4401509761810303s
Versatility | Serialization formats check for National Library of Sweden took 0.25639891624450684s
Availability | RDF dump link check for National Library of Sweden took 0.20926690101623535s
License | MR license check for National Library of Sweden took 0.324526309967041s
License | HR license check for National Library of Sweden took 0.32006311416625977s
Amount of data | Number of property check for National Library of Sweden took 0.2100534439086914s
Understandability | Number of label check for National Library of Sweden took 0.571561336517334s
Understandability | URI regex check for National Library of Sweden took 0.5237102508544922s
Understandability | Vocabs check for National Library of Sweden took 0.22129130363464355s
Verifiability | Authors check for National Library of Sweden took 0.2383430004119873s
Verifiability | Publishers check for National Library of Sweden took 0.23472189903259277s
Performance | Throughput check for National Library of Sweden took 10.317348718643188s
Amount of data | Check the number of entities for National Library of Sweden took 8.20159912109375e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.23363661766052246s
Interlinking | sameAs chians check for National Library of Sweden took 0.28160619735717773s
Interlinking | skos check for National Library of Sweden took 0.38462162017822266s
Interlinking | skos check for National Library of Sweden took 0.20437383651733398s
Timeliness | dataset update frequency check for National Library of Sweden took 0.22539591789245605s
Currency | Creation date check for National Library of Sweden took 0.4920520782470703s
Currency | Modification date check for National Library of Sweden took 0.4470548629760742s
Rep.Conc. | URIs length for National Library of Sweden took 85.97343039512634s
Interoperability | New vocabularies check for National Library of Sweden took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.21789073944091797s
Accuracy | Check Functional Property for National Library of Sweden took 0.25913357734680176s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.24858307838439941s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.2749495506286621s
Consistency | Disjoint class check for National Library of Sweden took 0.20282721519470215s
Consistency | Check Misplaced properties for National Library of Sweden took 60.58825445175171s
Consistency | Misplaced classes for National Library of Sweden took 1.1247193813323975s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.2089645862579346s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.248011827468872s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 62.7850296497345s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.27577853202819824s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.39174675941467285s
Security | Sign check for National Library of Sweden took 0.44040584564208984s
Availability | Check URIs Dereferenciability for National Library of Sweden took 10.269270658493042s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.3939321041107178s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.02093029022216797s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0006797313690185547s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.1920928955078125e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 2.1457672119140625e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.239776611328125e-05s
INFO | --- Analysis for NLS took 1371.838484287262s
Availability | SPARQL endpoint availability check for Japan Search took 1.6948351860046387s
Availability | VoID file availability check for Japan Search took 0.0005366802215576172s
Extra | Recovery of all triples for Japan Search took 3.212869882583618s
Performance | Total latancy measurement for Japan Search took 2.593600034713745s
Amount of data | Number of triples check for Japan Search took 4.838526010513306s
Interoperability | New terms check for Japan Search took 3.1987404823303223s
Versatility | Languages check for Japan Search took 0.28261542320251465s
Interpretability | Number of blank nodes check for Japan Search took 12.749827861785889s
Interpretability | RDF structures check for Japan Search took 0.890596866607666s
Versatility | Serialization formats check for Japan Search took 0.9020321369171143s
Availability | RDF dump link check for Japan Search took 0.3186929225921631s
License | MR license check for Japan Search took 0.490800142288208s
License | HR license check for Japan Search took 10.322030544281006s
Amount of data | Number of property check for Japan Search took 0.717693567276001s
Understandability | Number of label check for Japan Search took 2.742187738418579s
Understandability | URI regex check for Japan Search took 0.5512034893035889s
Understandability | Vocabs check for Japan Search took 0.26839590072631836s
Verifiability | Authors check for Japan Search took 0.31359052658081055s
Verifiability | Publishers check for Japan Search took 0.28461313247680664s
Performance | Throughput check for Japan Search took 11.307878494262695s
Amount of data | Check the number of entities for Japan Search took 5.650520324707031e-05s
Verifiability | Contribs. check for Japan Search took 0.30727148056030273s
Interlinking | sameAs chians check for Japan Search took 0.28464651107788086s
Interlinking | skos check for Japan Search took 0.2765541076660156s
Interlinking | skos check for Japan Search took 0.3074193000793457s
Timeliness | dataset update frequency check for Japan Search took 0.3114752769470215s
Currency | Creation date check for Japan Search took 0.6373920440673828s
Currency | Modification date check for Japan Search took 0.5469272136688232s
Rep.Conc. | URIs length for Japan Search took 13.929445505142212s
Interoperability | New vocabularies check for Japan Search took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.7348546981811523s
Accuracy | Check Empty annotation labels for Japan Search took 1.742356538772583s
Accuracy | Check White space in annotation for Japan Search took 0.02975773811340332s
Accuracy | Check Datatype consistency for Japan Search took 0.027902841567993164s
Consistency | Disjoint class check for Japan Search took 0.31867241859436035s
Consistency | Check Misplaced properties for Japan Search took 12.578221797943115s
Consistency | Misplaced classes for Japan Search took 1.0272736549377441s
Consistency | Check Ontology hijacking for Japan Search took 3.4288012981414795s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.2521724700927734s
Consistency | Check Invalid usage of undefined properties for Japan Search took 13.828687906265259s
Conciseness | Check Extensional conciseness for Japan Search took 0.03439211845397949s
Conciseness | Check Intensional conciseness for Japan Search took 1.0132689476013184s
Security | Sign check for Japan Search took 0.3094973564147949s
Availability | Check URIs Dereferenciability for Japan Search took 8.971104621887207s
Completeness | Calculation of interlinking completeness for Japan Search took 0.2855682373046875s
Reputation | Calculation of the PageRank for Japan Search took 0.022237062454223633s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0008561611175537109s
Interlinking | Calculation of Clustering coefficient for Japan Search took 2.3365020751953125e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 2.1457672119140625e-06s
Believability | Calculation of trust value for Japan Search took 1.2159347534179688e-05s
INFO | --- Analysis for Japan-Search took 409.51778507232666s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.2432661056518555s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.31258249282836914s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.020872831344604492s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.1682510375976562e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.1682510375976562e-05s
INFO | --- Analysis for Rijksmuseum took 5.194544076919556s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.6459357738494873s
Availability | VoID file availability check for Finnish Public Libraries took 0.0005402565002441406s
Extra | Recovery of all triples for Finnish Public Libraries took 17.385014057159424s
Performance | Total latancy measurement for Finnish Public Libraries took 1.3406424522399902s
Amount of data | Number of triples check for Finnish Public Libraries took 60.13700604438782s
Interoperability | New terms check for Finnish Public Libraries took 17.489468097686768s
Versatility | Languages check for Finnish Public Libraries took 60.212069511413574s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 60.21331000328064s
Interpretability | RDF structures check for Finnish Public Libraries took 0.3566892147064209s
Versatility | Serialization formats check for Finnish Public Libraries took 0.23821425437927246s
Availability | RDF dump link check for Finnish Public Libraries took 0.16013002395629883s
License | MR license check for Finnish Public Libraries took 0.11311793327331543s
License | HR license check for Finnish Public Libraries took 48.88675308227539s
Amount of data | Number of property check for Finnish Public Libraries took 0.3786134719848633s
Understandability | Number of label check for Finnish Public Libraries took 14.48490595817566s
Understandability | URI regex check for Finnish Public Libraries took 0.5718257427215576s
Understandability | Vocabs check for Finnish Public Libraries took 0.32460522651672363s
Verifiability | Authors check for Finnish Public Libraries took 0.1449885368347168s
Verifiability | Publishers check for Finnish Public Libraries took 0.41993117332458496s
Performance | Throughput check for Finnish Public Libraries took 10.64460802078247s
Amount of data | Check the number of entities for Finnish Public Libraries took 7.104873657226562e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.12461280822753906s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.47308897972106934s
Interlinking | skos check for Finnish Public Libraries took 0.12750840187072754s
Interlinking | skos check for Finnish Public Libraries took 0.12145757675170898s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.13260912895202637s
Currency | Creation date check for Finnish Public Libraries took 0.36863231658935547s
Currency | Modification date check for Finnish Public Libraries took 0.2691977024078369s
Rep.Conc. | URIs length for Finnish Public Libraries took 83.60565376281738s
Interoperability | New vocabularies check for Finnish Public Libraries took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.3345201015472412s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 8.087258338928223s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.1695797443389893s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.3968353271484375s
Consistency | Disjoint class check for Finnish Public Libraries took 0.1350090503692627s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.461711406707764s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 15.79130220413208s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.4625556468963623s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 61.50811505317688s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.685089588165283s
Security | Sign check for Finnish Public Libraries took 0.16054916381835938s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 0.9123954772949219s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.48200392723083496s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.02187633514404297s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.9788742065429688e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 2.1457672119140625e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 1.2636184692382812e-05s
INFO | --- Analysis for FI-Library took 676.3369207382202s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 2.702094793319702s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0005071163177490234s
Extra | Recovery of all triples for Shanghai Library Open Data Platform took 10.014420509338379s
Performance | Total latancy measurement for Shanghai Library Open Data Platform took 3.5663139820098877s
Amount of data | Number of triples check for Shanghai Library Open Data Platform took 1.184460163116455s
Interoperability | New terms check for Shanghai Library Open Data Platform took 4.813355207443237s
Versatility | Languages check for Shanghai Library Open Data Platform took 60.70987296104431s
Interpretability | Number of blank nodes check for Shanghai Library Open Data Platform took 17.29952883720398s
Interpretability | RDF structures check for Shanghai Library Open Data Platform took 1.1158831119537354s
Versatility | Serialization formats check for Shanghai Library Open Data Platform took 0.8889367580413818s
Availability | RDF dump link check for Shanghai Library Open Data Platform took 0.8087890148162842s
License | MR license check for Shanghai Library Open Data Platform took 1.2301018238067627s
License | HR license check for Shanghai Library Open Data Platform took 38.76365947723389s
Amount of data | Number of property check for Shanghai Library Open Data Platform took 0.690213680267334s
Understandability | Number of label check for Shanghai Library Open Data Platform took 2.013741970062256s
Understandability | URI regex check for Shanghai Library Open Data Platform took 1.6865553855895996s
Understandability | Vocabs check for Shanghai Library Open Data Platform took 0.7681434154510498s
Verifiability | Authors check for Shanghai Library Open Data Platform took 0.8879091739654541s
Verifiability | Publishers check for Shanghai Library Open Data Platform took 0.8433887958526611s
Performance | Throughput check for Shanghai Library Open Data Platform took 14.12935471534729s
Amount of data | Check the number of entities for Shanghai Library Open Data Platform took 8.845329284667969e-05s
Verifiability | Contribs. check for Shanghai Library Open Data Platform took 0.7639920711517334s
Interlinking | sameAs chians check for Shanghai Library Open Data Platform took 0.7286415100097656s
Interlinking | skos check for Shanghai Library Open Data Platform took 1.0728535652160645s
Interlinking | skos check for Shanghai Library Open Data Platform took 0.7314722537994385s
Timeliness | dataset update frequency check for Shanghai Library Open Data Platform took 0.8804726600646973s
Currency | Creation date check for Shanghai Library Open Data Platform took 1.4802565574645996s
Currency | Modification date check for Shanghai Library Open Data Platform took 1.5305149555206299s
Rep.Conc. | URIs length for Shanghai Library Open Data Platform took 9.83884334564209s
Interoperability | New vocabularies check for Shanghai Library Open Data Platform took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for Shanghai Library Open Data Platform took 0.7377338409423828s
Accuracy | Check Functional Property for Shanghai Library Open Data Platform took 0.7666738033294678s
Accuracy | Check Inverse Functional Property for Shanghai Library Open Data Platform took 0.7263588905334473s
Accuracy | Check Empty annotation labels for Shanghai Library Open Data Platform took 4.118137359619141s
Accuracy | Check White space in annotation for Shanghai Library Open Data Platform took 0.15097570419311523s
Accuracy | Check Datatype consistency for Shanghai Library Open Data Platform took 0.1381373405456543s
Consistency | Disjoint class check for Shanghai Library Open Data Platform took 0.8790416717529297s
Consistency | Check Misplaced properties for Shanghai Library Open Data Platform took 6.314203262329102s
Consistency | Misplaced classes for Shanghai Library Open Data Platform took 1.3486053943634033s
Consistency | Check Ontology hijacking for Shanghai Library Open Data Platform took 4.6092400550842285s
Consistency | Check Invalid usage of undefined classes for Shanghai Library Open Data Platform took 1.4085426330566406s
Consistency | Check Invalid usage of undefined properties for Shanghai Library Open Data Platform took 7.2235705852508545s
Conciseness | Check Extensional conciseness for Shanghai Library Open Data Platform took 0.16270685195922852s
Conciseness | Check Intensional conciseness for Shanghai Library Open Data Platform took 1.1839807033538818s
Security | Sign check for Shanghai Library Open Data Platform took 0.9712839126586914s
Availability | Check URIs Dereferenciability for Shanghai Library Open Data Platform took 10.384681940078735s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.42394566535949707s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.021225929260253906s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 2.0742416381835938e-05s
Interoperability | Check the re-using of existing vocabs for Shanghai Library Open Data Platform took 2.6226043701171875e-06s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.2159347534179688e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 350.17228412628174s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.404547929763794s
Availability | VoID file availability check for National Library Netherlands took 0.0005509853363037109s
Extra | Recovery of all triples for National Library Netherlands took 0.7187926769256592s
Performance | Total latancy measurement for National Library Netherlands took 0.7862060070037842s
Amount of data | Number of triples check for National Library Netherlands took 0.16565752029418945s
Interoperability | New terms check for National Library Netherlands took 1.4294867515563965s
Versatility | Languages check for National Library Netherlands took 58.1782591342926s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.19242215156555176s
Interpretability | RDF structures check for National Library Netherlands took 0.9201858043670654s
Versatility | Serialization formats check for National Library Netherlands took 1.149094820022583s
Availability | RDF dump link check for National Library Netherlands took 0.14734292030334473s
License | MR license check for National Library Netherlands took 1.3314871788024902s
License | HR license check for National Library Netherlands took 1.2298181056976318s
Amount of data | Number of property check for National Library Netherlands took 0.14858341217041016s
Understandability | Number of label check for National Library Netherlands took 0.964118480682373s
Understandability | URI regex check for National Library Netherlands took 0.33293700218200684s
Understandability | Vocabs check for National Library Netherlands took 1.85758638381958s
Verifiability | Authors check for National Library Netherlands took 1.6755414009094238s
Verifiability | Publishers check for National Library Netherlands took 0.15951752662658691s
Performance | Throughput check for National Library Netherlands took 13.668302297592163s
Amount of data | Check the number of entities for National Library Netherlands took 7.414817810058594e-05s
Verifiability | Contribs. check for National Library Netherlands took 1.312934398651123s
Interlinking | sameAs chians check for National Library Netherlands took 1.5718653202056885s
Interlinking | skos check for National Library Netherlands took 1.7828545570373535s
Interlinking | skos check for National Library Netherlands took 0.1494452953338623s
Timeliness | dataset update frequency check for National Library Netherlands took 0.15493154525756836s
Currency | Creation date check for National Library Netherlands took 1.3536076545715332s
Currency | Modification date check for National Library Netherlands took 0.3522031307220459s
Rep.Conc. | URIs length for National Library Netherlands took 3.0911850929260254s
Interoperability | New vocabularies check for National Library Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 1.6356861591339111s
Accuracy | Check Empty annotation labels for National Library Netherlands took 2.119730234146118s
Accuracy | Check White space in annotation for National Library Netherlands took 0.027451276779174805s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.027123212814331055s
Consistency | Disjoint class check for National Library Netherlands took 0.14552950859069824s
Consistency | Check Misplaced properties for National Library Netherlands took 2.518683433532715s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.7428770065307617s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.343808650970459s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.4888770580291748s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.02852916717529297s
Security | Sign check for National Library Netherlands took 0.1641404628753662s
Availability | Check URIs Dereferenciability for National Library Netherlands took 2176.3214271068573s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.815272331237793s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.02205348014831543s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 7.677078247070312e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 2.9802322387695312e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.2874603271484375e-05s
INFO | --- Analysis for National-Library-Netherlands took 2313.084985256195s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.4755640029907227s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.2921411991119385s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.02298116683959961s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.1920928955078125e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.2636184692382812e-05s
INFO | --- Analysis for Antique-Renaissance took 6.819039344787598s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 4.420168399810791s
Availability | VoID file availability check for ARTSDATA.CA took 0.0004165172576904297s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.2845580577850342s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.02061295509338379s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.2159347534179688e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 8.106231689453125e-06s
INFO | --- Analysis for ARTSDATA-CA took 9.985798120498657s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.09974908828735352s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005433559417724609s
Extra | Recovery of all triples for Architecture of Knowledge took 60.17064547538757s
Performance | Total latancy measurement for Architecture of Knowledge took 0.21415233612060547s
Amount of data | Number of triples check for Architecture of Knowledge took 6.1156017780303955s
Interoperability | New terms check for Architecture of Knowledge took 5.127165794372559s
Versatility | Languages check for Architecture of Knowledge took 60.16797685623169s
Interpretability | Number of blank nodes check for Architecture of Knowledge took 0.07095980644226074s
Interpretability | RDF structures check for Architecture of Knowledge took 0.25415468215942383s
Versatility | Serialization formats check for Architecture of Knowledge took 0.06247210502624512s
Availability | RDF dump link check for Architecture of Knowledge took 0.03283953666687012s
License | MR license check for Architecture of Knowledge took 0.09688472747802734s
License | HR license check for Architecture of Knowledge took 60.160013914108276s
Amount of data | Number of property check for Architecture of Knowledge took 0.06401848793029785s
Understandability | Number of label check for Architecture of Knowledge took 1.6641597747802734s
Understandability | URI regex check for Architecture of Knowledge took 0.06961679458618164s
Understandability | Vocabs check for Architecture of Knowledge took 0.03464460372924805s
Verifiability | Authors check for Architecture of Knowledge took 0.05072331428527832s
Verifiability | Publishers check for Architecture of Knowledge took 0.04104924201965332s
Performance | Throughput check for Architecture of Knowledge took 10.223533153533936s
Amount of data | Check the number of entities for Architecture of Knowledge took 6.651878356933594e-05s
Verifiability | Contribs. check for Architecture of Knowledge took 0.047881126403808594s
Interlinking | sameAs chians check for Architecture of Knowledge took 0.06052231788635254s
Interlinking | skos check for Architecture of Knowledge took 0.11409592628479004s
Interlinking | skos check for Architecture of Knowledge took 0.04233503341674805s
Timeliness | dataset update frequency check for Architecture of Knowledge took 0.037148475646972656s
Currency | Creation date check for Architecture of Knowledge took 0.15710663795471191s
Currency | Modification date check for Architecture of Knowledge took 0.15185093879699707s
Rep.Conc. | URIs length for Architecture of Knowledge took 87.4071946144104s
Interoperability | New vocabularies check for Architecture of Knowledge took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Architecture of Knowledge took 0.058373451232910156s
Accuracy | Check Functional Property for Architecture of Knowledge took 0.09763503074645996s
Accuracy | Check Inverse Functional Property for Architecture of Knowledge took 0.08153939247131348s
Accuracy | Check Empty annotation labels for Architecture of Knowledge took 49.65266561508179s
Accuracy | Check White space in annotation for Architecture of Knowledge took 3.0648882389068604s
Consistency | Disjoint class check for Architecture of Knowledge took 0.13988471031188965s
Consistency | Check Misplaced properties for Architecture of Knowledge took 29.60180687904358s
Consistency | Misplaced classes for Architecture of Knowledge took 0.10081148147583008s
Consistency | Check Ontology hijacking for Architecture of Knowledge took 39.471431732177734s
Consistency | Check Invalid usage of undefined properties for Architecture of Knowledge took 30.084893226623535s
Conciseness | Check Extensional conciseness for Architecture of Knowledge took 0.00016760826110839844s
Conciseness | Check Intensional conciseness for Architecture of Knowledge took 0.2110300064086914s
Security | Sign check for Architecture of Knowledge took 0.044158935546875s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.4019906520843506s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.0214846134185791s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.5497207641601562e-05s
Interoperability | Check the re-using of existing vocabs for Architecture of Knowledge took 1.9073486328125e-06s
Believability | Calculation of trust value for Architecture of Knowledge took 1.1444091796875e-05s
INFO | --- Analysis for ArCo took 578.3922309875488s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.3646223545074463s
Availability | VoID file availability check for ConfermentSampo took 0.0004975795745849609s
Extra | Recovery of all triples for ConfermentSampo took 101.71142506599426s
Performance | Total latancy measurement for ConfermentSampo took 0.8348431587219238s
Amount of data | Number of triples check for ConfermentSampo took 40.32542896270752s
Interoperability | New terms check for ConfermentSampo took 24.782147645950317s
Versatility | Languages check for ConfermentSampo took 38.90099501609802s
Interpretability | Number of blank nodes check for ConfermentSampo took 6.881193161010742s
Security | Check HTTPS for ConfermentSampo took 0.41080427169799805s
Interpretability | RDF structures check for ConfermentSampo took 0.195481538772583s
Versatility | Serialization formats check for ConfermentSampo took 0.20694851875305176s
Availability | RDF dump link check for ConfermentSampo took 3.193080186843872s
License | MR license check for ConfermentSampo took 0.19544124603271484s
License | HR license check for ConfermentSampo took 0.27913689613342285s
Amount of data | Number of property check for ConfermentSampo took 0.1879863739013672s
Understandability | Number of label check for ConfermentSampo took 9.963152170181274s
Understandability | URI regex check for ConfermentSampo took 0.34989309310913086s
Understandability | Vocabs check for ConfermentSampo took 0.18191003799438477s
Verifiability | Authors check for ConfermentSampo took 0.1942591667175293s
Verifiability | Publishers check for ConfermentSampo took 0.1998434066772461s
Performance | Throughput check for ConfermentSampo took 11.18998646736145s
Amount of data | Check the number of entities for ConfermentSampo took 0.0002925395965576172s
Verifiability | Contribs. check for ConfermentSampo took 0.19180655479431152s
Interlinking | sameAs chians check for ConfermentSampo took 0.49595046043395996s
Interlinking | skos check for ConfermentSampo took 0.15922927856445312s
Interlinking | skos check for ConfermentSampo took 0.1573796272277832s
Timeliness | dataset update frequency check for ConfermentSampo took 0.15892601013183594s
Currency | Creation date check for ConfermentSampo took 0.3683760166168213s
Currency | Modification date check for ConfermentSampo took 0.36479973793029785s
Rep.Conc. | URIs length for ConfermentSampo took 30.787374019622803s
Interoperability | New vocabularies check for ConfermentSampo took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.19481587409973145s
Accuracy | Check Functional Property for ConfermentSampo took 0.18505454063415527s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.16827106475830078s
Accuracy | Check Empty annotation labels for ConfermentSampo took 14.445827722549438s
Accuracy | Check White space in annotation for ConfermentSampo took 2.9965691566467285s
Consistency | Disjoint class check for ConfermentSampo took 0.16873836517333984s
Consistency | Check Misplaced properties for ConfermentSampo took 6.430354356765747s
Consistency | Check Ontology hijacking for ConfermentSampo took 14.995056867599487s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.5476293563842773s
Conciseness | Check Extensional conciseness for ConfermentSampo took 0.0001430511474609375s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.20841240882873535s
Security | Sign check for ConfermentSampo took 0.18018794059753418s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.47187328338623047s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.29367995262145996s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for ConfermentSampo took 1.049041748046875e-05s
INFO | --- Analysis for ConfermentSampo took 441.2331774234772s
Availability | SPARQL endpoint availability check for Museum Finland took 0.39555835723876953s
Availability | VoID file availability check for Museum Finland took 0.00044727325439453125s
Extra | Recovery of all triples for Museum Finland took 6.527362585067749s
Performance | Total latancy measurement for Museum Finland took 0.8105068206787109s
Amount of data | Number of triples check for Museum Finland took 0.3389263153076172s
Interoperability | New terms check for Museum Finland took 1.7004485130310059s
Versatility | Languages check for Museum Finland took 0.6923830509185791s
Interpretability | Number of blank nodes check for Museum Finland took 0.3261270523071289s
Security | Check HTTPS for Museum Finland took 0.24209094047546387s
Interpretability | RDF structures check for Museum Finland took 0.502312421798706s
Versatility | Serialization formats check for Museum Finland took 0.21564364433288574s
Availability | RDF dump link check for Museum Finland took 0.16350078582763672s
License | MR license check for Museum Finland took 0.18908333778381348s
License | HR license check for Museum Finland took 0.38824939727783203s
Amount of data | Number of property check for Museum Finland took 0.1836225986480713s
Understandability | Number of label check for Museum Finland took 0.355604887008667s
Understandability | URI regex check for Museum Finland took 0.31999635696411133s
Understandability | Vocabs check for Museum Finland took 0.1600041389465332s
Verifiability | Authors check for Museum Finland took 0.16981267929077148s
Verifiability | Publishers check for Museum Finland took 0.16073012351989746s
Performance | Throughput check for Museum Finland took 10.963562965393066s
Amount of data | Check the number of entities for Museum Finland took 3.218650817871094e-05s
Verifiability | Contribs. check for Museum Finland took 0.1591050624847412s
Interlinking | sameAs chians check for Museum Finland took 0.1610870361328125s
Interlinking | skos check for Museum Finland took 0.17821574211120605s
Interlinking | skos check for Museum Finland took 0.15838122367858887s
Timeliness | dataset update frequency check for Museum Finland took 0.1598217487335205s
Currency | Creation date check for Museum Finland took 0.35986971855163574s
Currency | Modification date check for Museum Finland took 0.3828296661376953s
Rep.Conc. | URIs length for Museum Finland took 3.2579095363616943s
Interoperability | New vocabularies check for Museum Finland took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.1853504180908203s
Accuracy | Check Functional Property for Museum Finland took 0.1672353744506836s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.15889573097229004s
Accuracy | Check Empty annotation labels for Museum Finland took 0.9846563339233398s
Accuracy | Check White space in annotation for Museum Finland took 0.061374664306640625s
Accuracy | Check Datatype consistency for Museum Finland took 0.9431378841400146s
Consistency | Disjoint class check for Museum Finland took 0.16700387001037598s
Consistency | Check Misplaced properties for Museum Finland took 0.6021971702575684s
Consistency | Check Ontology hijacking for Museum Finland took 2.0350468158721924s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.2581934928894043s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.4188687801361084s
Conciseness | Check Extensional conciseness for Museum Finland took 0.631389856338501s
Conciseness | Check Intensional conciseness for Museum Finland took 0.22462248802185059s
Security | Sign check for Museum Finland took 0.16706371307373047s
Availability | Check URIs Dereferenciability for Museum Finland took 2575.840920448303s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.7727272510528564s
Reputation | Calculation of the PageRank for Museum Finland took 0.021749019622802734s
Interlinking | Calculation of Degree of Connection for Museum Finland took 7.2479248046875e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 2.1457672119140625e-06s
Believability | Calculation of trust value for Museum Finland took 1.1444091796875e-05s
INFO | --- Analysis for FI-Museum took 2631.70357465744s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.18885231018066406s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0005764961242675781s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 15.838967561721802s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.8456752300262451s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 30.36035943031311s
Interoperability | New terms check for Mapping Manuscript Migrations took 5.024853706359863s
Versatility | Languages check for Mapping Manuscript Migrations took 75.24294567108154s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.02182674407959s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.40419983863830566s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.18975114822387695s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.1924278736114502s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.1591794490814209s
License | MR license check for Mapping Manuscript Migrations took 0.19524669647216797s
License | HR license check for Mapping Manuscript Migrations took 1.8059184551239014s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.19179749488830566s
Understandability | Number of label check for Mapping Manuscript Migrations took 8.756496906280518s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3458747863769531s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.15963292121887207s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.18349862098693848s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.18377113342285156s
Performance | Throughput check for Mapping Manuscript Migrations took 11.085169076919556s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0269596576690674s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.16659045219421387s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5156776905059814s
Interlinking | skos check for Mapping Manuscript Migrations took 0.16892004013061523s
Interlinking | skos check for Mapping Manuscript Migrations took 0.14889216423034668s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.17193365097045898s
Currency | Creation date check for Mapping Manuscript Migrations took 0.34473657608032227s
Currency | Modification date check for Mapping Manuscript Migrations took 0.1909503936767578s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 49.18205261230469s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.1590886116027832s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.1594409942626953s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.15986013412475586s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.161152601242065s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.404475450515747s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.6908533573150635s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.18241500854492188s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 23.879797220230103s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.13105320930481s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.555373191833496s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.5598623752593994s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.766437530517578s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.184891939163208s
Security | Sign check for Mapping Manuscript Migrations took 0.16774225234985352s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 21.744270086288452s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.3071751594543457s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.02104353904724121s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.9788742065429688e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 2.1457672119140625e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.0967254638671875e-05s
INFO | --- Analysis for MMM took 512.3882231712341s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.17603111267089844s
Availability | VoID file availability check for Semantic Kalevala took 0.0005748271942138672s
Extra | Recovery of all triples for Semantic Kalevala took 8.557615995407104s
Performance | Total latancy measurement for Semantic Kalevala took 0.813826322555542s
Amount of data | Number of triples check for Semantic Kalevala took 0.400256872177124s
Interoperability | New terms check for Semantic Kalevala took 1.5192852020263672s
Versatility | Languages check for Semantic Kalevala took 0.8826160430908203s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.36826086044311523s
Security | Check HTTPS for Semantic Kalevala took 0.22876906394958496s
Interpretability | RDF structures check for Semantic Kalevala took 0.23811554908752441s
Versatility | Serialization formats check for Semantic Kalevala took 0.18371987342834473s
Availability | RDF dump link check for Semantic Kalevala took 0.17540931701660156s
License | MR license check for Semantic Kalevala took 0.21692371368408203s
License | HR license check for Semantic Kalevala took 1.0873956680297852s
Amount of data | Number of property check for Semantic Kalevala took 0.33951354026794434s
Understandability | Number of label check for Semantic Kalevala took 1.4914777278900146s
Understandability | URI regex check for Semantic Kalevala took 0.3357250690460205s
Understandability | Vocabs check for Semantic Kalevala took 0.16170978546142578s
Verifiability | Authors check for Semantic Kalevala took 0.16835236549377441s
Verifiability | Publishers check for Semantic Kalevala took 0.16106200218200684s
Performance | Throughput check for Semantic Kalevala took 11.07017993927002s
Amount of data | Check the number of entities for Semantic Kalevala took 8.153915405273438e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.16533303260803223s
Interlinking | sameAs chians check for Semantic Kalevala took 0.17897772789001465s
Interlinking | skos check for Semantic Kalevala took 0.2878694534301758s
Interlinking | skos check for Semantic Kalevala took 0.16498088836669922s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.16959810256958008s
Currency | Creation date check for Semantic Kalevala took 0.3586757183074951s
Currency | Modification date check for Semantic Kalevala took 0.34307432174682617s
Rep.Conc. | URIs length for Semantic Kalevala took 4.845481634140015s
Interoperability | New vocabularies check for Semantic Kalevala took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.19076037406921387s
Accuracy | Check Functional Property for Semantic Kalevala took 0.18538117408752441s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.1519172191619873s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.9180071353912354s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.2949390411376953s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.417107343673706s
Consistency | Disjoint class check for Semantic Kalevala took 0.15529274940490723s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7758843898773193s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.383732318878174s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.4486677646636963s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.6364073753356934s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.8923065662384033s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.30050110816955566s
Security | Sign check for Semantic Kalevala took 0.1674938201904297s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2302.886288881302s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.524479866027832s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.5730314254760742s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.3589859008789062e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.6689300537109375e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.0967254638671875e-05s
INFO | --- Analysis for Semantic-Kalevala took 2368.872773885727s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 1.1370699405670166s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0006682872772216797s
Extra | Recovery of all triples for Smithsonian American Art Museum took 294.7203233242035s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.0342764854431152s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5899379253387451s
Interoperability | New terms check for Smithsonian American Art Museum took 2.9201250076293945s
Versatility | Languages check for Smithsonian American Art Museum took 32.81739521026611s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5976126194000244s
Security | Check HTTPS for Smithsonian American Art Museum took 0.36647963523864746s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.6108229160308838s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6734893321990967s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.6294682025909424s
License | MR license check for Smithsonian American Art Museum took 0.6448385715484619s
License | HR license check for Smithsonian American Art Museum took 17.11318302154541s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.6297547817230225s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5828285217285156s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1934826374053955s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.6160359382629395s
Verifiability | Authors check for Smithsonian American Art Museum took 0.6056606769561768s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.6206867694854736s
Performance | Throughput check for Smithsonian American Art Museum took 12.359437704086304s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 7.2479248046875e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.6174206733703613s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5786867141723633s
Interlinking | skos check for Smithsonian American Art Museum took 0.6019036769866943s
Interlinking | skos check for Smithsonian American Art Museum took 0.582655668258667s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.6707165241241455s
Currency | Creation date check for Smithsonian American Art Museum took 1.2191712856292725s
Currency | Modification date check for Smithsonian American Art Museum took 1.249382495880127s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 105.86660647392273s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5963623523712158s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 21.541595220565796s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.4962170124053955s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.194566249847412s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5857293605804443s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 4.085458517074585s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 94.44579458236694s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.5674350261688232s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 4.784126043319702s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.8269927501678467s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6245303153991699s
Security | Sign check for Smithsonian American Art Museum took 0.6113615036010742s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.385948181152344s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.46222686767578125s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.020829439163208008s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.6450881958007812e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 2.1457672119140625e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 1.239776611328125e-05s
INFO | --- Analysis for Smithsonian took 718.81152176857s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.22968006134033203s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.28296828269958496s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.1682510375976562e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.1205673217773438e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 10.54788613319397s
Availability | SPARQL endpoint availability check for Archives Hub took 20.7251398563385s
Availability | VoID file availability check for Archives Hub took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.32239866256713867s
Reputation | Calculation of the PageRank for Archives Hub took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.2636184692382812e-05s
Believability | Calculation of trust value for Archives Hub took 1.239776611328125e-05s
INFO | --- Analysis for Archives-Hub took 54.11448359489441s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.5978114604949951s
Availability | VoID file availability check for Yale centre of British Art took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.2870900630950928s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.020410776138305664s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.0967254638671875e-05s
Believability | Calculation of trust value for Yale centre of British Art took 1.33514404296875e-05s
INFO | --- Analysis for Yale took 4.891809940338135s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 262.80621457099915s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.3008701801300049s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 3.337860107421875e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.811981201171875e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.1444091796875e-05s
INFO | --- Analysis for ADL took 537.8213179111481s
Availability | SPARQL endpoint availability check for MusicKG took 0.7878446578979492s
Availability | VoID file availability check for MusicKG took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for MusicKG took 0.27390003204345703s
Reputation | Calculation of the PageRank for MusicKG took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.1920928955078125e-05s
Believability | Calculation of trust value for MusicKG took 1.1682510375976562e-05s
INFO | --- Analysis for MusicKG took 4.4915101528167725s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.840482234954834s
Availability | VoID file availability check for CIDOC-CRM took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.27795934677124023s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.2159347534179688e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.1920928955078125e-05s
INFO | --- Analysis for CIDOC-CRM took 4.3119354248046875s
Availability | SPARQL endpoint availability check for Mondis took 0.32134103775024414s
Availability | VoID file availability check for Mondis took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Mondis took 0.28717970848083496s
Reputation | Calculation of the PageRank for Mondis took 0.02121114730834961s
Interlinking | Calculation of Degree of Connection for Mondis took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.2159347534179688e-05s
Believability | Calculation of trust value for Mondis took 1.2874603271484375e-05s
INFO | --- Analysis for Mondis took 3.6418750286102295s
Availability | SPARQL endpoint availability check for DigitalNZ took 2.6112825870513916s
Availability | VoID file availability check for DigitalNZ took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.3037090301513672s
Reputation | Calculation of the PageRank for DigitalNZ took 0.021078109741210938s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.2159347534179688e-05s
Believability | Calculation of trust value for DigitalNZ took 1.0251998901367188e-05s
INFO | --- Analysis for DigitalNZ took 6.711646318435669s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.17284822463989258s
Availability | VoID file availability check for Fondazione Zeri took 0.00067138671875s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.30462098121643066s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.1920928955078125e-05s
Believability | Calculation of trust value for Fondazione Zeri took 1.0013580322265625e-05s
INFO | --- Analysis for Fondazione-Zeri took 3.605721950531006s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.23592829704284668s
Availability | VoID file availability check for Digital Public Library of America took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.3096351623535156s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.021619081497192383s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.430511474609375e-05s
Believability | Calculation of trust value for Digital Public Library of America took 1.3589859008789062e-05s
INFO | --- Analysis for Library-of-America took 4.257410526275635s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.9853758811950684s
Availability | VoID file availability check for Auckland Museum took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.2977175712585449s
Reputation | Calculation of the PageRank for Auckland Museum took 0.02087855339050293s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.2874603271484375e-05s
Believability | Calculation of trust value for Auckland Museum took 1.2636184692382812e-05s
INFO | --- Analysis for Auckland-Museum took 7.077059030532837s
Availability | SPARQL endpoint availability check for National Library of Spain took 1.7148735523223877s
Availability | VoID file availability check for National Library of Spain took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.2839803695678711s
Reputation | Calculation of the PageRank for National Library of Spain took 0.02219533920288086s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.33514404296875e-05s
Believability | Calculation of trust value for National Library of Spain took 1.3828277587890625e-05s
INFO | --- Analysis for BNE took 5.039547681808472s
Availability | SPARQL endpoint availability check for National Library of Korea took 1.3859622478485107s
Availability | VoID file availability check for National Library of Korea took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.33963727951049805s
Reputation | Calculation of the PageRank for National Library of Korea took 0.020783424377441406s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.3113021850585938e-05s
Believability | Calculation of trust value for National Library of Korea took 1.3828277587890625e-05s
INFO | --- Analysis for Korea-Library took 4.672606468200684s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.6300368309020996s
Availability | VoID file availability check for The State Russian Museum took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.2974369525909424s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.020944595336914062s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.2159347534179688e-05s
Believability | Calculation of trust value for The State Russian Museum took 1.239776611328125e-05s
INFO | --- Analysis for Russian-Museum took 4.926308870315552s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.8972194194793701s
Availability | VoID file availability check for National Library of Scotland took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.31540536880493164s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.021061182022094727s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.3828277587890625e-05s
Believability | Calculation of trust value for National Library of Scotland took 1.2636184692382812e-05s
INFO | --- Analysis for National-Library-of-Scotland took 11.105725288391113s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.37134885787963867s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.3426964282989502s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.020739316940307617s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.2636184692382812e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.33514404296875e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.896794319152832s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.22842025756835938s
Availability | VoID file availability check for OntoComedySources took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.28945446014404297s
Reputation | Calculation of the PageRank for OntoComedySources took 0.02097606658935547s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.239776611328125e-05s
Believability | Calculation of trust value for OntoComedySources took 1.1920928955078125e-05s
INFO | --- Analysis for OntoComedySources took 4.564666986465454s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.21980047225952148s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.2883164882659912s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.021299362182617188s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.239776611328125e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.0251998901367188e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 4.57367467880249s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.2530076503753662s
Availability | VoID file availability check for SaintGall Ontology took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.2713921070098877s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.020499229431152344s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.1920928955078125e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for SaintGall-Ontology took 3.4079041481018066s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.8481554985046387s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.28854966163635254s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.33514404296875e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 4.4607062339782715s
Availability | SPARQL endpoint availability check for ICON took 0.34055113792419434s
Availability | VoID file availability check for ICON took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for ICON took 0.31424474716186523s
Reputation | Calculation of the PageRank for ICON took 0.020625829696655273s
Interlinking | Calculation of Degree of Connection for ICON took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for ICON took 2.0742416381835938e-05s
Believability | Calculation of trust value for ICON took 1.239776611328125e-05s
INFO | --- Analysis for ICON took 4.528059482574463s
Availability | SPARQL endpoint availability check for Polifonia took 0.2763485908508301s
Availability | VoID file availability check for Polifonia took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Polifonia took 0.287276029586792s
Reputation | Calculation of the PageRank for Polifonia took 0.022441864013671875s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.2636184692382812e-05s
Believability | Calculation of trust value for Polifonia took 1.1444091796875e-05s
INFO | --- Analysis for Polifonia took 11.545220136642456s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.2487189769744873s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0007781982421875s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.3049275875091553s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.2636184692382812e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 1.1444091796875e-05s
INFO | --- Analysis for Atlas-of-Paths took 4.227163791656494s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.20062661170959473s
Availability | VoID file availability check for Music Note Ontology took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.30098390579223633s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.021267175674438477s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.7404556274414062e-05s
Believability | Calculation of trust value for Music Note Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for Music-Note-Ontology took 119.37363386154175s
Availability | SPARQL endpoint availability check for HaMSE took 0.21586036682128906s
Availability | VoID file availability check for HaMSE took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for HaMSE took 0.3004639148712158s
Reputation | Calculation of the PageRank for HaMSE took 0.022234439849853516s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.1444091796875e-05s
Believability | Calculation of trust value for HaMSE took 1.049041748046875e-05s
INFO | --- Analysis for HaMSE took 6.358875513076782s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.13059782981872559s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.2886204719543457s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.021123170852661133s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.2636184692382812e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 1.0013580322265625e-05s
INFO | --- Analysis for FOod took 5.045454740524292s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 1.5032649040222168s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.31101274490356445s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.3113021850585938e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 9.775161743164062e-06s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 6.076796531677246s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 3.5751397609710693s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.2984580993652344s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.021031856536865234s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.3113021850585938e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 9.775161743164062e-06s
INFO | --- Analysis for ARIADNE took 8.143401384353638s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.35932421684265137s
Availability | VoID file availability check for Odeuropa Ontology took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.2808053493499756s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.021956920623779297s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.1920928955078125e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Odeuropa took 3.6317567825317383s

--- Total time for analysis:497766.5477194786s ---
--- Total time for analysis:138.26848547763294 hours ---