JSON-LD Preloaded
JSON-LD with preloaded contexts.
Features
This gem uses the preloading capabilities in JSON::LD::Context
to create ruby context definitions for common JSON-LD contexts to dramatically reduce processing time when any preloaded context is used in a JSON-LD document. As a consequence, changes made to these contexts after the gem release will not be loaded.
Contexts are taken from https://github.com/json-ld/json-ld.org/wiki/existing-contexts:
- ActivityStreams 2.0
- AesKeyWrappingKey2019 Crypto Suite
- Age Verification
- Authorization Capabilities (zCap)
- Bitstring Status List v1.0
- Concealed Id Token
- CSVW Namespace Vocabulary Terms
- CultureGraph EntityFacts
- Data Integrity v1.0
- Data Integrity v2.0
- DCC (Decentralized Credentials Consortium) Core Context
- Decentralized Identifiers (DID) Core Spec v1
- Ed25519Signature2018 Suite
- Ed25519Signature2020 Suite
- FOAF
- GeoJSON-LD
- Hydra
- IIIF Image API
- IIIF Presentation API
- LDP
- Linked Open Vocabularies (LOV)
- Multikey v1.0
- Open Badges (OBI)
- prefix.cc
- http://prefix.cc/context (and subsets using URLs of the form http://prefix.cc/foaf,rdf,rdfs.file.jsonld)
- RDF Data Cube
- RDFa Core Initial Context
- Research Object Bundle
- package.json
- Schema.org
- http://schema.org (needs content negotiation)
- Sha256HmacKey2019 Crypto Suite
- Vaccination Certificate Vocabulary v0.1
- vCard Ontology
- http://www.w3.org/2006/vcard/ns (needs content negotiation)
- Veres One DID Method
- Verifiable Credentials Data Model v1
- Verifiable Credentials Data Model v2
- Verifiable Credentials Revocation List 2020
- WebKMS (Key Management System)
- X25519KeyAgreementKey2020 Suite
Dependencies
Change Log
Mailing List
Author
Contributing
- Do your best to adhere to the existing coding conventions and idioms.
- Don't use hard tabs, and don't leave trailing whitespace on any line.
- Do document every method you add using YARD annotations. Read the tutorial or just look at the existing code for examples.
- Don't touch the
json-ld.gemspec
,VERSION
orAUTHORS
files. If you need to change them, do so on your private branch only. - Do feel free to add yourself to the
CREDITS
file and the corresponding list in the theREADME
. Alphabetical order applies. - Do note that in order for us to merge any non-trivial changes (as a rule of thumb, additions larger than about 15 lines of code), we need an explicit public domain dedication on record from you, which you will be asked to agree to on the first commit to a repo within the organization. Note that the agreement applies to all repos in the Ruby RDF organization.
License
This is free and unencumbered public domain software. For more information, see https://unlicense.org/ or the accompanying UNLICENSE file.