Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Cross-Origin Resource Sharing ( is enabled for SPARQL endpoints served from This means that endpoint URLs can be entered into JavaScript-based SPARQL editors and services such as YASGUI (

Constructing a URL

URLs that access the SPARQL endpoints are constructed from the following components in sequence. (The value in the Example column column for vocabulary identifier is artificially chosen; it does not correspond to a vocabulary published at RVA.)

The RVA hostname and API prefix

The vocabulary identifier

Vocabulary owner, vocabulary title, version title, separated by underscores

The SPARQL QueryThe text ?query= followed by the SPARQL Query, encoded using percent encoding (*%20{?s%20?p%20?o}


  • The components of the vocabulary identifier are turned into “slugs” ( before inclusion in the URL. In practice, this means conversion to lower case, and the replacement of all non-alphanumeric data with hyphens.  You do not have to guess what a slug will be ; each vocabulary available through Sesame on RVA has, on its view page, a sample link to a SPARQL endpoint.
  • A small number of vocabularies of particular significance have vocabulary identifiers that do not follow the pattern shown in the table above. For example, the ARDC-Curated version of the ANZSRC 2020 Fields of Research vocabulary has vocabulary identifier anzsrc-2020-for. Please check each vocabulary's view page in the portal to confirm its endpoint URL.


There's a list of the supported formats in the first table at: http Pick the format you want from the left column; specify the value in the right column in the "Accept" header.