npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

tin-can-json-schema

v2.0.0

Published

JSON Schema files for structures in the Experience API

Downloads

179

Readme

Tin Can Schema

The folder(s) here contain JSON schema for Tin Can API objects. They are used to validate objects against the Tin Can API specification.

The schema are designed to be language-independent; the only requirements are

  1. That the validator must support draft-4 JSON schema, and

  2. That the validator has some way of registering Regular Expressions to support the format field. This is not a hard requirement, but without this support, strings will not be verified for their format.

We are testing the schema using Tin Can Validator.

Structure

Each directory contains a complete set of parts that can be easily assembled into a complete schema file.

A formats sub-directory may be present. This contains Regular Expression strings in JSON format to validate special strings like UUIDs, version numbers and URIs. These are not part of the schema itself, but must be registered with the schema validator to enable string format checking.

Build the schema (automatic)

You can use Tin Can Validator to do this for you:

git clone https://github.com/RusticiSoftware/TinCanValidator
cd TinCanValidator
./joinSchema.js path/to/TinCanSchema/<version> result.json

Build the schema (manual)

If you don't want to use that, follow these instructions:

// 1. Make a skeleton:
result = {
    "$schema": "http://json-schema.org/draft-04/schema#",
    "type": "object",
    "additionalProperties": false,
    "properties": {}
}

// 2. For each JSON file:
files = [ "account.json", "..." ]
for (var i=0; i<files.length; i++) {
    var fname = files[i];

    // a. Parse it to an object and verify that it is valid JSON
    try {
        stringData = readFile(fname);
        data = JSON.parse(stringData);
    } catch (err) {
        // handle the error
    }

    // b. Check that the file name matches the id:
    if ("#" + fname.split('.')[0] !== data["id"]) {
        // handle the error
    }

    // c. Verify that the object is a valid schema:
    if (!YourValidator.validateSchema(data)) {
        // handle the error
    }

    // d. Remove the "$schema" field from the data, if present:
    if (data["$schema"]) delete data["$schema"];

    // e. Add the data to the "properties" field of the skeleton:
    id = data["id"].slice(1);  // slice off the '#' prefix
    result["properties"][id] = data;
}

// 3. Register the schema with your validator:
YourValidator.addSchema("tcapi:<version>", result);

// 4. Now to register the formats. Load and validate formats/formats.json:
try {
    stringData = readFile("formats/formats.json");
    data = JSON.parse(stringData);
} catch (err) {
    // handle the error
}

// 5. For each item in the data, make the Regex and register it with your validator:
for (item in data.keys()) {
    rgx = new RegExp(data[item]);
    YourValidator.addFormat(item, rgx);
}

// 6. Now you can validate stuff!
function validateAs(obj, id) {
    schema = { "$ref": "tcapi:<version>#" + id };
    YourValidator.validate(obj, schema);
}