Following edits are required:
list_spec.html
has JavaScript list object named aslist_groups
for list of group IDs- Edit
list_spec.html
for title lines (e.g.h1
) - Edit
list_spec.json
following data format
JSON file list_spec.json
is organized as following format:
{
"spec name by github repository like 'immersive-web/webxr'": {
"info": {} // currently nothing inside
"spec": [ // list of levels
{
"level": 1, // number of level
"shortname": "shortname in /TR/",
"tag": { // TAG review history
"YYYY/MM/DD short text": "github issue link"
},
"events":[ //list of events, for transition
{
"target": "name of transition", // like "wg", "fpwd", "cr", etc.
"expected": "YYYY/MM", // expected transition date, like list of HRs for CR
// following two are used for 'Group decision by' part
"cfc": "URL for CfC on transition", // normally mail list archive
"resolution": "URL for resolution of CfC on transition",
// following two are used for 'Published' and 'Publication request' part, and will not be shown if not set
"date": "date of publish",
"transition": "URL of github issue on w3c/transitions repository",
"pre": { // list of pre process items before transition
// this include early stage ones (e.g. HR for CR)
"summary": "URL" // will be shown as link
// see below for list of possible keywords
},
"post": { // list of post process items after transition, like wide review
// same as 'pre'
}
},
{ // continue for other transitions
}
]
},
{ // continue for information of another level
}]
},
"second spec name": {
// same as first
}
}
- summary: github issue of tracker for summary of pre/post processes (e.g. HR, announce)
- Horizontal reviews
- tag (better to be included for pre-CR review), normally in "tag" list
- a11y
- i18n
- privacy
- security
- wbs: WBS for W3C-wide review (assuming only AC review after PR)
- news: post to
w3.org/blog/news
on publication - cfw: Call for Exclusion (patent policy)
TBD for external groups including liaisons