<inserted> scribenick: cris
McCool: any guest other than Philipp Blum from RIOT OS?
Kaz: there's Hiroshi Fujisawa from NHK
McCool: ok noted
McCool: I noticed that Hiroshi was
here also yesterday. I need to note that in the agenda
... Rob Smith from Away Team Software might follow up about geolocation
... any objection to publish the minutes?
... ok accepted
McCool: we are going to document a
set a link relation types
... we have a document in wot-architecture repo
... I'll add the link in agenda
... please if you have a proposal for link relation types use
that md file
... in the end I image to have a dedicated section in Thing
Description spec
Sebastian: what do you expect? we already have a section for links
McCool: yeah but we don't provide any example for relation types
Sebastian: ok
McCool: I have a quick update about F2F
<kaz> vF2F wiki
McCool: we defined an agenda for
f2f
... however we didn't schedule a slot for plugfest report
... we could squish down security
Sebastian: I think it is better
to have PF report at the very beginning of the F2F
... if we can't. we could do it in the first testing call
McCool: the problem is that the first call is far. Therefore, we have to do some work and write down in the issue tracker what we have done.
Sebastian: I agree
McCool: yeah the problem is that
everything in the F2F is pretty packed.
... I'd record everything today, I think it is the best
option.
Kaz: it is ok to record the problems using GitHub Issues. But we should still make brief report out during the vF2F as well.
McCool: Right. What I am planning to
do it is just mention that we noted the outcomes in the issue
on the testing report
... I'll schedule a time slot
... Ege could you do this report?
Ege: I am not sure
McCool: I'll do it don't worry
... any other updates?
McCool: could you please finish your demo? yesterday we had some connection issues
Endo: we created a PR yesterday.
<kaz> PR 88
McCool: ok you updated the readme and uploaded pictures/videos
<kaz> updated README.md by NHK
Endo: we added node-red screenshots. where you can see our contribution highlighted
McCool: thanks it is
interesting
... can we see the video?
Endo: sure, it's a short video: 20 second
McCool: really nice video
... and use case
... thanks also for the screenshots!
Sebastian: thank you also from my side! It is nice to see different things from other contributors
McCool: let's go to the next PR
... PR #89 from Toumura-san
... it is a really nice contribution
Sebastian: yes indeed
McCool: once we have semantics you
could organize nodes in node-red.
... about the limitation (authorization not supported). we are
going to require authentication in TDD and in the future we
should solve this issue
... probably we should add an issue in your repository.
Toumura: we still don't have a public repository
McCool: it's nice that you also provided slides and video
McCool: David might be interested in
this work too
... the story here it is that with node-red you can do IoT
orchestration in less in 30 sec. it is awesome
Sebastian: where are TDs stored?
Toumura: the server has a DB populated with mDNS
McCool: mDNS is one discovery method, in the future the work from the discovery task force might help
Kaz: I suggest we raise GitHub issues to let us track the results. Also we might want to put together a PlugFest guideline based on all the accomplishments from the PlugFest this time.
<McCool> https://github.com/w3c/wot-testing/issues/92
McCool: we have one more PR #90
<inserted> scribenick: kaz
<inserted> PR 90
Cristiano: TD for a sprinkler
McCool: every 20 seconds, you get data from the sensor
Cristiano: yes
McCool: would merge the PR and also
raise an issue for the accomplishment
... (adds Farm/TUM mashup in addition to NHK and Node-red
discovery integration)
<inserted> scribenick: cris
McCool: we could evolve this in an example
<kaz> Issue 76
McCool: I'm marking Map visualization as outcome.
<kaz> Issue 71
McCool: about expirementation with TDD and node-wot. did we do that?
Cristiano: no I didn't
McCool: yeah we have to make sure
that we have compatible implementations
... Ok I marked as a followup
<inserted> Issue 87
McCool: issue 87 is also a follow up
<inserted> Issue 91
McCool: issue 91 is more related to
marketing
... about community building we are still working on it.
... Philip do you want to speak about it?
Philipp: I just added my view as outsider of the group
Sebastian: thank you for point
this out. you are not the only one.
... we are doing our best to solve this issue
... we have also a new landing page
... there is a developer space
<dape> see https://w3c.github.io/wot-marketing/
Sebastian: it is still under discussion
<dape> some more planned updates, see https://danielpeintner.github.io/wot-marketing/
Philipp: this is why I mentioned about doing outside the w3c. it is more reactive
Ege: json schema have a tag on
stackoverflow
... also other wg created outside communities
McCool: we also have a lot of material but we need to organize it
Kaz: let's move the discussion to
the marketing call
... and find some possible solutions.
McCool: (adds "PlugFest Outcome" label and "Plugfest Followup" label to the GitHub Issues from the online PlugFest)
<kaz> Issue 60
Daniel: could you please link issue 76 in 60?
McCool: sure
... btw, we are getting out of time..
<kaz> updated comment for issue 60
<kaz> Issue 61
<kaz> comment added to Issue 61
<kaz> Issue 62
<kaz> comment added to Issue 62
<kaz> Issue 47 on scenario for OneDM
<kaz> comment added to Issue 47
<kaz> ("Plugfest Outcome" label and "Plugfest Followup" label also added)
<kaz> Issue 58 on geolocation annotation
<kaz> ("Plugfest Outcome" label and "Plugfest Followup" label also added)
McCool: take your time to review the
issues that we marked today
... we are going to discuss them in the vF2F
<kaz> Issue 92 on consolidated accomplishments
McCool: cris can you make a screenshot of your mashup?
Cristiano: sure I'll probably make a video
McCool: it was a great PlugFest, thank you everybody
Kaz: And thank you, Michael, for you efforts as well :)
Sebastian: thank you everyone you did great!
[adjourned]