Group items tagged

JSON-LD (JavaScript Object Notation for Linking Data) is a lightweight Linked Data format that gives your data context. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on the already successful JSON format and provides a way to help JSON data interoperate at Web-scale. If you are already familiar with JSON, writing JSON-LD is very easy. These properties make JSON-LD an ideal Linked Data interchange language for JavaScript environments, Web service, and unstructured databases such as CouchDB and MongoDB.

"JSON-LD is a lightweight Linked Data format. It is easy for humans to read and write. It is based on the already successful JSON format and provides a way to help JSON data interoperate at Web-scale. JSON-LD is an ideal data format for programming environments, REST Web services, and unstructured databases such as CouchDB and MongoDB."

"JSON-LD Schema Generator For SEO"

RDF format transformations http://triplr.org/output/source-uri output-format is one of html, json, ntriples, rdf or turtle.  source-uri is like example.org/foo/bar

Triplify provides a building block for the "semantification" of Web applications. Triplify is a small plugin for Web applications, which reveals the semantic structures encoded in relational databases by making database content available as RDF, JSON or Linked Data.

The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores. The protocol emerged from experiences implementing AtomPub clients and servers in a variety of products over the past several years. OData is being used to expose and access information from a variety of sources including, but not limited to, relational databases, file systems, content management systems and traditional Web sites.

The (semantic) web is one of the most promising application areas for SWI-Prolog. Prolog handles the semantic web RDF model naturally, where RDF provides a stable model for knowledge representation with shared semantics. It turns out that Prolog is also quite capable of providing web-services (HTTP), especially where it comes to dynamic generation of HTML pages and providing data for Javascript web-applications using the JSON serialisation.

This web data platform supports several generations of standards and recommendations:Web 1 and 2: DAV, AJAX, JSONP, CORSRead/Write Linked Data, RDF/XML/JSON content negotiation, SPARQL 1.1, and WebID

Instead of writing a whole new, dedicated HTTP API to your site, publish your data using common JSON object formats, and link your data up, both within your own sites and to other sites. Become part of a global Object Network!

HTML microdata [MICRODATA] is an extension to HTML used to embed machine-readable data into HTML documents. Whereas the microdata specification describes a means of markup, the output format is JSON. This specification describes processing rules that may be used to extract RDF [RDF-CONCEPTS] from an HTML document containing microdata.

Sweet Tools (Sem Web) This Sweet Tools listing is also available as a structured data view via conStruct (pick the Sweet Tools dataset). In addition, you may download the dataset in RDF/XML, semantic wikitext, tab separated values, JSON or generated HTML by hovering over the 'Category' label at upper right and clicking the scissors icon.

A simple but powerful service that delivers RDF-based structured descriptions of Web addressable resources (documents or real world objects) in a variety of formats through Generic HTTP URIs. The underlying technology is Virtuoso's Sponger, which takes an existing Web-accessible resource (webpage, media) and generates an RDF graph of its metadata using existing well-known ontologies as well as site-specific knowledge. URIBurner then re-presents this data as either a new HTML webpage, or directly as RDF in a variety of serializations (RDF/XML, text/n3, turtle, JSON).

The name and tool relies on and/or is inspired by SPARQL, Google visualization API, SPARQLer, Snorql and Spark. All the major chart types offered by the Google Visualization API are supported by Sgvizler. The user inputs a SPARQL query which is sent to a designated SPARQL endpoint. Sgvizler parses the results into the JSON format that Google prefers and displays the chart using the Google Visualization API or a custom-made visualization or formatting function.

This API provides a simple way to access information about people held in the Dbpedia 3.6 dataset. Currently the API supports the following requests: /people - List all people /people/artists - List all artists /people/athletes - List all athletes /people/scientists - List all scientists /people/writers - List all writers The API conforms to the Linked Data API specification so supports multiple output options including simple JSON and XML formats, as well as standard RDF serializations.

"Rules have many uses, coming in a multitude of forms. RuleML is a unifying system of families of languages for Web rules over Web documents and data. RuleML is specified syntactically through schema languages (normatively, in Relax NG), originally developed for XML and transferable to other formats such as JSON. Since Version 1.02, rather than assuming predefined default semantics, RuleML allows partially constrained semantic profiles and fully-specified semantics."

The Structured Data Linter is a tool aiding webmasters and web developers to verify the structured data present in their HTML pages. Search engines use structured data to understand webpages more accurately and to present enhanced search results. The Linter understands the microdata, JSON-LD and RDFa formats according to their latest specifications. Note however that it does not guarranty that all consumers (e.g. search engines) will make use of all the structured data available in your page. The linter does not currently support microformats (contributions welcome).