Skip to content
HTML Python JavaScript Shell CSS XSLT
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
ARCHIVE move architecture and proposals to archive Jul 16, 2019
MARKETING Create Jun 11, 2019
PRESENTATIONS Merge pull request #884 from danielpeintner/2019-tpac-fukuoka-slides-… Oct 14, 2019
charters remove Proposed from the title tag as well Oct 21, 2019
current-practices Updates Oct 31, 2017
f2f Create Oct 2, 2019
liaisons Add files via upload May 16, 2017
linked-data Slides from TF-LD related to the use of "Feature of Interest" from io… Jun 22, 2018
plugfest Update Oct 2, 2019
proposals Update Oct 4, 2019
scripting Update Feb 9, 2017
security-privacy Updating threat model to use correct terms and new threats Sep 4, 2017
tech-landscape Fix tech landscape editor and date for Feb 14, 2019
testfest add update log for old plugfest May 22, 2019
testing sync testing tools Jul 16, 2019
thing-description corrected JSON-LD context (minor fixes) Mar 20, 2018
ucr-doc Fix Use Cases and Requirements doc for Feb 14, 2019
workshop/ws2 add id to submission.html Aug 6, 2019
.gitignore Remove test output noise Jun 12, 2019
.gitmodules add thingweb-playground as submodule Jan 29, 2019
.nojekyll Try to disable page build Jun 18, 2019
.pr-preview.json pr-preview for the draft WG Charter Aug 28, 2019
FujitsuPreparation180228.pdf Add a new material for meeting. Feb 28, 2018 Remove Gitter and obsolete Travis build info Jun 17, 2019
w3c.json Per Mar 7, 2019

Web of Things

This is a repository for the W3C Web of Things Interest Group.

How to Get Involved

Web-site based Pull-Request

  • Fork the w3c/wot repository into your own account (botton in the top right corner)
  • Navigate to a file in your master branch that you want to change (e.g.,{your-account}/wot/blob/master/charters/wot-ig-2016.html or{your-account}/wot/blob/master/charters/wot-wg-2016.html)
  • Click the edit icon in the upper right (pen next to Raw/Blame/History)
  • Make your edits (e.g., directly in the online editor or by copying the text to your favorite editor and back)
  • Give a meaningful commit message (i.e., do not leave "Update ...")
  • Choose Create a new branch for this commit and start a pull request and give a proper name (e.g., charters-ig-scope-plugfest)
  • Click Propose file change
  • Skip the form, since you do not want to create a PR to your fork. Instead, go to, where GitHub will have found your new branch and will offer to open a pull-request (base fork: w3c/wot, base: master ... head fork: {your-account}/wot, compare: {your-branch}).
  • If you have a separate change proposal for the same file, go back to your master branch and repeat the process from clicking the edit icon.
  • If the pull-request discussion expects you to update your change proposal, go to your branch corresponding to the PR, click the edit icon, and commit directly to that branch.

Command-line based Pull-Request

  • Fork the w3c/wot repository into your own account
  • Create a branch in your fork for one particular topic (e.g., a single IG scope item) with a proper name (e.g., charter-ig-scope-plugfest)
  • Make your edits and commit
  • Push the new branch to your own repository fork
  • GitHub will automatically offer to open a pull-request to w3c/wot (from your new branch to master)

Github Help

You can’t perform that action at this time.