Endpoint URI
Site Description
Organization Information
Data specified by dcterms:publisher in VoID
License Information
Data specified by dcterms:license in VoID
Supported Language
Data specified by sd:supportedLanguage in Service Description
  • SPARQL10Query
True if a query using 'SERVICE' keyword returns a result, otherwise false.
GRAPH Keyword
True if a query using 'GRAPH' keyword returns a result, otherwise false.
Data Scale
This number represents the scale of data.
The value is determined by a formula, x = log10N where N is the number of data entries.
Ranked based on the following table
A81 - 100
B61 - 80
C41 - 60
D21 - 40
E0 - 20
A (97)
True if a response header of the endpoint contains 'access-control-allow-origin: *', otherwise false.
URI Indexed
True if URI patterns of the endpoint are defined by us. These are used for checking content negotiation and Four Principles of Linked Data
Last Checked
Time when the crawler accessed and how long it took last time
2024-06-13 14:25:37 UTC (5m 35s)
Class Structure
The link to the site where you can learn the data structure

Please see this document for more details about Umaka Score.


Availability (100.0)Alive (Alive Score)
Alive monitoring score that takes the value from 0 to 100. If the crawler fails to access the endpoint, the score drops from the previous score day by day. If the crawler successfully accesses to the endpoint, the score rises day by day based on the previous score.
Freshness (100.0)Last Updated
The last updated date.
The date in Service Description or VoID are taken, if any.
Operation (100.0)Service Description
True if Service Description can be retrieved as turtle or rdf+xml, otherwise false.
True if VoID can be found on well-known URI, otherwise false.
Usefulness (96.4)
This value shows how much metadata can be retrieved using the specified SPARQL query.
Zero if any graph information can be retrieved.
For each graph, we score the status by retrieving classes, labels, properties and datatypes. The average of the scores are shown.
Please see the following pages for more details:
This value shows how the endpoint uses common ontologies. We calculate the value as the average of the rate of the ontologies used in properties in metadata for each graph.
Please see also the following pages:
Links to Other Dataset
List of datasets specified by void:Linkset in VoID
Data Entry
Number of statements in the endpoint.
Support for HTML Data Format
True if the endpoint returns a response in HTML format, otherwise false.
Support for Turtle Data Format
True if the endpoint returns a response in Turtle format, otherwise false.
Support for RDF/XML Data Format
True if the endpoint returns a response in RDF/XML format, otherwise false.
Validity (90.0)4 Principles of Linked Data
This shows how much the endpoint follows the four principles of Linked Data:
  • Use URIs as names for things
  • Use HTTP URIs so that people can look up those names.
  • When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)
  • Include links to other URIs. so that they can discover more things.
Please see the following page for more details:
URIs are used as names?
Always true, because this is mandatory if the target data is RDF and it does not affect Umakadata score.
HTTP URIs are used?
True if all the subjects are HTTP URI, otherwise false. Blank nodes can be a subject, but not all of them.
URI provides useful information?
True if the endpoint returns some data when issuing a GET request to an HTTP URI of a subject, otherwise false.
Include links to other URIs?
True if the endpoint contains owl:sameAs or rdf:seeAlso dataset, otherwise false.
Cool URI
We score the cool URI according 4 criteria:
  • the address of the endpoint is represented using host name not IP address.
  • the endpoint should listen to 80 port.
  • the URI of the endpoint does not contain URL parameters.
  • the length of the URI is less than 30 characters.
Please see the following pages for more details:
Performance (99.5)
This icon indicates the database is medium scale. (7.0 ≤ Data Scale < 9.0)
Execution Time
This value represents the processing performance. It is calculated as a difference of the response time retrieving the number of classes query from its ASK{} query. The final value is obtained by averaging over the results taken by three times.