jsonld.js | A JSON-LD Processor and API implementation in JavaScript | JSON Processing library

by digitalbazaar JavaScript Version: v8.1.1 License: Non-SPDX

X-Ray Key Features Code Snippets(2)Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | jsonld.js Summary

jsonld.js is a JavaScript library typically used in Utilities, JSON Processing applications. jsonld.js has no bugs, it has no vulnerabilities and it has medium support. However jsonld.js has a Non-SPDX License. You can download it from GitHub, Maven.

This library is an implementation of the [JSON-LD][] specification in JavaScript. JSON, as specified in [RFC7159][], is a simple language for representing objects on the Web. Linked Data is a way of describing content across different documents or Web sites. Web resources are described using IRIs, and typically are dereferencable entities that may be used to find more information, creating a "Web of Knowledge". [JSON-LD][] is intended to be a simple publishing method for expressing not only Linked Data in JSON, but for adding semantics to existing JSON. JSON-LD is designed as a light-weight syntax that can be used to express Linked Data. It is primarily intended to be a way to express Linked Data in JavaScript and other Web-based programming environments. It is also useful when building interoperable Web Services and when storing Linked Data in JSON-based document storage engines. It is practical and designed to be as simple as possible, utilizing the large number of JSON parsers and existing code that is in use today. It is designed to be able to express key-value pairs, RDF data, [RDFa][] data, [Microformats][] data, and [Microdata][]. That is, it supports every major Web-based structured data model in use today. The syntax does not require many applications to change their JSON, but easily add meaning by adding context in a way that is either in-band or out-of-band. The syntax is designed to not disturb already deployed systems running on JSON, but provide a smooth migration path from JSON to JSON with added semantics. Finally, the format is intended to be fast to parse, fast to generate, stream-based and document-based processing compatible, and require a very small memory footprint in order to operate.

Support

Quality

Security

License

Reuse

Support

jsonld.js has a medium active ecosystem.

It has 1532 star(s) with 205 fork(s). There are 63 watchers for this library.

It had no major release in the last 6 months.

There are 105 open issues and 220 have been closed. On average issues are closed in 356 days. There are 25 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of jsonld.js is v8.1.1

Quality

jsonld.js has 0 bugs and 0 code smells.

Security

jsonld.js has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jsonld.js code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jsonld.js has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

jsonld.js releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed jsonld.js and discovered the below as its top functions. This is intended to give you an instant insight into jsonld.js implemented functionality, and help decide if they suit your requirements.

Compact JSON data from JSON files .

Get all kandi verified functions for this library.

jsonld.js Key Features

No Key Features are available at this moment for jsonld.js.

jsonld.js Examples and Code Snippets

HTTP Security Header Not Detected in opencart

JavaScript

Lines of Code : 598

License : Strong Copyleft (CC BY-SA 4.0)

Copy

# ######################################################################
# # CROSS-ORIGIN                                                       #
# ######################################################################

# -----------------

Add ld+json script tag in client-side React

JavaScript

Lines of Code : 57

License : Strong Copyleft (CC BY-SA 4.0)

Copy

import React from 'react';
import MetaTags from 'react-meta-tags';
import JsonLd from 'path_to_jsonld';


export default class MetaComponent extends React.Component {
  render() {
   return (
    
      
        {this.props.title}

Community Discussions

Trending Discussions on jsonld.js

Json-ld not being converted to RDF as expected

JSON-LD Frame: framed object properties as term only (not as IRI)

Failed to parse some ontologies

QUESTION

Json-ld not being converted to RDF as expected

Asked 2020-Jan-17 at 21:22

I've converting some JSON-ld to RDF however it doesn't seem to produce RDF with the subject as I'd expect.

So, my JSON-ld looks like this:

...

ANSWER

Answered 2020-Jan-17 at 21:22

You need to use @id (or an alias) to define the subject of the node object. You could potentially defined "persondid" as @id in the context.

You defined "hasUpdateTime" to expand to "schema:updateTime", so the expanded RDF should use "http://schema.org/updateType" as the predicate. If you want the value to be a single URI associated with "Full", use type coercion on "hasUpdateType". Something like the following may be closer to what you want.

Source https://stackoverflow.com/questions/59770597

QUESTION

JSON-LD Frame: framed object properties as term only (not as IRI)

Asked 2018-Sep-23 at 12:23

I'm learning how to use JSON-LD frames using Node jsonld.js, and I'm wondering why some properties are labeled as IRI whereas others are labeled as terms, and I can't see no obvious reason for that difference.

Here's the sample.

For example, in that sample, the name property is labeled as expected, whereas in other cases it's labeled as http://www.schema.org/name, same with url and http://www.schema.org/url; and I can't figure out why:

...

ANSWER

Answered 2018-Sep-23 at 01:07

It's necessary that the term match the IRI you use for the property. For example, schema.org defines name as http://schema.org/name. In your example, you have http://www.schema.org/name.

There are also several places where values which should be IRIs (URLs) are treated as text, for this you want to use something like "http://schema.org/image": {"@id": "/static/track_images_200/lr1734_2009720_1372375126.jpg"}

Part of term selection looks to be sure that a value matches the appropriate @type definition within the context. For example, image is set to {"@type": "@id"}, so it will only match things that look like that.

Here's an updated example on the playground.

Source https://stackoverflow.com/questions/52459565

QUESTION

Failed to parse some ontologies

Asked 2018-Sep-03 at 07:06

When parsing a set of ontologies, some of the files give me the following error while others work well (Note that I am using OWL API 5.1.6):

...

ANSWER

Answered 2018-Sep-02 at 22:10

This error is saying that one of the ontologies you're parsing is not valid JSON/LD format.

To fix this, you have to do two things:

Ensure the format that's being used is the one you expect: OWLAPI, if no format is specified, will attempt to use all parsers available until one of them successfully parses the ontology
Fix the input data if the format is correct: in this case, for JSON/LD, the error is on line 3

If the format used is not what should be, you need to specify a format in your code - for that, you'll have to add a snippet of the code you're using to parse your files.

Source https://stackoverflow.com/questions/52140638

Community Discussions, Code Snippets contain sources that include Stack Exchange Network