Download the PHP package accredifysg/php-json-ld without Composer

On this page you can find all versions of the php package accredifysg/php-json-ld. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package php-json-ld

PHP-JSON-LD

A PHP implementation of the JSON-LD 1.1 specification.

PHP-JSON-LD implements all six JSON-LD 1.1 processing algorithms — Expansion, Compaction, Flattening, Serialize to RDF (toRdf), RDF to JSON-LD (fromRdf), and Framing — validated against the official W3C test suites (1,287 of 1,302 tests passing, with Compaction and Flattening fully conformant) and cross-checked against reference implementations for identical canonical RDF output. The public API is stable and the project follows Semantic Versioning.

Highlights

Installation

Requires PHP 8.2+. The bundled HttpDocumentLoader needs a PSR-18 HTTP client and PSR-17 request factory (e.g. guzzlehttp/guzzle + guzzlehttp/psr7); alternatively, implement Accredify\JsonLd\Contracts\DocumentLoader yourself and no HTTP client is required.

Usage

To serve known contexts from local files (recommended for verifiable credentials), implement Accredify\JsonLd\Contracts\DocumentLoader. See tests/Interop/Support/FixtureDocumentLoader.php for a compact example.

Framing note: a frame's {} wildcard cannot be represented in PHP's associative-array model (it decodes identically to []), so the framing API treats an empty frame value as match none and accepts the documented Expansion::FRAME_WILDCARD sentinel for a wildcard.

Safe mode

JSON-LD processing is lossy by design: an undefined term, a relative IRI, or a malformed value is silently dropped rather than reported. For documents that feed RDF canonicalization and signing, that is a security hole — W3C VC-DATA-INTEGRITY 1.0 §2.4.3 "Securing Data Losslessly" makes failing closed a normative requirement:

Implementations that use JSON-LD processing, such as RDF Dataset Canonicalization [RDF-CANON], MUST throw an error, which SHOULD be DATA_LOSS_DETECTION_ERROR, when data is dropped by a JSON-LD processor, such as when an undefined term is detected in an input document.

Pass safe: true (mirroring jsonld.js's safe option) and every drop site throws Accredify\JsonLd\Exceptions\DataLossException instead:

The default (safe: false) is byte-identical to previous releases and to the spec-mandated lossy behaviour the W3C suites expect. Canonicalization/signing pipelines should always opt in: an empty-output check catches only the total-drop case, while safe mode also catches partial drops — an undefined credentialSubject claim that would otherwise sign, verify, and remain attacker-editable.

Event codes use jsonld.js's safe-mode catalog (lib/events.js) where an equivalent site exists:

invalid property (undefined / null-mapped / keyword-shaped terms), free-floating scalar, object with only @value, object with only @list, object with only @id, object with only @language, empty object, null @value value, reserved term, reserved @id value, reserved @reverse value, relative @vocab reference (document-level and scoped), relative @id reference, relative @type reference (at expansion and serialization), relative subject reference, relative predicate reference, relative object reference, relative graph reference, blank node predicate (suppressed by produceGeneralizedRdf: true), invalid @language value (malformed BCP47 tags — at expansion, toRdf, and fromRdf, like jsonld.js), rdfDirection not set.

Drop sites specific to this implementation carry their own codes: context load failed (a scoped context needs a DocumentLoader none is wired), invalid scoped term definition, invalid @direction value (a malformed @direction in hand-built expanded input handed directly to the serializer — the public pipeline rejects it at expansion as an unconditional error), invalid @id value (non-string @id relabelled as a blank node), invalid @value serialization (non-scalar @value coerced to ""), invalid @json serialization (NaN/Infinity in a @json literal), invalid map key (PHP decodes numeric-string JSON keys to integers, which jsonld.js would process), and dropped object (residual malformed shapes).

Not flagged, by design: null property/entry values (the spec's removal semantics, not data loss), a scoped '@language': null / '@direction': null reset (this processor's output for it is already correct), @index entries that carry no RDF statement (spec-correct), frame match patterns during frame() (wildcards and @value: null are queries, not data), and spec-mandated duplicate collapsing in the node map.

One deliberate divergence from jsonld.js: a genuine keyword used as a node entry where it is meaningless (@default / @vocab / a frame keyword outside a frame) throws invalid property here, because its value IS dropped from the expanded output — jsonld.js safe mode stays silent on those.

Conformance

The package is tested against the official W3C JSON-LD 1.1 test suite (git submodule at tests/w3c/; harness documented in tests/W3c/README.md).

Algorithm Spec W3C suite Passing Conformance
Expansion §5.5 385 381 4 documented blockers
Compaction §5.6 246 246 100%
Serialize to RDF (toRdf) §7 467 463 4 documented blockers
Flattening §4.6 58 58 100%
RDF to JSON-LD (fromRdf) §4.9 54 50 4 documented blockers
Framing framing §4 92 89 3 documented blockers

Totals: 1,287 / 1,302 passing. The 15 residual non-conformances are negative-test, non-normative, or environment limits, carried as an explicit expected-failure allowlist (tests/W3c/KnownBlockers.php) that gates CI in both directions — a new regression fails the build, and so does a listed blocker that starts passing:

Implementation report

A W3C EARL implementation report is generated for each release and submitted to the JSON-LD 1.1 implementation report. To regenerate it:

Tests marked specVersion: json-ld-1.0 are excluded from the report, matching the consolidated report's JSON-LD 1.1 scope.

Interoperability

The W3C suite alone cannot catch a processor that is consistently wrong: internal sign/verify round-trips recompute the same dataset on both sides, and a divergence only surfaces when another implementation checks the signature. tests/Interop closes that gap with realistic VC 2.0 and Open Badges v3 documents whose RDFC-1.0 canonical N-Quads — the exact bytes an eddsa-rdfc-2022 proof is computed over — are pinned to goldens generated by jsonld.js and compared as datasets on every CI run.

Development notes

tests/Algorithms/Characterization/ holds JSON snapshots of the expander's output over sample verifiable-credential documents. They are not a spec-conformance reference; they pin behaviour so any change to expansion output lands as a reviewable diff, to be paired with matching updates in downstream consumers (e.g. signed-credential fixtures).

License

MIT © Accredify


All versions of php-json-ld with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
psr/http-client Version ^1.0
psr/http-factory Version ^1.0
psr/http-message Version ^1.1 || ^2.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package accredifysg/php-json-ld contains the following files

Loading the files please wait ...