ReSpec is a JS library that makes it easier to write technical specifications, or documents that tend to be technical in nature in general. It was originally designed for the purpose of writing W3C specifications, but has since grown to be able to support other outputs as well.
ReSpec is not endorsed by W3C and nobody should expect the W3C Webmaster to provide advice on problems encountered with ReSpec, or on why it may be failing to produce pubrules-compliant content.
Want to change a bibliographical reference?
Bibliographical references have been moved out of ReSpec. You want to use this: http://www.specref.org/
Want to see complete documentation?
How to contribute?
It is common for people to contribute to RS, notably to make changes to the biblio references. You certainly are welcome to submit whatever change you wish to (though if it's a complex feature please try to coordinate with others first to avoid working long on something that will then be rejected).
If you're familiar with GitHub then contributing is simple: just fork and make pull requests. Please
just be careful to note that the primary branch is
gh-pages and not
master (this ensures that
the result gets published on the Web). More importantly, please note that the development branch
develop. If you are making patches and pull requests, please base them off this branch.
If you're not familiar with GitHub, you need to follow the following steps:
- Get a GitHub account. This is done quickly, and the GH people will not bother you at all. Plus, it's pretty much a requirement for the majority of OSS communities these days.
- If all you want to make is a small, simple change, you can use the Web interface. Navigate to the file that you want to change, click “Edit this file” in the toolbar, then save your changes — they will get sent to the project for approval (which ought to be quick).
- If you wish to make more complex changes, you will need to fork the project (click “Fork”), clone the resulting repository, make the changes there, and push it back. Then click the “Pull Request” button. This allows you to request that the project integrate your changes. Those should normally get processed relatively fast (depending on how complex they are).
Running the test suite
There are two options to run these tests locally: in a browser or using PhantomJS.
Running the test suite in a browser
Tests need to be served from the root of the repository to function properly. Any server will do,
but here's an example using Python's
$ cd /path/to/repo/ $ python -m SimpleHTTPServer Serving HTTP on 0.0.0.0 port 8000 ...
http://localhost:8000/tests/SpecRunner.html with any recent browser will launch the
Running the test suite in PhantomJS
PhantomJS is a headless, WebKit-based browser. It allows running the tests directly from the command line.
Once these dependencies are installed, running the test suite should be as simple as:
$ npm test
That command is an alias for
$ node ./tests/headless.js
If you want to run only a subset of the tests, you can filter which jasmine specs are loaded by specifying additional parameters to that command. For instance,
$ node ./tests/headless.js contiguous
will run only tests whose spec filenames contains "contiguous". You can make a union of these filters by adding more parameters.
Whenever you run the test suite a new build is made for you. You can run
obtain the same result.
Normally, only the maintainers make releases. But in the eventuality that they aren't available, others can follow this process:
- Make sure you are up to date and on the develop branch (git up; git checkout develop)
- Bump the version in
- Run the build script (node tools/build-w3c-common.js). This should respond "OK!" (if not, fix the issue).
- Add the new build (git add builds/respec-w3c-common-3.x.y.js).
- Commit your changes (git commit -am v3.x.y)
- Merge to gh-pages (git checkout gh-pages; git merge develop)
- Tag the release (git tag v3.x.y) and be sure that git is pushing tags.
- Push everything back to the server (make sure you are pushing at least the
The simplest way of doing this, is to just run
tools/release.js. This will prompt you a few times
with the above process. Note that you will need gpg and a key with which to sign the tag.
That should be all. Normally, within a few minutes the W3C server will have picked up, gzipped, and published the latest and greatest version.