diff --git a/README.md b/README.md
index 043daad..368868f 100644
--- a/README.md
+++ b/README.md
@@ -1,40 +1,9 @@
 # W3C Automotive Working Group
 
-This is the repository for the specifications created by the [Automotive Working Group](http://www.w3.org/auto/wg/).
+This was the repository for the specifications created by the [Automotive Working Group](http://www.w3.org/auto/wg/).
 
-> The mission of the Automotive Working Group is to develop Open Web Platform specifications for HTML5/JavaScript application developers enabling Web connectivity through in-vehicle infotainment systems and vehicle data access protocols. The API is agnostic with regard to the connection used.
+The group closed in November of 2023 and the work is continuing with [COVESA](https://covesa.global) with whom W3C has had a long standing collaboration.
 
-The specifications in this repository are as follows:
-- [Vehicle Information Service Specification](https://www.w3.org/TR/vehicle-information-service/) (git)
-- [Vehicle Information Service Specification version 2 - CORE](https://raw.githack.com/w3c/automotive/gh-pages/spec/VISSv2_Core.html) (git)
-- [Vehicle Information Service Specification version 2 - TRANSPORT](https://raw.githack.com/w3c/automotive/gh-pages/spec/VISSv2_Transport.html) (git)
+You may find the Vehicle Information Service Specification (VISS) at [https://github.com/COVESA/vehicle-information-service-specification](https://github.com/COVESA/vehicle-information-service-specification) and the open source reference implementation at [https://github.com/COVESA/vissr](https://github.com/COVESA/vissr)
 
-## Repository Layout
-
-- /media_tuner/ - deliverables from the Media Tuner Task Force
-- /vehicle_data/ - working copies of the vehicle and information API specifications 
-
-## Tools
-
-- [ReSpec](https://www.w3.org/respec/) has been used to style the specifications allowing the editors to focus on functionality and ensure consistency and referential integrity
-- The [API Design Cookbook](http://www.w3.org/TR/api-design/) has been used as a guide for the use of WebIDL
-
-## Style Guidelines
-
-### JavaScript Style Guidelines
-
-JavaScript should be written using the [JSCS](http://jscs.info/) rule set defined by [Echidna](https://github.com/w3c/echidna/blob/master/.jscs.json).
-
-## Contribution Guidelines
-
-In order to join the W3C Automotive Working Group please read our [Charter](https://www.w3.org/2021/05/autowg-charter.html) and visit [Join](https://www.w3.org/groups/wg/auto/instructions) for further instructions.
-
-- Issues can be submitted [here](https://github.com/w3c/automotive/issues).
-- Commit history can be found [here](https://github.com/w3c/automotive/commits).
-- The public mailing list for the Automotive Working Group can be found [here](https://lists.w3.org/Archives/Public/public-automotive/).
-
-Pull requests will be evaluated by the editors before merging into the documents.
-
-## Commit Message Format
-
-Please include the name of the relevant document within the title of the issue/pull request e.g. "[data-spec] My Issue or Pull Request Title".
+> The mission of the W3C Automotive Working Group was to develop Open Web Platform specifications for HTML5/JavaScript application developers enabling Web connectivity through in-vehicle infotainment systems and vehicle data access protocols. The API is agnostic with regard to the connection used.