Skip to content

Pas transposition process#409

Open
daniel-montalvo wants to merge 17 commits intomainfrom
pas-faq
Open

Pas transposition process#409
daniel-montalvo wants to merge 17 commits intomainfrom
pas-faq

Conversation

@daniel-montalvo
Copy link
Contributor

This generates a new page within the guide to go through the steps involved in the PAS transposition process. This is mostly based on previously existing materials on the public guide as well
as on the Hitchhiker's guide.

plehegar and others added 9 commits March 7, 2026 05:43
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
plehegar and others added 3 commits March 7, 2026 05:46
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Copy link
Member

@tidoust tidoust left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @daniel-montalvo! I think it would be good to move or integrate the Selection Process page in the Guidebook afterwards as it currently still sits in a member-only page, but that can be done later on.


The scope of our application is "**Core Web Technologies**", defined in our proposal as "any stable core Web technologies produced by W3C that are also in scope of ISO/IEC JTC 1". That establishes the baseline of what we may submit. Tutorials, tests, primers, and other Recommendations of similar types would be out of scope.

A [Selection Process](https://www.w3.org/2010/07/potential-pas.html) for handling PAS was developed and reviewed within W3C. W3C's goal is to submit specifications that help avoid market fragmentation, improve deployment, and facilitate government procurement, and at the same time are stable and widely accepted.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The selection process page is member-only. We'll probably want to move the process to a public page. In the meantime, it seems a good idea to clarify that the link is member-only:

Suggested change
A [Selection Process](https://www.w3.org/2010/07/potential-pas.html) for handling PAS was developed and reviewed within W3C. W3C's goal is to submit specifications that help avoid market fragmentation, improve deployment, and facilitate government procurement, and at the same time are stable and widely accepted.
A [Selection Process](https://www.w3.org/2010/07/potential-pas.html) (member-only link) for handling PAS was developed and reviewed within W3C. W3C's goal is to submit specifications that help avoid market fragmentation, improve deployment, and facilitate government procurement, and at the same time are stable and widely accepted.


The complete guide for this process is in the [ISO/JTC1 Standing Document (PDF)](https://jtc1info.org/wp-content/uploads/2022/01/SD-9-Guide-to-the-Transposition-of-PAS-2021.pdf).

The following is a quick overview of what happens and who is in charge, as well as known rough time estimates. This is based on our experience in submitting [Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/WAI/news/2025-10-21/wcag22-iso/).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The following is a quick overview of what happens and who is in charge, as well as known rough time estimates. This is based on our experience in submitting [Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/WAI/news/2025-10-21/wcag22-iso/).
The following is a quick overview of what happens and who is in charge, as well as known rough time estimates. This is based on experience in submitting [Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/WAI/news/2025-10-21/wcag22-iso/).


The following is a quick overview of what happens and who is in charge, as well as known rough time estimates. This is based on our experience in submitting [Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/WAI/news/2025-10-21/wcag22-iso/).

* W3C agrees to submit a specification to ISO.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"W3C" is a vague entity, I suggest to link back to the selection process:

Suggested change
* W3C agrees to submit a specification to ISO.
* W3C agrees to submit a specification to ISO (see the [Selection Process](https://www.w3.org/2010/07/potential-pas.html), member-only link)


* W3C agrees to submit a specification to ISO.

* W3C lets our PAS Mentor (currently Norbert Bensalem) know about our intent to submit the specification. He may ask us to provide rationale for the following:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The links are to team-only exchanges. I suspect that the communication with the PAS Mentor are handled by the Team in any case. As above, it seems good to make that explicit:

Suggested change
* W3C lets our PAS Mentor (currently Norbert Bensalem) know about our intent to submit the specification. He may ask us to provide rationale for the following:
* W3C Staff lets our PAS Mentor (currently Norbert Bensalem) know about our intent to submit the specification. He may ask us to provide rationale for the following (team-only links):


On a practical side, W3C already engages in a number of [liaisons](../../liaisons/) between ISO committees and W3C Working Groups.

It would be desirable automate the conversion process from our HTML format to the PDF ISO wants, to ease the editorial work around manual conversion. We are in conversation about adding more automation to the ISO part, but we've reached no conclusion as to what this would look like nor when this would be available. No newline at end of file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The guidebook being public, "we" does not really mean much in the guidebook. At least, it does not mean "W3C Staff".

Suggested change
It would be desirable automate the conversion process from our HTML format to the PDF ISO wants, to ease the editorial work around manual conversion. We are in conversation about adding more automation to the ISO part, but we've reached no conclusion as to what this would look like nor when this would be available.
It would be desirable to automate the conversion process from our HTML format to the PDF ISO wants, to ease the editorial work around manual conversion. W3C Staff is in conversation about adding more automation to the ISO part, but no conclusion has been reached as to what this would look like nor when this would be available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants