From 4a4569e85583f7fa2413fbbc639bc29e3ca3ed0e Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Wed, 18 Dec 2024 15:20:40 +0100 Subject: [PATCH 1/5] add root readme --- proposals/README.md | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 proposals/README.md diff --git a/proposals/README.md b/proposals/README.md new file mode 100644 index 00000000..4e0951d4 --- /dev/null +++ b/proposals/README.md @@ -0,0 +1,4 @@ +# 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. From 52137bba62b77615bf7cd4a9da315ab7226259cf Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Wed, 18 Dec 2024 15:20:49 +0100 Subject: [PATCH 2/5] add information on broken link --- proposals/project-management/project-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/project-management/project-management.md b/proposals/project-management/project-management.md index 9581353f..3da4a7c5 100644 --- a/proposals/project-management/project-management.md +++ b/proposals/project-management/project-management.md @@ -50,7 +50,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 (this project is now deleted and an up to date one is available at ) - 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. From 023bcc0641581de04a39b17e28143dca17e430c6 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Wed, 18 Dec 2024 15:29:28 +0100 Subject: [PATCH 3/5] rename file --- proposals/project-management/{project-management.md => README.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename proposals/project-management/{project-management.md => README.md} (100%) diff --git a/proposals/project-management/project-management.md b/proposals/project-management/README.md similarity index 100% rename from proposals/project-management/project-management.md rename to proposals/project-management/README.md From 712fb9464f54e947bdd97f7f9a496e1cd336a228 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Wed, 18 Dec 2024 15:31:46 +0100 Subject: [PATCH 4/5] explain proposal status --- proposals/README.md | 16 ++++++++++++++++ proposals/hypermedia-control-2/README.md | 3 +++ proposals/hypermedia-control/README.md | 3 +++ proposals/hypermerdia-control-3/README.md | 3 +++ proposals/project-management/README.md | 3 +++ proposals/simplified-td/index.html | 3 +++ 6 files changed, 31 insertions(+) diff --git a/proposals/README.md b/proposals/README.md index 4e0951d4..a812fe8f 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -2,3 +2,19 @@ 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 | diff --git a/proposals/hypermedia-control-2/README.md b/proposals/hypermedia-control-2/README.md index 990fb112..71ee347f 100644 --- a/proposals/hypermedia-control-2/README.md +++ b/proposals/hypermedia-control-2/README.md @@ -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) diff --git a/proposals/hypermedia-control/README.md b/proposals/hypermedia-control/README.md index b8fc63bf..89915d7c 100644 --- a/proposals/hypermedia-control/README.md +++ b/proposals/hypermedia-control/README.md @@ -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: diff --git a/proposals/hypermerdia-control-3/README.md b/proposals/hypermerdia-control-3/README.md index adeac09d..25e797e9 100644 --- a/proposals/hypermerdia-control-3/README.md +++ b/proposals/hypermerdia-control-3/README.md @@ -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: diff --git a/proposals/project-management/README.md b/proposals/project-management/README.md index 3da4a7c5..3feb20a5 100644 --- a/proposals/project-management/README.md +++ b/proposals/project-management/README.md @@ -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. diff --git a/proposals/simplified-td/index.html b/proposals/simplified-td/index.html index 10c1baa4..a9ce6301 100644 --- a/proposals/simplified-td/index.html +++ b/proposals/simplified-td/index.html @@ -63,6 +63,9 @@ +

+ Proposal Status: Rejected +

This document summarizes the discussions on simplifying the JSON-LD 1.0-based From 7124a13c0053522d73a787e9b0d7b12f3562843f Mon Sep 17 00:00:00 2001 From: egekorkan Date: Wed, 18 Dec 2024 14:32:53 +0000 Subject: [PATCH 5/5] Prettified Code! --- proposals/README.md | 12 ++++++------ proposals/simplified-td/index.html | 4 +--- 2 files changed, 7 insertions(+), 9 deletions(-) diff --git a/proposals/README.md b/proposals/README.md index a812fe8f..2c2110f0 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -11,10 +11,10 @@ The status of a proposal is indicated next to it with the following meanings: - 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 | +| 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 | diff --git a/proposals/simplified-td/index.html b/proposals/simplified-td/index.html index a9ce6301..42fb6eed 100644 --- a/proposals/simplified-td/index.html +++ b/proposals/simplified-td/index.html @@ -63,9 +63,7 @@ -

- Proposal Status: Rejected -

+

Proposal Status: Rejected

This document summarizes the discussions on simplifying the JSON-LD 1.0-based