Skip to content

chore: Include schema and documentation development instructions in README.md for better discoverability#452

Open
damaz91 wants to merge 13 commits into
mainfrom
chore/readme-update
Open

chore: Include schema and documentation development instructions in README.md for better discoverability#452
damaz91 wants to merge 13 commits into
mainfrom
chore/readme-update

Conversation

@damaz91
Copy link
Copy Markdown
Contributor

@damaz91 damaz91 commented May 19, 2026

Description

Include schema and documentation development instructions in README.md for better discoverability

Category (Required)

Please select one or more categories that apply to this change.

  • Core Protocol: Changes to the base communication layer, global context, or breaking refactors. (Requires Technical Council approval)
  • Governance/Contributing: Updates to GOVERNANCE.md, CONTRIBUTING.md, or CODEOWNERS. (Requires Governance Council approval)
  • Capability: New schemas (Discovery, Cart, etc.) or extensions. (Requires Maintainer approval)
  • Documentation: Updates to README, or documentations regarding schema or capabilities. (Requires Maintainer approval)
  • Infrastructure: CI/CD, Linters, or build scripts. (Requires DevOps Maintainer approval)
  • Maintenance: Version bumps, lockfile updates, or minor bug fixes. (Requires DevOps Maintainer approval)
  • SDK: Language-specific SDK updates and releases. (Requires DevOps Maintainer approval)
  • Samples / Conformance: Maintaining samples and the conformance suite. (Requires Maintainer approval)
  • UCP Schema: Changes to the ucp-schema tool (resolver, linter, validator). (Requires Maintainer approval)
  • Community Health (.github): Updates to templates, workflows, or org-level configs. (Requires DevOps Maintainer approval)

Checklist

  • I have followed the Contributing Guide (including Conventional Commits title requirements and ! for breaking changes).
  • I have updated the documentation (if applicable).
  • My changes pass all local linting and formatting checks.

@damaz91 damaz91 requested review from a team as code owners May 19, 2026 09:43
@damaz91 damaz91 requested review from archrao and kmcduffie May 19, 2026 09:43
@damaz91 damaz91 added the documentation Improvements or additions to documentation label May 19, 2026
Comment thread README.md Outdated
Comment thread README.md Outdated
### Schema Development

Schemas live in `source/` and are published with `ucp_*` annotations intact.
Agents use [ucp-schema](https://github.com/universal-commerce-protocol/ucp-schema)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Define "Agents" better? What are they, how do they "use" ucp-schema?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please take a look now

Comment thread README.md Outdated
Comment thread README.md

The local version of the documentation website will then be available at
**<http://127.0.0.1:8000>**

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Final nit: maybe add that for contributing to SDKs, Samples, Conformance or other repos, the README in those repos will contain relevant information on specific developer workflows / instructions?

@ptiper ptiper requested review from pemamian and removed request for archrao and kmcduffie May 20, 2026 12:53
Comment thread README.md
1. Ensure `ucp-schema` is installed:

```bash
cargo install ucp-schema # from crates.io
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one of these lines is enough for having the cargo, right ? so i suggest splitting the bash code section in 2 and putting an OR in between. (lazy developer would just copy the lines and run in command line and would have issues running both)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants