Skip to content

Add scope diagrams section with C4 Level 1 and Level 2 diagrams#159

Open
jeremycaine wants to merge 1 commit into
w3c:mainfrom
jeremycaine:scope-diagrams
Open

Add scope diagrams section with C4 Level 1 and Level 2 diagrams#159
jeremycaine wants to merge 1 commit into
w3c:mainfrom
jeremycaine:scope-diagrams

Conversation

@jeremycaine

@jeremycaine jeremycaine commented May 15, 2026

Copy link
Copy Markdown

Editorial - Clarify systems diagram (at least scope/system context; platform independent model)


Preview | Diff

System(client, "Client application", "Requests and manages resources")
System(lws, "LWS server", "Manages resource hierarchy and access")
System_Ext(idp, "Identity provider", "Issues signed credentials")
System_Ext(ext, "External resources", "Web resources under management")

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What do you mean by "external resources"? Are these the same as the "LWS resources" we defined in the terminology? If so, it might be best to re-use that term.

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.

Suggested change
System_Ext(ext, "External resources", "Web resources under management")
System_Ext(ext, "LWS resources", "Web resources under management")

Rel(rm, era, "resolves resource")
Rel(era, ext, "accesses")
```
Issue: The internal organisation of container, containment and linkset management within the LWS server is not yet defined in the protocol. This diagram reflects current terminology and is subject to revision.

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.

Suggested change
Issue: The internal organisation of container, containment and linkset management within the LWS server is not yet defined in the protocol. This diagram reflects current terminology and is subject to revision.
Issue: The internal organisation of container, containment, and linkset management within the LWS server is not yet defined in the protocol. This diagram reflects current terminology and is subject to revision.

Comment thread lws10-core/index.html
@@ -171,8 +171,36 @@ <h2>Security and Privacy</h2>
A <dfn>LWS Client</dfn> is an HTTP client [[!rfc9112]] that complies with all of the relevant "MUST" statements in this specification. Specifically, the relevant normative "MUST" statements in <a href="#operations"></a> of this document MUST be respected.

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.

Suggested change
A <dfn>LWS Client</dfn> is an HTTP client [[!rfc9112]] that complies with all of the relevant "MUST" statements in this specification. Specifically, the relevant normative "MUST" statements in <a href="#operations"></a> of this document MUST be respected.
An <dfn>LWS Client</dfn> is an HTTP client [[!rfc9112]] that complies with all of the relevant "MUST" statements in this specification. Specifically, the relevant normative "MUST" statements in <a href="#operations"></a> of this document MUST be respected.

@elf-pavlik

Copy link
Copy Markdown
Member

@jeremycaine In various projects I've been using https://likec4.dev/

There's even some work on embedding it in specs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants