From f68e54af45d730ffdfbc1f221f9d8cb1bbe8fe40 Mon Sep 17 00:00:00 2001 From: w3c-validate-repos-bot <> Date: Tue, 20 Jun 2023 00:21:52 +0000 Subject: [PATCH] Update report.json, rec-track-repos.json, hr-repos.json --- report.json | 85 ++++------------------------------------------------- 1 file changed, 5 insertions(+), 80 deletions(-) diff --git a/report.json b/report.json index 7fd47831..a8a93e4f 100644 --- a/report.json +++ b/report.json @@ -9056,7 +9056,7 @@ } ] }, - "timestamp": "2023-06-19T00:20:12.434Z", + "timestamp": "2023-06-20T00:21:51.994Z", "repos": [ { "id": "MDEwOlJlcG9zaXRvcnk4MTAyMTg2MA==", @@ -61414,7 +61414,7 @@ "license": null, "codeOfConduct": null, "readme": { - "text": "# Media Working Group\n\nThis repository hosts the [home page of the Media Working Group](https://www.w3.org/media-wg/). The group uses the [issue tracker](https://github.com/w3c/media-wg/issues) to track group-wide discussions and resolutions.\n\n## Specifications\n\nSpecifications published by the Media Working Group are developed in separate GitHub repositories:\n\n* [Autoplay Policy Detection](https://github.com/w3c/autoplay/)\n* [Encrypted Media Extensions (EME)](https://github.com/w3c/encrypted-media/)\n* [Media Capabilities](https://github.com/w3c/media-capabilities/)\n* [Media Playback Quality](https://github.com/w3c/media-playback-quality/)\n* [Media Session](https://github.com/w3c/mediasession/)\n* [Media Source Extensions™ (MSE)](https://github.com/w3c/media-source/)\n* [Picture-in-picture](https://github.com/w3c/picture-in-picture/)\n* [WebCodecs](https://github.com/w3c/webcodecs/)\n" + "text": "# Media Working Group\n\nThis repository hosts the [home page of the Media Working Group](https://www.w3.org/media-wg/). The group uses the [issue tracker](https://github.com/w3c/media-wg/issues) to track group-wide discussions and resolutions.\n\n## Specifications\n\nSpecifications published by the Media Working Group are developed in separate GitHub repositories:\n\n* [Audio Session](https://github.com/w3c/audio-session)\n* [Autoplay Policy Detection](https://github.com/w3c/autoplay/)\n* [Encrypted Media Extensions (EME)](https://github.com/w3c/encrypted-media/)\n * [Encrypted Media Extensions Initialization Data Format Registry](https://github.com/w3c/encrypted-media/tree/main/format-registry/initdata)\n * [Encrypted Media Extensions Stream Format Registry](https://github.com/w3c/encrypted-media/tree/main/format-registry/stream)\n* [Media Capabilities](https://github.com/w3c/media-capabilities/)\n* [Media Playback Quality](https://github.com/w3c/media-playback-quality/)\n* [Media Session](https://github.com/w3c/mediasession/)\n* [Media Source Extensions™ (MSE)](https://github.com/w3c/media-source/)\n * [Media Source Extensions Byte Stream Format Registry](https://github.com/w3c/mse-byte-stream-format-registry)\n * [WebM Byte Stream Format](https://github.com/w3c/mse-byte-stream-format-webm)\n * [ISO BMFF Byte Stream Format](https://github.com/w3c/mse-byte-stream-format-isobmff)\n * [MPEG-2 Transport Streams Byte Stream Format](https://github.com/w3c/mse-byte-stream-format-mp2t)\n * [MPEG Audio Byte Stream Format](https://github.com/w3c/mse-byte-stream-format-mpeg-audio)\n* [Picture-in-picture](https://github.com/w3c/picture-in-picture/)\n* [WebCodecs](https://github.com/w3c/webcodecs/)\n * [WebCodecs Codec Registry](https://github.com/w3c/webcodecs/)\n * [WebCodecs VideoFrame Metadata Registry](https://github.com/w3c/webcodecs/)\n" }, "w3c": { "group": 115198, @@ -106002,7 +106002,7 @@ "license": null, "codeOfConduct": null, "readme": { - "text": "# W3C frontend website\n\nSymfony frontend website for w3.org\n\n## Reporting issues\n\nPlease report any issues to the [w3c-website](https://github.com/w3c/w3c-website/issues) repo.\n\n## Getting started\n\nThis document is a summary of what you need to know when working on this project. Please also read the more [detailed project documentation](docs/README.md)\n\n### In this document\n\n* [Site URLs](#site-urls)\n* [Deployment](#deployment)\n* [Installation](#installation)\n* [Built with](#built-with)\n* [Credits](#credits)\n\n## Site URLs (TBC)\n\n### Production\nLive:\n* https://www.w3.org\n* https://www.w3.org/_build_summary.json (very brief summary of latest deployment)\n\nBeta:\n* https://beta.w3.org\n* https://beta.w3.org/_build_summary.json\n\n### Staging\n* https://www-staging.w3.org\n* https://www-staging.w3.org/_build_summary.json\n\n### Development\n* https://www-dev.w3.org\n* https://www-dev.w3.org/_build_summary.json\n\nAccess to https://www-dev.w3.org is restricted by IP.\n\n### Local\n* http://localhost:8000/ (see [running application locally](#running-application-locally)) \n\n## Deployment (TBC)\n\nThe project uses [Deployer](https://deployer.org/) to perform deployment. For full deployment details/options view [docs/deployment](docs/deployment.md)\n\nPlease note this project uses a local instance of Deployer (installed via Composer), as opposed to a global version of Deployer. This is so we\ncan make use of other Composer packages in deployment tasks reliably (otherwise there can be clashes between global and local version of the same packages).\n\nTo run deployments please use:\n\n````\nvendor/bin/dep deploy \n````\n\nTo deploy a specific branch use\n\n````\nvendor/bin/dep deploy --branch=\n````\n\nE.g.\n\n```\nvendor/bin/dep deploy development --branch=develop\n```\n\n### SSH access\nTo connect to the server directly at the correct path for an environments current release, run the following from the root of the project\n\n````\nvendor/bin/dep ssh \n````\n\n## Installation\n\nThese instructions will get you a copy of the project up and running on your local machine for development and testing purposes.\n\nMore on the [Git workflow for this project](docs/git_workflow.md).\n\n### Requirements\n\n* PHP 7.4\n* [Composer](https://getcomposer.org/)\n* [Symfony CLI](https://symfony.com/download#step-1-install-symfony-cli)\n\n### Clone the repository\n\n`git clone git@github.com:w3c/website-frontend.git`\n\nRun `composer install`\n\n### Configuration\nCreate a local environment file and populate the required variables (see `.env.local.dist`):\n\n```\ncp .env.local.dist .env.local\n```\n\nYou can talk to another developer about what these values should contain.\n\n### Running application locally\n\nYou can run the frontend application locally at http://localhost:8000/ by running the command:\n\n```\nsymfony server:start\n```\n\n## Built with\n\n- [Symfony](https://symfony.com/)\n- [Strata Frontend](https://github.com/strata/frontend)\n- [W3C Design System](https://github.com/w3c/w3c-website-templates-bundle/) (used as a Symfony template bundle)\n" + "text": "# W3C frontend website\n\nSymfony frontend website for w3.org\n\n## Reporting issues\n\nPlease report any issues to the [w3c-website](https://github.com/w3c/w3c-website/issues) repo.\n\n## Getting started\n\nThis document is a summary of what you need to know when working on this project. Please also read the more [detailed project documentation](docs/README.md)\n\n### In this document\n\n* [Site URLs](#site-urls)\n* [Deployment](#deployment)\n* [Installation](#installation)\n* [Built with](#built-with)\n\n## Site URLs\n\n### Production\nLive:\n* https://www.w3.org\n* https://www.w3.org/_build_summary.json (very brief summary of latest deployment)\n\n### Staging\n* https://www-staging.w3.org\n* https://www-staging.w3.org/_build_summary.json\n\n### Development\n* https://www-dev.w3.org\n* https://www-dev.w3.org/_build_summary.json\n\nUsed to test new functionality / changes. Access to development is restricted by IP address.\n\n### Local\n* http://localhost:8000/ (see [running application locally](#running-application-locally)) \n\n## Deployment\n\nThe project uses [Deployer](https://deployer.org/) to perform deployment.\n\nPlease note this project uses a local instance of Deployer (installed via Composer), as opposed to a global version of Deployer.\n\nTo run deployments please use:\n\n````\nvendor/bin/dep deploy \n````\n\nTo deploy a specific branch use\n\n````\nvendor/bin/dep deploy --branch=\n````\n\nE.g.\n\n```\nvendor/bin/dep deploy development --branch=feature/my-branch-name\n```\n\n### SSH access\nTo connect to the server directly at the correct path for an environments current release, run the following from the root of the project\n\n````\nvendor/bin/dep ssh \n````\n\n## Updating HTML templates\n\nThe HTML templates are stored in [w3c-website-templates-bundle](https://github.com/w3c/w3c-website-templates-bundle)\n\nThese can be updated by deploying changes to the [design system](https://github.com/w3c/w3c-website-templates-bundle/blob/main/design-system.md) \nand running `composer update` in this project.\n\nYou can also test changes either by deploying a branch to the staging environment for the design system, or by [testing a development branch on the frontend website](https://github.com/w3c/w3c-website-templates-bundle/blob/main/design-system.md#testing-a-development-branch-on-your-front-end-website). \n\n## Installation\nw\nThese instructions will get you a copy of the project up and running on your local machine for development and testing purposes.\n\nMore on the [Git workflow for this project](docs/git_workflow.md).\n\n### Requirements\n\n* PHP 8.1+\n* [Composer](https://getcomposer.org/)\n* [Symfony CLI](https://symfony.com/download#step-1-install-symfony-cli)\n\n### Clone the repository\n\n`git clone git@github.com:w3c/website-frontend.git`\n\n### Install Composer dependencies\n\n```bash\ncomposer install\n```\n\n***Note:*** If you already have this project installed locally and you're having trouble seeing any changes, make sure you have cleared your Symfony cache using the `bin/console cache:clear` command.\n\n### Configuration\n\nCreate a local env file:\n\n```\ntouch .env.local\n```\n\nAnd set:\n* APP_ENV (dev, staging, prod)\n* APP_URL\n* W3C_API_KEY\n* CRAFTCMS_API_URL\n* CRAFTCMS_API_READ_TOKEN\n* CRAFTCMS_API_PUBLISH_TOKEN \n\nYou can access your W3C API Key from your [W3C account](https://auth.w3.org/login).\n\nYou can find your API Read and Publish tokens by going to the Craft CMS dashboard (see the [Craft repo](https://github.com/w3c/w3c-website-craft)).\n\nYou can check what env files are being loaded in your environment by running `php bin/console debug:dotenv`\n\n### Running application locally\n\nBefore running the below command, please ensure you have the [Symfony CLI installed](https://symfony.com/download#step-1-install-symfony-cli)\n\nOnce you have the Symfony CLI installed (or you have ensured you already have it installed), you can run the frontend application locally at http://localhost:8000/ by running\n\n```\nsymfony server:start\n```\nIn your terminal\n\n***Note:*** A good way to test if something will break if you deploy it to live is to switch your local env’s CraftCMS API URL and Read and Publish tokens to the production CMS\n**(Please be careful about any changes you make in the Production CMS as they will be visible on the live site)**\n\n## Built with\n\n- [Symfony](https://symfony.com/)\n- [Craft CMS API](https://craftcms.com/docs/4.x/graphql.html)\n- [Strata Frontend](https://github.com/strata/frontend)\n- [W3C Design System](https://github.com/w3c/w3c-website-templates-bundle/) (used as a Symfony template bundle)\n" } }, { @@ -106315,7 +106315,7 @@ }, "codeOfConduct": null, "readme": { - "text": "# W3C website template bundle & Design System\n\n## Design System\n\nThis repo contains the design system documentation, frontend assets and example Twig templates. \n\nDocumentation for implementing the W3C website design can be found on the [Design System website](https://design-system.w3.org/).\n\nTo make updates to these see [design system](design-system.md).\n\nPlease report any issues to the [w3c-website](https://github.com/w3c/w3c-website/issues) repo.\n\n## Template bundle\n\nThis repo also contains a Symfony bundle which loads the frontend assets and has a set of Twig templates available \nto build Symfony apps using the W3C website design system.\n\n### How to use the design system templates in Symfony\n\nThe design system contains [example Twig templates](design-system-templates) that cover all design patterns used\non the W3C website. These are simplified templates to help illustrate usage. \n\nTo actually use the design system Twig templates, you need to copy these to the [Symfony bundle templates](templates) \nand customise them for use in your application. At present we're building the \n[W3C frontend application](https://github.com/w3c/w3c-website-frontend) which will power \nw3.org. As we build pages we are copying the design system templates across to the bundle templates \nand modifying them for real-world usage. \n\nLong-term the plan is to be able to use the Symfony bundle templates in a range of different \nSymfony applications - though some refactoring may need to be done to ensure the templates work easily \nacross different applications.\n\n### Installation\n\nYou can install this in your Symfony app via:\n\n```bash\ncomposer require w3c/website-templates-bundle:dev-main\n```\n\nThis requires PHP 7.4+\n\nOn installation, front-end assets (CSS, JavaScript, fonts, etc.) will be copied into the public directory of the application.\nYou will find them in the folder `public/bundles/w3cwebsitetemplates/dist/assets`.\nYou will need to update the assets base URL to point to that folder. This can be done in your application `config/packages/assets.yaml` file for example.\n\nExample syntax (provided you have defined an `%app.app_url%` parameter):\n\n```yaml\nframework:\n assets:\n packages:\n main:\n base_urls: '%app.app_url%/bundles/w3cwebsitetemplates/dist/assets/'\n```\nYou can now use the W3C Twig templates and front-end assets in your application.\n\n### Usage\n\nThe templates available can be found in this bundle's 'templates' folder. You can reference them in your application using the\nhandle `@W3CWebsiteTemplates`. E.g.\n\n```twig\n{% extends '@W3CWebsiteTemplates/base.html.twig' %}\n```\n\n### Overriding the templates\n\nTemplates can be overridden in the `templates/bundles/w3cwebsitetemplates/` directory in your \nSymfony project, using the same name and path as the original templates.\n\n## Reporting issues\n\nPlease report any issues to the [w3c-website](https://github.com/w3c/w3c-website/issues) repo.\n" + "text": "# W3C website template bundle & Design System\n\nThe Symfony website templates for [w3.org](https://github.com/w3c/w3c-website-frontend), this also generates the\nstatic HTML [design system website](https://design-system.w3.org/).\n\n## Design System\n\nThis repo contains the design system documentation, frontend assets and example Twig templates. \n\nDocumentation for implementing the W3C website design can be found on the [Design System website](https://design-system.w3.org/).\n\nTo make updates or to deploy the design system itself see [design system](design-system.md).\n\nPlease report any issues to the [w3c-website](https://github.com/w3c/w3c-website/issues) repo.\n\n## Template bundle\n\nThis repo also contains a Symfony bundle which loads the frontend assets and has a set of Twig templates available \nto build Symfony apps using the W3C website design system.\n\n### How to use the design system templates in Symfony\n\nThe design system contains [example Twig templates](design-system-templates) that cover all design patterns used\non the W3C website. These are simplified templates to help illustrate usage. \n\nTo actually use the design system Twig templates, you need to copy these to the [Symfony bundle templates](templates) \nand customise them for use in your application. At present we're building the \n[W3C frontend application](https://github.com/w3c/w3c-website-frontend) which will power \nw3.org. As we build pages we are copying the design system templates across to the bundle templates \nand modifying them for real-world usage. \n\nLong-term the plan is to be able to use the Symfony bundle templates in a range of different \nSymfony applications - though some refactoring may need to be done to ensure the templates work easily \nacross different applications.\n\n### Installation\n\nYou can install this in your Symfony app via:\n\n```bash\ncomposer require w3c/website-templates-bundle:dev-main\n```\n\nThis requires PHP 7.4+\n\nOn installation, front-end assets (CSS, JavaScript, fonts, etc.) will be copied into the public directory of the application.\nYou will find them in the folder `public/bundles/w3cwebsitetemplates/dist/assets`.\nYou will need to update the assets base URL to point to that folder. This can be done in your application `config/packages/assets.yaml` file for example.\n\nExample syntax (provided you have defined an `%app.app_url%` parameter):\n\n```yaml\nframework:\n assets:\n packages:\n main:\n base_urls: '%app.app_url%/bundles/w3cwebsitetemplates/dist/assets/'\n```\nYou can now use the W3C Twig templates and front-end assets in your application.\n\n### Usage\n\nThe templates available can be found in this bundle's 'templates' folder. You can reference them in your application using the\nhandle `@W3CWebsiteTemplates`. E.g.\n\n```twig\n{% extends '@W3CWebsiteTemplates/base.html.twig' %}\n```\n\n### Overriding the templates\n\nTemplates can be overridden in the `templates/bundles/w3cwebsitetemplates/` directory in your \nSymfony project, using the same name and path as the original templates.\n\n## Reporting issues\n\nPlease report any issues to the [w3c-website](https://github.com/w3c/w3c-website/issues) repo.\n" } }, { @@ -147127,7 +147127,7 @@ "body": "# Code of Ethics and Professional Conduct\n\nWebAssembly operates under the W3C's\n[Code of Ethics and Professional Conduct][]:\n\n> W3C is a growing and global community where participants choose to work\n> together, and in that process experience differences in language, location,\n> nationality, and experience. In such a diverse environment, misunderstandings\n> and disagreements happen, which in most cases can be resolved informally. In\n> rare cases, however, behavior can intimidate, harass, or otherwise disrupt one\n> or more people in the community, which W3C will not tolerate.\n>\n> A Code of Ethics and Professional Conduct is useful to define accepted and\n> acceptable behaviors and to promote high standards of professional\n> practice. It also provides a benchmark for self evaluation and acts as a\n> vehicle for better identity of the organization.\n\nWe want our community group to act according to these guidelines, and\nparticipants to hold each other to these high standards. If you have any questions\nor are worried that the code isn't being followed, please contact the Community\nGroup's chairs at `team-wasm-chairs@w3.org` (note: this list is also\nvisible to W3C staff). For very serious concerns, the W3C has [procedures][]\nallowing you to access its ombuds directly and confidentially.\n\n [Code of Ethics and Professional Conduct]: https://www.w3.org/Consortium/cepc\n [procedures]: https://www.w3.org/Consortium/pwe/#Procedures\n" }, "readme": { - "text": "# [Example WASI proposal]\n\nThis template can be used to start a new proposal, which can then be proposed in the WASI Subgroup meetings.\n\nThe sections below are recommended. However, every proposal is different, and the community can help you flesh out the proposal, so don't block on having something filled in for each one of them.\n\nThank you to the W3C Privacy CG for the [inspiration](https://github.com/privacycg/template)!\n\n# [Title]\n\nA proposed [WebAssembly System Interface](https://github.com/WebAssembly/WASI) API.\n\n### Current Phase\n\n[Fill in the current phase, e.g. Phase 1]\n\n### Champions\n\n- [Champion 1]\n- [Champion 2]\n- [etc.]\n\n### Phase 4 Advancement Criteria\n\nTODO before entering Phase 2.\n\n## Table of Contents [if the explainer is longer than one printed page]\n\n- [Introduction](#introduction)\n- [Goals [or Motivating Use Cases, or Scenarios]](#goals-or-motivating-use-cases-or-scenarios)\n- [Non-goals](#non-goals)\n- [API walk-through](#api-walk-through)\n - [Use case 1](#use-case-1)\n - [Use case 2](#use-case-2)\n- [Detailed design discussion](#detailed-design-discussion)\n - [[Tricky design choice 1]](#tricky-design-choice-1)\n - [[Tricky design choice 2]](#tricky-design-choice-2)\n- [Considered alternatives](#considered-alternatives)\n - [[Alternative 1]](#alternative-1)\n - [[Alternative 2]](#alternative-2)\n- [Stakeholder Interest & Feedback](#stakeholder-interest--feedback)\n- [References & acknowledgements](#references--acknowledgements)\n\n### Introduction\n\n[The \"executive summary\" or \"abstract\". Explain in a few sentences what the goals of the project are, and a brief overview of how the solution works. This should be no more than 1-2 paragraphs.]\n\n### Goals [or Motivating Use Cases, or Scenarios]\n\n[What is the end-user need which this project aims to address?]\n\n### Non-goals\n\n[If there are \"adjacent\" goals which may appear to be in scope but aren't, enumerate them here. This section may be fleshed out as your design progresses and you encounter necessary technical and other trade-offs.]\n\n### API walk-through\n\nThe full API documentation can be found [here](wasi-proposal-template.md).\n\n[Walk through of how someone would use this API.]\n\n#### [Use case 1]\n\n[Provide example code snippets and diagrams explaining how the API would be used to solve the given problem]\n\n#### [Use case 2]\n\n[etc.]\n\n### Detailed design discussion\n\n[This section should mostly refer to the .wit.md file that specifies the API. This section is for any discussion of the choices made in the API which don't make sense to document in the spec file itself.]\n\n#### [Tricky design choice #1]\n\n[Talk through the tradeoffs in coming to the specific design point you want to make.]\n\n```\n// Illustrated with example code.\n```\n\n[This may be an open question, in which case you should link to any active discussion threads.]\n\n#### [Tricky design choice 2]\n\n[etc.]\n\n### Considered alternatives\n\n[This section is not required if you already covered considered alternatives in the design discussion above.]\n\n#### [Alternative 1]\n\n[Describe an alternative which was considered, and why you decided against it.]\n\n#### [Alternative 2]\n\n[etc.]\n\n### Stakeholder Interest & Feedback\n\nTODO before entering Phase 3.\n\n[This should include a list of implementers who have expressed interest in implementing the proposal]\n\n### References & acknowledgements\n\nMany thanks for valuable feedback and advice from:\n\n- [Person 1]\n- [Person 2]\n- [etc.]\n" + "text": "# `wasi-cloud-core`\n\nA proposed [WebAssembly System Interface](https://github.com/WebAssembly/WASI) API.\n\n### Current Phase\n\n`wasi-cloud-core` is currently in [Phase 1](https://github.com/WebAssembly/WASI/blob/main/Proposals.md#phase-1---feature-proposal-cg).\n\n### Champions\n\n- [Dan Chiarlone](https://github.com/danbugs)\n- [David Justice](https://github.com/devigned)\n- [Jiaxiao Zhou](https://github.com/Mossaka)\n\n### Phase 4 Advancement Criteria\n\n`wasi-cloud-core` should have at least two implementations (i.e., from service providers, and or cloud providers), and, at the very minimum, pass the testsuite for Windows, Linux, and MacOS.\n\n## Table of Contents [if the explainer is longer than one printed page]\n\n- [Introduction](#introduction)\n\n### Introduction\n\n> Note: This proposal currently only contains the proposed WIT interfaces; more work is necessary to fully document the proposal.\n\n`wasi-cloud-core` World aims to provide a generic way for WASI applications to interact with services. This world is created by including many other WASI worlds being proposed in the WASI community. The following is a list of the worlds that are currently being included in `wasi-cloud-core`.\n\n- [wasi-keyvalue](https://github.com/WebAssembly/wasi-keyvalue)\n- [wasi-messaging](https://github.com/WebAssembly/wasi-messaging)\n- [wasi-http](https://github.com/WebAssembly/wasi-http)\n- [wasi-runtime-config](https://github.com/WebAssembly/wasi-runtime-config)\n- [wasi-distributed-lock-service](https://github.com/WebAssembly/wasi-distributed-lock-service)\n- [wasi-sql](https://github.com/WebAssembly/wasi-sql)\n- [wasi-blob-store](https://github.com/WebAssembly/wasi-blob-store)\n\nThis list of services provide a set of capabilities that are common to many applications. Examples: handling an HTTP request, responding to a pub/sub message, storing a key/value pair, etc. It targets a wide range of applications, from long-running services to \"bursty workloads\" like Edge functions, serverless functions or Cloud events.\n\nThis set of capabilities are derived from the best practices of building distributed applications. It is not intended to be a complete set of capabilities, but rather are needed by 80% of applications.\n" } }, { @@ -178801,81 +178801,6 @@ } ] }, - "110166": { - "id": 110166, - "name": "Web Machine Learning Community Group", - "is_closed": false, - "description": "The mission of the Web Machine Learning Community Group (WebML CG) is to make Machine Learning a first-class web citizen by incubating and developing a dedicated low-level Web API for machine learning inference in the browser. Please see the charter for more information.\r\n\r\nThe group invites browser engine developers, hardware vendors, web application developers, and the broader web community with interest in Machine Learning to participate.", - "shortname": "webmachinelearning", - "discr": "w3cgroup", - "type": "community group", - "_links": { - "self": { - "href": "https://api.w3.org/groups/cg/webmachinelearning" - }, - "homepage": { - "href": "https://www.w3.org/community/webmachinelearning/" - }, - "users": { - "href": "https://api.w3.org/groups/cg/webmachinelearning/users" - }, - "services": { - "href": "https://api.w3.org/groups/cg/webmachinelearning/services" - }, - "chairs": { - "href": "https://api.w3.org/groups/cg/webmachinelearning/chairs" - }, - "join": { - "href": "https://www.w3.org/community/webmachinelearning/join" - }, - "participations": { - "href": "https://api.w3.org/groups/cg/webmachinelearning/participations" - } - }, - "fullshortname": "cg/webmachinelearning", - "repos": [ - { - "name": "charter", - "fullName": "webmachinelearning/charter" - }, - { - "name": "meetings", - "fullName": "webmachinelearning/meetings" - }, - { - "name": "model-loader", - "fullName": "webmachinelearning/model-loader" - }, - { - "name": "proposals", - "fullName": "webmachinelearning/proposals" - }, - { - "name": "test-data", - "fullName": "webmachinelearning/test-data" - }, - { - "name": "webmachinelearning.github.io", - "fullName": "webmachinelearning/webmachinelearning.github.io" - }, - { - "name": "webnn-baseline", - "fullName": "webmachinelearning/webnn-baseline" - }, - { - "name": "webnn-native", - "fullName": "webmachinelearning/webnn-native" - }, - { - "name": "webnn-polyfill", - "fullName": "webmachinelearning/webnn-polyfill" - }, - { - "name": "webnn-samples", - "fullName": "webmachinelearning/webnn-samples" - } - ] - }, "110458": { "id": 110458, "name": "RDF-DEV Community Group",