Skip to content

update terminology for Agent to align with system componentsadded clarity to agent definition #201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jeremycaine wants to merge 1 commit into from
Closed

update terminology for Agent to align with system componentsadded clarity to agent definition #201

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion lws10-core/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,7 +173,7 @@ <h2>Terminology</h2>
This specification defines the following terms:
</p>
<ul>
<li><dfn data-lt="agents">agent</dfn> &mdash; a person, social entity, or software identified by a URI.</li>
<li><dfn data-lt="agents">agent</dfn> &mdash; a person, social entity, or software identified by a URI. An agent uses software (e.g. browser, curl, software library etc) to make LWS Client requests to the LWS Server.</li>

@acoburn acoburn Jul 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

In general, a terminology section establishes what things are: their identity, nature and relationships. Behavioral requirements (what they do and how they interact), such as what is added here, belong in normative sections.

I do not believe we should make this change to the definition of agent.

@jeremycaine jeremycaine Jul 16, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

I believe we need more clarity for implementation on the flow of interaction e.g. agent -> lws client -> lws-server.

If you agree, where in the spec should we add that detail - it could be covered in the text descriptions that go with the diagrams.

@elf-pavlik elf-pavlik Jul 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think this could be taken into account in

I recall that it came up while we were discussing that PR and looking at the User entity.
da07c8f seems to address it already

@jeremycaine jeremycaine Jul 16, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

ok I think the minutes said put this in #159, I was mistaken - I'll close this and bring this text into the description part of the diagram (I've already update the diagrams to use agent instead of user)

<li><dfn data-lt="authentication credentials">authentication credential</dfn> &mdash; a security token that asserts claims about an <a>agent</a> or end-user. This token is secured with a cryptographic proof.
Examples of authentication credentials include assertions of identity such as OpenID Connect ID Tokens and SAML-based assertions as well as assertions of
capability such as ZCAPs.
Expand Down
Loading