Skip to content

Remove 'Unstable Features' section #168

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

Open
acoburn wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Remove 'Unstable Features' section #168

Show file tree
Hide file tree
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
4 changes: 0 additions & 4 deletions lws10-core/Unstable-Features.md
View file
Open in desktop

This file was deleted.

4 changes: 0 additions & 4 deletions lws10-core/Unstable-Features/Inbox.md
View file
Open in desktop

This file was deleted.

2 changes: 0 additions & 2 deletions lws10-core/Unstable-Features/Notifications.md
View file
Open in desktop

This file was deleted.

4 changes: 0 additions & 4 deletions lws10-core/Unstable-Features/Profile-Negotiation-on-Resources.md
View file
Open in desktop

This file was deleted.

39 changes: 0 additions & 39 deletions lws10-core/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -296,45 +296,6 @@ <h2>Resource Identification</h2>
<div data-include="Resource-Identification.md" data-include-format="markdown" data-include-replace="true"></div>
</section>

<section id="unstable-features" data-feature-status="unstable">
<h2>Unstable Features</h2>
<div class="advisement">
<p>
The features described in this section are being drafted to ground discussions and may be removed if there is:
</p>
<ul>
<li>Lack of consensus to include them, or</li>
<li>Lack of implementation of those features</li>
</ul>
</div>

<div data-include="Unstable-Features.md" data-include-format="markdown" data-include-replace="true"></div>

<section id="profile-negotiation">
<h3>Profile Negotiation on Resources</h3>
Comment thread
acoburn marked this conversation as resolved.
<p>
<span class="TODO">Define mechanisms for content negotiation based on profiles, allowing clients to request specific representations or views of resources (e.g., JSON-LD contexts, different RDF serializations, or application-specific profiles).</span>
</p>
<div data-include="Unstable-Features/Profile-Negotiation-on-Resources.md" data-include-format="markdown" data-include-replace="true"></div>
</section>

<section id="notifications">
<h3>Notifications</h3>
<p>
<span class="TODO">Define notification mechanisms that allow clients to be informed of changes to resources, including subscription models, event formats, and delivery mechanisms.</span>
</p>
<div data-include="Unstable-Features/Notifications.md" data-include-format="markdown" data-include-replace="true"></div>
</section>

<section id="inbox-semantics">
<h3>Inbox</h3>

@jeswr jeswr Jun 6, 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 see no open issues for inboxes. @acoburn could you please identify if there is an issue open for this topic, and if not, open one so it remains tracked.

@acoburn acoburn Jun 15, 2026 •
edited
Loading

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Inboxes are used with Access Requests, and issue #142 already is tracking the clarification of that relationship

<p>
<span class="TODO">Define inbox resources with specific semantics within LWS, including message posting, retrieval, and management capabilities for asynchronous communication patterns.</span>
</p>
<div data-include="Unstable-Features/Inbox.md" data-include-format="markdown" data-include-replace="true"></div>
</section>
</section>

<section id="portability-considerations">
<h2>Portability Considerations</h2>
<p>
Expand Down
Loading