Skip to content

chore(spec/flows): editorial changes#663

Open
meyerweb wants to merge 6 commits into
WICG:mainfrom
meyerweb:flows-spec
Open

chore(spec/flows): editorial changes#663
meyerweb wants to merge 6 commits into
WICG:mainfrom
meyerweb:flows-spec

Conversation

@meyerweb

Copy link
Copy Markdown
Contributor

A variety of small typo, formatting, and wording fixes in the WM Flows specification.

@netlify

netlify Bot commented Apr 29, 2026

Copy link
Copy Markdown

Deploy Preview for webmonetization-preview ready!

Name Link
🔨 Latest commit 5d425d9
🔍 Latest deploy log https://app.netlify.com/projects/webmonetization-preview/deploys/69f250231c4af30008014a2c
😎 Deploy Preview https://deploy-preview-663--webmonetization-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@sidvishnoi sidvishnoi changed the title Flows spec corrrections chore(spec/flows): editorial changes May 13, 2026

<aside class="example" title="Set as structured header">
With |headerName|=`Content-Digest`, |key|=`sha-512`, |value|=`aByteSequence`:
With |headerName|=`Content-Digest`, |key|=`sha-512`, |value|=:`aByteSequence`:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This change feels little odd..

<dt><dfn>Grants</dfn></dt>
<dd>
A delegation of authorization from a resource owner to a client, allowing the client to access protected resources or perform actions on the owner’s behalf. In Rafiki, this process is managed by the authorization server, which issues grants as access tokens. These grants permit clients to interact with Open Payments APIs to, for example, create payments and retrieve account information, based on the permissions granted by the resource owner.
As per GNAP, a delegation of authorization from a resource owner to a client, allowing the client to access protected resources or perform actions on the owner’s behalf. In Rafiki, this process is managed by the authorization server, which issues grants as access tokens. These grants permit clients to interact with Open Payments APIs to, for example, create payments and retrieve account information, based on the permissions granted by the resource owner.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
As per GNAP, a delegation of authorization from a resource owner to a client, allowing the client to access protected resources or perform actions on the owner’s behalf. In Rafiki, this process is managed by the authorization server, which issues grants as access tokens. These grants permit clients to interact with Open Payments APIs to, for example, create payments and retrieve account information, based on the permissions granted by the resource owner.
As per [[GNAP]], a delegation of authorization from a resource owner to a client, allowing the client to access protected resources or perform actions on the owner’s behalf. In Rafiki, this process is managed by the authorization server, which issues grants as access tokens. These grants permit clients to interact with Open Payments APIs to, for example, create payments and retrieve account information, based on the permissions granted by the resource owner.

Comment thread specification/index.html
Comment on lines +590 to +598
<aside class="note" title="Divergence from the Payment Request API">
<p>
This member’s definition is left as a generic string to maximize
flexibility; for example, if a new currency representation
standard emerges to supplement or replace ISO 4217. This also
permits Web Monetization implementors to support the numeric
ISO 4217 codes (as string equivalents) where needed.
</p>
</aside>

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Let's avoid these changes until we finalize in #440.

@sidvishnoi sidvishnoi added the specification Work required on specification label May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

specification Work required on specification

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants