├── .pr-preview.json
├── CONTRIBUTING.md
├── README.md
├── _config.yml
├── charters
└── README.md
├── css
└── main.css
├── index.html
├── js
└── newsfeed.js
├── w3c.json
└── wiki
├── PubStatus
└── README.md
├── README.md
└── index.md
/.pr-preview.json:
--------------------------------------------------------------------------------
1 | {
2 | "src_file": "index.html",
3 | "type": "respec"
4 | }
5 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | Contributions to the Web Performance repositories are intended to become part of Recommendation-track documents governed by the
2 | [W3C Patent Policy](http://www.w3.org/Consortium/Patent-Policy-20040205/) and
3 | [Document License](http://www.w3.org/Consortium/Legal/copyright-documents). To make substantive contributions to specifications, you must either participate
4 | in the relevant W3C Working Group or make a non-member patent licensing commitment.
5 |
6 | If you are not the sole contributor to a contribution (pull request), please identify all
7 | contributors in the pull request comment.
8 |
9 | To add a contributor (other than yourself, that's automatic), mark them one per line as follows:
10 |
11 | ```
12 | +@github_username
13 | ```
14 |
15 | If you added a contributor by mistake, you can remove them in a comment with:
16 |
17 | ```
18 | -@github_username
19 | ```
20 |
21 | If you are making a pull request on behalf of someone else but you had no part in designing the
22 | feature, you can remove yourself with the above syntax.
23 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # W3C Web of Things Working Group – [Web Site](https://www.w3.org/WoT/WG/) Sources
2 |
3 | This repository contains the sources for https://www.w3.org/WoT/WG/
4 |
5 | ## Contributing
6 |
7 | Editorial changes that improve the readability of the pages or correct spelling or grammatical mistakes are welcome, and may be done directly from the Web interface of GitHub.
8 | However, in general changes should be done by pull requests. Please follow the following guidelines for the contribution workflow:
9 | - Fork the repository, then clone the fork.
10 | - Create a local branch in your fork, push commits there, then make a pull request. After the pull request is merged, the local branch can be optionally deleted.
11 | - Sign the commits (use e.g. `git commit -s -m "message"`).
12 | - Make commit messages specific and informative, e.g. by including issue numbers.
13 | - For bigger commits, the first line of the commit message should be a short summary, then after an empty line a more detailed description or rationale of the commit should follow.
14 | - Similarly, pull request comments should follow the same principles as commit messages.
15 | - For HTML files please provide a link to a rendered diff in the pull request, using the [W3C HTML diff tool](https://services.w3.org/htmldiff) for comparing two versions of the same file from different forks and branches. See an example [here](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fw3c.github.io%2Fwot-scripting-api%2F&doc2=https%3A%2F%2Fraw.githubusercontent.com%2Fdanielpeintner%2Fwot-scripting-api%2Fmaster%2Findex.html).
16 | Note that the tool expects the "raw" link to the files, for instance this file's raw link is [https://github.com/w3c/wotwg/raw/master/README.md](https://github.com/w3c/wotwg/raw/master/README.md) that resolves to [https://raw.githubusercontent.com/w3c/wotwg/master/README.md](https://raw.githubusercontent.com/w3c/wotwg/master/README.md), and can be obtained by clicking on the `Raw` button when the file is displayed on the github web page.)
17 | - Pull requests should be reviewed and approved by someone else (typically an editor), then approved and merged by an editor or chair.
18 | - The preferred way to merge a pull request is by creating a merge commit, or by squashing (select the option from the pull-down menu right to the merge button). To keep full history, rebase merge is fine if commits are well defined and formatted.
19 |
20 | Please read [CONTRIBUTING.md](CONTRIBUTING.md), about licensing contributions.
21 |
--------------------------------------------------------------------------------
/_config.yml:
--------------------------------------------------------------------------------
1 | gems:
2 | - jekyll-redirect-from
3 |
--------------------------------------------------------------------------------
/charters/README.md:
--------------------------------------------------------------------------------
1 | Charters for the WoT WG. Those with "draft" in the name are not yet official.
2 |
--------------------------------------------------------------------------------
/css/main.css:
--------------------------------------------------------------------------------
1 | body {
2 | margin:0;padding:0;
3 | background: white;
4 | max-width: 100%;
5 | font-family: Helvetica,sans-serif;
6 | }
7 |
8 | h1 {
9 | color: black;
10 | text-align: center;
11 | font-size: 2rem;
12 | font-weight: 500;
13 | text-shadow: 1px 1px #ccc;
14 | }
15 | h2, h3, h4, h5, h6 {
16 | font-weight: 300;
17 | }
18 | h2 {
19 | font-size: 1.3rem;
20 | border-bottom: 3px solid #eee;
21 | }
22 | h3 { font-size: 1.1rem; }
23 | ul, ul li {
24 | display: block;
25 | margin: 0; padding: 0;
26 | }
27 |
28 | a, a:visited, a:hover, a:focus {
29 | color: #4184F3;
30 | background: transparent;
31 | }
32 | a, a:visited {
33 | text-decoration: none;
34 | }
35 | a:hover, a:focus {
36 | text-decoration: underline;
37 | }
38 |
39 | /*** header ***/
40 | header {
41 | background: #005A9C url("/Icons/w3c_home_white_transp.png") no-repeat left center;
42 | color: white;
43 | padding-left: 68px;
44 | margin: 0;
45 | }
46 | header ul {
47 | display: flex;
48 | flex-wrap: wrap;
49 | justify-content: space-around;
50 | }
51 | header a, header a:visited {
52 | border-bottom: 1px solid #005A9C;
53 | display: block;
54 | color: white;
55 | text-decoration: none;
56 | font-weight: bold;
57 | padding: 0.5rem;
58 | }
59 | header a:hover, header a:focus {
60 | background: white;
61 | color: black;
62 | text-decoration: none;
63 | font-weight: bold;
64 | }
65 |
66 | /*** main ***/
67 | main {
68 | display: flex;
69 | flex-flow: column;
70 | background: white;
71 | color: black;
72 | line-height: 1.2;
73 | margin-left: 1rem;
74 | margin-right: 1rem;
75 | }
76 |
77 | main table {
78 | width: 100%;
79 | }
80 |
81 | main > * {
82 | padding-right: 0;
83 | padding-left: 0;
84 | }
85 |
86 | main nav {
87 | order: 1;
88 | margin-top: 1rem;
89 | margin-bottom: 1rem;
90 | padding-top: 0.5ex;
91 | padding-bottom: 0.5ex;
92 | border-top: 2px solid #ccc;
93 | }
94 | main nav h3 {
95 | padding-bottom: 0.2ex;
96 | border-bottom: 3px solid #eee;
97 | }
98 | main nav li {
99 | font-weight: 500;
100 | padding: 0.5ex;
101 | border-bottom: 1px solid #ccc;
102 | }
103 |
104 | aside {
105 | margin-top: 1rem;
106 | margin-bottom: 1rem;
107 | border-top: 2px solid #ddd;
108 | }
109 |
110 | figcaption {
111 | text-align: left; font-style: italic; font-size: small;
112 | }
113 | #mission {
114 | border-bottom: 1px solid #ddd;
115 | }
116 |
117 | #mission p {
118 | font-style: italic;
119 | margin-left: 2rem;
120 | margin-right: 2rem;
121 | }
122 |
123 | article {
124 | margin-bottom: 3rem;
125 | border-bottom: 1px solid #ddd;
126 | }
127 | article:last-child {
128 | border-bottom: none;
129 | }
130 |
131 | article h3 {
132 | padding-top: 0.5ex;
133 | margin: 0;
134 | width: 100%;
135 | }
136 |
137 | /*** footer ***/
138 |
139 | footer {
140 | background: #005A9C;
141 | color: white;
142 | margin: 0;
143 | padding-right: 0.5rem;
144 | padding-left: 0.5rem;
145 | padding-top: 0.5rem;
146 | padding-bottom: 0.5rem;
147 | text-align: left;
148 | display: flex;
149 | flex-direction: row;
150 | justify-content: space-around;
151 | }
152 | footer p { margin: 0; padding: 0;}
153 | footer a, footer a:visited, footer a:focus, footer a:hover {
154 | color: white;
155 | font-weight: bold;
156 | }
157 |
158 | @media screen and (min-width: 78rem) {
159 | main {
160 | flex-flow: row;
161 | justify-content: space-around;
162 | align-items: flex-start;
163 | }
164 | main > * {
165 | padding-right: 1rem;
166 | padding-left: 1rem;
167 | }
168 | main nav {
169 | order: 0;
170 | border-top: none;
171 | border-right: 2px solid #ccc;
172 | }
173 | main nav h3 {
174 | text-align: right;
175 | }
176 | main #content {
177 | max-width: 50rem;
178 | }
179 | aside {
180 | max-width: 20em;
181 | border-top: none;
182 | border-left: 2px solid #ccc;
183 | }
184 | }
185 |
--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | W3C Web of Things Working Group
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
26 |
27 |
28 |
29 |
63 |
64 |
65 |
Web of Things Working Group
66 |
67 |
68 |
Our Mission
69 |
70 | The Web of Things seeks to counter the fragmentation of
71 | the IoT through standard complementing building blocks
72 | (e.g., metadata and APIs) that enable easy integration
73 | across IoT platforms and application domains. This Working
74 | Group Charter covers those aspects that
75 | the Web
76 | of Things Interest Group believes are mature enough to
77 | progress to W3C Recommendations. Further background is
78 | available in the accompanying
79 | white paper.
80 |