Revise README for Consent-Aware HTTP Framework#25
Conversation
Updated the README to reflect new framework name and author, and revised content for clarity and structure. Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6c83cb27ac
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| == License | ||
|
|
||
| See link:RSR-COMPLIANCE.md[RSR-COMPLIANCE.md] for Rhodium Standard Repository compliance status. | ||
| See IETF Trust Legal Provisions (BCP 78 and BCP 79). |
There was a problem hiding this comment.
Restore accurate license attribution in README
The README now tells readers to use IETF Trust Legal Provisions for licensing, but the repository’s actual license artifacts define different terms (e.g., the root LICENSE file). This can cause adopters and distributors to apply the wrong legal obligations, which is a material compliance regression.
Useful? React with 👍 / 👎.
| /http-430/ HTTP 430 Consent Required | ||
| /agent-identification/ AI Agent Identification Protocol | ||
| /content-provenance/ Content Provenance Protocol | ||
| /compliance-reporting/ AI Compliance Reporting Framework | ||
| /consent-management/ Web Consent Management Protocol (planned / draft) |
There was a problem hiding this comment.
List only existing paths in repository structure
This structure map enumerates top-level directories that do not exist in the current repository (for example /http-430/, /agent-identification/, and /content-provenance/). Contributors using this section to navigate will be sent to dead paths, so the section should either match the real tree or clearly mark entries as future-only.
Useful? React with 👍 / 👎.
| * Ethical AI practitioners | ||
| * IETF working groups | ||
| * Journalism ethics communities | ||
| All components are currently Internet-Drafts (Work in Progress). |
There was a problem hiding this comment.
Avoid overstating draft status for all components
The status text claims all framework components are currently Internet-Drafts, but this repo only contains draft files for a subset of the protocols described earlier. That mismatch overstates publication maturity and can mislead readers evaluating what has actually been drafted.
Useful? React with 👍 / 👎.
Updated the README to reflect new framework name and author, and revised content for clarity and structure.