ucan-wg / ucan-wg/invocation

Does an Invocation have an `nbf`?

Open
#45 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
20
Forks
7
PR merge metrics
No merged PRs in 30d

Description

All token payloads are supposed to include the nbf, but Invocation currently doesn't have one in its spec. I'm not sure how useful it would be, but if Invocation isn't supposed to (optionally) have one, it should be taken off the payload requirement for tokens for clarity.

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.

Research direction

Start with the linked UCAN payload requirement and the Invocation specification. Determine whether Invocation payloads include an optional nbf; done means the specification and token-payload requirement agree and the resulting rule is explicit.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.