node-w3capi — A JavaScript client for the W3C API

This library provides a client for the W3C API, which exposes information about things such as specifications, groups, users, etc. It follows a simple pattern in which one builds up a query, and then causes the data to be fetched.

Usage

Server-side

The usual:

npm install node-w3capi

and then:

var w3capi = require('node-w3capi');

Client-side

Grab the AMD module (lib/w3capi.js) and use it, eg via RequireJS:

requirejs(['w3capi'], function(w3capi) {
});

API

This documentation does not describe the fields that the various objects have; refer to the W3C API's documentation for that.

Everything always starts in the same way:

This gives you a client instance that's immediately ready to work. You then chain some methods to specify what you want to get, and fetch with a callback. For example:

var handler = function (err, data) {
    if (err) return console.error("[ERROR]", err);
    console.log(data);
};

// just list all the groups
w3capi.groups()
   .fetch(handler);

// get the editors for a specific version of a specification
w3capi.specification("SVG11")
   .version("20030114")
   .editors
   .fetch(handler);

If you are familiar with the W3C API you know that it supports paging. This library hides that fact and when it sees a paged list of results it always fetches the whole set. Typically that is a very reasonable number of items.

fetch([options], cb)

All queries end with a call to fetch(). You can pass { embed: true } as an option if you with for the returned value to embed some of the content from the API (this matches ?embed=true). At this point that is the only option. You can do without the options altogether.

The cb receives the typical err and data parameters.

If no cb parameter is provided, the fetch() method instead returns a promise that will resolve with the expected data.

Specifications

Usage summary:

w3capi.specifications().fetch()
w3capi.specification("SVG").fetch()
w3capi.specification("SVG").versions().fetch()
w3capi.specification("SVG").version("19991203").fetch()
w3capi.specification("SVG").version("19991203").deliverers().fetch()
w3capi.specification("SVG").version("19991203").editors().fetch()
w3capi.specification("SVG").version("19991203").successors().fetch()
w3capi.specification("SVG").version("19991203").predecessors().fetch()
w3capi.specification("SVG11").latest().fetch()
w3capi.specification("SVG").superseded().fetch()
w3capi.specification("SVG11").supersedes().fetch()

You can list all specifications, or get a single one using its shortname. For a given specification, you can list its versions and for a given version its editors and deliverers (the groups who shipped it), as well as which versions were the previous or next. You can know which specification supersedes or was superseded by which other. You can use latest() to get the latest version without having to list them.

Groups and charters

Usage summary:

w3capi.groups().fetch()
w3capi.group(54381).fetch()
w3capi.group(54381).chairs().fetch()
w3capi.group(54381).services().fetch()
w3capi.group(54381).specifications().fetch()
w3capi.group(54381).teamcontacts().fetch()
w3capi.group(54381).users().fetch()
w3capi.group(54381).charters().fetch()
w3capi.group(46884).charter(89).fetch()
w3capi.group(46884).participations().fetch()

You can list all groups or get a specific one by its ID (this is the same ID used in IPP, if you're familiar with that — also the same used in ReSpec for the group). There are several sublists that can be obtained, that are hopefully self-explanatory. The charters can be listed, and a specific charter can be fetched given its ID (an opaque number).

Users

Usage summary:

w3capi.user("ivpki36ou94oo08osswccs80gcwogwk").fetch()
w3capi.user({type: "github", id: "1479073"}).fetch()
w3capi.user("ivpki36ou94oo08osswccs80gcwogwk").affiliations().fetch()
w3capi.user("ivpki36ou94oo08osswccs80gcwogwk").groups().fetch()
w3capi.user("ivpki36ou94oo08osswccs80gcwogwk").participations().fetch()
w3capi.user("ivpki36ou94oo08osswccs80gcwogwk").specifications().fetch()

Users cannot be listed, and the ID used to fetch them is an opaque identifier (not the ID used internally in the system so as to make it harder to slurp them all in). Alternatively, users can be fetched by their known 3rd-party account id (assuming they have been connected from the user profile). Various sublists can be obtained.

Functions

Usage summary:

w3capi.functions().fetch()
w3capi.function(109).fetch()
w3capi.function(109).services().fetch()
w3capi.function(109).users().fetch()

Functions are an organisational structure internal to the W3C, of little interest to the outside world.

Services

Usage summary:

w3capi.services(2).fetch()
w3capi.services(2).groups().fetch()

Services model tools that groups (or functions) can use, such as IRC, a bug tracker, a mailing list, etc. At this point in time, the services database isn't well-maintained but it could become more useful in future.

Affiliations

Usage summary:

w3capi.affiliations().fetch()
w3capi.affiliation(1234).fetch()
w3capi.affiliation(1234).participants().fetch()
w3capi.affiliation(1234).participations().fetch()

Participations

Usage summary:

w3capi.participation(555).fetch()
w3capi.participation(555).participants().fetch()