-
-
Notifications
You must be signed in to change notification settings - Fork 76
Installing QUDT for Consumers
This page describes installation methods for a "consumer" who just wants to use the QUDT ontology in their own application, but not to change it in any way. There is a companion page here that describes how a developer can install the QUDT in ways that support contributing new Units, QuantityKinds, or even community extensions, via GitHub Pull Requests.
Go the the Releases page and choose any version. The latest version not marked "Snapshot" is the most recent stable release. If you want the absolute latest, choose the Snapshot release, but there may be some experimental, not-yet-stable changes. Once you have downloaded either the zip or tar.gz file, unzip the file to place the expanded folders wherever you need them. In addition, please note the configuration of the facade file.
For the Linked Data community, you can just refer to any of the QUDT graphs or instances as resolvable URIs. This approach works well with Protege using the "Open from URL" menu item. Since Protege transitively follows owl:imports statements, you probably want to just load http://qudt.org/vocab/unit/ and it will bring in all the other schema and vocabulary graphs needed. (Loading the units graph leaves out the physical constants graph and the currency graph. If you want either or both of those, load them instead).
One of the imported files - the "facade" file that is resolvable on the web (http://qudt.org/schema/facade/qudt) - is configured to load the OWL schema rather than the SHACL schema, so Protege users will be in the OWL world using this method. This is different from the downloaded Release graph that imports the SHACL schema. For more information, see the README that shows the imports closure diagram.
So, for example, if you want the latest Units graph in its entirety, refer to it as http://qudt.org/vocab/unit/ in your application. Variants such as https://qudt.org/vocab/unit/ and https://qudt.org/2.1/vocab/unit also work. (All http: requests are automatically redirected to https: requests). We will be moving toward full semantic versioning soon, so you can link to the latest, un-versioned URI, or to a specific version this way.
In the same way, you can refer to an individual Unit (or other instance), such as http://qudt.org/vocab/unit/A for the Ampere. We use content negotiation, so if you enter that in a browser, you get an HTML page. The same URI from an application will give you a Turtle snippet. (You can look at the snippet in your browser by entering http://qudt.org/vocab/unit/A.ttl)