Meeting minutes
Minutes
<kaz> Sep-25
McCool: publishing the minutes; no objections
PRs
TPAC Discovery Discussion
wot PR 1134 - Create 2023-09-14-WoT-TPAC-Discovery-Discussion.md
Farshid: SparkPlug B may have some relevant specification for MQTT discovery
https://
Farshid: The MQTT payloads could be just raw TDs, the tricky part is designing the topic structure. Everything else can be designed around the native MQTT features.
Luca: Do we want to support brownfield devices? Using Sparkplug B is just one of the many brownfields we can look into, see also Homie for another.
McCool: adding as follow-up to the document (see the PR)
<McCool_> w3c/
McCool: PR merged.
Capture frozen resources for publication
<McCool_> wot-discovery PR 516 - Capture frozen resources for publication
McCool: placing ontology and context files under a versioned publication directory. This is the staging area before copying files over to the wot-resources repo.
McCool: correcting discovery context URLs
McCool: The next issue is that the link to TD refers to the old, 2019 version
Andrea: It should point to the latest TD ontology
… which is https://
<Zakim> cris__, you wanted to react to a previous speaker
McCool: the URL is the same, but TD v1.1 ontology has been updated
Cristiano: we decided to keep the URL for v1 for backward compatibility purposes
McCool: The structure of TD resource files are different from what is proposed in discovery; the WG agreed on this during the main call.
Kaz: There may have been some misunderstanding
Kaz: I'm OK with the content and thank you for the discussion. However, as discussed during the main call last week, putting the resources files under the tentative "/publication" area would be dangerous.
… these resource files need to be stable, while the index.html file to be updated multiple times based on the Pubrules Checker's results during the publication preparation period./
McCool: removing the v1 directory, since by convention we keep v1 files flat and add sub-directories for follow-up versions.
Kaz: I've checked the minutes from the main call on Sep 27, and apparently it was rather myself who misunderstood the resolution :(
… the resolution from the last Main call agrees with the proposed approach in this PR, so if you still want to go for this direction, let's do so. However, we need to be aware of the potential danger and remember the official resources to be referred and to be maintained will be the resources under "wot-resources" repository.
<kaz> (some more discussion on the content)
McCool: Agreement to use UTF-8 encoding
McCool: The URLs aren't reachable in the staging area. How do we test them?
Andrea: I can commit to doing some manual testing, as wrong URLs cause major issues in our projects.
McCool: Even though the resources are frozen, we can still do bug fixes
… testing should be a separate issue on Github
McCool: Let's publish and create a separate issue for testing
<McCool_> proposal: McCool to finish last two points (line endings, UTF-8), then merge PR516 and proceed with publication.
RESOLUTION: McCool to finish last two points (line endings, UTF-8), then merge PR516 and proceed with publication.
<kaz> [adjourned]