- Handle unset
rdfDirection
the same asnull
.
- Emit
toRdf
warning if@direction
is used andrdfDirection
is not set.
- Add safe mode support for
@direction
. Using@direction
withoutrdfDirection
set will cause a safe mode failure.
- Fix handling of graph property with empty array.
- Fix safe mode for
@graph
use cases.- Check all elements of graph property with array.
- Fix test
pr41
of protected redefinition of equivalent id terms. - Fix relative IRI parsing.
- Update for latest rdf-canon changes: test suite location, README, links,
and identifiers.
- Skip test with 'U' escapes. Will enable when rdf-canonize dependency is updated.
- Test on Node.js 20.x.
- Align test and benchmark code with rdf-canonize.
- NOTE: This changes various testing and benchmark runner features and options.
- Update env var usage.
- Use more common code between Node.js and karma tests.
- Conditionally load test suites.
- Fix various minor bugs.
- Add multiple jobs benchmarking support.
- Update benchmark compare script.
- Improve safe mode for
@graph
use cases. - Fix
@json
frame test 0069.
- Don't fail in safe mode for a value object with
"@type": "@json"
.
relative property reference
event renamed torelative predicate reference
.relative type reference
event renamed torelative object reference
.
- BREAKING: By default, set safe mode to
true
andbase
tonull
incanonize
. Applications that were previously canonizing data may see new errors if their data did not fully define terms or used relative URLs that would be dropped when converting to canonized RDF. Now these situations are caught viasafe
mode by default, informing the developer that they need to fix their data.
- compact t0111 test: "Keyword-like relative IRIs"
- Change EARL Assertor to Digital Bazaar, Inc.
- Update eslint dependencies.
- Support benchmarks in Karma tests.
- Support test environment in EARL output.
- Support benchmark output in EARL output.
- Benchmark comparison tool.
- Add "safe mode" to all APIs. Enable by adding
{safe: true}
to API options. This mode causes processing to fail when data constructs are encountered that result in lossy behavior or other data warnings. This is intended to be the common way that digital signing and similar applications use this library.
- Experimental non-standard
protectedMode
option. - BREAKING: Various console warnings were removed. The newly added "safe mode" can stop processing where these warnings occurred.
- BREAKING: Remove
compactionMap
andexpansionMap
. Their known use cases are addressed with "safe mode" and future planned features.
- BREAKING: Drop testing and support for Node.js 12.x. The majority of the
code will still run on Node.js 12.x. However, the
@digitalbazaar/http-client@3
update uses a newerky-universal
which uses a top-levelawait
that is unsupported in older Node.js versions. That causes the includednode
documentLoader
to not function and tests to fail. If you wish to still use earlier Node.js versions, you may still be able to do so with your own customdocumentLoader
. - BREAKING:
npm
prepublish
script changed toprepack
. Thedist/
contents will not be generated by default for development installs. Runnpm run build
if needed. This was done to avoid extra work only needed for packing and publication, and for temporarywebpack
version issues. A new CIbuild
test has been added to check builds pass. Theprepack
script could beprepare
instead if use cases exist where that is needed. File an issue if this is a concern. - Update to
@digitalbazaar/http-client@3
:- Pulls in newer
ky
andky-universal
that should address security alerts and provide other improvements. - Use global
URL
interface to handle relative redirects.
- Pulls in newer
- Update
rdf-canonize
.
- Use
globalThis
to set globals in browser contexts. - Split platform support out into Node.js and browser files.
- Update
@digitalbazaar/http-client
dependency to address engine compatibility issues with newer Node.js versions. - Update dependencies.
- Browser override path style.
- Support is dropped for Node.js versions earlier than v12. This reduces the maintenance burden of being limited by older APIs, development tools, and dependencies. If you need to use an earlier Node.js then either use a previous jsonld.js version or use translation tools and polyfills as needed. (The built-in process to make browser bundles may work for this.) Bug fixes and updates may be back-ported to previous versions from time to time or on request (preferably with a patch).
- Node.js documentLoader now uses
@digitalbazaar/http-client
instead ofrequest
. - BREAKING: Only support Node.js >= 12. Remove related unneeded polyfills,
tests, and
node6
output. Update dependencies that needed newer Node.js versions. - Use Babel
usage
mode rather than listing individual polyfills. May increase bundle size due to more accurate support of intended output targets. - Default Node.js document loader
user-agent
header set to "jsonld.js".
- Distribute a
jsonld.esm.min.js
bundle optimized for the features available in browsers that support ES Modules. - Default Node.js document loader
httpAgent
andhttpsAgent
options. - Add note to README about setting a custom
user-agent
header for the default Node.js document loader.
- Use of deprecated library
request
in Node.js documentLoader. - BREAKING: Parameter
request
has been removed from the Node.js documentLoader. - Node.js documentLoader should no longer be included in browser build.
- State which protected term is being redefined.
- Switch to
core-js@3
.
- BREAKING: RDFa parser moved to
jsonld-rdfa
package, removexmldom
dependency.
- Add
yallist
to packages run through babel for bundles. Fixes use offunction*
.
- Add
lru-cache
to packages run through babel for bundles. Fixes use of arrow functions.
- Update
rdf-canonize
to 2.0.1. - NOTE: The
rdf-canonize
update changes browser support and removes forge in favor of the WebCryptocrypto.subtle
API. A WebCrypto polyfill may be required if a jsonld.js API is used that callsrdf-canonize
. The polyfill is needed if older browsers are targeted or when not using a secure context on some modern browsers. Due to other concerns and the expected minimal impact of this change, it is happening in a minor release. Please provide feedback if this decision causes problems. - Node.js 6 is no longer tested due to development tool dependency updates and to avoid adding additional testing complexity. Node.js 6 will otherwise still be supported until the next major release. Please report any issues found.
- Empty-property scoped context should not effect the outer context. Note that in situations where this fix is used there is now an extra clone of the active context which could potentially cause performance issues.
- Fix XHR document loader Link header processing.
- Support recusrive scoped contexts.
- Various EARL report updates.
- Fixed
prependBase
to start path with a '/' for a zero length path if there is an authority in base.
- Better support for using a processed context for
null
and caching@import
. - Don't set
@base
in initial context and don't resolve a relative IRI when setting@base
in a context, so that the document location can be kept separate from the context itself. - Use
package.json
version
field for EARL reports.
- Exclude
@type
from added values in Merge Node Maps step 2.2.1.
- This release adds support for a majority of JSON-LD 1.1. Significant thanks goes to Gregg Kellogg!
- BREAKING: A notable change is that the framing
omitGraph
default changed to match the JSON-LD 1.1 Framing spec. This is likely to cause issues in most current uses offrame()
. Result handling similar toframed['@graph'][0]
will have to be changed. Check your code. - The spec calls for various situations to issue warnings. This is currently
done with
console.warn
. This will be replaced by a new event notification API in an upcoming release.
- More support for
"@type": "@none"
. - JSON literal value handling issues (
null
and[]
). - Always pass
typeScopedContext
to_expandObject
. - Allow a keyword to exist when expanding in
_expandObject
when the key is@included
or@type
. - Improve
isDouble
to look for big integers. - URI
removeDotSegments
only ensures preceding '/' if was already absolute. - Do minimal checking to see if IRIs are valid by making sure they contain no whitespace.
- Terms of the form of an IRI must map to the same IRI.
- Terms of the form of a relative IRI may not be used as prefixes.
- Match spec error code "invalid context entry" vs "invalid context member".
- Keywords may not be used as prefixes.
- Handle term definition on
@type
with empty map. - Handling of
@
values for@reverse
. - Changes in object embedding.
- Better support for graph framing.
- Better frame validation.
- Wildcard matching on
@id
and otherrequireAll
semantics. - Default frame for lists.
- Check unused scoped contexts for validity.
- Keep term definitions mapping to null so they may be protected.
- NOTE:
LINK_HEADER_REL
inlib/constants.js
has been deprecated and renamed toLINK_HEADER_CONTEXT
. It remains for now but will be removed in a future release. - Changed framing defaults
embed
to "@once" and warn on "@first" or "@last".pruneBlankNodeIdentifiers
based on processingMode.omitGraph
based on processingMode.
- Replaced
removePreserve
withcleanupPreserve
andcleanupNulls
. - Remove unused framing
graphStack
code that was removed from the spec.
- Support for
"@import"
. - Added support for
@included
blocks - Skip things that have the form of a keyword, with warning.
- Support for expansion and compaction of values container
"@direction"
. - Support for RDF transformation of
@direction
whenrdfDirection
is 'i18n-datatype'. - Top level
@graph
omitted ifomitGraph
istrue
. - Check for invalid values of
@embed
. - Support default values for
@type
when framing.
- More support for
"@type": "@none"
. - JSON literal value handling issues (
null
and[]
). - Fix resolving context
null
values.
isKeyword()
optimization for non-keyword fast path.
- JSON literal value handling issues.
- An important BREAKING change in this release is the removal of callback
support in favor of Promises and async/await. This release does not
include a backwards compatible layer. If you need callback support, please
use the 1.x releases, the Node.js
callbackify
feature, or another similar utility library. Suggestions on how best to provide a backwards compatibility layer are welcome.
- Expanding the value of a graph container which is already a graph object generates a recursive graph object.
- Compacting multiple nodes in a graph container places them in
@included
. - Indexing on
@type
requires@type
to be either@id
or@vocab
, and defaults to@id
. - Expanding/compacting type scoped contexts uses context before applying new versions to look for type scopes.
- Default processing mode changed to json-ld-1.1. Allows a 1.1 context to be used after non-1.1 contexts.
- Indexing on an arbitrary property, not just
@index
. @vocab
can be relative or a Compact IRI in 1.1, resolved against either a previous@vocab
,@base
or document base.- Better checking of absolute IRIs.
- Terms that begin with a ':' are not considered absolute or compact IRIs.
- Don't use terms with
"@prefix": false
or expanded term definitions to construct compact IRIs. @type
may be used as a term definition only if"@container": "@set"
.- Improve support for term propagation.
- Context propagation no longer strictly related to use for property-scoped or term-scoped contexts and can be overridden.
- Refactored internal context resolution. Processed context cache feature added. To be documented later.
- BREAKING: Remove callback API support. This includes removing support for callback-based document loaders and RDF parsers. This is done to facilitate JSON-LD 1.1 document loader features and to remove deprecated code.
- BREAKING: Remove deprecated
loadDocument
API and obsoleteDocumentCache
. - BREAKING: Remove deprecated support for parsing legacy dataset format.
- Run babel on canonicalize. Fixes arrow function compatibility issue.
- Support literal JSON.
- NOTE: The JSON serialization is based on the JSON Canonicalization
Scheme (JCS) drafts. Changes in the JCS algorithm could cause changes in
the
toRdf
output.
- NOTE: The JSON serialization is based on the JSON Canonicalization
Scheme (JCS) drafts. Changes in the JCS algorithm could cause changes in
the
- Support list of lists.
- Allow overriding of protected terms when redefining to the same
definition, modulo the
protected
flag itself. - Fix type-scoped context application:
- Ensure values and subject references are expanded and compacted using type-scoped contexts, if available.
- Ensure
@type
values are evaluated against the previous context, not the type-scoped context.
- Ensure
@type
-scoped terms are limited to their@type
-scoped object.
- Testing: Use explicit id and description skipping regexes.
- Usage of JavaScript Object property names in data.
- NOTE: A class of bugs was causing term names such as
toString
,valueOf
, and others to be dropped or produce bogus output. The fix could cause output triples to differ from previous versions if those special names were used. - Specifically, the problem was using
x in obj
instead ofobj.hasOwnProperty(x)
or aMap
. - Fixed usage in contexts for expand and compact.
- Attempted fixes in other parts of the code with similar
x in obj
usage. Finding actual realistic failing test cases proved difficult.
- NOTE: A class of bugs was causing term names such as
- Testing: Improve skip logging.
- Testing:
skip
andonly
flags in manifests. - Testing:
VERBOSE_SKIP=true
env var to debug skipping. - Support
@protected
. - Support experimental non-standard
protectedMode
option.
- Handle
<subject> <rdf:first> <rdf:nil>
triple.
- Improve handling of canonize test cases.
- Update rdf-canonize dependency to address N-Quads parsing bug.
- Switch to eslint.
- Optimize ensuring value is an array.
- Update canonize docs.
- rdf-canonize updated:
- BREAKING: A fix was applied that makes the canonical output format
properly match the N-Triples canoncial format. This fixes the format to no
longer escape tabs in literals. This may cause canonical output from
jsonld.normalize()
/jsonld.canonize()
to differ from previous versions depending on your literal data. If a backwards compatibility mode is needed please use 1.4.x and file an issue. - BREAKING: rdf-canonize-native was removed as an indirect optional
dependency and the JavaScript implemenation is now the default. The former
usePureJavaScript
flag was removed and a newuseNative
flag was added to force use of the native bindings. Higher level applications must explicitly installrdf-canonize-native
to use this mode. Note that in many cases the JavaScript implemenation will be faster. Apps should be benchmarked before using the specialized native mode. - NOTE: The Travis-CI C++11 compiler update fixes are no longer needed when using jsonld.js! rdf-canonize-native was updated to not use C++11 features and is also no longer a direct or indirect dependency of jsonld.js.
- BREAKING: A fix was applied that makes the canonical output format
properly match the N-Triples canoncial format. This fixes the format to no
longer escape tabs in literals. This may cause canonical output from
rdfn:Urgna2012EvalTest
andrdfn:Urdna2015EvalTest
tests should compare with expected output.
- PhantomJS is deprecated, now using headless Chrome with Karma.
- NOTE: Using headless Chrome vs PhantomJS may cause newer JS features to slip into releases without proper support for older runtimes and browsers. Please report such issues and they will be addressed.
- Update webpack and babel.
- Use CommonJS style in main file.
- NOTE: This change might cause problems if code somehow was still
using the long deprecated
jsonldjs
global. Any dependants on this feature should update to use bundler tools such as webpack or usejsonld
in the distributed bundle.
- NOTE: This change might cause problems if code somehow was still
using the long deprecated
- Use rdf-canonize to compare n-quads test results.
- Maintain multiple graphs.
- Sort
@type
when looking for scoped contexts.
- Use JSON-LD WG tests.
- Categorize and skip failing tests.
- Fix source map generation.
- The updated rdf-canonize extracted out native support into rdf-canonize-native and now has an optional dependency on this new module. If you have build tools available it will still build and use native support otherwise it will fallback to less performant JS code.
- If you wish to require the native
rdf-canonize
bindings, add a dependency in your code tordf-canonize-native
to insure it is installed. - Some systems such as Travis CI currently only have
ancient compilers installed by default. Users of
rdf-canonize
, and hencejsonld.js
, previously required special setup so therdf-canonize
native bindings would be installable. If CI testing is not performance critical you can now simplify your CI config, let those bindings fail to install, and use the JS fallback code.
- Update
rdf-canonize
dependency to 0.3.
- Initial support for benchmarking.
- Basic callback interface tests.
- Add README note about running json-ld.org test suite.
- Callback version of every test.
- Callback interface tests added to catch callback API errors.
- Avoids duplication of running every test for promises and callbacks.
- Simplifies testing code and makes async/await conversion easier.
- Add
skipExpansion
flag totoRdf
andcanonize
.
- Fix
_findContextUrls
refactoring bug from 1.0.3.
- Improve performance of active context cache and find context urls:
- Use Map/Set.
- Cache initial contexts based on options.
- Reduce lookups.
- Update webpack/karma core-js usage:
- Add Map, Set, and Array.from support.
- Handle compactArrays option in
@graph
compaction. - Many eslint fixes.
- Add missing await to createNodeMap() and merge().
- Don't always use arrays for
@graph
. Fixes 1.0 compatibility issue.
- 1.0.0!
- Semantic Versioning is now past the "initial development" 0.x.y stage (after 7+ years!).
- Conformance:
- JSON-LD 1.0 + JSON-LD 1.0 errata
- JSON-LD 1.1 drafts
- Thanks to the JSON-LD and related communities and the many many people over the years who contributed ideas, code, bug reports, and support!
- Expansion and Compaction using scoped contexts on property and
@type
terms. - Expansion and Compaction of nested properties.
- Index graph containers using
@id
and@index
, with@set
variations. - Index node objects using
@id
and@type
, with@set
variations. - Framing default and named graphs in addition to merged graph.
- Value patterns when framing, allowing a subset of values to appear in the output.
- ES2018 features are being used. Update version check to use generated Node.js 6 code when using Node.js earlier than 8.6.0.
- Typo handling legacy N-Quads dataset format.
- Include String startsWith() compatibility code.
- Use the W3C standard MIME type for N-Quads of "application/n-quads". Accept "application/nquads" for compatibility.
- Fix fromRdf with input triple having a nil subject.
- BREAKING: Release 0.5.x as latest branch. See the many many changes below since 0.4.x including many potential breaking changes.
- BREAKING: Remove
jsonld.version
API andpkginfo
dependency. This feature added complexity and browser issues and the use case is likely handled by semantic versioning and using a proper dependency.
- Do not use native types to create IRIs in value expansion.
- Improved error detection for
@container
variations. - Handle empty and relative
@base
. - Remove shortcut from compactIri when IRI is a keyword (fixes compact-0073).
- Set processingMode from options or first encountered context.
- Use array representation of
@container
in processing. - BREAKING: Check for keys in term definition outside that expected:
@container
,@id
,@language
,@reverse
, and@type
. This also sets up for additional keywords in 1.1.
- BREAKING: Use RDF JS (rdf.js.org) interfaces for internal representation of dataset and quads. This should only break code that was using undocumented internal data structures, backwards-compat code exists to handle external RDF parsers.
- Update
rdf-canonize
to dependency with native support.
- Allow empty lists to be compacted to any
@list
container term. Fixes compact-0074 test.
- Remote context retrieval bug.
- BREAKING: Remove
promisify
API.
- BREAKING: Remove top-layer errors.
- BREAKING: Remove deprecated extensions API, including
jsonld.request
.
- Add
expansionMap
andcompactionMap
options. These functions may be provided that will be called when an unmapped value or property will be dropped during expansion or compaction, respectively. The function map return eitherundefined
to cause the default behavior, some other value to use instead of the default expanded/compacted value, or it may throw an error to stop expansion/compaction.
- BREAKING: Remove deprecated
objectify
andprependBase
APIs. Nowobjectify
can be achieved via the@link
option in framing andprependBase
can be found viaurl.prependBase
. - BREAKING: Remove deprecated
namer
option from all public APIs, useissuer
instead. - BREAKING: Last active context used is no longer returned as an optional
parameter to the
compact
callback. - BREAKING: Do not expose deprecated
DocumentCache
.
- BREAKING: Change default canonicalization algorithm to
URDNA2015
.
- Callbackify bugs.
- Document loaders.
- Request queue.
- Handling of exceptions in callbacks.
- Various toRDF tests.
- Move tests from test/ to tests/.
- Run all test-suite tests with promises and callbacks.
- Use Node.js "global" or webpack polyfill.
- Distribute all js files, for real this time.
- Fix
toRDF()
.
- Distribute all js files.
- Generate all js files for Node.js 6.
- Significant code reorganization and splitting into multiple files.
- BREAKING: Explicit IE8 support. Webpack, babel, and/or polyfills may be of help if support is still needed.
- BREAKING: jQuery document loader. Use the XHR loader.
Object.keys
polyfill. Other tools can provide this.
- Handling of "global".
- Distribute browser files.
- Distribute unminified bundle.
- Add .editorconfig support.
fetch-test-suites
and relatedfetch-*-test-suite
NPM scripts.- Support for
@graph
@container
.
- Bower support. Use NPM, a NPM proxy site, or build your own bundle.
- Makefile. Use NPM script targets.
- Update url parser to remove default ports from URLs.
- Skip spec version 1.1 tests.
- BREAKING: Only support Node.js 6.x and later with ES2015 features.
- Build and use custom Node.js 6.x output so async/await/etc can be used.
- BREAKING: Move
js/jsonld.js
tolib/jsonld.js
. - BREAKING: Switch to CommonJS.
- BREAKING: Fixes to allow RFC3986 tests to pass. Some URI edge cases and certain base URIs with dot segments may cause different URI outputs.
- Switch to Karma for browser testing.
- Switch to webpack to build browser bundles.
- Add explicit feature compatibility libs to browser bundles.
- Use async APIs for test generation.
- Done to allow testing in Node.js and browsers.
- Required major testing changes to make everything async.
- Workarounds added to get async generated mocha tests working.
- Improved support for loading various types of tests.
- Can load local files, test manifests, or plain js files (in Node.js).
- Use ES2015 in tests and babel/webpack to support older platforms.
- Use rdf-canonize library, remove local implementation.
- Fix
promises.compact
API when called with only 2 parameters.
- Add optimization for finding best CURIE matches.
- Add optimization for compacting keywords.
- Add optimizations for _compactIri.
- Revert es6-promise dependency to 2.x to avoid auto-polyfill behavior.
- Testing document loader.
- Add
headers
andrequest
option for node doc loader.
- Include local tests.
- N-Quads comments pattern.
- Local tests.
- Document cache in default node document loader is broken; disable until HTTP caching is implemented.
- N-Quads may contain comments.
- Add inputFormat and algorithm options to normalize.
- Add support for normalization test suite.
- Support URDNA2015 normalization algorithm.
- Add async scheduling of normalization algorithms.
- Ignore null values in language maps.
- Ignore jsonld-request and pkginfo for browserify.
- "request" extension moved to jsonld-request. This was done to simplify
the core JSON-LD processing library. In particular, the extension pulled in
RDFa processing code and related dependencies. The old method of using this
extension of
jsonld.use('request')
is deprecated in favor of using the new module directly. - The
jsonld
tool moved to jsonld-cli. This was also done to simplify the core JSON-LD processing library and because it uses the jsonld-request module.
- See git history for changes.