acl:
filename: @vocabulary/acl/acl.nq
type: PrefixMapping
prefix: acl
uri: http://www.w3.org/ns/auth/acl#

Activity Streams 2.0
filename: @vocabulary/as/as.nq
description: Extended Activity Streams 2.0 Vocabulary
type: PrefixMapping
prefix: as
uri: https://www.w3.org/ns/activitystreams#

b59:
filename: @vocabulary/b59/b59.nq
type: PrefixMapping
prefix: b59
uri: https://barnard59.zazuko.com/vocab#

The Bibliographic Ontology
filename: @vocabulary/bibo/bibo.nq
description: The Bibliographic Ontology describes bibliographic things on the semantic Web in RDF. This ontology can be used as a citation ontology, as a document classification ontology, or simply as a way to describe any kind of document in RDF. It has been inspired by many existing document description metadata formats, and can be used as a common ground for converting other bibliographic data sources.
type: PrefixMapping
prefix: bibo
uri: http://purl.org/ontology/bibo/

cc:
filename: @vocabulary/cc/cc.nq
type: PrefixMapping
prefix: cc
uri: http://creativecommons.org/ns#

Ontology for Certificates and crypto stuff.
filename: @vocabulary/cert/cert.nq
description: Ontology for Certificates and crypto stuff. This is in development. Some other ontologies to look at: * http://www.w3.org/2000/10/swap/crypto + has cwm builtins: http://www.w3.org/2000/10/swap/doc/Trust - a bit old perhaps. It imports daml+oil - would help to be more completely specified - uses literals as subjects a little liberally, which makes this a bit difficult to work with frameworks that don't permit this * http://xmlns.com/wot/0.1/ - limited very much to PGP (though on can map PGP to X509) - a little coarse grained, mixes up the PGP certificate with the PGP public key * Todo: - add some classes and relations for DSA - should this all be in one file? Or should this be cut up a little? Say one file for the general CERT ontology, and then files for RSA, DSA, PGP, etc... Or perhaps it does not really matter? - expand more on the certification side of things - verify this by security experts - owl2 has some constructs for combined inverse functional properties. This may be useful to use in defining an RSA key which is identified by two numbers. - also create html version of the spec by using this as a template. - should comments such as this be in html?
type: PrefixMapping
prefix: cert
uri: http://www.w3.org/ns/auth/cert#

Representing Content in RDF
filename: @vocabulary/cnt/cnt.nq
description: Representing Content in RDF as defined by http://www.w3.org/TR/Content-in-RDF/
type: PrefixMapping
prefix: cnt
uri: http://www.w3.org/2011/content#

code:
filename: @vocabulary/code/code.nq
type: PrefixMapping
prefix: code
uri: https://code.described.at/

QUDT VOCAB Physical Constants Release 3.1.10
filename: @vocabulary/constant/constant.nq
type: PrefixMapping
prefix: constant
uri: http://qudt.org/vocab/constant/

crm:
filename: @vocabulary/crm/crm.nq
description: CIDOC CRM v7.1.3 implemented in RDFS This is the implementation approved by the 58th CRM-SIG meeting (March 2024) as the current RDFS version for the CIDOC CRM namespace. Note that this is NOT a definition of the CIDOC CRM, but a CIDOC CRM compatible implementation of an RDF Schema derived from the authoritative release of the CIDOC CRM v7.1.3 on February 2024 https://cidoc-crm.org/Version/version-7.1.3 by an automated algorithm. It is intended for an assumed majority of uses. Depending on the application, users may create adequate extensions compatible with the logical definitions of the CIDOC CRM. Created by FORTH-ICS February 13, 2024 CC BY 4.0 https://creativecommons.org/licenses/by/4.0/legalcode Encoding Rules: 1. The RDF spelling rules do not allow blanks. Hence we have replaced them by underscores. For instance "E63_Beginning_of_Existence" or "P2i_is_type_of". 2. RDF does not allow to instantiate properties beginning from a range value. Therefore, each CRM property is represented as two RDFS properties. For instance "P2 has type (is type of)" is represented as: "P2_has_type" for the domain to range direction and "P2i_is_type_of" for the range to domain direction. 3. The primitive values "E60 Number", "E61 Time Primitive", "E62 String", "E94 Space Primitive" and "E95 Spacetime Primitive" referred in the Model for formal completeness are interpreted as rdfs:literal. 4. RDF does not support properties of properties, therefore, users may create their own subProperties for CRM properties that have a type property such as "P3 has note": Instead of P3 has note (P3-1 has type : parts description) declare <rdf:Property rdf:about="P3_parts_description"> <rdfs:domain rdf:resource="E1_CRM_Entity"/> <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/> <rdfs:subPropertyOf rdf:resource="P3_has_note"/> </rdf:Property> 5. Scope notes are represented as <rdfs:comment> elements. 6. In addition this encoding contains labels in languages different from Englis…
type: PrefixMapping
prefix: crm
uri: http://www.cidoc-crm.org/cidoc-crm/

CSVW Namespace Vocabulary Terms
filename: @vocabulary/csvw/csvw.nq
description: This document describes the RDFS vocabulary description used in the Metadata Vocabulary for Tabular Data tabular-metadata along with the default JSON-LD Context.
type: PrefixMapping
prefix: csvw
uri: http://www.w3.org/ns/csvw#

Common Tag vocabulary
filename: @vocabulary/ctag/ctag.nq
description: Common Tag RDF vocabulary, described using W3C RDF Schema. Common Tags allows documents and document fragments (any resource which can be identified by a URI) to be labeled with keywords and URIs, unambigiously idenfying the concepts covered by the resource.
type: PrefixMapping
prefix: ctag
uri: http://commontag.org/ns#

Cube Schema
filename: @vocabulary/cube/cube.nq
type: PrefixMapping
prefix: cube
uri: https://cube.link/

QUDT VOCAB Currency Units Release 3.0.0
filename: @vocabulary/cur/cur.nq
type: PrefixMapping
prefix: cur
uri: http://qudt.org/vocab/currency/

SPARQL Vocabulary for SHACL
filename: @vocabulary/dash-sparql/dash-sparql.nq
description: Defines SHACL functions (with URIs) representing the built-in SPARQL 1.1 functions and operators such as isIRI and / (divide). Each of these is represented by an instance of sh:Function with a URI such as sparql:divide. The declared parameters indicate the number of arguments but no other constraints have been added.
type: PrefixMapping
prefix: dash-sparql
uri: http://datashapes.org/sparql#

DASH Data Shapes Vocabulary
filename: @vocabulary/dash/dash.nq
description: DASH is a SHACL library for frequently needed features and design patterns. The constraint components in this library are 100% standards compliant and will work on any engine that fully supports SHACL.
type: PrefixMapping
prefix: dash
uri: http://datashapes.org/dash#

The DBpedia Ontology
filename: @vocabulary/dbo/dbo.nq
description: The DBpedia ontology provides the classes and properties used in the DBpedia data set.
type: PrefixMapping
prefix: dbo
uri: http://dbpedia.org/ontology/

Dublin Core Metadata Element Set, Version 1.1
filename: @vocabulary/dc11/dc11.nq
type: PrefixMapping
prefix: dc11
uri: http://purl.org/dc/elements/1.1/

Metadata terms for vocabulary description
filename: @vocabulary/dcam/dcam.nq
type: PrefixMapping
prefix: dcam
uri: http://purl.org/dc/dcam/

The data catalog vocabulary
filename: @vocabulary/dcat/dcat.nq
description: DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation. DCAT is defined at http://www.w3.org/TR/vocab-dcat/. Any variance between that normative document and this schema is an error in this schema.
type: PrefixMapping
prefix: dcat
uri: http://www.w3.org/ns/dcat#

DCMI Type Vocabulary
filename: @vocabulary/dcmitype/dcmitype.nq
type: PrefixMapping
prefix: dcmitype
uri: http://purl.org/dc/dcmitype/

DCMI Metadata Terms - other
filename: @vocabulary/dcterms/dcterms.nq
type: PrefixMapping
prefix: dcterms
uri: http://purl.org/dc/terms/

dig:
filename: @vocabulary/dig/dig.nq
type: PrefixMapping
prefix: dig
uri: http://www.ics.forth.gr/isl/CRMdig/

QUDT Disciplines Ontology
filename: @vocabulary/discipline/discipline.nq
type: PrefixMapping
prefix: discipline
uri: http://qudt.org/vocab/discipline/

Description of a Project (DOAP) vocabulary
filename: @vocabulary/doap/doap.nq
description: The Description of a Project (DOAP) vocabulary, described using W3C RDF Schema and the Web Ontology Language.
type: PrefixMapping
prefix: doap
uri: http://usefulinc.com/ns/doap#

The Data Product (DPROD) Ontology
filename: @vocabulary/dprod/dprod.nq
description: DPROD extends DCAT to enable publishers to describe Data Products and data services in a decentralized way.
type: PrefixMapping
prefix: dprod
uri: https://ekgf.github.io/dprod/

dpv:
filename: ontologies/dpv.nq
type: PrefixMapping
prefix: dpv
uri: http://www.w3.org/ns/dpv#

Data Quality Vocabulary
filename: @vocabulary/dqv/dqv.nq
description: The Data Quality Vocabulary (DQV) is seen as an extension to DCAT to cover the quality of the data, how frequently is it updated, whether it accepts user corrections, persistence commitments etc. When used by publishers, this vocabulary will foster trust in the data amongst developers.
type: PrefixMapping
prefix: dqv
uri: http://www.w3.org/ns/dqv#

Datatype Ontology
filename: @vocabulary/dtype/dtype.nq
type: PrefixMapping
prefix: dtype
uri: http://www.linkedmodel.org/schema/dtype#

Dataset Usage Vocabulary
filename: @vocabulary/duv/duv.nq
description: The Dataset Usage Vocabulary (DUV) is used to describe consumer experiences, citations, and feedback about datasets from the human perspective.
type: PrefixMapping
prefix: duv
uri: http://www.w3.org/ns/duv#

Evaluation and Report Language (EARL) 1.0 Schema
filename: @vocabulary/earl/earl.nq
description: Formal schema of the Evaluation and Report Language (EARL) 1.0
type: PrefixMapping
prefix: earl
uri: http://www.w3.org/ns/earl#

EBUCore - the Dublin Core for media
filename: @vocabulary/ebucore/ebucore.nq
description: Guidelines: for the purpose of flexibility and interoperability with a wider range of implementations, some properties purposefully do not have a range and accept either a resource or a literal. When a resource is used, it is recommended to reuse objects defined in the model (e.g. pair hasEvent/Event or hasRole/Role). Example 1: x hasRole 'actor'. Example 2: x hasRole _:Role_1 (a reference to the Concept identifier from a SKOS Role vocabulary defined in the ontology).
type: PrefixMapping
prefix: ebucore
uri: http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#

Exif data description vocabulary
filename: @vocabulary/exif/exif.nq
description: Vocabulary to describe an Exif format picture data. All Exif 2.2 tags are defined as RDF properties, as well as several terms to help this schema.
type: PrefixMapping
prefix: exif
uri: http://www.w3.org/2003/12/exif/ns#

Friend of a Friend (FOAF) vocabulary
filename: @vocabulary/foaf/foaf.nq
description: The Friend of a Friend (FOAF) RDF vocabulary, described using W3C RDF Schema and the Web Ontology Language.
type: PrefixMapping
prefix: foaf
uri: http://xmlns.com/foaf/0.1/

frbr:
filename: @vocabulary/frbr/frbr.nq
type: PrefixMapping
prefix: frbr
uri: http://purl.org/vocab/frbr/core#

GeoSPARQL Ontology
filename: @vocabulary/geo/geo.nq
description: An RDF/OWL vocabulary for representing spatial information
type: PrefixMapping
prefix: geo
uri: http://www.opengis.net/ont/geosparql#

geof:
filename: @vocabulary/geof/geof.nq
type: PrefixMapping
prefix: geof
uri: http://www.opengis.net/def/function/geosparql/

geor:
filename: @vocabulary/geor/geor.nq
type: PrefixMapping
prefix: geor
uri: http://www.opengis.net/def/rule/geosparql/

gml:
filename: @vocabulary/gml/gml.nq
type: PrefixMapping
prefix: gml
uri: http://www.opengis.net/ont/gml#

The Geonames ontology
filename: @vocabulary/gn/gn.nq
description: The Geonames ontologies provides elements of description for geographical features, in particular those defined in the geonames.org data base
type: PrefixMapping
prefix: gn
uri: http://www.geonames.org/ontology#

The GoodRelations Vocabulary for Semantic Web-based E-Commerce
filename: @vocabulary/gr/gr.nq
description: The GoodRelations ontology provides the vocabulary for annotating e-commerce offerings (1) to sell, lease, repair, dispose, or maintain commodity products and (2) to provide commodity services. GoodRelations allows describing the relationship between (1) Web resources, (2) offerings made by those Web resources, (3) legal entities, (4) prices, (5) terms and conditions, and the aforementioned ontologies for products and services (6). For more information, see http://purl.org/goodrelations/ Note: The base URI of GoodRelations is http://purl.org/goodrelations/v1. Please make sure you are only using element identifiers in this namespace, e.g. http://purl.org/goodrelations/v1#BusinessEntity. There may be copies of the ontology file on the Web which can be retrieved from other locations, BUT THOSE LOCATIONS MUST NOT BE USED AS THE BASIS OF IDENTIFIERS. If you use GoodRelations for scientific purposes, please cite our paper: Hepp, Martin: GoodRelations: An Ontology for Describing Products and Services Offers on the Web, Proceedings of the 16th International Conference on Knowledge Engineering and Knowledge Management (EKAW2008), September 29 - October 3, 2008, Acitrezza, Italy, Springer LNCS, Vol. 5268, pp. 332-347. PDF at http://www.heppnetz.de/publications/
type: PrefixMapping
prefix: gr
uri: http://purl.org/goodrelations/v1#

grddl:
filename: @vocabulary/grddl/grddl.nq
type: PrefixMapping
prefix: grddl
uri: http://www.w3.org/2003/g/data-view#

gs1:
filename: @vocabulary/gs1/gs1.nq
type: PrefixMapping
prefix: gs1
uri: https://gs1.org/voc/

General Transit Feed Specification
filename: @vocabulary/gtfs/gtfs.nq
description: This ontology is a translation of the General Transit Feed Specification towards URIs. Its intended use is creating an exchange platform where the Linked GTFS model can be used as a start to get the right data into the right format. For semantics of the classes and properties, see https://developers.google.com/transit/gtfs/reference.
type: PrefixMapping
prefix: gtfs
uri: http://vocab.gtfs.org/terms#

HTTP in RDF
filename: @vocabulary/http/http.nq
description: A namespace for describing HTTP messages (http://www.w3.org/Protocols/rfc2616/rfc2616.html)
type: PrefixMapping
prefix: http
uri: http://www.w3.org/2011/http#

The Hydra Core Vocabulary
filename: @vocabulary/hydra/hydra.nq
description: The Hydra Core Vocabulary is a lightweight vocabulary to create hypermedia-driven Web APIs. By specifying a number of concepts commonly used in Web APIs it enables the creation of generic API clients.
type: PrefixMapping
prefix: hydra
uri: http://www.w3.org/ns/hydra/core#

ical:
filename: @vocabulary/ical/ical.nq
type: PrefixMapping
prefix: ical
uri: http://www.w3.org/2002/12/cal/icaltzd#

la:
filename: @vocabulary/la/la.nq
type: PrefixMapping
prefix: la
uri: https://linked.art/ns/terms/

The W3C Linked Data Platform (LDP) Vocabulary
filename: @vocabulary/ldp/ldp.nq
description: Vocabulary URIs defined in the Linked Data Platform (LDP) namespace.
type: PrefixMapping
prefix: ldp
uri: http://www.w3.org/ns/ldp#

list:
filename: @vocabulary/list/list.nq
type: PrefixMapping
prefix: list
uri: http://www.w3.org/2000/10/swap/list#

ISA Programme Location Core Vocabulary
filename: @vocabulary/locn/locn.nq
description: This is a new version of the final draft published by the European Commission in May 2012, revised according to the results of the ISA Core Location Pilot (see Section Change History for the list of changes). It is currently under the control of the Locations and Addresses Community Group, but is not under active development or review. Comments and queries should be sent to that group via public-locadd@w3.org. Terms defined here may be deprecated by that or future groups but will not disappear or their definition change.
type: PrefixMapping
prefix: locn
uri: http://www.w3.org/ns/locn#

log:
filename: @vocabulary/log/log.nq
type: PrefixMapping
prefix: log
uri: http://www.w3.org/2000/10/swap/log#

Lexvo.org Ontology
filename: @vocabulary/lvont/lvont.nq
description: Lexvo.org Ontology
type: PrefixMapping
prefix: lvont
uri: http://lexvo.org/ontology#

Metadata4Ing: An ontology for describing the generation of research data within a scientific activity.
filename: @vocabulary/m4i/m4i.nq
description: Metadata4Ing defines classes and properties or reuses such classes and properties from other ontologies to describe research processes and research data management in NFDI4Ing. New concepts and properties are located in the namespace of Metadata4Ing. Metadata4Ing does not import complete ontologies for the sake of relevance, readability, understandability and usability by and for engineers. Instead, it tries to make re-use of existing identifiers for classes and properties by re-using all or a relevant subset of the axioms from the original ontology. These statements have been extracted in different ways, e.g. by using Protégé tools importing an ontology and copying axioms of relevant items to Metadata4Ing or by download from data services or raw files of ontologies and manual copypasting. In some cases there was a need to extend or modify the original set of statements about an entity, e.g. because labels and definitions were expressed with a different owl:AnnotationProperty than the rest of Metadata4Ing, or because a rdfs:label or a rdfs:comment in any of the languages we would like to support was missing. Any editorial changes on elements from external ontologies are declared in Metadata4Ing by an annotation with skos:editorialNote at item-level. To get the original set of statements we encourage to visit the original namespace of the respective item. Metadata4Ing reuses elements from the following ontologies: - BIRO = Bibliographic Reference Ontology - CR = Croissant - DCAT = Data Catalog - DCC = Digital Calibration Certificate - DCTERMS = Dublin Core Terms - EMMO = European Materials and Modelling Ontology - FOAF = Friend of a Friend - OBO = Open Biological and Biomedical Ontologies: - BFO = Basic Formal Ontology - RO = Relation Ontology - OWL = Web Ontology Language - PIMS-II = PIMS Interoperability Infrastructure - PROV = Provenance Namespace - QUDT = Quantities, Units, Dimensions and Types - RDF = Resource Description Framework - RDFS = RDF Schema - SCHEMA =…
type: PrefixMapping
prefix: m4i
uri: http://w3id.org/nfdi4ing/metadata4ing#

ma:
filename: @vocabulary/ma/ma.nq
description: Created by Tobias Buerger, Jean Pierre Evain and Pierre-Antoine Champin with the RDFS Taskforce within the W3C Media Annotation Working Group.
type: PrefixMapping
prefix: ma
uri: http://www.w3.org/ns/ma-ont#

MADS/RDF (Metadata Authority Description Schema in RDF)
filename: @vocabulary/mads/mads.nq
description: This document describes the MADS/RDF (Metadata Authority Description Schema in RDF) vocabulary, a data model for authority and vocabulary data used within the library and information science (LIS) community, which is inclusive of museums, archives, and other cultural institutions. It is presented as an OWL ontology. MADS/RDF is a knowledge organization system (KOS) designed for use with controlled values for names (personal, corporate, geographic, etc.), thesauri, taxonomies, subject heading systems, and other controlled value lists. It is closely related to SKOS, the Simple Knowledge Organization System and a widely supported and adopted RDF vocabulary. Given the close relationship between the aim of MADS/RDF and the aim of SKOS, the MADS ontology has been fully mapped to SKOS. Unlike SKOS, however, which is very broad in its application, MADS/RDF is designed specifically to support authority data as used by and needed in the LIS community and its technology systems. For example, MADS/RDF provides a means to record data from the Machine Readable Cataloging (MARC) Authorities format in RDF for use in semantic applications and Linked Data projects. MADS/RDF is designed to support the description of cultural and bibliographic resources. Data described using MADS/RDF, therefore, assists with identifying and annotating bibliographic and cultural resources. MADS/RDF is not focused on the description of Real World Objects. Although a MADS/RDF description may contain information specific to the Real World Object associated with the MADS/RDF authoritative label, the MADS/RDF ontology distinguishes between these two entities – the RWO and the Authority. Updated: 4 March 2024. Addition of new class: Medium, an accidental omission from earlier updates. The MADS/RDF to SKOS/RDF mapping was done by Antoine Isaac. The MADS/RDF model and ontology benefited significantly as a result of the fruitful discussions surrounding his effort to map the MADS/RDF ontology to SKOS.
type: PrefixMapping
prefix: mads
uri: http://www.loc.gov/mads/rdf/v1#

math:
filename: @vocabulary/math/math.nq
type: PrefixMapping
prefix: math
uri: http://www.w3.org/2000/10/swap/math#

meta:
filename: @vocabulary/meta/meta.nq
type: PrefixMapping
prefix: meta
uri: https://cube.link/meta/

Web Annotation Ontology
filename: @vocabulary/oa/oa.nq
description: The Web Annotation ontology defines the terms of the Web Annotation vocabulary. Any changes to this document MUST be from a Working Group in the W3C that has established expertise in the area.
type: PrefixMapping
prefix: oa
uri: http://www.w3.org/ns/oa#

og:
filename: @vocabulary/og/og.nq
type: PrefixMapping
prefix: og
uri: http://ogp.me/ns#

Solid OIDC
filename: @vocabulary/oidc/oidc.nq
description: The OpenID Connect vocabulary used by the Solid-OIDC authentication specification.
type: PrefixMapping
prefix: oidc
uri: http://www.w3.org/ns/solid/oidc#

Core organization ontology
filename: @vocabulary/org/org.nq
description: Vocabulary for describing organizational structures, specializable to a broad variety of types of organization.
type: PrefixMapping
prefix: org
uri: http://www.w3.org/ns/org#

The OWL 2 Schema vocabulary (OWL 2)
filename: @vocabulary/owl/owl.nq
description: This ontology partially describes the built-in classes and properties that together form the basis of the RDF/XML syntax of OWL 2. The content of this ontology is based on Tables 6.1 and 6.2 in Section 6.4 of the OWL 2 RDF-Based Semantics specification, available at http://www.w3.org/TR/owl2-rdf-based-semantics/. Please note that those tables do not include the different annotations (labels, comments and rdfs:isDefinedBy links) used in this file. Also note that the descriptions provided in this ontology do not provide a complete and correct formal description of either the syntax or the semantics of the introduced terms (please see the OWL 2 recommendations for the complete and normative specifications). Furthermore, the information provided by this ontology may be misleading if not used with care. This ontology SHOULD NOT be imported into OWL ontologies. Importing this file into an OWL 2 DL ontology will cause it to become an OWL 2 Full ontology and may have other, unexpected, consequences.
type: PrefixMapping
prefix: owl
uri: http://www.w3.org/2002/07/owl#

pim:
filename: @vocabulary/pim/pim.nq
type: PrefixMapping
prefix: pim
uri: http://www.w3.org/ns/pim/space#

pipeline:
filename: @vocabulary/pipeline/pipeline.nq
type: PrefixMapping
prefix: pipeline
uri: https://pipeline.described.at/

prefix:
filename: @vocabulary/prefix/prefix.nq
type: PrefixMapping
prefix: prefix
uri: http://qudt.org/vocab/prefix/

W3C PROVenance Interchange
filename: @vocabulary/prov/prov.nq
description: This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/ Archives/Public/public-prov-comments/). All feedback is welcome.
type: PrefixMapping
prefix: prov
uri: http://www.w3.org/ns/prov#

Vocabulary for multi-dimensional (e.g. statistical) data publishing
filename: @vocabulary/qb/qb.nq
description: This vocabulary allows multi-dimensional data, such as statistics, to be published in RDF. It is based on the core information model from SDMX (and thus also DDI).
type: PrefixMapping
prefix: qb
uri: http://purl.org/linked-data/cube#

QUDT VOCAB Dimension Vectors Release 3.1.10
filename: @vocabulary/qkdv/qkdv.nq
type: PrefixMapping
prefix: qkdv
uri: http://qudt.org/vocab/dimensionvector/

quantitykind:
filename: @vocabulary/quantitykind/quantitykind.nq
type: PrefixMapping
prefix: quantitykind
uri: http://qudt.org/vocab/quantitykind/

qudt:
filename: @vocabulary/qudt/qudt.nq
type: PrefixMapping
prefix: qudt
uri: http://qudt.org/schema/qudt/

RDA Unconstrained properties
filename: @vocabulary/rdau/rdau.nq
type: PrefixMapping
prefix: rdau
uri: http://rdaregistry.info/Elements/u/

The RDF Concepts Vocabulary (RDF)
filename: @vocabulary/rdf/rdf.nq
description: This is the RDF Schema for the RDF vocabulary terms in the RDF Namespace, defined in RDF 1.1 Concepts.
type: PrefixMapping
prefix: rdf
uri: http://www.w3.org/1999/02/22-rdf-syntax-ns#

RDFa Vocabulary for Term and Prefix Assignment, and for Processor Graph Reporting
filename: @vocabulary/rdfa/rdfa.nq
description: This document describes the RDFa Vocabulary for Term and Prefix Assignment. The Vocabulary is used to modify RDFa 1.1 processing behavior.
type: PrefixMapping
prefix: rdfa
uri: http://www.w3.org/ns/rdfa#

The RDF Schema vocabulary (RDFS)
filename: @vocabulary/rdfs/rdfs.nq
type: PrefixMapping
prefix: rdfs
uri: http://www.w3.org/2000/01/rdf-schema#

relation:
filename: @vocabulary/relation/relation.nq
type: PrefixMapping
prefix: relation
uri: https://cube.link/relation/

RDF Review Vocabulary
filename: @vocabulary/rev/rev.nq
description: Vocabulary for expressing reviews and ratings using the Resource Description Framework. It is compatible with hReview and conforms to OWL Lite
type: PrefixMapping
prefix: rev
uri: http://purl.org/stuff/rev#

International Council on Archives Records in Contexts Ontology (ICA RiC-O) version 1.1
filename: @vocabulary/rico/rico.nq
description: Introduction RiC-O (Records in Contexts-Ontology) is an OWL ontology for describing archival record resources. As the third part of Records in Contexts standard, it is a formal representation of Records in Contexts Conceptual Model (RiC-CM). This version, which is v1.1, is the latest official release. It is compliant with RiC-CM v1.0. The following diagram shows the main RiC-CM 1.0 entities and a few relations between them: RiC-O design principles The following design principles were followed when developing RiC-O. 1. RiC-O is a domain and reference ontology. RiC-O provides a generic vocabulary and formal rules for creating RDF datasets (or generating them from existing archival metadata) that describe in a consistent way any kind of archival record resource. It supports publishing RDF datasets as Linked Data, querying them using SPARQL, and making inferences using the logic of the ontology. While some projects have built some specific ontologies for describing archives, in 2013 no generic domain ontology existed for the specific needs of the archival community. This is why EGAD decided to develop RiC-O as a part of RiC standard. Apart from this first, main target, RiC-O, as a technical implementation of RiC-CM that also extends and refines it and that includes formal logic, can guide or inspire, in many ways, the development of any tool or system that manages (i.e. stores, enables to edit or processes) and publishes descriptive archival metadata.. Of course, other technical implementations of RiC-CM may be developed later on. Also, the current technical implementations of the former ICA standards, e.g. EAD and EAC-CPF XML schemas, should be made closer to RiC-CM in the future; on this topic, see the news and announcements of the Technical Subcommittee on Encoded Archival Standards (TS-EAS) of the Society of American Archivists. As RiC-O is a generic, domain ontology, it does not address by itself every specific need or expectation that may occur in every archival i…
type: PrefixMapping
prefix: rico
uri: https://www.ica.org/standards/RiC/ontology#

R2RML vocabulary
filename: @vocabulary/rr/rr.nq
description: RDB to RDF Mapping Language - Vocabulary
type: PrefixMapping
prefix: rr
uri: http://www.w3.org/ns/r2rml#

rss:
filename: @vocabulary/rss/rss.nq
type: PrefixMapping
prefix: rss
uri: http://purl.org/rss/1.0/

schema:
filename: @vocabulary/schema/schema.nq
type: PrefixMapping
prefix: schema
uri: http://schema.org/

sd:
filename: @vocabulary/sd/sd.nq
type: PrefixMapping
prefix: sd
uri: http://www.w3.org/ns/sparql-service-description#

Vocabulary for publishing SDMX statistical data in RDF
filename: @vocabulary/sdmx/sdmx.nq
description: This vocabulary extends the data cube vocabulary to support publication of statistical data in RDF, using an information model based on SDMX
type: PrefixMapping
prefix: sdmx
uri: http://purl.org/linked-data/sdmx#

sem:
filename: @vocabulary/sem/sem.nq
type: PrefixMapping
prefix: sem
uri: http://semanticweb.cs.vu.nl/2009/11/sem/

set:
filename: @vocabulary/set/set.nq
type: PrefixMapping
prefix: set
uri: http://www.w3.org/2000/10/swap/set#

sf:
filename: @vocabulary/sf/sf.nq
type: PrefixMapping
prefix: sf
uri: http://www.opengis.net/ont/sf#

sh:
filename: @vocabulary/sh/sh.nq
type: PrefixMapping
prefix: sh
uri: http://www.w3.org/ns/shacl#

Shape Expression Vocabulary
filename: @vocabulary/shex/shex.nq
description: This document describes the RDFS vocabulary description used in the Shape Expression Language (ShEx) shex-semantics along with the default JSON-LD Context and shape expression to validate RDF versions of shapes.
type: PrefixMapping
prefix: shex
uri: http://www.w3.org/ns/shex#

SHACL for SHACL
filename: @vocabulary/shsh/shsh.nq
description: This shapes graph can be used to validate SHACL shapes graphs against a subset of the syntax rules.
type: PrefixMapping
prefix: shsh
uri: http://www.w3.org/ns/shacl-shacl#

SIOC Core Ontology Namespace
filename: @vocabulary/sioc/sioc.nq
description: SIOC (Semantically-Interlinked Online Communities) is an ontology for describing the information in online communities. This information can be used to export information from online communities and to link them together. The scope of the application areas that SIOC can be used for includes (and is not limited to) weblogs, message boards, mailing lists and chat channels.
type: PrefixMapping
prefix: sioc
uri: http://rdfs.org/sioc/ns#

SKOS Vocabulary
filename: @vocabulary/skos/skos.nq
description: An RDF vocabulary for describing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies.
type: PrefixMapping
prefix: skos
uri: http://www.w3.org/2004/02/skos/core#

Solid Terms
filename: @vocabulary/solid/solid.nq
description: The Solid Terms vocabulary defines terms referenced in Solid specifications.
type: PrefixMapping
prefix: solid
uri: http://www.w3.org/ns/solid/terms#

Sensor, Observation, Sample, and Actuator (SOSA) Ontology
filename: @vocabulary/sosa/sosa.nq
description: This ontology is based on the SSN Ontology by the W3C Semantic Sensor Networks Incubator Group (SSN-XG), together with considerations from the W3C/OGC Spatial Data on the Web Working Group.
type: PrefixMapping
prefix: sosa
uri: http://www.w3.org/ns/sosa/

QUDT VOCAB Systems of Units Release 3.1.10
filename: @vocabulary/sou/sou.nq
type: PrefixMapping
prefix: sou
uri: http://qudt.org/vocab/sou/

Semantic Sensor Network Ontology
filename: @vocabulary/ssn/ssn.nq
description: This ontology describes sensors, actuators and observations, and related concepts. It does not describe domain concepts, time, locations, etc. these are intended to be included from other ontologies via OWL imports.
type: PrefixMapping
prefix: ssn
uri: http://www.w3.org/ns/ssn/

stat:
filename: @vocabulary/stat/stat.nq
type: PrefixMapping
prefix: stat
uri: http://www.w3.org/ns/posix/stat#

string:
filename: @vocabulary/string/string.nq
description: String Processing Ontology
type: PrefixMapping
prefix: string
uri: http://www.w3.org/2000/10/swap/string#

test:
filename: @vocabulary/test/test.nq
type: PrefixMapping
prefix: test
uri: http://www.w3.org/2006/03/test-description#

OWL-Time
filename: @vocabulary/time/time.nq
type: PrefixMapping
prefix: time
uri: http://www.w3.org/2006/time#

unit:
filename: @vocabulary/unit/unit.nq
type: PrefixMapping
prefix: unit
uri: http://qudt.org/vocab/unit/

vaem:
filename: @vocabulary/vaem/vaem.nq
type: PrefixMapping
prefix: vaem
uri: http://www.linkedmodel.org/schema/vaem#

VANN: A vocabulary for annotating vocabulary descriptions
filename: @vocabulary/vann/vann.nq
description: This document describes a vocabulary for annotating descriptions of vocabularies with examples and usage notes.
type: PrefixMapping
prefix: vann
uri: http://purl.org/vocab/vann/

Ontology for vCard
filename: @vocabulary/vcard/vcard.nq
description: Ontology for vCard based on RFC6350
type: PrefixMapping
prefix: vcard
uri: http://www.w3.org/2006/vcard/ns#

void:
filename: @vocabulary/void/void.nq
type: PrefixMapping
prefix: void
uri: http://rdfs.org/ns/void#

SemWeb Vocab Status ontology
filename: @vocabulary/vs/vs.nq
description: An RDF vocabulary for relating SW vocabulary terms to their status.
type: PrefixMapping
prefix: vs
uri: http://www.w3.org/2003/06/sw-vocab-status/ns#

VSO: The Vehicle Sales Ontology for Semantic Web-based E-Commerce
filename: @vocabulary/vso/vso.nq
description: VSO: The Vehicle Sales Ontology A Web vocabulary for describings cars, boats, bikes, and other vehicles for e-commerce. Vocabulary: http://purl.org/vso/ns Namespace: http://purl.org/vso/ns# The Vehicle Sales Ontology is designed to be used in combination with GoodRelations, a standard vocabulary for the commercial aspects of offers for sale or rental. See http://purl.org/goodrelations/ for more information.
type: PrefixMapping
prefix: vso
uri: http://purl.org/vso/ns#

POWDER-S Vocabulary
filename: @vocabulary/wdrs/wdrs.nq
description: This file specifies the set of classes and properties used in the RDF/OWL version of POWDER documents.
type: PrefixMapping
prefix: wdrs
uri: http://www.w3.org/2007/05/powder-s#

WGS84 Geo Positioning: an RDF vocabulary
filename: @vocabulary/wgs/wgs.nq
description: A vocabulary for representing latitude, longitude and altitude information in the WGS84 geodetic reference datum. Version $Id: wgs84_pos.rdf,v 1.22 2009/04/20 15:00:30 timbl Exp $. See http://www.w3.org/2003/01/geo/ for more details.
type: PrefixMapping
prefix: wgs
uri: http://www.w3.org/2003/01/geo/wgs84_pos#

XKOS: an SKOS extension for representing statistical classifications
filename: @vocabulary/xkos/xkos.nq
description: This ontology is based on work initiated at Dagstuhl Schloss in September 2011
type: PrefixMapping
prefix: xkos
uri: http://rdf-vocabulary.ddialliance.org/xkos#

xsd:
filename: @vocabulary/xsd/xsd.nq
type: PrefixMapping
prefix: xsd
uri: http://www.w3.org/2001/XMLSchema#