Update report.json, rec-track-repos.json, hr-repos.json

w3c-validate-repos-bot · w3c-validate-repos-bot · commit 2ea2c75fe74c · 2025-01-09T00:23:46.000Z
diff --git a/report.json b/report.json
@@ -335,6 +335,7 @@
       "w3c/hcls-fhir-rdf",
       "w3c/hcls-natural-product-drug-interaction-fair",
       "w3c/hr-time",
+      "w3c/html-aam",
       "w3c/html-media",
       "w3c/html-transcript",
       "w3c/i18n-glossary",
@@ -848,11 +849,6 @@
         "error": "doesn't match CG contributing",
         "contributing": "# Handshake Protocol Community Group\n\nThis repository is being used for work in the W3C Handshake Protocol Community Group, governed by the [W3C Community License\nAgreement (CLA)](http://www.w3.org/community/about/agreements/cla/). To make substantive contributions,\nyou must join the CG.\n\nIf you are not the sole contributor to a contribution (pull request), please identify all\ncontributors in the pull request comment.\n\nTo add a contributor (other than yourself, that's automatic), mark them one per line as follows:\n\n```\n+@github_username\n```\n\nIf you added a contributor by mistake, you can remove them in a comment with:\n\n```\n-@github_username\n```\n\nIf you are making a pull request on behalf of someone else but you had no part in designing the\nfeature, you can remove yourself with the above syntax.\n"
       },
-      {
-        "repo": "w3c/html-aam",
-        "error": "doesn't match SW or DOC contributing",
-        "contributing": "Contributions to this repository are intended to become part of Recommendation-track documents\ngoverned by the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy/) and\n[Document License](https://www.w3.org/Consortium/Legal/copyright-documents). To contribute, you must\neither participate in the relevant W3C Working Group or make a non-member patent licensing\ncommitment.\n\nIf you are not the sole contributor to a contribution (pull request), please identify all\ncontributors in the pull request's body or in subsequent comments.\n\n To add a contributor (other than yourself, that's automatic), mark them one per line as follows:\n\n ```\n +@github_username\n ```\n\n If you added a contributor by mistake, you can remove them in a comment with:\n\n ```\n -@github_username\n ```\n\n If you are making a pull request on behalf of someone else but you had no part in designing the\n feature, you can remove yourself with the above syntax.\n\n## Tests\nFor normative changes, a corresponding\n[web-platform-tests](https://github.com/web-platform-tests/wpt) PR should be included. Typically,\nboth PRs will be merged at the same time. Note that a test change that contradicts the spec should\nnot be merged before the corresponding spec change. If testing is not practical, please explain why\nand if appropriate [file an issue](https://github.com/web-platform-tests/wpt/issues/new) to follow\nup later. Add the `type:untestable` or `type:missing-coverage` label as appropriate.\n"
-      },
       {
         "repo": "w3c/html-aria",
         "error": "doesn't match SW or DOC contributing",
@@ -2541,6 +2537,7 @@
       "w3c/hcls-fhir-rdf",
       "w3c/hcls-natural-product-drug-interaction-fair",
       "w3c/hlreq",
+      "w3c/html-aam",
       "w3c/html-media",
       "w3c/html-transcript",
       "w3c/i18n-glossary",
@@ -4597,11 +4594,6 @@
         "error": "doesn't match SW or DOC license",
         "license": "All documents in this Repository are licensed by contributors\nunder the \n[W3C Software and Document License](http://www.w3.org/Consortium/Legal/copyright-software).\n\n"
       },
-      {
-        "repo": "w3c/html-aam",
-        "error": "doesn't match SW or DOC license",
-        "license": "All documents in this Repository are licensed by contributors\nunder the\n[W3C Software and Document License](http://www.w3.org/Consortium/Legal/copyright-software).\n"
-      },
       {
         "repo": "w3c/html-aria",
         "error": "doesn't match SW or DOC license",
@@ -6927,6 +6919,10 @@
         "repo": "w3c/hns-core-spec",
         "error": "main branch is not protected"
       },
+      {
+        "repo": "w3c/html-aam",
+        "error": "main branch is not protected"
+      },
       {
         "repo": "w3c/interactive-media-cg",
         "error": "main branch is not protected"
@@ -7857,10 +7853,6 @@
         "repo": "w3c/gyroscope",
         "error": "main branch protection is not admin enforced"
       },
-      {
-        "repo": "w3c/html-aam",
-        "error": "gh-pages branch protection is not admin enforced"
-      },
       {
         "repo": "w3c/html-aria",
         "error": "gh-pages branch protection is not admin enforced"
@@ -9882,7 +9874,7 @@
       }
     ]
   },
-  "timestamp": "2025-01-08T00:23:26.686Z",
+  "timestamp": "2025-01-09T00:23:45.948Z",
   "repos": [
     {
       "id": "MDEwOlJlcG9zaXRvcnk4MTAyMTg2MA==",
@@ -19223,7 +19215,7 @@
       },
       "codeOfConduct": null,
       "readme": {
-        "text": "# FedID CG Federated Credentials Management\n\nThis is the repository for the W3C's FedID CG Federated Credentials Management API.\n\nExplainer: [explainer.md](explainer.md)\n\nWork-in-progress specification: <https://w3c-fedid.github.io/FedCM/>\n\n## Introduction\n\nAs the web has evolved there have been ongoing privacy-oriented changes\n([example](https://blog.chromium.org/2020/01/building-more-private-web-path-towards.html)) and underlying privacy\n[principles](https://github.com/michaelkleber/privacy-model). With those\nchanges some underlying assumptions of the web are changing. One of those\nchanges is the deprecation of third-party cookies. While overall good for the\nweb, third-party cookie deprecation leaves holes in how some existing systems\non the web were designed and deployed.\n\nFederated Credentials Management API aims to fill the specific hole left by\nthe removal of third-party cookies on federated login. Historically this has\nrelied on third-party cookies or navigational redirects in order to function\nas they were the primitives provided by the web.\n\nThe [explainer](explainer.md) and [spec](https://w3c-fedid.github.io/FedCM)\nprovide a potential API and the rational behind how that API was designed.\n\n## Contributing\n\nMuch of the FedCM specification has evolved due to the experimentation detailed\nin the [explorations](explorations/README.md). The explorations documents give a good\noverview of the _why_ of the FedCM API. Please read over the documents to\nunderstand how the current API has evolved.\n\nThere are several ways to contribute to the Federated Credential Management API.\n\n * If you're an interested party and have potential requirements, they can be\n   submitted to the [IDBrowserUseCases](https://github.com/IDBrowserUseCases/docs)\n   repository. There are also discussions ongoing in the\n   [Fed-ID CG](https://www.w3.org/community/fed-id/) about the various use cases.\n\n * If you'd like to try out the current demo of the FedCM API you can follow the\n   [HOWTO](explorations/HOWTO-chrome.md) document.\n\n * If you're an Identity Provider, there are two sides of the implementation that\n   will be needed and any feedback on either side is appreciated.\n\n   1. The [Identity Provider API](https://w3c-fedid.github.io/FedCM/#idp-api) describes\n      the manifest and API needed server side.\n   2. The [Browser API](https://w3c-fedid.github.io/FedCM/#browser-api) describes the JavaScript\n      interface to FedCM which will need to be utilized.\n\n * If you're a Relying Party (i.e. website) and would like to test the changes out\n   we'd appreciate feedback, you'll need to do something similar to the\n   [HOWTO.md](explorations/HOWTO-chrome.md) to setup a fake IDP which can serve the needed\n   JavaScript. (Until an IDP provides first party JavaScript to work with FedCM\n   this integration will be tricker). You can also review the demo provided by the\n   HOWTO and take a look at the\n   [Relying Party API](https://w3c-fedid.github.io/FedCM/#rp) to see what is needed\n   on the RP side.\n\n## Code of Conduct\n\nThis group operates under [W3C's Code of Conduct Policy](http://www.w3.org/Consortium/cepc/).\n"
+        "text": "# FedID CG Federated Credentials Management\n\nThis is the repository for the W3C's FedID CG Federated Credentials Management API.\n\nDeveloper documentation: [Federated Credential Management (FedCM) API](https://developer.mozilla.org/en-US/docs/Web/API/FedCM_API)\n\nWork-in-progress specification: <https://w3c-fedid.github.io/FedCM/>\n\n## Introduction\n\nAs the web has evolved there have been ongoing privacy-oriented changes\n([example](https://blog.chromium.org/2020/01/building-more-private-web-path-towards.html)) and underlying privacy\n[principles](https://github.com/michaelkleber/privacy-model). With those\nchanges some underlying assumptions of the web are changing. One of those\nchanges is the deprecation of third-party cookies. While overall good for the\nweb, third-party cookie deprecation leaves holes in how some existing systems\non the web were designed and deployed.\n\nFederated Credentials Management API aims to fill the specific hole left by\nthe removal of third-party cookies on federated login. Historically this has\nrelied on third-party cookies or navigational redirects in order to function\nas they were the primitives provided by the web.\n\nThe [documentation](https://developer.mozilla.org/en-US/docs/Web/API/FedCM_API)\nand [spec](https://w3c-fedid.github.io/FedCM) provide a potential API and the\nrationale behind that API's design.\n\n## Contributing\n\nMuch of the FedCM specification has evolved due to the experimentation detailed\nin the [explorations](explorations/README.md). The explorations documents give a good\noverview of the _why_ of the FedCM API. Please read over the documents to\nunderstand how the current API has evolved.\n\nThere are several ways to contribute to the Federated Credential Management API.\n\n * If you're an interested party and have potential requirements, they can be\n   submitted to the [IDBrowserUseCases](https://github.com/IDBrowserUseCases/docs)\n   repository. There are also discussions ongoing in the\n   [Fed-ID CG](https://www.w3.org/community/fed-id/) about the various use cases.\n\n * If you'd like to try out the current demo of the FedCM API you can follow the\n   [HOWTO](explorations/HOWTO-chrome.md) document.\n\n * If you're an Identity Provider, there are two sides of the implementation that\n   will be needed and any feedback on either side is appreciated.\n\n   1. The [Identity Provider API](https://w3c-fedid.github.io/FedCM/#idp-api) describes\n      the manifest and API needed server side.\n   2. The [Browser API](https://w3c-fedid.github.io/FedCM/#browser-api) describes the JavaScript\n      interface to FedCM which will need to be utilized.\n\n * If you're a Relying Party (i.e. website) and would like to test the changes out\n   we'd appreciate feedback, you'll need to do something similar to the\n   [HOWTO.md](explorations/HOWTO-chrome.md) to setup a fake IDP which can serve the needed\n   JavaScript. (Until an IDP provides first party JavaScript to work with FedCM\n   this integration will be tricker). You can also review the demo provided by the\n   HOWTO and take a look at the\n   [Relying Party API](https://w3c-fedid.github.io/FedCM/#rp) to see what is needed\n   on the RP side.\n\n## Code of Conduct\n\nThis group operates under [W3C's Code of Conduct Policy](http://www.w3.org/Consortium/cepc/).\n"
       },
       "prpreview": {
         "src_file": "spec/index.bs",
@@ -53667,7 +53659,7 @@
         }
       ],
       "defaultBranch": {
-        "name": "gh-pages"
+        "name": "main"
       },
       "environments": {
         "nodes": [
@@ -53691,26 +53683,14 @@
       "w3cjson": {
         "text": "{\n  \"group\": 83726,\n  \"contacts\": [\n    \"michael-n-cooper\",\n    \"ruoxiran\"\n  ],\n  \"policy\": \"restricted\",\n  \"shortName\": \"html-aam-1.0\",\n  \"repo-type\": \"rec-track\"\n}\n"
       },
-      "prpreviewjson": {
-        "text": "\n{\n    \"src_file\": \"index.html\",\n    \"type\": \"respec\"\n}\n"
-      },
+      "prpreviewjson": null,
       "autoPublish": null,
       "travis": null,
-      "contributing": {
-        "text": "Contributions to this repository are intended to become part of Recommendation-track documents\ngoverned by the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy/) and\n[Document License](https://www.w3.org/Consortium/Legal/copyright-documents). To contribute, you must\neither participate in the relevant W3C Working Group or make a non-member patent licensing\ncommitment.\n\nIf you are not the sole contributor to a contribution (pull request), please identify all\ncontributors in the pull request's body or in subsequent comments.\n\n To add a contributor (other than yourself, that's automatic), mark them one per line as follows:\n\n ```\n +@github_username\n ```\n\n If you added a contributor by mistake, you can remove them in a comment with:\n\n ```\n -@github_username\n ```\n\n If you are making a pull request on behalf of someone else but you had no part in designing the\n feature, you can remove yourself with the above syntax.\n\n## Tests\nFor normative changes, a corresponding\n[web-platform-tests](https://github.com/web-platform-tests/wpt) PR should be included. Typically,\nboth PRs will be merged at the same time. Note that a test change that contradicts the spec should\nnot be merged before the corresponding spec change. If testing is not practical, please explain why\nand if appropriate [file an issue](https://github.com/web-platform-tests/wpt/issues/new) to follow\nup later. Add the `type:untestable` or `type:missing-coverage` label as appropriate.\n"
-      },
-      "license": {
-        "text": "All documents in this Repository are licensed by contributors\nunder the\n[W3C Software and Document License](http://www.w3.org/Consortium/Legal/copyright-software).\n"
-      },
-      "codeOfConduct": {
-        "body": "# Code of Conduct\n\nAll documentation, code and communication under this repository are covered by the [W3C Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/).\n"
-      },
+      "contributing": null,
+      "license": null,
+      "codeOfConduct": null,
       "readme": {
-        "text": "# HTML-AAM\n\n*****\n PLEASE NOTE\n\n The files for this spec are now being updated in the ARIA repository: https://github.com/w3c/aria/tree/main/html-aam\n\n All new updates need to be made in those files.\n\n Please do not make new PRs against this repository. \n*****\n\n\nHTML Accessibility API Mappings (html-aam) developed by the [Accessible Rich Internet Applications Working Group](https://www.w3.org/WAI/ARIA/) (previously the [Web Applications Working Group](https://www.w3.org/2019/webapps/)). It is the basis of the [Editor's Draft version of the specification](https://w3c.github.io/html-aam/).  You can also compare against [the most recent published version](https://www.w3.org/TR/html-aam-1.0/).\n\nThis specification was part of the [ARIA suite](https://www.w3.org/WAI/ARIA/deliverables). General information about editing the specification is in the [main ARIA repository readme](https://github.com/w3c/aria/).\n\n"
-      },
-      "prpreview": {
-        "src_file": "index.html",
-        "type": "respec"
+        "text": "# Specification 'html-aam'\n\nThis is the issue tracking repository for HTML Accessibility API Mappings (html-aam). You can read the [Editor's Draft version of the specification here](https://w3c.github.io/html-aam/).\n\nYou can also compare against [the most recent published version here](https://www.w3.org/TR/html-aam-1.0/).\n\nTo open a PR, please see the [main ARIA repository where the specification lives](https://github.com/w3c/aria/html-aam). This specification is part of the [ARIA suite](https://www.w3.org/WAI/ARIA/deliverables), and uses the same code structure and build tools as other ARIA suites. General information about editing specifications is in the [main ARIA repository readme](https://github.com/w3c/aria/).\n\nThis specification was previously developed by the [Web Applications Working Group](https://www.w3.org/2019/webapps/)\n"
       },
       "w3c": {
         "group": 83726,
@@ -162841,7 +162821,7 @@
         "body": "# Code of Conduct\n\nAll documentation, code, communication and discussion in this repository are covered by the [W3C Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/).\n"
       },
       "readme": {
-        "text": "This repository contains the [Editor's Draft](https://w3ctag.github.io/security-questionnaire/) of the [Self-Review Questionnaire: Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/) document, which spec authors can use to identify and work through possible security and privacy concerns related to their spec.\n\nThe questionnaire is a joint product of the [TAG](https://tag.w3.org/) and [PING](https://www.w3.org/Privacy/IG/).\n\nWhen folks request a [design review](https://github.com/w3ctag/design-reviews) from the TAG, [filling out](questionnaire.markdown) the security and privacy questionnaire helps the TAG to understand potential security and privacy issues and mitigations for the design, and can save us asking redundant questions.\n\nBefore requesting security and\nprivacy review\nfrom the security reviewers and PING, respectively, documents must\ncontain both \"Security Considerations\" and \"Privacy Considerations\"\nsections for their documents, as described in Section 2.15.  While\nyour answers to the questions in this document will inform your\nwriting of those sections, it is not appropriate to merely copy this\nquestionnaire into those sections.\n\n[Further instructions on requesting security and privacy reviews can be found in the Guide.](https://w3c.github.io/documentreview/#how_to_get_horizontal_review)\n\n\n\n"
+        "text": "This repository contains the [Editor's Draft](https://w3ctag.github.io/security-questionnaire/) of the [Self-Review Questionnaire: Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/) document, which spec authors can use to identify and work through possible security and privacy concerns related to their spec.\n\nThe questionnaire is a joint product of three groups: the [TAG](https://tag.w3.org/), [PING](https://www.w3.org/Privacy/IG/), and the [Security Interest Group](https://www.w3.org/groups/ig/security/).\n\nWhen folks request a [design review](https://github.com/w3ctag/design-reviews) from the TAG, [filling out](questionnaire.markdown) the security and privacy questionnaire helps the TAG to understand potential security and privacy issues and mitigations for the design, and can save us asking redundant questions.\n\nBefore requesting security and\nprivacy review\nfrom the Security Interest Group and PING, respectively, documents must\ncontain both \"Security Considerations\" and \"Privacy Considerations\"\nsections for their documents, as described in Section 2.15.  While\nyour answers to the questions in this document will inform your\nwriting of those sections, it is not appropriate to merely copy this\nquestionnaire into those sections.\n\n[Further instructions on requesting security and privacy reviews can be found in the Guide.](https://w3c.github.io/documentreview/#how_to_get_horizontal_review)\n\n\n\n"
       },
       "prpreview": {
         "src_file": "index.bs",
