From 94017aec79277233a07e5090182f9bb35c6823ab Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Fri, 15 Sep 2023 12:54:59 +0200 Subject: [PATCH 1/5] add proposal for WG and IG liaison --- liaisons.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/liaisons.md b/liaisons.md index e9244da..1171c9e 100644 --- a/liaisons.md +++ b/liaisons.md @@ -1,3 +1,20 @@ ## Liaisons to the W3C WoT Community Group -To be decided +### Web of Things Interest and Working Group (Proposed) + +Collaboration on the following topics: + +- Bindings +- Use Cases +- Requirements +- Feedback on Draft Specifications +- Outreach of WG Activities +- Joint Activities such as Plugfests +- Contribution to WG test cases from CG Participants +- Feature Proposals + +Further clarifications on the following points are being worked on: + +- How the collaboration will work, what is the process +- Detailing what those topics mean +- Roles of the CG and WG participants per point/topic From 19fb148f60c3fcbf6001a09e8dfb168466d65b72 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Thu, 23 Nov 2023 10:05:07 +0100 Subject: [PATCH 2/5] incorporate input from internal meeting and office hours --- liaisons.md | 58 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+) diff --git a/liaisons.md b/liaisons.md index 1171c9e..8436d15 100644 --- a/liaisons.md +++ b/liaisons.md @@ -2,6 +2,64 @@ ### Web of Things Interest and Working Group (Proposed) +> The part below until a horizontal line is written by the CG using inputs from the TPAC Joint Meeting, CG Internal Meeting and Office Hours inputs. Please scroll to [Original Input](#original-input) + +The WoT IG/WG collaboration is categorized based on the type of collaboration. Below are the categories and the scope of the collaboration. + +Note: WG/IG refers to both WoT Interest and Working Group. CG refers to the WoT CG. + +#### Documents + +If the CG wants to produce a document, it has to be a CG report covered by the [W3C CLA](https://www.w3.org/community/about/process/cla/). +This means that the CG does not contribute to WG or IG documents by editing them or doing Pull Requests directly. +Related WG/IG documents can adopt the content from CG reports using Section 9 of the [W3C CLA](https://www.w3.org/community/about/process/cla/). +Any CG document category that is related to a WG/IG document category (e.g. use cases, bindings), MUST comply with the format and content requirements set by the WG/IG. +If the CG decides to diverge from those requirements, the WG/IG MUST authorize this. +CG reports, as explained in the CG charter, can be in the form of Markdown, HTML, or similar. (TODO: Update CG Charter). + +Examples of document categories that are related to WG/IG, which can be CG reports as explained above: + +- Use cases +- Requirements +- Feature Proposals +- Bindings + +#### Role of WoT CG + +The role of the WoT CG in this collaboration is defined in two categories: enabling a low entry barrier and doing outreach. + +##### Low entry barrier to be involved in WoT + +Given that there are membership fees to participate in the CG, more participants be exchanging ideas on WoT-related topics. +More specifically, the WoT CG participants can: + +- start WoT-related discussions within CG, +- work on CG reports that are non-normative, +- experiment with implementations and features of the WoT WG reports. + +##### Outreach + +The CG uses various channels administrated by the CG to reach a broad audience who is interested in WoT. +This also enables the low-entry barrier principle above. + +#### Events + +The WG/IG collaborates on Plugfest events with the CG, thus leveraging the community to get a wider audience. +WG/IG can collaborate with other CGs and liaisons as well. +There can be other WG/IG joint meetings with the CG, such as Face to Face, TPAC meetings. + +#### Test Cases + +CG participants CAN contribute to the testing activity of the WG/IG Task Forces. +The CG participants MUST contribute test cases to the CG GitHub repository. +Also, the inputs MUST comply with WG requirements on the quality, folder structure, file name conventions etc. + +--- + +#### Original Input + +The part below is written together with IG/WG in the TPAC 2023 Joint Meeting. + Collaboration on the following topics: - Bindings From e6604418f42bbe90bb1ed9dbcfd2ece207396e43 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Thu, 30 Nov 2023 17:53:17 +0100 Subject: [PATCH 3/5] rework the english and structure of the text --- liaisons.md | 57 ++++++++++++++++++++++++++++++----------------------- 1 file changed, 32 insertions(+), 25 deletions(-) diff --git a/liaisons.md b/liaisons.md index 8436d15..eb36d38 100644 --- a/liaisons.md +++ b/liaisons.md @@ -1,23 +1,34 @@ ## Liaisons to the W3C WoT Community Group -### Web of Things Interest and Working Group (Proposed) +The liaisons of the W3C WoT CG are not explicitly outlined in the CG charter; however, they are documented in this document. +This markdown document details each liaison and explains the extent of its scope. -> The part below until a horizontal line is written by the CG using inputs from the TPAC Joint Meeting, CG Internal Meeting and Office Hours inputs. Please scroll to [Original Input](#original-input) +Current liaisons: -The WoT IG/WG collaboration is categorized based on the type of collaboration. Below are the categories and the scope of the collaboration. +- [Web of Things Interest and Working Group](#web-of-things-interest-and-working-group) -Note: WG/IG refers to both WoT Interest and Working Group. CG refers to the WoT CG. +### Web of Things Interest and Working Group + +> [!NOTE] +> This is only a draft. + +> The content below, until the horizontal line, is composed by the CG based on inputs from the TPAC Joint Meeting, CG Internal Meeting, and Office Hours inputs. Please refer to [Original Input](#original-input) for the discussion results form W3C TPAC 2023. + +The WoT IG/WG liaison is categorized based on the nature of collaboration. +The categories below explain the scope of collaboration. + +Note: WG/IG collectively refers to both WoT Interest and Working Group, while CG pertains to the WoT CG. #### Documents -If the CG wants to produce a document, it has to be a CG report covered by the [W3C CLA](https://www.w3.org/community/about/process/cla/). -This means that the CG does not contribute to WG or IG documents by editing them or doing Pull Requests directly. -Related WG/IG documents can adopt the content from CG reports using Section 9 of the [W3C CLA](https://www.w3.org/community/about/process/cla/). -Any CG document category that is related to a WG/IG document category (e.g. use cases, bindings), MUST comply with the format and content requirements set by the WG/IG. -If the CG decides to diverge from those requirements, the WG/IG MUST authorize this. -CG reports, as explained in the CG charter, can be in the form of Markdown, HTML, or similar. (TODO: Update CG Charter). +If the CG intends to produce a document, it must adhere to the [W3C CLA](https://www.w3.org/community/about/process/cla/). +This mandates that the CG doesn't directly edit or open Pull Requests to change WG/IG documents. +Relevant WG/IG documents may incorporate content from CG reports following Section 9 of the [W3C CLA](https://www.w3.org/community/about/process/cla/). +Any CG document related to a WG/IG document type (e.g. use cases, bindings), MUST comply with the format and content requirements established by the WG/IG. +Deviating from these requirements requires explicit authorization from the WG/IG. +CG reports, as explained by the CG charter, may take the form of Markdown, HTML, or similar formats (TODO: Update CG Charter). -Examples of document categories that are related to WG/IG, which can be CG reports as explained above: +Examples of document types pertinent to WG/IG, eligible as CG reports: - Use cases - Requirements @@ -26,33 +37,29 @@ Examples of document categories that are related to WG/IG, which can be CG repor #### Role of WoT CG -The role of the WoT CG in this collaboration is defined in two categories: enabling a low entry barrier and doing outreach. +The role of the CG in this collaboration is categorized into two: facilitating a low entry barrier and engaging in outreach. -##### Low entry barrier to be involved in WoT +##### Facilitating a Low Entry Barrier for WoT Involvement -Given that there are membership fees to participate in the CG, more participants be exchanging ideas on WoT-related topics. -More specifically, the WoT CG participants can: +Considering the existence of membership fees for WG/IG participation, fostering more participants to exchange ideas on WoT-related topics becomes relevant. -- start WoT-related discussions within CG, -- work on CG reports that are non-normative, -- experiment with implementations and features of the WoT WG reports. +CG participants can actively and openly exchange ideas on WoT-related topics within the CG, collaborate on non-normative CG reports, and experiment with the implementations of the WG/IG reports. ##### Outreach -The CG uses various channels administrated by the CG to reach a broad audience who is interested in WoT. -This also enables the low-entry barrier principle above. +The CG utilizes various channels under CG administration to reach a broad audience interested in WoT, aligning with the low-entry barrier principle. #### Events -The WG/IG collaborates on Plugfest events with the CG, thus leveraging the community to get a wider audience. -WG/IG can collaborate with other CGs and liaisons as well. -There can be other WG/IG joint meetings with the CG, such as Face to Face, TPAC meetings. +The WG/IG collaborates on Plugfest events with the CG, thereby leveraging the community to garner a wider audience. +WG/IG may also engage in collaboration with other CGs and liaisons. +Joint meetings, such as Face to Face (F2F) and TPAC meetings, may be convened between WG/IG and the CG. #### Test Cases -CG participants CAN contribute to the testing activity of the WG/IG Task Forces. +CG participants are permitted to contribute to the testing activity of the WG/IG Task Forces. +Contributions must adhere to WG requirements regarding quality, folder structure, file naming conventions, and other specifications. The CG participants MUST contribute test cases to the CG GitHub repository. -Also, the inputs MUST comply with WG requirements on the quality, folder structure, file name conventions etc. --- From 38eb06343444bf48836109fba95de8b6b53e0906 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Mon, 4 Dec 2023 17:20:59 +0100 Subject: [PATCH 4/5] align RFC conformance --- liaisons.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/liaisons.md b/liaisons.md index eb36d38..ded341d 100644 --- a/liaisons.md +++ b/liaisons.md @@ -7,10 +7,14 @@ Current liaisons: - [Web of Things Interest and Working Group](#web-of-things-interest-and-working-group) +> [!NOTE] +> The key words MAY, MUST, MUST NOT, RECOMMENDED, SHOULD, and SHOULD NOT in this document are to be interpreted as described in [BCP 14](https://www.rfc-editor.org/info/bcp14) [RFC2119](https://www.rfc-editor.org/rfc/rfc2119) [RFC8174](https://www.rfc-editor.org/rfc/rfc8174) when, and only when, they appear in all capitals, as shown here. + ### Web of Things Interest and Working Group > [!NOTE] -> This is only a draft. +> This is only a draft until a resolution is reached in both WG/IG and CG. These will be documented via email. +> The CG Charter MAY need changes to satisfy the liaison. Agreeing on this document implies agreeing on the corresponding CG Charter changes. > The content below, until the horizontal line, is composed by the CG based on inputs from the TPAC Joint Meeting, CG Internal Meeting, and Office Hours inputs. Please refer to [Original Input](#original-input) for the discussion results form W3C TPAC 2023. @@ -21,12 +25,12 @@ Note: WG/IG collectively refers to both WoT Interest and Working Group, while CG #### Documents -If the CG intends to produce a document, it must adhere to the [W3C CLA](https://www.w3.org/community/about/process/cla/). -This mandates that the CG doesn't directly edit or open Pull Requests to change WG/IG documents. -Relevant WG/IG documents may incorporate content from CG reports following Section 9 of the [W3C CLA](https://www.w3.org/community/about/process/cla/). +If the CG intends to produce a document, it MUST adhere to the [W3C CLA](https://www.w3.org/community/about/process/cla/). +This mandates that the CG participants don't directly edit or open Pull Requests to change WG/IG documents. +Relevant WG/IG documents MAY incorporate content from CG reports following Section 9 of the [W3C CLA](https://www.w3.org/community/about/process/cla/). Any CG document related to a WG/IG document type (e.g. use cases, bindings), MUST comply with the format and content requirements established by the WG/IG. Deviating from these requirements requires explicit authorization from the WG/IG. -CG reports, as explained by the CG charter, may take the form of Markdown, HTML, or similar formats (TODO: Update CG Charter). +CG reports, as explained by the CG charter, MAY take the form of Markdown, HTML, or similar formats Examples of document types pertinent to WG/IG, eligible as CG reports: @@ -43,7 +47,7 @@ The role of the CG in this collaboration is categorized into two: facilitating a Considering the existence of membership fees for WG/IG participation, fostering more participants to exchange ideas on WoT-related topics becomes relevant. -CG participants can actively and openly exchange ideas on WoT-related topics within the CG, collaborate on non-normative CG reports, and experiment with the implementations of the WG/IG reports. +CG participants CAN actively and openly exchange ideas on WoT-related topics within the CG, collaborate on non-normative CG reports, and experiment with the implementations of the WG/IG reports. ##### Outreach @@ -52,13 +56,13 @@ The CG utilizes various channels under CG administration to reach a broad audien #### Events The WG/IG collaborates on Plugfest events with the CG, thereby leveraging the community to garner a wider audience. -WG/IG may also engage in collaboration with other CGs and liaisons. +WG/IG MAY also engage in collaboration with other CGs and liaisons. Joint meetings, such as Face to Face (F2F) and TPAC meetings, may be convened between WG/IG and the CG. #### Test Cases CG participants are permitted to contribute to the testing activity of the WG/IG Task Forces. -Contributions must adhere to WG requirements regarding quality, folder structure, file naming conventions, and other specifications. +Contributions MUST adhere to WG requirements regarding quality, folder structure, file naming conventions, and other specifications. The CG participants MUST contribute test cases to the CG GitHub repository. --- From 07e9b2edc039210fea93ff6aca8b43007bafff14 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Mon, 4 Dec 2023 17:29:04 +0100 Subject: [PATCH 5/5] incorporate @lu-zero feedback --- liaisons.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/liaisons.md b/liaisons.md index ded341d..cc4a08f 100644 --- a/liaisons.md +++ b/liaisons.md @@ -43,7 +43,7 @@ Examples of document types pertinent to WG/IG, eligible as CG reports: The role of the CG in this collaboration is categorized into two: facilitating a low entry barrier and engaging in outreach. -##### Facilitating a Low Entry Barrier for WoT Involvement +##### Ensuring a Low Entry for WoT Involvement Considering the existence of membership fees for WG/IG participation, fostering more participants to exchange ideas on WoT-related topics becomes relevant. @@ -51,7 +51,7 @@ CG participants CAN actively and openly exchange ideas on WoT-related topics wit ##### Outreach -The CG utilizes various channels under CG administration to reach a broad audience interested in WoT, aligning with the low-entry barrier principle. +The CG utilizes various channels under the CG administration to reach a broad audience interested in WoT, aligning with the low-entry barrier principle. #### Events