Skip to main content


We are in the process of rolling out a soft launch of the RDA website, which includes a new member platform. Existing RDA members PLEASE REACTIVATE YOUR ACCOUNT using this link: Visitors may encounter functionality issues with group pages, navigation, missing content, broken links, etc. As you explore the new site, please provide your feedback using the UserSnap tool on the bottom right corner of each page. Thank you for your understanding and support as we work through all issues as quickly as possible. Stay updated about upcoming features and functionalities:


Nicholas Car

Hi Jakob,
Thanks for adding VocPrez! Regarding the information you have: VocPrez is a stand-alone tool and is just used for that Department of Natural Resources, Mines and Energy’s vocabularies but it can be used anywhere, so it’s not ties to that domain at all, it’s just pure SKOS-based. So the best link for VocPrez, the system, is really it’s repository at , not this instance URI of . Also, the API should really be “Linked Data API” and perhaps “+ SPARQL” since it’s designed to deliver content online as RDF + HTML first with SPARQL only as a backup endpoint for down-stream systems to use.
Yes, I know about Skosmos (and PoolParty, and a few others). There are two main motivations for VocPrez:
1. To act as a replacement for a previous read-only SKOS vocab front-end – SISSVoc
– We have a legacy set of installations of SISSVoc ( ), a read-only SKOS vocab Linked Data front end developed on top of Epimorphics’ ELDA, that we wish to replace
– SISSVoc uses old Java libraries that are no longer well maintained and so we developed VocPrez in modern Python to do a similar to but to be easier to maintain.
– VocPrez is template-based and pretty simple as far as web frameworks for Linked Data go
Like SISSVoc, VocPrez doesn’t manage vocabs, only deliver them as Linked Data – RDF & HTML. VocPrez can also use multiple back-ends so you can use, say, VocBench or PoolParty as a vocab development environment with VocPrez in front for online delivery. For the the instances in production now, Oracle, GitHub, RDF files, SPARQL endpoints and custom APIs are all used for the back-end
2. To implement Content Negotiation by Profile
The soon-to-be W3C recommendation ConnegP ( ) includes standard methods of asking for profiles of specifications and VocPrez uses a Python library, pyLDAPI ( ) that is one of the ConnegP demonstration toolkits.
Thanks for pointing out that broken Alternates profile link! We are updating VocPrez to match changes in the ConnegP draft and, in this case, we are a week or two behind catching up to a change made in the way the Alternate Profile access is listed. Will try and fix now!