update terminology for Agent to align with system componentsadded clarity to agent definition#201
update terminology for Agent to align with system componentsadded clarity to agent definition#201jeremycaine wants to merge 1 commit into
Conversation
| </p> | ||
| <ul> | ||
| <li><dfn data-lt="agents">agent</dfn> — a person, social entity, or software identified by a URI.</li> | ||
| <li><dfn data-lt="agents">agent</dfn> — 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> |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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)
4 participants
add more precision to the role of agent and the different ways in which is can be a LWS Client to an LWS Server.
Preview | Diff