8000 [meta] Publish a revised Candidate Recommendation · Issue #406 · w3c/presentation-api · GitHub
[go: up one dir, main page]

Skip to content

[meta] Publish a revised Candidate Recommendation #406

@anssiko

Description

@anssiko

[All - please let us know if you have any comments or concerns with this publication plan. Silence is considered consent.]

There has been substantive changes to the Presentation API since the latest Candidate Recommendation 14 July 2016 thanks to extensive implementation feedback and findings from the conformance testing of the API. See also the visual HTML diff between the CR and the latest Editor's Draft. Given that, we should publish a revised Candidate Recommendation.

Per the process for revising a CR, the group needs to address the following requirements to make that happen:

  • must show that the revised specification meets all Working Group requirements, or explain why the requirements have changed or been deferred,
  • must specify the deadline for further comments, which must be at least four weeks after publication, and should be longer for complex documents,
  • must document the changes since the previous Candidate Recommendation,
  • must show that the proposed changes have received wide review, and
  • may identify features in the document as "at risk". These features may be removed before advancement to Proposed Recommendation without a requirement to publish a new Candidate Recommendation.

To tick the boxes, I suggest we:

  • use the deadline of four weeks for further comments,
  • document high-level changes since the first CR in the Status of This Document section, and in addition, link to the GitHub compare (or the HTML diff) for the detailed changes (@mfoltzgoogle could you help compile the high-level list?),
  • regarding the wide review of the changes, @tidoust let us know your recommendation how to handle the wide review of the delta,
  • document "at risk" features in the SoTD section as well -- implementers @mfoltzgoogle @schien et al.: please let us know if there are features in the spec you are considering not to implement.

Finally, after we've ticked the above boxes, @tidoust will help us acquire the approval from the Director to publish a revision, and I expect will help prepare a publication-ready updated CR snapshot:

  • must obtain the Director's approval to publish a revision of a Candidate Recommendation

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0