- From: Bernard Lynch <bernard@aivisibilityarchitects.com>
- Date: Mon, 13 Apr 2026 05:02:29 +0000
- To: "public-ai-web-visibility@w3.org" <public-ai-web-visibility@w3.org>
- CC: team-community-process <team-community-process@w3.org>, Ian Jacobs <ij@w3.org>
- Message-ID: <TY0PR0101MB484457EAB11595EA54495315AF242@TY0PR0101MB4844.apcprd01.prod.exchange>
Dear Group, I am writing to inform you of corrections made to the group charter and the AIVA Terminology Index, and to open a 7-day review period during which participants may raise objections. Background Since the group launched in February 2026, I have been working with Ian Jacobs (W3C staff contact) to ensure the group's documentation is properly aligned with W3C Community Group standards and process. Ian identified a number of issues that I should have caught before publication, and I want to be transparent with the group about what those issues were and what I have done to correct them. The problems were mine. I was moving quickly to get the group established and the Terminology Index published, and in doing so I created confusion between three separate tracks — the IETF Internet-Draft, the Zenodo publication corpus, and this W3C Community Group. That confusion showed up in the documents in ways that needed to be fixed. What Was Wrong The AIVA Terminology Index was published with a status of "CG-DRAFT published by the AI Visibility Lifecycle Framework Community Group." This was incorrect. The CG has not adopted the document — it is my document, submitted as proposed input for the group's review and collaborative development. Ian rightly pointed out that the CG cannot claim authorship of a document it has not produced. The document also contained references to the IETF Internet-Draft in its header and metadata, which created confusion about the relationship between the vocabulary document and the IETF work. A conformance section using normative RFC 2119 language was also present, which in W3C's view makes a document a specification rather than a vocabulary — inconsistent with the group's charter which states no specifications will be produced. The charter itself listed a deliverable — a CG Report mirroring the canonical IETF specification — that Ian correctly questioned. The CG should not be producing a mirror of an IETF document. The charter also referenced the IETF Internet-Draft in several places in a way that blurred the boundary between the two tracks. What Has Been Corrected AIVA Terminology Index — a corrected version has been uploaded to Zenodo (DOI: 10.5281/zenodo.19505331): - Status changed to "Author's draft — submitted to the AI Visibility Lifecycle Framework Community Group as proposed input" - All IETF Internet-Draft references removed - Conformance section removed entirely - Document clearly identifies Bernard Lynch and AI Visibility Architecture Group Limited as author and publisher throughout The WordPress landing page and Zenodo description have been updated to match. Charter v1.1 (13 April 2026) — updated in the GitHub repository: - The deliverable mirroring the IETF specification removed from Section 3.2 - All IETF Internet-Draft references removed from Sections 1.1, 4, and 14 - The mirroring notice removed from Section 9 All changes are live across GitHub, Zenodo, and the WordPress landing page. 7-Day Review Period As Chair I am treating these as corrections made in response to W3C staff feedback. If any participant wishes to raise an objection to any of these changes, please do so on this mailing list within 7 days of this message — by 20 April 2026. If no objections are raised the corrections will stand as agreed. I want to thank Ian Jacobs for his patience and careful guidance through this process. This is my first time running a W3C Community Group and it has not gone as smoothly as I had hoped. I am committed to running the group properly from this point forward and welcome any feedback from participants. Kind regards, Bernard Lynch Chair, AI Visibility Lifecycle Framework Community Group AI Visibility Architecture Group Limited ORCID: 0009-0007-6170-7818
Received on Monday, 13 April 2026 05:02:37 UTC