inrupt/lit-term-js

TypeScript definitions for jest

TypeScript plugin for ESLint

An ESLint custom parser which leverages TypeScript ESTree

Import with sanity.

Runs prettier as an eslint rule

Delightful JavaScript Testing.

Check license info for a package

A TypeScript/JavaScript implementation of the RDF/JS data factory.

Seamless integration between Rollup and TypeScript. Now with errors.

A Jest transformer with source map support that lets you use Jest to test projects written in TypeScript

TypeScript is a language for application scale JavaScript development

Bundle of vocabularies that includes the following: - acl: [Generator provided] - Web Access Control Vocabulary - acp: A vocabulary to structure policy-based access controls for the Solid ecosystem. - oidc: The OpenID Connect vocabulary used by the Solid-OIDC authentication specification. - solid: The Solid Terms vocabulary defines terms referenced in Solid specifications. - solid_meta_acl: The Solid vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by the Solid ACL system. - solid_meta_client: The Solid vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by Solid clients. - solid_meta_server_creational: The Solid vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server creation time. - solid_meta_server_runtime: The Solid vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server creation time. - solid_sd: The Solid Service Description vocabulary describes the services provided by a Solid Server. - solid_service_core: The Solid vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) commonly used across Solid services. - ws: This extension adds predicates making explicit some implicit knowledge in the Workspace ontology.

Bundle of vocabularies that includes the following: - acl: [Generator provided] - Web Access Control Vocabulary - altr: This ontology allows for the description of representations of Internet resources. Representations may conform to prof:Profile instances and may have the format of a particular dct:MediaType. - as: Extended Activity Streams 2.0 Vocabulary - bookmark: [Generator provided] - W3C Bookmark vocabulary - cred: A vocabulary for the Data Model for W3C Verifiable Credentials. - dcat: 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. - dcterms: [Generator provided] - Dublin Core Terms - for describing resources - doap: [Generator provided] - Description of a Project (DOAP) vocabulary - earl: [Generator provided] - Evaluation and Report Language (EARL) - foaf: [Generator provided] - Friend of a friend, v0.99 - http: A namespace for describing HTTP messages (http://www.w3.org/Protocols/rfc2616/rfc2616.html) - httph-inrupt: This vocabulary is a one deemed to contain all HTTP headers. The rdflib.js library uses it as for relationships between an HTTP response and the content (value) of the HTTP header in that response. The ontology is deemed to contain one property for every HTTP header, standard or not. The property in this ontology has a localname which is the header field converted to lower case. - hydra: 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. - ical: [Generator provided] - iCal - a vocabulary for description of events and calendars - jsonld: This is a vocabulary document and is used to achieve certain features of the JSON-LD language. - ldp: Vocabulary URIs defined in the Linked Data Platform (LDP) namespace. - odrl: The ODRL Vocabulary and Expression defines a set of concepts and terms (the vocabulary) and encoding mechanism (the expression) for permissions and obligations statements describing digital content usage based on the ODRL Information Model. - olo: [Generator provided] - OLO (Ordered List Ontology) - for describing ordered lists - owl: 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. - posix: A vocabulary for the basic POSIX terms. - prov-o: 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 [email protected] (subscribe [email protected], archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome. - qb: 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). - rdf: [Generator provided] - RDF (Resource Description Framework) - a framework for representing information in the Web - rdfs: [Generator provided] - RDFS (RDF Schema) - a data-modelling vocabulary for RDF data - rlog: Inrupt-created copy of RLOG, needed due to Server 500 errors resolving original uni-leipzig.org! - schema-inrupt: Inrupt extension to Schema.org terms providing multilingual alternative names (i.e., labels) and translations for comments (e.g., for use directly as labels or tool-tips in user interfaces or error messages). This extension very deliberately cherry-picks the individual terms from Schema.org that Inrupt currently deem generally useful for Solid and Solid applications (meaning we can provide a much cleaner, less noisy and smaller bundle size when generating programming language artifacts that provide convenient constants for just these selected terms, rather than including the over 2,500 terms currently defined in Schema.org). - sd: [Generator provided] - SPARQL Service Description vocabulary - sdmx-dimension: [Generator provided] - SDMX Dimension Vocabulary - sec: [Generator provided] - Security vocabulary - shex: 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. - sioc: 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. - skos: 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. - skos-xl: An RDF vocabulary extending SKOS and allowing the description and linking of lexical entities. - ui: [Generator provided] - UI Ontology - ui-inrupt: Extension to UI terms providing multilingual alternative names and translations for comments (e.g., for use directly as labels or tool-tips in user interfaces or error messages) - vann: A vocabulary for annotating vocabulary descriptions (VANN). - vcard: Ontology for vCard based on RFC6350 - void: The Vocabulary of Interlinked Datasets (VoID) is an RDF Schema vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. This document provides a formal definition of the new RDF classes and properties introduced for VoID. It is a companion to the main specification document for VoID, <em><a href="http://www.w3.org/TR/void/">Describing Linked Datasets with the VoID Vocabulary</a></em>. - vs: This vocabulary was created in the FOAF project, based on experience with FOAF, Dublin Core and other early RDF vocabularies. Deployment experience shows that changing namespace URIs is expensive and unrewarding, so this vocabulary provides terms to support in-place evolution of structured data vocabularies. By indicating status at the level of terms rather than vocabularies, dictionary-style, fine grained improvements become easier. Different organizations and parties can agree or disagree on the status of a vocabulary term; however the status published alongside the term may deserve special attention. Future work could include patterns for citing announcements and decisions, or using SKOS to decentralise the extension of the basic status levels. - xsd: A vocabulary for describing XML Schema datatypes.

Bundle of vocabularies that includes the following: - inrupt_common: The Inrupt common vocabulary - just commonly used terms across all Inrupt products and services. - inrupt_consent: Consent vocabulary defining Inrupt-specific terms, especially terms that provide context - inrupt_gen: The Artifact Generator vocabulary - part of the collection of utility libraries to ease the adoption of RDF for developers. - inrupt_meta_client: This vocabulary provides client metadata terms (e.g., classes, properties and text strings (e.g., informative labels or error messages)) used by clients at runtime. - inrupt_meta_server_creational: A vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server creation time. - inrupt_meta_server_runtime: A vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server runtime. - inrupt_meta_shacl: A vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) usable by SHACL validation engines at runtime. - inrupt_metric: The Inrupt Metric Ontology contains vocab terms to represent metric statistics - inrupt_request: The Solid vocabulary providing terms for a various Named Graphs that make up a request. For example; Headers, Body, Metadata, ACL, etc. - inrupt_request_body: The Solid vocabulary providing terms for a request body (in this case, we're really just providing the Named Graph details (e.g., the IRI for the named graph itself), since the contents of a request body are completely arbitrary.

Bundle of vocabularies that includes the following: - inrupt_test: The Inrupt test vocabulary - just commonly used terms across all Inrupt tests.

Bundle of vocabularies that includes the following: - inrupt_test: The Inrupt test vocabulary - just commonly used terms across all Inrupt tests.

Bundle of vocabularies that includes the following: - inrupt_common: The Inrupt common vocabulary - just commonly used terms across all Inrupt products and services. - inrupt_consent: Consent vocabulary defining Inrupt-specific terms, especially terms that provide context - inrupt_gen: The Artifact Generator vocabulary - part of the collection of utility libraries to ease the adoption of RDF for developers. - inrupt_meta_client: This vocabulary provides client metadata terms (e.g. classes, properties and text strings (e.g., informative labels or error messages)) used by clients at runtime. - inrupt_meta_server_creational: The LIT vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by LIT servers at server creation time. - inrupt_meta_server_runtime: The LIT vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by LIT servers at server runtime. - inrupt_meta_shacl: The LIT vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) usable by SHACL validation engines at runtime. - inrupt_metric: The Inrupt Metric Ontology contains vocab terms to represent metric statistics - inrupt_request: The Solid vocabulary providing terms for a various Named Graphs that make up a request. For example; Headers, Body, Metadata, ACL, etc. - inrupt_request_body: The Solid vocabulary providing terms for a request body (in this case, we're really just providing the Named Graph details (e.g. the IRI for the named graph itself), since the contents of a request body are completely arbitrary.

Bundle of vocabularies that includes the following: - inrupt_notification: The Inrupt notification vocabulary. - inrupt_websub: The Inrupt WebSub vocabulary.

Bundle of vocabularies that includes the following: - inrupt_common: The Inrupt common vocabulary - just commonly used terms across all Inrupt products and services. - inrupt_consent: Consent vocabulary defining Inrupt-specific terms, especially terms that provide context - inrupt_gen: The Artifact Generator vocabulary - part of the collection of utility libraries to ease the adoption of RDF for developers. - inrupt_meta_client: This vocabulary provides client metadata terms (e.g., classes, properties and text strings (e.g., informative labels or error messages)) used by clients at runtime. - inrupt_meta_server_creational: A vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server creation time. - inrupt_meta_server_runtime: A vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server runtime. - inrupt_meta_shacl: A vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) usable by SHACL validation engines at runtime. - inrupt_metric: The Inrupt Metric Ontology contains vocab terms to represent metric statistics - inrupt_request: The Solid vocabulary providing terms for a various Named Graphs that make up a request. For example; Headers, Body, Metadata, ACL, etc. - inrupt_request_body: The Solid vocabulary providing terms for a request body (in this case, we're really just providing the Named Graph details (e.g., the IRI for the named graph itself), since the contents of a request body are completely arbitrary.

Bundle of vocabularies that includes the following: - acl: [Generator provided] - Web Access Control Vocabulary - acp: A vocabulary to structure policy-based access controls for the Solid ecosystem. - solid: The Solid Terms vocabulary defines terms referenced in Solid specifications. - solid_meta_acl: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by the Solid ACL system. - solid_meta_client: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by Solid clients. - solid_meta_server_creational: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server creation time. - solid_meta_server_runtime: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server creation time. - solid_sd: The Solid Service Description vocabulary describes the services provided by a Solid Server. - solid_service_core: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) commonly used across Solid services. - ws: This extension adds predicates making explicit some implicit knowledge in the Workspace ontology.

Bundle of vocabularies that includes the following: - inrupt_common: The Inrupt common vocabulary - just commonly used terms across all Inrupt products and services. - inrupt_consent: Consent vocabulary defining Inrupt-specific terms, especially terms that provide context - inrupt_gen: The Artifact Generator vocabulary - part of the collection of utility libraries to ease the adoption of RDF for developers. - inrupt_meta_client: This vocabulary provides client metadata terms (e.g. classes, properties and text strings (e.g., informative labels or error messages)) used by clients at runtime. - inrupt_meta_server_creational: The LIT vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by LIT servers at server creation time. - inrupt_meta_server_runtime: The LIT vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by LIT servers at server runtime. - inrupt_meta_shacl: The LIT vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) usable by SHACL validation engines at runtime. - inrupt_metric: The Inrupt Metric Ontology contains vocab terms to represent metric statistics - inrupt_request: The Solid vocabulary providing terms for a various Named Graphs that make up a request. For example; Headers, Body, Metadata, ACL, etc. - inrupt_request_body: The Solid vocabulary providing terms for a request body (in this case, we're really just providing the Named Graph details (e.g. the IRI for the named graph itself), since the contents of a request body are completely arbitrary.

Bundle of vocabularies that includes the following: - inrupt_test: The Inrupt test vocabulary - just commonly used terms across all Inrupt tests.

Bundle of vocabularies that includes the following: - acl: [Generator provided] - Web Access Control Vocabulary - acp: A vocabulary to structure policy-based access controls for the Solid ecosystem. - solid: The Solid Terms vocabulary defines terms referenced in Solid specifications. - solid_meta_acl: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by the Solid ACL system. - solid_meta_client: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by Solid clients. - solid_meta_server_creational: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server creation time. - solid_meta_server_runtime: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server creation time. - solid_sd: The Solid Service Description vocabulary describes the services provided by a Solid Server. - solid_service_core: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) commonly used across Solid services. - ws: This extension adds predicates making explicit some implicit knowledge in the Workspace ontology.

Bundle of vocabularies that includes the following: - inrupt_notification: The Inrupt notification vocabulary. - inrupt_websub: The Inrupt WebSub vocabulary.

Bundle of vocabularies that includes the following: - acl: [Generator provided] - Web Access Control Vocabulary - altr: This ontology allows for the description of representations of Internet resources. Representations may conform to prof:Profile instances and may have the format of a particular dct:MediaType. - as: Extended Activity Streams 2.0 Vocabulary - bookmark: [Generator provided] - W3C Bookmark vocabulary - cred: A vocabulary for the Data Model for W3C Verifiable Credentials. - dcat: 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. - dcterms: [Generator provided] - Dublin Core Terms - for describing resources - doap: [Generator provided] - Description of a Project (DOAP) vocabulary - earl: [Generator provided] - Evaluation and Report Language (EARL) - foaf: [Generator provided] - Friend of a friend, v0.99 - http: A namespace for describing HTTP messages (http://www.w3.org/Protocols/rfc2616/rfc2616.html) - httph-inrupt: This vocabulary is a one deemed to contain all HTTP headers. The rdflib.js library uses it as for relationships between an HTTP response and the content (value) of the HTTP header in that response. The ontology is deemed to contain one property for every HTTP header, standard or not. The property in this ontology has a localname which is the header field converted to lower case. - hydra: 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. - ical: [Generator provided] - iCal - a vocabulary for description of events and calendars - jsonld: This is a vocabulary document and is used to achieve certain features of the JSON-LD language. - ldp: Vocabulary URIs defined in the Linked Data Platform (LDP) namespace. - odrl: The ODRL Vocabulary and Expression defines a set of concepts and terms (the vocabulary) and encoding mechanism (the expression) for permissions and obligations statements describing digital content usage based on the ODRL Information Model. - olo: [Generator provided] - OLO (Ordered List Ontology) - for describing ordered lists - owl: 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. - posix: A vocabulary for the basic POSIX terms. - prov-o: 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 [email protected] (subscribe [email protected], archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome. - qb: 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). - rdf: [Generator provided] - RDF (Resource Description Framework) - a framework for representing information in the Web - rdfs: [Generator provided] - RDFS (RDF Schema) - a data-modelling vocabulary for RDF data - rlog: Inrupt-created copy of RLOG, needed due to Server 500 errors resolving original uni-leipzig.org! - schema-inrupt: Inrupt extension to Schema.org terms providing multilingual alternative names (i.e., labels) and translations for comments (e.g., for use directly as labels or tool-tips in user interfaces or error messages). This extension very deliberately cherry-picks the individual terms from Schema.org that Inrupt currently deem generally useful for Solid and Solid applications (meaning we can provide a much cleaner, less noisy and smaller bundle size when generating programming language artifacts that provide convenient constants for just these selected terms, rather than including the over 2,500 terms currently defined in Schema.org). - sd: [Generator provided] - SPARQL Service Description vocabulary - sdmx-dimension: [Generator provided] - SDMX Dimension Vocabulary - sec: [Generator provided] - Security vocabulary - shex: 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. - sioc: 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. - skos: 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. - skos-xl: An RDF vocabulary extending SKOS and allowing the description and linking of lexical entities. - ui: [Generator provided] - UI Ontology - ui-inrupt: Extension to UI terms providing multilingual alternative names and translations for comments (e.g., for use directly as labels or tool-tips in user interfaces or error messages) - vann: A vocabulary for annotating vocabulary descriptions (VANN). - vcard: Ontology for vCard based on RFC6350 - void: The Vocabulary of Interlinked Datasets (VoID) is an RDF Schema vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. This document provides a formal definition of the new RDF classes and properties introduced for VoID. It is a companion to the main specification document for VoID, <em><a href="http://www.w3.org/TR/void/">Describing Linked Datasets with the VoID Vocabulary</a></em>. - vs: This vocabulary was created in the FOAF project, based on experience with FOAF, Dublin Core and other early RDF vocabularies. Deployment experience shows that changing namespace URIs is expensive and unrewarding, so this vocabulary provides terms to support in-place evolution of structured data vocabularies. By indicating status at the level of terms rather than vocabularies, dictionary-style, fine grained improvements become easier. Different organizations and parties can agree or disagree on the status of a vocabulary term; however the status published alongside the term may deserve special attention. Future work could include patterns for citing announcements and decisions, or using SKOS to decentralise the extension of the basic status levels. - xsd: A vocabulary for describing XML Schema datatypes.

Bundle of vocabularies that includes the following: - lit-core: The LIT Core Ontology. The LIT is intended to be a collection of utility libraries to ease the adoption of RDF for developers. - lit_consent: Consent vocabulary defining LIT-specific terms, especially terms that provide context - lit-request-body: The Solid vocabulary providing terms for a request body (in this case, we&#x27;re really just providing the Named Graph details (e.g. the IRI for the named graph itself), since the contents of a request body are completely arbitrary. - lit-request: The Solid vocabulary providing terms for a various Named Graphs that make up a request. For example; Headers, Body, Metadata, ACL, etc. - lit-meta-client: The LIT vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by LIT clients at runtime. - lit-meta-shacl: The LIT vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) usable by SHACL validation engines at runtime. - lit-meta-server-creational: The LIT vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by LIT servers at server creation time. - lit-meta-server-runtime: The LIT vocabulary providing terms (e.g. classes, properties and text strings (e.g. informative labels or error messages) used by LIT servers at server runtime. - met: The LIT Metrics Ontology contains vocab terms to represent metric statistics

Bundle of vocabularies that includes the following: - acl: [Generator provided] - Web Access Control Vocabulary - altr: This ontology allows for the description of representations of Internet resources. Representations may conform to prof:Profile instances and may have the format of a particular dct:MediaType. - as: Extended Activity Streams 2.0 Vocabulary - bookmark: [Generator provided] - W3C Bookmark vocabulary - cred: A vocabulary for the Data Model for W3C Verifiable Credentials. - dcat: 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. - dcterms: [Generator provided] - Dublin Core Terms - for describing resources - doap: [Generator provided] - Description of a Project (DOAP) vocabulary - earl: [Generator provided] - Evaluation and Report Language (EARL) - foaf: [Generator provided] - Friend of a friend, v0.99 - http: A namespace for describing HTTP messages (http://www.w3.org/Protocols/rfc2616/rfc2616.html) - httph-inrupt: This vocabulary is a one deemed to contain all HTTP headers. The rdflib.js library uses it as for relationships between an HTTP response and the content (value) of the HTTP header in that response. The ontology is deemed to contain one property for every HTTP header, standard or not. The property in this ontology has a localname which is the header field converted to lower case. - hydra: 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. - ical: [Generator provided] - iCal - a vocabulary for description of events and calendars - jsonld: This is a vocabulary document and is used to achieve certain features of the JSON-LD language. - ldp: Vocabulary URIs defined in the Linked Data Platform (LDP) namespace. - odrl: The ODRL Vocabulary and Expression defines a set of concepts and terms (the vocabulary) and encoding mechanism (the expression) for permissions and obligations statements describing digital content usage based on the ODRL Information Model. - olo: [Generator provided] - OLO (Ordered List Ontology) - for describing ordered lists - owl: 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. - posix: A vocabulary for the basic POSIX terms. - prov-o: 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 [email protected] (subscribe [email protected], archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome. - qb: 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). - rdf: [Generator provided] - RDF (Resource Description Framework) - a framework for representing information in the Web - rdfs: [Generator provided] - RDFS (RDF Schema) - a data-modelling vocabulary for RDF data - rlog: Inrupt-created copy of RLOG, needed due to Server 500 errors resolving original uni-leipzig.org! - schema-inrupt: Inrupt extension to Schema.org terms providing multilingual alternative names (i.e. labels) and translations for comments (e.g. for use directly as labels or tool-tips in user interfaces or error messages). This extension very deliberately cherry-picks the individual terms from Schema.org that Inrupt currently deem generally useful for Solid and Solid applications (meaning we can provide a much cleaner, less noisy and smaller bundle size when generating programming language artifacts that provide convenient constants for just these selected terms, rather than including the over 2,500 terms currently defined in Schema.org). - sd: [Generator provided] - SPARQL Service Description vocabulary - sdmx-dimension: [Generator provided] - SDMX Dimension Vocabulary - sec: [Generator provided] - Security vocabulary - shex: [Generator provided] - Shape Expressions (ShEx) - for validating RDF - skos: 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. - skos-xl: An RDF vocabulary extending SKOS and allowing the description and linking of lexical entities. - ui: [Generator provided] - UI Ontology - ui-inrupt: Extension to UI terms providing multilingual alternative names and translations for comments (e.g. for use directly as labels or tool-tips in user interfaces or error messages) - vann: A vocabulary for annotating vocabulary descriptions (VANN). - vcard: Ontology for vCard based on RFC6350 - void: The Vocabulary of Interlinked Datasets (VoID) is an RDF Schema vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. This document provides a formal definition of the new RDF classes and properties introduced for VoID. It is a companion to the main specification document for VoID, <em><a href="http://www.w3.org/TR/void/">Describing Linked Datasets with the VoID Vocabulary</a></em>. - vs: This vocabulary was created in the FOAF project, based on experience with FOAF, Dublin Core and other early RDF vocabularies. Deployment experience shows that changing namespace URIs is expensive and unrewarding, so this vocabulary provides terms to support in-place evolution of structured data vocabularies. By indicating status at the level of terms rather than vocabularies, dictionary-style, fine grained improvements become easier. Different organizations and parties can agree or disagree on the status of a vocabulary term; however the status published alongside the term may deserve special attention. Future work could include patterns for citing announcements and decisions, or using SKOS to decentralise the extension of the basic status levels. - xsd: A vocabulary for describing XML Schema datatypes.

Bundle of vocabularies that includes the following: - inrupt_test: The Inrupt test vocabulary - just commonly used terms across all Inrupt tests.

Bundle of vocabularies that includes the following: - acl: [Generator provided] - Web Access Control Vocabulary - altr: This ontology allows for the description of representations of Internet resources. Representations may conform to prof:Profile instances and may have the format of a particular dct:MediaType. - as: Extended Activity Streams 2.0 Vocabulary - bookmark: [Generator provided] - W3C Bookmark vocabulary - cred: A vocabulary for the Data Model for W3C Verifiable Credentials. - dcat: 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. - dcterms: [Generator provided] - Dublin Core Terms - for describing resources - doap: [Generator provided] - Description of a Project (DOAP) vocabulary - earl: [Generator provided] - Evaluation and Report Language (EARL) - foaf: [Generator provided] - Friend of a friend, v0.99 - http: A namespace for describing HTTP messages (http://www.w3.org/Protocols/rfc2616/rfc2616.html) - httph-inrupt: This vocabulary is a one deemed to contain all HTTP headers. The rdflib.js library uses it as for relationships between an HTTP response and the content (value) of the HTTP header in that response. The ontology is deemed to contain one property for every HTTP header, standard or not. The property in this ontology has a localname which is the header field converted to lower case. - hydra: 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. - ical: [Generator provided] - iCal - a vocabulary for description of events and calendars - jsonld: This is a vocabulary document and is used to achieve certain features of the JSON-LD language. - ldp: Vocabulary URIs defined in the Linked Data Platform (LDP) namespace. - odrl: The ODRL Vocabulary and Expression defines a set of concepts and terms (the vocabulary) and encoding mechanism (the expression) for permissions and obligations statements describing digital content usage based on the ODRL Information Model. - olo: [Generator provided] - OLO (Ordered List Ontology) - for describing ordered lists - owl: 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. - posix: A vocabulary for the basic POSIX terms. - prov-o: 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 [email protected] (subscribe [email protected], archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome. - qb: 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). - rdf: [Generator provided] - RDF (Resource Description Framework) - a framework for representing information in the Web - rdfs: [Generator provided] - RDFS (RDF Schema) - a data-modelling vocabulary for RDF data - rlog: Inrupt-created copy of RLOG, needed due to Server 500 errors resolving original uni-leipzig.org! - schema-inrupt: Inrupt extension to Schema.org terms providing multilingual alternative names (i.e. labels) and translations for comments (e.g. for use directly as labels or tool-tips in user interfaces or error messages). This extension very deliberately cherry-picks the individual terms from Schema.org that Inrupt currently deem generally useful for Solid and Solid applications (meaning we can provide a much cleaner, less noisy and smaller bundle size when generating programming language artifacts that provide convenient constants for just these selected terms, rather than including the over 2,500 terms currently defined in Schema.org). - sd: [Generator provided] - SPARQL Service Description vocabulary - sdmx-dimension: [Generator provided] - SDMX Dimension Vocabulary - sec: [Generator provided] - Security vocabulary - shex: [Generator provided] - Shape Expressions (ShEx) - for validating RDF - skos: 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. - skos-xl: An RDF vocabulary extending SKOS and allowing the description and linking of lexical entities. - ui: [Generator provided] - UI Ontology - ui-inrupt: Extension to UI terms providing multilingual alternative names and translations for comments (e.g. for use directly as labels or tool-tips in user interfaces or error messages) - vann: A vocabulary for annotating vocabulary descriptions (VANN). - vcard: Ontology for vCard based on RFC6350 - void: The Vocabulary of Interlinked Datasets (VoID) is an RDF Schema vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. This document provides a formal definition of the new RDF classes and properties introduced for VoID. It is a companion to the main specification document for VoID, <em><a href="http://www.w3.org/TR/void/">Describing Linked Datasets with the VoID Vocabulary</a></em>. - vs: This vocabulary was created in the FOAF project, based on experience with FOAF, Dublin Core and other early RDF vocabularies. Deployment experience shows that changing namespace URIs is expensive and unrewarding, so this vocabulary provides terms to support in-place evolution of structured data vocabularies. By indicating status at the level of terms rather than vocabularies, dictionary-style, fine grained improvements become easier. Different organizations and parties can agree or disagree on the status of a vocabulary term; however the status published alongside the term may deserve special attention. Future work could include patterns for citing announcements and decisions, or using SKOS to decentralise the extension of the basic status levels. - xsd: A vocabulary for describing XML Schema datatypes.

Bundle of vocabularies that includes the following: - acl: [Generator provided] - Web Access Control Vocabulary - acp: A vocabulary to structure policy-based access controls for the Solid ecosystem. - oidc: The OpenID Connect vocabulary used by the Solid-OIDC authentication specification. - solid: The Solid Terms vocabulary defines terms referenced in Solid specifications. - solid_meta_acl: The Solid vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by the Solid ACL system. - solid_meta_client: The Solid vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by Solid clients. - solid_meta_server_creational: The Solid vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server creation time. - solid_meta_server_runtime: The Solid vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) used by Solid servers at server creation time. - solid_sd: The Solid Service Description vocabulary describes the services provided by a Solid Server. - solid_service_core: The Solid vocabulary providing terms (e.g., classes, properties and text strings (e.g. informative labels or error messages) commonly used across Solid services. - ws: This extension adds predicates making explicit some implicit knowledge in the Workspace ontology.