Skip to content

Commit

Permalink
Merge pull request #1997 from w3c/ege-respec-config-for-tdnext
Browse files Browse the repository at this point in the history
Preparation for TD Next Work
  • Loading branch information
egekorkan committed Apr 16, 2024
2 parents 1bcd99e + 83c6068 commit 1e16b24
Show file tree
Hide file tree
Showing 4 changed files with 32 additions and 52 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ This repository covers the W3C Web of Things Thing Description family of specifi
### Thing Description 1.0

- [REC](https://www.w3.org/TR/2020/REC-wot-thing-description-20200409/) - Official recommendation version of the Thing Description 1.0
- [GitHub branch for the 1.1 REC](https://github.com/w3c/wot-thing-description/tree/wot-td-1.0) - Branch that corresponds to the Thing Description 1.0 files
- [GitHub branch for the 1.0 REC](https://github.com/w3c/wot-thing-description/tree/wot-td-1.0) - Branch that corresponds to the Thing Description 1.0 files
- [errata](https://w3c.github.io/wot-thing-description/errata.html) - Errata for version 1.0
- [Implementation Report](https://w3c.github.io/wot-thing-description/testing/report.html) - Implementation report of the TD 1.0 features

Expand Down
40 changes: 15 additions & 25 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -3,18 +3,17 @@
<head>
<!-- <link rel="stylesheet" href="testing/atrisk.css"> -->
<meta charset="utf-8" />
<title>Web of Things (WoT) Thing Description 1.1</title>
<title>Web of Things (WoT) Thing Description - Next</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
<script class="remove">
var respecConfig = {
specStatus: "ED",
crEnd: "2019-06-13",
previousMaturity: "FPWD",
previousPublishDate: "2020-11-24",
implementationReportURI: "https://w3c.github.io/wot-thing-description/testing/report11.html",
//, processVersion: 2020
//, wgPatentPolicy: "PP2017" // deprecated, "group" option sets this automatically
shortName: "wot-thing-description11",
// crEnd: "2019-06-13",
// previousMaturity: "REC",
// previousPublishDate: "2023-12-05",
prevRecURI: "https://www.w3.org/TR/2023/REC-wot-thing-description11-20231205/",
// implementationReportURI: "https://w3c.github.io/wot-thing-description/testing/report11.html",
shortName: "wot-thing-description-next", // temporary for now
copyrightStart: 2017,
noLegacyStyle: true,
inlineCSS: true,
Expand Down Expand Up @@ -161,15 +160,6 @@
}
},
otherLinks: [
{
key: "Previous Recommendation",
data: [
{
value: "https://www.w3.org/TR/2020/REC-wot-thing-description-20200409/",
href: "https://www.w3.org/TR/2020/REC-wot-thing-description-20200409/"
}
]
},
{
key: "Contributors",
data: [
Expand Down Expand Up @@ -377,7 +367,7 @@
<section id="abstract">
<p>
This document describes a formal information model and a common representation for a Web of Things (WoT) Thing
Description 1.1. A Thing Description describes the metadata and interfaces of <a>Things</a>, where a
Description Next Version. A Thing Description describes the metadata and interfaces of <a>Things</a>, where a
<a>Thing</a> is an abstraction of a physical or virtual entity that provides interactions to and participates in
the Web of Things. Thing Descriptions provide a set of interactions based on a small vocabulary that makes it
possible both to integrate diverse devices and to allow diverse applications to interoperate. Thing
Expand All @@ -392,9 +382,9 @@
</p>

<p>
This specification describes a superset of the features defined in Thing Description 1.0
[[WOT-THING-DESCRIPTION10]]. Unless otherwise specified, documents created with version 1.0 of this
specification remain compatible with Thing Description 1.1.
This specification continues the work of [[WOT-THING-DESCRIPTION11]] with no guarantees on backwards
compatibility. In case of no backwards compatibility, there will be concrete guidelines for implementers to
migrate to the new version.
</p>
</section>

Expand All @@ -421,18 +411,18 @@
<li>A <a href="#td-writeall-consumer">behavioral assertion</a> for <code>writeallproperties</code> that allows rejection of incomplete writes.</li>
</ul>
-->
<p>
<!-- <p>
Future updates to this specification may incorporate
<a href="https://www.w3.org/2021/Process-20211102/#allow-new-features">new features</a>.
</p>
</p> -->

<p>
<!-- <p>
The Web of Things Working Group intends to submit this document for consideration as a
<abbr title="World Wide Web Consortium">W3C</abbr> Proposed Recommendation after at least the minimum CR review
period has passed. However, before PR transition is requested, any features or assertions currently marked as
at-risk that did not appear in the TD 1.0 specification and do not have at least two implementations at that
time will either be removed or converted into informative statements, as appropriate.
</p>
</p> -->
</section>

<section id="introduction" class="informative">
Expand Down
40 changes: 15 additions & 25 deletions index.template.html
Original file line number Diff line number Diff line change
Expand Up @@ -3,18 +3,17 @@
<head>
<!-- <link rel="stylesheet" href="testing/atrisk.css"> -->
<meta charset="utf-8" />
<title>Web of Things (WoT) Thing Description 1.1</title>
<title>Web of Things (WoT) Thing Description - Next</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
<script class="remove">
var respecConfig = {
specStatus: "ED",
crEnd: "2019-06-13",
previousMaturity: "FPWD",
previousPublishDate: "2020-11-24",
implementationReportURI: "https://w3c.github.io/wot-thing-description/testing/report11.html",
//, processVersion: 2020
//, wgPatentPolicy: "PP2017" // deprecated, "group" option sets this automatically
shortName: "wot-thing-description11",
// crEnd: "2019-06-13",
// previousMaturity: "REC",
// previousPublishDate: "2023-12-05",
prevRecURI: "https://www.w3.org/TR/2023/REC-wot-thing-description11-20231205/",
// implementationReportURI: "https://w3c.github.io/wot-thing-description/testing/report11.html",
shortName: "wot-thing-description-next", // temporary for now
copyrightStart: 2017,
noLegacyStyle: true,
inlineCSS: true,
Expand Down Expand Up @@ -161,15 +160,6 @@
}
},
otherLinks: [
{
key: "Previous Recommendation",
data: [
{
value: "https://www.w3.org/TR/2020/REC-wot-thing-description-20200409/",
href: "https://www.w3.org/TR/2020/REC-wot-thing-description-20200409/"
}
]
},
{
key: "Contributors",
data: [
Expand Down Expand Up @@ -377,7 +367,7 @@
<section id="abstract">
<p>
This document describes a formal information model and a common representation for a Web of Things (WoT) Thing
Description 1.1. A Thing Description describes the metadata and interfaces of <a>Things</a>, where a
Description Next Version. A Thing Description describes the metadata and interfaces of <a>Things</a>, where a
<a>Thing</a> is an abstraction of a physical or virtual entity that provides interactions to and participates in
the Web of Things. Thing Descriptions provide a set of interactions based on a small vocabulary that makes it
possible both to integrate diverse devices and to allow diverse applications to interoperate. Thing
Expand All @@ -392,9 +382,9 @@
</p>

<p>
This specification describes a superset of the features defined in Thing Description 1.0
[[WOT-THING-DESCRIPTION10]]. Unless otherwise specified, documents created with version 1.0 of this
specification remain compatible with Thing Description 1.1.
This specification continues the work of [[WOT-THING-DESCRIPTION11]] with no guarantees on backwards
compatibility. In case of no backwards compatibility, there will be concrete guidelines for implementers to
migrate to the new version.
</p>
</section>

Expand All @@ -421,18 +411,18 @@
<li>A <a href="#td-writeall-consumer">behavioral assertion</a> for <code>writeallproperties</code> that allows rejection of incomplete writes.</li>
</ul>
-->
<p>
<!-- <p>
Future updates to this specification may incorporate
<a href="https://www.w3.org/2021/Process-20211102/#allow-new-features">new features</a>.
</p>
</p> -->

<p>
<!-- <p>
The Web of Things Working Group intends to submit this document for consideration as a
<abbr title="World Wide Web Consortium">W3C</abbr> Proposed Recommendation after at least the minimum CR review
period has passed. However, before PR transition is requested, any features or assertions currently marked as
at-risk that did not appear in the TD 1.0 specification and do not have at least two implementations at that
time will either be removed or converted into informative statements, as appropriate.
</p>
</p> -->
</section>

<section id="introduction" class="informative">
Expand Down
2 changes: 1 addition & 1 deletion proposals/project-management/project-management.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ This allows us to limit the load of a person per 1-2 week time frame and thus pr

- **Step 0:** An issue shows up.
- **Step 1:** The TF acts fast to categorize and refine it. The steps are detailed below and reflected also in the sorting table example towards the end. Step 2, 3 or 4 is picked based on categorization in this step. The initial categorization can happen outside of the calls but issues that need thorough analysis and refinement would typically in a meeting.
1. **Left Path:** The issue is identified to have Use Case relevant content where a deeper understanding is needed. In **Step 2** It is moved to the Use Cases repository.
1. **Left Path:** The issue is identified to have Use Case relevant content where a deeper understanding is needed. In **Step 2** It is moved to the Use Cases repository.
2. **Right Path:** The issue is created by the Use Cases TF. In **Step 3** the TD TF analyzes it, which can result in smaller issues, more description etc. This is also reflected in the sorting table. Note that this is closely related with the [Use Cases Process](https://github.com/w3c/wot-usecases/blob/main/Process.md) where the result of the gap analysis and feature definition are the inputs to this point.
3. **Middle Path:** The issue is identified to be handled by the TF alone. These are issues about tooling, editorial fixes, etc. The TF labels it and moves it to the relevant column in the sorting table.
- Note: During the refinement of an issue (understanding, labeling) in step 3 or step 4, it is placed in a column in the sorting table based on the category. Categories such as `bindings`, `data mapping`, `tooling`, which are [work items](https://github.com/w3c/wot/blob/main/planning/ThingDescription/work-items.md) (big topics), are separate a columns. Categories such as `editorial`, `bug` are grouped in one column called `other`.
Expand Down

0 comments on commit 1e16b24

Please sign in to comment.