Meeting minutes
Review draft minutes
<dape> s/scribenickL dape///
<Sebastian walks over the minutes>
Sebastian: Minutes look good, any objection?
-> none -> minutes approved
group decision to proceed to CR transition with TD 1.1
https://
Sebastian: working on it
Next week TestFest is planned
https://
Sebastian: Shall we have a TD meeting next week?
… every day there is TestFest
… no conflict with TD call
<Ege> +1 to having the meeting
Sebastian: personally prefer having a meeting
Cristiano: Agree to have a call, lots of things to discuss
Kaz: I would like to cancel
… 3 weeks continuous meetings
Sebastian: Okay, suggest to cancel meeting but we should keep working on PRs and issues
Sebastian: Different(new?) slot for bindings discussions
… 1 hour is not enough at the moment
… maybe use "editors" slot... besides the TD slot?
Ege: +1
Cristiano: +1
Ege: will send email to Jan and Klaus to confirm availability
Kaz: change slot regularly?
Sebastian: No, keep 1 hour in TD call slot
… an additional slot in editors call timeframe
Kaz: keeping 2 hour TD call and another 1 hour call for Binding?
Sebastian: Yes
Kaz: Maybe we should have an official announcement
Sebastian: Suggest to use email send by Ege ...
… people should have blocker in calendar
Kaz: Email suggestion is fine
… we should make a resolution during the main call
Sebastian: Sure
Binding Topics
Ege: would like to take a look at some PRs
<Ege> https://
Husky Tutorial
https://
Ege: adds small line... fixes issue
… make clear what to do
… suggest to merge ...
<kaz> merged
Adding WoT to titles
https://
Ege: individual bindings are not aligned
… this PR fixes it.. adding also WoT
Sebastian: +1
… PR merged
Kaz: from my viewpoint, the sub-documents could be subsections of the WoT Binding Templates spec so that we don't need to care about the titles of those sub-documents.
Ege: big discussion.. please open issue
Kaz: WCAG (Web Content Accessibility Guidelines) has similar structure.. but we can think about which would be better
<kaz> WCAG 2.1 REC
Fixing GitHub URLs
https://
Ege: Problem was that people got 404
… should always have the root repo in the links
… PR fixes issues in all the cases
… merged
Links to ontology in MQTT
https://
Ege: links showing errors.. not pointing to ontology document correctly
… PR adds full URL link
… when publishing we need to be aware of these links
Kaz: we can host ontology ... but we need to see the need of hosting on W3C side
… could be hosted somewhere else as well... need discussion
Ege: Would delay our work
… in the future we should really work together with other SDOs
… for now github seems fine also
Kaz: I organized break-out session for SDO collaboration
… various SDOs have started ontology discussions already
… need for standardized ontology is accepted
… ideal situation: collaboration w.r.t. ontology based on linked data
Ege: Agree
… will open issue to track this problem
Cristiano: Agree with the discussion
… prefer keeping ontology on Github for now.. otherwise tools get broken
… suggest to propose *our* ontology
… can ask other SDOs for feedback
… w.r.t. the PR... we can improve the process in the future tweaking the renderer
Sebastian: General comment: we have same situation with OPC-UA
… expect OPCUA to setup ontology
… we would like to work on this kind of collaboration
… similarly for ECHONET et cetera
Kaz: technically key question: who defines what
… need for data catalog to identify where to start the search
… should have collaborative discussion with all the related SDOs including OPC UA, IEC, ISO, ITU-T, etc.
Ege: <merging PR>
<kaz> s/who defines what, which definition to be referred to for what purpose/
HTTP Field Value
https://
Ege: issue created by Luca Barbato
… http fieldValue should be optional
Ege: PR can be merged later (related PR 181 needs to be merged first)
MQTT Examples
https://
Ege: fixes examples, commas etc
… no objections -> merging
MQTT topic and topicfilter
https://
Ege: still needs work from my side
<Ege leaving>
TD Topics
Sebastian: couple of PRs
minor typos
https://
Sebastian: small typo fixes
… looks good
Sebastian: merging
Fix shacl, context and ontology
https://
Sebastian: Suggest to postpone
… asked Etienne to check the PR
… let's wait for her feedback
Cristiano: fine by me
… btw, found other issues while working on it
Kaz: editorial fixes are fine, but technically we've already fixed the spec, so we should talk about update policy before diving into the new PRs.
Sebastian: PR has no impact on document itself
Kaz: should editorial label
Sebastian: Yes, thanks
Remove custom RFC 9200 bibliography entry
https://
Sebastian: official RFC now
Jan: content is the same
Sebastian: looks good
… merging
Aug 2022 impl report update
https://
Sebastian: I am okay to merge.. no direct impact on TD ... just an update of the report
… merging
editoral fixes/changes
https://
Sebastian: integrated review comments
Cristiano: +1
Sebastian: merging
replace remaining tm:required
https://
Sebastian: missed to update some old required statements
… one note is not very clear .. not related to PR
… editors note need to be removed anyway in the process
… suggest to clarify in a later point in time
<resolving PR conflicts>
Sebastian: no objections -> merging
update TD Context Extensions CoAP example
https://
Sebastian: text in section was not clear.. pointing to the "future"
… PR updates this para and points to editors draft
… the namespace in use does not exist yet
… need to publish binding on W3C domain
… wondering how we organize binding references/links
Sebastian: Kaz, do you have a proposal about the namespace structure ?
… see https://
Kaz: I personally think ... or I am not really sure whether W3C should host it
… suggest to talk with PLH
… purpose of reference is getting the ontology
… as tentative solution we can host on Github
… suggest with other SDOs
Sebastian: namespace from Github becomes very long
Kaz: length of URL should not matter much
Sebastian: Okay, I suggest to talk with Ralph also
Kaz: initial discussion with PLH
Sebastian: noted him in PR
Kaz: will start discussion thread with you and McCool
update def. semantic tag
https://
Sebastian: got review that we should be clearer what semantic tag means
… Ben proposed this change
… took over his proposal
Cristiano: +1
Daniel: +1
<SK resolving merge conflict>
Sebastian: no objections -> merging
add changes section for Fourth Public Working Draft
https://
Sebastian: PR adds new changes section
… changes look good
<cris_> +1
Sebastian: no objections -> merging
align formatting for examples
https://
Daniel: Style is more verbose using jsonlint
Cristiano: I think it is fine
… not that many big examples
… we could use json linter (used by node-wot)
Daniel: Would be good
… tooling might be tricky
Sebastian: JSON-LD does not seem very consistent either
… side-comments: snippets not always show highlighting
Daniel: broken JSON does not render nicely
Kaz: save the static HTML ... should not care about ReSpec bug
… if static HTML is fine
Sebastian: prefer to have the less verbose version
… could have the *compact* version for the main examples
Daniel: Not sure if fixing some examples make sense
… will try to find a better solution
Update policy
<sebastian> README.md of the wot-thing-description repository which includes the update policy
[[ Please notice that Thing Description 1.1 is in the review phase for the Candidate Recommendation (CR) transition. In this and subsequent phase, only editorial changes (e.g., adding examples, additional explanations) and bug fixes can be applied to the editorial draft. New feature requests can not be considered and will be postponed to the next version of the Thing Description. ]]
Kaz: Based on this policy we should identify "editorial" label PRs
Sebastian: All PRs do not affect spec..
… can add an additional note that PRs need "editorial" label
Kaz: Thanks!
[adjourned]