Skip to content
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

Proposals Folder Explanation #2062

Merged
merged 5 commits into from
Dec 18, 2024
Merged

Proposals Folder Explanation #2062

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
4a4569e
add root readme
egekorkan Dec 18, 2024
52137bb
add information on broken link
egekorkan Dec 18, 2024
023bcc0
rename file
egekorkan Dec 18, 2024
712fb94
explain proposal status
egekorkan Dec 18, 2024
7124a13
Prettified Code!
egekorkan Dec 18, 2024
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
20 changes: 20 additions & 0 deletions proposals/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
# Proposals to the WoT TD Specification

This folder contains proposals that do not fit a single issue or pull request when the discussions take place.
Based on the content of these proposals, big features can be evaluated in a defined folder and not mix with the editor's drafts.

The status of a proposal is indicated next to it with the following meanings:

- In Progress: The proposal is being actively discussed
- Rejected: The proposal is not accepted by the TF
- Paused: The proposal is not rejected but there is no active work happening on it
- Accepted: The proposal is in use by the TF
- Retired: The proposal was accepted and used but it is not relevant anymore and thus is retired.

| Proposal Name and Link | Status |
| ---------------------------------------------------- | -------- |
| [Simplified TD](./simplified-td/index.html) | Rejected |
| [Hypermedia 1](./hypermedia-control/README.md) | Paused |
| [Hypermedia 2](./hypermedia-control-2/README.md) | Paused |
| [Hypermedia 3](./hypermedia-control-3/README.md) | Paused |
| [Project Management](./project-management/README.md) | Accepted |
3 changes: 3 additions & 0 deletions proposals/hypermedia-control-2/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
# Hypermedia Control on the Web of Things

> [!NOTE]
> Proposal Status: Paused

This proposal introduces a generic hypermedia control framework for the Web of Things (WoT) that is similar to that of @vcharpenay but uses static TDs and focuses on action affordances.
The ideas were introduced also [at this comment](https://github.com/w3c/wot-thing-description/issues/302#issuecomment-627500213)

Expand Down
3 changes: 3 additions & 0 deletions proposals/hypermedia-control/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
# Hypermedia Control on the Web of Things

> [!NOTE]
> Proposal Status: Paused

This proposal introduces a generic hypermedia control framework for the Web of Things (WoT).

TL;DR:
Expand Down
3 changes: 3 additions & 0 deletions proposals/hypermerdia-control-3/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
# Yet another Action Model

> [!NOTE]
> Proposal Status: Paused

This proposal wants to overcame problems around the other proposals of a new hypermedia action model. In particular, it
should address the following concerns:

Expand Down
5 changes: 4 additions & 1 deletion .../project-management/project-management.md → proposals/project-management/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
# WoT Project Management Process

> [!NOTE]
> Proposal Status: Accepted

The main question to answer is "How do we organize the work?".
We want to have one place to look for the list of "work" to do in a short period.
To do that, a prioritization should happen and should be aligned with use cases and requirements.
Expand Down Expand Up @@ -50,7 +53,7 @@ The lifecycle is also reflected in a table below. The example below can be consi
- Ideally, we should discuss our requirements and what people want to see. Mandating a mechanism that the moderators like but is disliked by everyone else should be avoided.
- The goal is to make it more systematic than "copy-pasting the agenda, look into issues and PRs"
- The process for generating features from use cases should be taken into account
- We can use a tool like GitHub Projects. A premature example is available at https://github.com/orgs/w3c/projects/31
- We can use a tool like GitHub Projects. A premature example is available at <https://github.com/orgs/w3c/projects/31> (this project is now deleted and an up to date one is available at <https://github.com/orgs/w3c/projects/80>)
- Mahda Noura: Only assigning an issue is not enough, because the number can increase and we can lose oversight/prioritization.
- Cristiano Aguzzi: Assigning should happen when you know that person can do it in 1-2 weeks.
- Jan Romann: Splitting issues definitely helps. We should limit the workload of an issue in the beginning or use checkboxes per small item and open a "spinoff" issue.
Expand Down
1 change: 1 addition & 0 deletions proposals/simplified-td/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,7 @@
</style>
</head>
<body>
<p class="note">Proposal Status: Rejected</p>
<section id="abstract">
<p>
This document summarizes the discussions on simplifying the JSON-LD&nbsp;1.0-based
Expand Down