Add TransactionUUID to SimpleEvent spec

Open
#74 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Open content/docs/wrp/simple-messages.md and compare the Simple Event definition with the Request-Response description of transaction_uuid. Resolve whether the same wording and functionality should apply, then document transaction_uuid as a required field with the agreed description.

Written by the indexing model from the issue text.

Description

documentation enhancement

https://github.com/xmidt-org/docs/blob/main/content/docs/wrp/simple-messages.md

The transaction_uuid should be added as a required field for the Simple Event. Do we want the same description/functionality as the Request-Response?

This SHOULD be a UUID, but the web router SHALL NOT validate this data. The web router SHALL treat this data as opaque.

Dominant language
SCSS
Stars
1
Forks
6
Avg merge
1m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from xmidt-org/docs

All issues in xmidt-org/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.