W3C

– DRAFT –
WoT-WG - TD-TF

07 June 2023

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Kaz_Ashimura, Michael_Koster, Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
Ege
Scribe
cris__, kaz

Meeting minutes

minutes

<McCool_> May-31

minutes review

Ege: cristiano's name is misspelled
… discussed about timeslot changes
… and introduced the new moderation configuration
… finally we recorded the resolution to publish the protocol binding document
… we also discuss big architecture refactoring
… missing slides

Koster: I'll merge PR with the slides

Ege: ok, thanks

<kaz> wot PR 1091 - Create 2023-31-05-tdnext.pdf

Ege: we went back to the implementation report and reached the resolution to publish TD
… ok fixes has been made, minutes approved (slides link will be added later)

Kaz: fixed slides link

Ege: great

<kaz> (Minutes approved)

Timeslot length and preference

Ege: it will stay as it is for this charter
… we would do a general check for people availability before changing.

moderation rules

Ege: I think we should document it somewhere

Kaz: right, as a starting policy we can simply copy the basic policy you presented at the top of the wiki page.

<mjk> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2023-31-05-tdnext.pdf

Ege: anything to add?
… ok

Ongoing topics

Ege: do you want to add anything to the Thing Description topics to discuss during TPac?

Binding Templates publication check

Ege: do we need to do something?

Kaz: if the static version for publication is stable enough, I'll work on that. That means you should not add any more edits ;)

<Ege> https://github.com/w3c/wot-binding-templates/blob/main/publication/note3/Overview.html is cleaned up version

Thing Description

Update implementation description

<kaz> wot-thing-description PR 1838 - Update Implementation Descriptions

Ege: PR in flight, there was some discussion

McCool: implementations are inconsistency named

Cristiano: will update the directory name

Ege: wot-testing has a PR with the description.

<Ege> wot-testing PR 582 - Add wot-rust implementation description around wot-rust implementation

McCool: we can merge it

<kaz> (PR 582 merged)

Ege: should we merge the TD PR 1838 today?

McCool: yes, please I'll follow up with another one. Just to make sure, Kaz, would it be OK to keep the Implementation Report updated during the Proposed REC transition procedure?

Kaz: yes

(PR 1838 merged)

PR publication prep

<kaz> wot-thing-description PR 1837 - PR Publication Prep

Ege: I worked the static version for publication
… I did some changes to the index.html
… very boring, I summarized in the PR

<kaz> diff

Ege: then I did the tooling checks
… I added PR config to respec inside the ver11/6-pr
… no css problems

<Ege> CSS: https://jigsaw.w3.org/css-validator/validator?uri=https%3A%2F%2Fcdn.statically.io%2Fgh%2Fw3c%2Fwot-thing-description%2Ff014c9592d80d8c3b5da278ff2f89763e8f085fa%2Fpublication%2Fver11%2F6-pr%2FOverview.html&profile=css3svg&usermedium=all&warning=1&vextwarning=&lang=en

Ege: link checker is showing false positives

<Ege> Link Checker: https://validator.w3.org/checklink?uri=https%3A%2F%2Fcdn.statically.io%2Fgh%2Fw3c%2Fwot-thing-description%2Ff014c9592d80d8c3b5da278ff2f89763e8f085fa%2Fpublication%2Fver11%2F6-pr%2FOverview.html&hide_type=all&depth=&check=Check

McCool: what is the broken link mean in this context?

Kaz: if you can see the expected section then there is no problem
… it might be a bug of the tool
… it could be related to the ietf html

Ege: same thing happen with github
… note that is just the fragment

Ege: also I got an 401

Kaz: that link is for AC review, don't worry about the error

Ege: there is redirection but the link checker report 500

Kaz: if the content is correct there is no problem

Ege: I did not bother about redirection warnings

Kaz: right

Ege: then we don't have any other errors
… after these checks I controlled Pubrules

Kaz: have you used static urls in github.io ?
… you can doublecheck the tools after merging the PR with the static page

Ege: pubrules checker results in some warnings
… we add a warning to convey that new features may be added in the future

Kaz: note that Pubrules Checker and ReSpec are matained by different people
… usually that note should be inserted in the status section
… in theory ReSpec should inject that automatically

Ege: ok

McCool: ok but let's do this consistently in all the relevant documents

Ege: then I got another warning about messing the end date

Kaz: it dipends on the actual publication date. I'll handle that.

Ege: ok that's all
… any other comments?

Ege: wait I noticed that the future update warning mention process 2021 we are not following that

Kaz: right

McCool: the warning says *may*

Kaz: we are following 2021

Ege: ah ok

Ege: there is an error

Kaz: we can fix it offline

McCool: just let me know how fix it

Ege: should we merge PR?

Kaz: yes

Ege: merged

pending issues by REC

Issue 1753

<kaz> wot-thing-description Issue 1753 - Informative text on text direction handling

Ege: there is informative text to be added

McCool: I think we should defer this to TD 2.0. In the current status I'd accept only typo fixes

Ege: ok deferred to 2.0

Issue 1769

<kaz> wot-thing-description Issue 1769 - Informative text on text direction handling

Ege: we should have a static version of our schema
… how to proceed ?

Kaz: we talked about this months ago, I need a concrete URL
… creating a subdirectory under existing namespace is easier

Ege: alright

Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).