Main WoT WebConf

From Web of Things Interest Group
Jump to: navigation, search

The Main WoT Web Conference is for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or follow the links below to the individual task force Wiki pages.

Contents

WebConf Information

Call Logistics

Please check times carefully in your timezone. Daylight Savings time started in the US on March 13. All meetings are set in W3C relative US Eastern time. On March 27, most places in Europe will also start Daylight savings. Therefore in Europe and in places without daylight savings, times for meetings will shift around these dates.

Time

Wednesdays at

  • 8am US Eastern
  • 5am US Pacific
  • 1pm GMT (and UTC, for now)
  • 2pm Central Europe
  • 10pm Japan

WebEx


Note: To avoid a repetition of fraudulent calls, the ICS files, host codes and meeting passwords should not be shared on the public list or a public wiki or other web page, e.g. in the agenda or minutes.

IRC

The IRC is used for the minutes, speaker queue, and sharing links etc.

Schedule

Deliverable and F2F Meeting Plan

The schedule is under discussion; please see the draft in the wot repo.

Special Meetings to Discuss Next Charter


Preparation

Session 1

Day 1 - Jan 16

Length: 1h

Chair: McCool

Scribe: Ege

Day 2 - Jan 17

Length: 1h

Chair: McCool

Scribe: Kaz

Carried forward:

  • Security
    • Onboarding process
    • Consolidation of security assertions
    • Key distribution e.g. via DID
  • Discovery
    • Geolocation (TD/data vocab + query filters)
    • Normative query language (e.g. JSON Path)
    • Registry for Introductions?
  • Architecture update
  • TD update
  • Profile update
  • Scripting

Day 3 - Jan 18

Length: 2h

Chair: Sebastian

Scribe: Michael McCool (first hour), Michael Koster (second hour)

Day 4 - Jan 19

Length: 1h

Chair: McCool

Scribe: Kaz/?

  • Organization (10m)
    • Agenda
  • Review Current Draft
  • Issues and PRs
  • Next Steps
  • AOB

Session 2

Day 2 - Feb 14

Length: 2h

Chair: McCool

Scribe: Kaz

Day 2 - Feb 15

Length: 2h

Chair: McCool

Scribe: Sebastian/Daniel

  • Organization (5m)
    • note: we need to add an issue to the strategy funnel repo for this rechartering procedure - Kaz will work on that.
  • Review Issues and PRs
  • Discuss remaining issues and assign Owners
  • Review and close old PRs and issues, e.g. in wot

Day 3 - Feb 16

Length: 2h

Chair: McCool

Scribe: Cristiano/Ege

  • Organization (5m)
  • Review Issues, PRs, and Status
  • Discuss remaining issues and assign Owners
  • Next Step
    • When are we done?
      • Any other W3C groups or external groups to mention?
      • Remaining work - how to review and finalize?
      • Schedule
    • Strategy funnel issue

Session 3

Day 1 - Feb 21

Length: 1h

Chair: McCool

Scribe: Lagally

Day 2 - Feb 23

Length: 1h

Chair: McCool

Scribe: Luca

  • Organization (5m)
  • Review Issues, PRs, and Status
  • Document Organization
  • Next Steps
    • Are we done?
    • Strategy funnel issue

Session 4

Day 1 - Feb 27

Length: 1h

Chair: McCool

Scribe: Andrea

Day 2 - Feb 28

Length: 1h

Chair: McCool

Scribe: Kaz

  • Organization (5+5m)
  • Review Issues, PRs, and Status (45m)
  • Next Steps (5m)
    • Are we done?
    • if so, create strategy funnel issue, resolution text
    • if not...

Day 3 - Mar 1

Length: 1h

Chair: McCool

Scribe: Cristiano

  • Organization (5+5m)
    • Daylight Savings announcement
  • Review Issues, PRs, and Status (45m)
    • Mission Statement
    • Scope
    • Architecture Status

Day 4 - Mar 2

Length: 1h

Chair: McCool

Scribe: Kaz

  • Organization (5+5m)
  • Review Issues, PRs, and Status (45m)
  • Next Steps (5m)
    • Update extension schedule
    • Are we done?
    • if so, create strategy funnel issue, resolution text
    • if not...

Session 5

Day 1 - Mar 8

Length: 45m

Chair: McCool

Scribe:

  • Organization (5m)
  • Review Issues, PRs, and Status (35m)
  • Next Steps (5m)
    • Update extension schedule
    • Are we done?
    • if so, create strategy funnel issue, resolution text
    • if not... mtg Mar 9 during Arch slot?

Day 2 - Mar 9

Length: 1h (-5m)

Chair: McCool

Scribe:

  • Organization (5m)
  • Process
    • What needs to be decided?
      • Making Architecture normative or informative
        • What are some smaller, more manageable questions that we can answer first?
      • If Architecture is not normative, what do we do instead?
        • Moving assertions to other deliverables is just one option
      • Where can existing *categories* of normative content be moved, in theory?
        • ... but probably not details of individual assertions
        • better to defer detailed discussion/refinement of individual assertions to new charter
    • How can we make this decision?
      • Process, analysis, proposals, resolution, consensus or ... (gasp) vote?
    • What is the deadline?
  • Related Issues
    • Should Scripting API be normative?
      • Some assertions in Architecture, e.g. about the runtime, are there because the Scripting API is not normative.
    • Should there be a normative Security and Privacy document?
      • Some assertions about secure transport (for example) do not really belong in existing deliverables.
      • Proposed new topics like onboarding also don't really fit into existing deliverables.
    • What constitutes "evidence of implementability"?
      • In some cases, we have assertions at risk even though the assertion is clearly implementable, i.e. support for secure updates or use of DTLS 1.3.
  • Next Steps (5m)
    • Update extension schedule
    • Are we done?
    • if so, create strategy funnel issue, resolution text
    • if not... when do we meet again? See: Process, above

Session 6

Day 1 - Mar 13

Length: 1h (-5m)

Chair: McCool

Scribe: Luca

Day 2 - Mar 15

Length: 30m (part of main call)

Chair: McCool

Scribe: Sebastian/Kaz

Day 3 - Mar 16

Length: 1h - 5m Chair: McCool

Scribe: Kaz

Session 7

Day 1 - Mar 22

Length: 30m (part of main call)

Chair: McCool

Scribe: Sebastian/Kaz

  • Organization (5m)
    • Draft Charter
    • need a resolution to send for AC review
      • When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
  • Identifying what to be resolved before the AC Review
    • Mission, Motivation, Scope
      • WoT deployment for actual IoT industries based on stronger liaisons with related SDOs
    • Normative delivarables - abstract description of each expected deliverable (including why it's necessary)
      • Architecture
      • Discovery
      • Thing Description (including Binding)
      • Profile
    • Informative Deliverables
      • Use Cases and Requirements
      • Security and Privacy GUidelines
      • Test suite / Implementationr reports
      • Best Practices
      • Scripting API
      • Binding sub-documents
    • relationship among deliverables should be clarified (separately from the Charter discussion itself)
    • Timeline
      • What to be done by when?
    • Coordination
      • policy on how to deal with contributions and liaisons, etc.
      • Relationship (1) among WoT Groups and (2) between WoT and other SDOs should be clarified (separately from the Charter discussion itself)
  • How to deal with the details?
    • We should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked.
  • Remaining PRs and Issues - https://github.com/w3c/wot-charter-drafts/labels/WG%20New%20Charter%20Plans%202023
  • Contributions - which PRs and Issues are related to which topics above?
  • Next Steps - timeline for the rechartering procedure

Day 2 - Mar 23

Length: 30m (part of main call)

Chair: McCool

Scribe: Sebastian/Kaz

  • Organization (5m)
    • Draft Charter
    • need a resolution to send for AC review
      • When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
  • Identifying what to be resolved before the AC Review
    • Mission, Motivation, Scope
      • WoT deployment for actual IoT industries based on stronger liaisons with related SDOs
    • Normative delivarables - abstract description of each expected deliverable (including why it's necessary)
      • Architecture
      • Discovery
      • Thing Description (including Binding)
      • Profile
    • Informative Deliverables
      • Use Cases and Requirements
      • Security and Privacy GUidelines
      • Test suite / Implementationr reports
      • Best Practices
      • Scripting API
      • Binding sub-documents
    • relationship among deliverables should be clarified (separately from the Charter discussion itself)
    • Timeline
      • What to be done by when?
    • Coordination
      • policy on how to deal with contributions and liaisons, etc.
      • Relationship (1) among WoT Groups and (2) between WoT and other SDOs should be clarified (separately from the Charter discussion itself)
  • How to deal with the details?
    • We should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked.
  • Remaining PRs and Issues - https://github.com/w3c/wot-charter-drafts/labels/WG%20New%20Charter%20Plans%202023
  • Contributions - which PRs and Issues are related to which topics above?
  • Next Steps - timeline for the rechartering procedure

Session 8

Day 1 - Mar 27

Length: 2h (replacing Scripting and Security)

Chair: McCool

Scribe: Luca

Day 2 - Mar 29

Length: 30m (part of main call)

Chair: McCool

Scribe:

Upcoming Publication Moratoriums

  • None currently

Events

Past


Upcoming

  • TBD

Useful resources

Ongoing Items

Ongoing Action Items

Publication

Wide Review

Communications
Done
Mostly Done
  • TD: TAG: still under review, TAG has done first pass, "largely happy", but want to re-review after seeing Architecture
In Progress
Drafts
To Do
  • Clean up and label issues (all repos)

Explainers

NECESSARY for wide review process. Would be good to link them together.

Process

Resources

  • Tools for W3C Spec Work
  • Useful material for process, minute-taking IRC setup, wide review, etc.
  • Any comments or requests for improvement?

Editors

  • Ongoing topics to discuss in Editor's call:
    • Terminology discussion
    • Document consistency check between Architecture and other specs (Scripting, Discovery)
    • Draft implementation reports
    • Schedule review

Use Case Review

Collaborations

Status of collaborations with Other W3C Groups.

WoT CG

WoT Japanese CG

Spatial Data on the Web IG

  • Ontology needed for geolocation data for use with WoT
  • Overlap with some external liaisons, e.g. with OGC, OpenAR, IEEE
  • Joint discussion with the Spatial Data on the Web WG (SDW-WG) on Jun 23 - draft minutes
    • joint call during TPAC not possible, instead want online meeting
    • We need to define next-charter deliverables, e.g. geolocation ontologies, discovery extensions, etc.
    • Next joint meeting on July 21 during the SDW call

Accessibility IG

  • To Do: Update/Add Use Cases and Requirements

Charters

WG Rechartering

  • AFTER the 12mo extension
  • Draft WG Charter for the next period, 2022
  • To do: update draft based on latest template for 2023
  • To do: update deliverables, calendar, etc.
  • See https://github.com/w3c/wot/issues/978
  • Need to finalize and submit the new WG charter a few months before the end of the extended charter
  • Planned meetings Jan 16-18 to finalize new draft
    • Monday Jan 16: 8am-9am Eastern
    • Tuesday Jan 17: 8am-9am Eastern
    • Wednesday Jan 18: 8am-10am Eastern
  • should consider a common model for IoT security as well as data model and protocol

Liaisons

Status of engagements with external standards organizations.

OPC UA

ITU-T SG20

  • Next steps
    • ITU-T wants to "... focus on ontologies, digital twin and AI related aspects in the smart city context."
    • Plan to develop a document on a new smart cities ontology as an initial step.
    • Gyu Myoung Lee shared slides from WF-IoT
    • Next SG20 mtg is 19-28 July 2022; need further followup before then
    • We have proposed Gyu Myoung Lee joining a near-future main call for a 15 discussion

ECHONET

  • Next steps:
    • Clearly define concrete use cases and technical requirements for ECHONET/WoT Binding
    • Gap analysis: Identify missing features needed in WoT-next (to be covered in next charter)
    • Initial discussion to be done within the WoT-JP CG while we (WoT-WG/IG) are concentrating on spec finalization.

IEC CDD (Common Data Dictionary)

  • Ontologies for various industries - IEC61360, IEC62656
    • Units are a current topic of discussion, relevant to Profiles
  • Previous contacts with ISO TC184/SC4:
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • New contact with current IEC SC 3D - talking about how to proceed
    • They'd like to start with collaboration with the WoT-JP CG and bring feedback/input to the WoT-WG later.
    • Kaz will join their meeting on July 22 to confirm the next steps.
    • They already have liaison with ISO TC184/SC4 and ECLASS.

ECLASS

  • overlap with IEC discussion (see above)
  • need clarification on how to refer to their ontologies from TD
  • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
  • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed

T2TRG/IETF

OneDM

OGC/OpenAR - Geospatial Data

  • Overlap in collaboration with Spatial Data on the Web IG
  • some discussion during the Use Cases call on Jan-25
  • Continue the discussion in Use Cases call

Microsoft DTDL

  • resources
  • Joint discussion with Microsoft DTDL on Tuesday, June 21
    • Minutes
    • Next steps:
      • Another meeting in about month, in UC slot: July 19
      • Agenda:
        • Goal is interconversion
        • need test plugfest project
        • need mapping of features, identification of gaps in our specs (both TD and Discovery), vocabulary

IEEE P2874

Possible

Cancellations and Schedule Updates

NOTE: If a meeting is marked as "tentative" in the W3C Calendar it means it is cancelled - people editing such calls should also put "CANCELLED" in the title. We are not "cancelling" meetings in that system since it can't be undone.

  • Monday
    • Scripting API call cancelled on March 20
  • Tuesday
    • Use Case
      • Next call - March 14 (8am EASTERN, 2pm CET)
      • hold the meeting every Tuesday for a while
    • Editors' calls only if necessary
    • Marketing
      • Now 30m only, starting a half-past the hour
      • Chairs and team contact will generally attend only first meeting each month
  • Wednesday
    • Profile cancelled March 29
  • Thursday
    • Architecture cancelled March 30

Note: Please look in W3C Calendar for updated WebEx invites for Use Cases and Editor's calls. Note that if you see both a canceled meeting and an "active" meeting, it means I had to "uncancel" a meeting by creating a new entry, and the meeting will be held.

Agenda

29 March 2023

Chair: McCool

Regrets: any?

Scribe: Koster

  • Guests, New Members, and Invited Experts
  • Minutes
  • Quick updates
    • any?
  • Planning
    • Test Dev Meeting
      • First meeting for TD
        • Global Meeting: second hour of TD slot - 3/29 15:00 UTC
        • JP Meeting: 3/28 14:00 JST - done yesteday
      • Second meeting for Architecture - to be decided
        • Use Arch call Mar 30 to finalize Dev review material for Arch?
        • Arch call cancelled March 30, reviews to be done offline
        • Dev meetings for Arch on April 12? (Second hour of TD call slot)
      • Third meeting for Discovery - to be decided
        • Use Discovery calls Apr 3/10 to prep Dev review material for Discovery?
        • Dev meetings for Discovery on April 17? (Discovery call slot)
    • Testfest during the week of April 3
      • 3 days - 1h meeting a day
      • Tuesday at 10am Eastern (after use cases call)
      • Wed at 9am Eastern (testing call)
      • Thursday at 9am Eastern (after arch call)
    • Binding Meetup
      • JP Meetup by WoT-JP CG
        • two more meetings with IPA DADC (Takenaka) and NHK to be organized after the Test Dev Meeting
      • What about a possible Global Meetup?
  • Publications progress check
  • WG Charter
    • Draft proposed WG Charter
    • How to proceed?
      • need a resolution to send for AC review
      • continue Charter Meetings... see Session 6, Day 2 agenda
        • When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
        • what to be described by the Charter
        • abstract description of each expected deliverable (including why it's necessary)
        • relationship among deliverables
        • policy on how to deal with contributions and liaisons, etc.
      • we should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked
    • Testimonials
      • Need to start collecting these, note they are now separate from implementation descriptions
      • Who/For What/Until When/How?
    • Societal Impact Questionnaire
  • Review Liaisons - should be discussed as part of the new WG Charter topic.
  • Review Collaborations
    • Anything?
  • Review Ongoing Action Items
  • TF Reports
  • AOB?

22 March 2023

Chair: Sebastian

Regrets: McCool

Scribe: Cristiano

  • Guests, New Members, and Invited Experts
  • Minutes
  • Quick updates
    • Use Case policy discussion
      • Policy for use case collection to be decided, e.g., how to get use cases from which industry how, and how to extract requirements from those industry-based use cases
      • Use Case Requirements - Template - Geolocation PR
      • Should be discussed during the Use Cases calls.
  • Planning
    • Testing
      • Testing Developer Meeting during the week of March 27 - Doodle
        • Global Meeting:
          • Reuse second hour of TD slot: 3/29 15:00 UTC
          • Use Architecture call too?
        • JP Meeting:
          • 3/30 11:00 JST
          • Note: Takenaka can't make March 30th, so should consider 3/28 13:00 JST as well.
          • WoT-JP guys need clarification on what all the at-risk features really mean before the JP Meeting.
        • Is 1h enough for both Arch and TD? What about Discovery?
        • We may need to have additional Dev meetings...
        • What order do we do them in? Material for TD is mostly ready, others not.
        • Proposal (McCool):
          • Use Arch call Mar 23 to finalize charter
          • Use Dev meetings Mar 28/29 to review TD assertions
          • Use Arch call Mar 30 to finalize Dev review material for Arch
          • Use Discovery calls Apr 3/10 to prep Dev review material for Discovery
          • Schedule additional Dev meetings for Arch and Discovery, maybe April 5 and April 12.
      • Testfest during the week of April 3
        • 3 days - 1h meeting a day
        • Tuesday at 10am Eastern (after use cases call)
        • Wed at 9am Eastern (testing call)
        • Thursday at 9am Eastern (after arch call)
    • Binding Meetup
      • JP Meetup by WoT-JP CG
        • two more meetings planned with IPA DADC and NHK to be organized
      • What about a possible Global Meetup?
  • Publications progress check
  • WG Charter
    • Draft proposed WG Charter
    • How to proceed?
      • need a resolution to send for AC review
      • continue Charter Meetings... see Session 6, Day 2 agenda
        • When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
        • what to be described by the Charter
        • abstract description of each expected deliverable (including why it's necessary)
        • relationship among deliverables
        • policy on how to deal with contributions and liaisons, etc.
      • we should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked
    • Testimonials
      • Need to start collecting these, note they are now separate from implementation descriptions
      • Who/For What/Until When/How?
    • Societal Impact Questionnaire
  • Review Liaisons - should be discussed as part of the new WG Charter topic.
  • Review Collaborations
    • Anything?
  • Review Ongoing Action Items
  • TF Reports
  • AOB?

15 March 2023

Chair: McCool

Regrets: any?

Scribe: Sebastian

  • Guests, New Members, and Invited Experts
  • Minutes - review skipped?
  • Quick updates
    • Use Cases call on March 14 cancelled due to DST change confusion - When to have the next call?
      • Discussion:
        • Policy for use case collection to be decided, e.g., how to get use cases from which industry how, and how to extract requirements from those industry-based use cases
        • Use Case Requirements - Template - Geolocation PR
    • Cancellations and TF Meeting Schedule
  • Planning
    • Testing
      • Testfest during the week of March 20 - Doodle
        • Current candidates
          • Monday, 3/20 12:00 UTC (5:00 PDT, 9:00 ADT, 13:00 CET, 21:00 JST)
          • Monday, 3/20 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST)
          • Monday, 3/20 14:00 UTC (7:00 PDT, 11:00 ADT, 15:00 CET, 23:00 JST)
          • Wednesday, 3/22 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST)
          • Thursday, 3/23 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST)
          • Thursday, 3/23 14:00 UTC (7:00 PDT, 11:00 ADT, 15:00 CET, 23:00 JST)
      • Testing Developer Meeting during the week of March 27 - Doodle
        • Global Meeting candidates:
          • 3/27 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST) w/o Toumura
          • 3/28 12:00 UTC (5:00 PDT, 9:00 ADT, 13:00 CET, 21:00 JST) w/o Lagally
          • 3/28 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST) w/o Lagally
          • 3/29 01:00 UTC (18:00-1d PDT, 21:00-1d ADT, 02:00 CET, 10:00 JST) w/o Lagally
          • 3/29 02:00 UTC (19:00-1d PDT, 22:00-1d ADT, 03:00 CET, 11:00 JST) w/o Lagally
          • 3/29 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST) w/o Lagally
          • 3/30 01:00 UTC (18:00-1d PDT, 21:00-1d ADT, 02:00 CET, 10:00 JST) w/o Lagally
          • 3/30 02:00 UTC (19:00-1d PDT, 22:00-1d ADT, 03:00 CET, 11:00 JST) w/o Lagally
          • 3/30 09:00 UTC (02:00 PDT, 05:00 ADT, 11:00 CET, 18:00 JST) w/o Koster
          • 3/30 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST) w/o Lagally
          • 3/30 14:00 UTC (7:00 PDT, 11:00 ADT, 15:00 CET, 23:00 JST) w/o Lagally
        • JP Meeting candidates
          • 3/28 13:00 JST
          • 3/30 11:00 JST

8 March 2023

Chair: McCool

Regrets: Sebastian

Scribe: Daniel

1 March 2023

Used for charter discussion.

22 February 2023

Chair: McCool/Sebastian

Regrets: any?

Scribe: Ege

15 February 2023

Cancelled due to the Charter Meeting.

8 February 2023

Chair: Sebastian/McCool

Regrets: any?

Scribe: Daniel

1 February 2023

Chair: McCool/Sebastian

Regrets: any?

Scribe: Sebastian

25 January 2023

Chair: Sebastian/McCool

Regrets: any?

Scribe: Michael Koster

11 January 2023

Chair: McCool/Sebastian

Regrets: any?

Scribe: Cristiano

Repo Management

Renaming Master to Main

See: Renaming the "master" branches to "main" (Member-only)

  • Make sure to update your forks and local copies
  • BEFORE making change in local copies or fork, check in all pending edits/updates
  • Do NOT rebase a fork until you make this change
  • To change in forks, look under Settings/Branches and change "master" to "main"
  • For local copies...
  • Simple way: delete and reclone
  • Alternatively, for local direct clones of the w3c repo
      1. git branch -m master main
      2. git fetch origin
      3. git branch -u origin/main main
  • See above link for instructions

You can understand what this does better by reading the git branch docs.

Here -m "moves" the branch (renaming master to main locally, basically) and -u associates a remote "upstream" branch with a local branch, so that git pull does the right thing (for instance). Note this means that you MUST update the remote first before trying to update your local copies. If you have other remotes you don't have to do anything, just either use the new branch name explicitly (e.g. git fetch upstream; git merge upstream/main) or make sure the upstream repo has renamed master to main if you want fetch and merge corresponding branches in one step using git pull upstream. Here upstream is the name that I (McCool) use for a remote pointing at the w3c repo in MY setup. I cloned my original local copies from my own fork on github, so I have origin pointing at my own fork. I then used git remote add upstream https://github.com/w3c/wot-testing to add an additional remote called upstream pointed at the corresponding W3C repo I can use for rebasing, etc. I do PRs by pushing up changes to my own fork, then doing PRs to the W3C repos from there using the web interface. See above link for more instructions.

Past Content

Retrieved from "https://www.w3.org/WoT/IG/wiki/index.php?title=Main_WoT_WebConf&oldid=15790"