Token creation

The automated publication workflow requires a token associated with the specification you want to publish. Send an email to your team contact or your chair if you need a token.

Team contacts and chairs can use a form to request a token. That form takes 2 parameters:

• specification url: the latest version url of the specification, e.g. http://www.w3.org/TR/<shortname>
• source of the specification: for security reasons, a token is also associated with a document origin. When using Echidna, if the URL of the document/manifest doesn't begin with the source provided, the system will deny the request. For example, if the document is hosted on GitHub, the source should probably be something like https://w3c.github.io/<repo>.

NOTE: the token is meant to be private, and only shared among the Working Group participants.

This token will be necessary later: you will need to pass it along to the Echidna HTTP endpoint every time you request a new WD to be published, as explained here.