Meeting minutes
<zkis> Agenda:
<dape> https://
Minutes
Daniel: last week no call
Daniel: not sure why the
minutes reports Smart City Workshop
… we discussed about f2f and testing
… I also mentioned that the dates are overlapping
with my vacation plans
… the rest of the minutes was about issue
193
… the discussion focused on echonet
example
… should write property operation return
something?
… the consensus was to not return
anything
… but if the binding using some returned values the
implementation might throw an error to inform the application
logic
… we should make this clear in the
document
… no changes are required to the API
Zoltan: yes
Daniel: minutes approved
quick updates
Daniel: proposal during
the test week no call
… but the test fest does not conflict with the
scripting call
… theoretically we could do it
Kaz: I expected that the ordinary calls would be cancelled
Daniel: for me it is ok to cancel
Zoltan: I can join if there's a call
Cristiano: ok for cancel
Daniel: if nothing urgent comes up, no call
Daniel: I'll be on
vacation from the 12 to the end of june
… some of you can schedule calls? do we have
anything to present during the F2F ?
Cristiano: I think we don't have so many updates right now
Daniel: june it is pretty packed up maybe we will skip a few calls
Zoltan: we should get inputs from bindings and TD
Daniel: we can discuss about open issues with different task force
Zoltan: we could take an hour an just finish eairler
Daniel: should we add a bullet point dedicated to scripting?
Cristiano: why don't we split our topics into the different task force topics?
Daniel: yes, let me do it
issues
Daniel: please review the
three big issue dedicated to TD, discovery, and security
… before F2F and Testing
<kaz> Issue 313 - ThingDescription TaskForce related issues
Cristiano: I think topic in issue 313 should be moved under PartialTD validation
Daniel: yes
<kaz> Issue 314 - Discovery TaskForce related issues
Daniel: please also check
issue 314
… it would be also useful to discover local things
around me
… there is a dedicated issue
Zoltan: we have use cases before experiments with the feature.
daniel: I'd to have the
possibility to look for things around me at operational time
… it seems that right now we focus just on the
second phase discovery
… we should explore it also in
node-wot
… the next task force topic was about
security
… it goes around provisioning of security
credential and management api
… zoltan proposed to move the discussion to another
document
… about our API we should be able to pick one of
the configurations and assing to the specific Thing
Cristiano: yes
<kaz> Issue 315 - Security TaskForce related issues
Daniel: node wot uses a configuration file that has a map with ids and credentials
Cristiano: yes, it is basic and it works only if you know beforhand the id of the consumed thing
Daniel: yes, you need to first add the credentials and then consume the thing
Zoltan: the principle
that there's no man in the middles
… we should not give then plain to other software
agents
Daniel: there's no way to
specify which security to use in an expose thing
… selectivly
Zoltan: we already agreed that exposing a Thing is a system level privildge
Daniel: we could have a code example about it
Zoltan: we could use
"special things" that contains this kind of information
… so we might not need a new api
… but then we need a way to discovery
them
Cristiano: it is not a bad idea, but maybe a little bit overkill
Zoltan: we maybe just need special filters in the discovery
Daniel: I am not sure about the example in 299
Zoltan: yeah I was thinking about the source of information about the supported security schemes
Daniel: what about a setSecurityHandler
Zoltan: yeah you need
to have it for each interaction level
… we can think a nice api to do it after production
phase
Daniel: we are almost there, but just to be precise we are missing the securityDefinitions
Zoltan: yes about that
we have the two options presented above: one funciton or a special
Thing object
… if it is an api it needs to be controller by
authorization coinstraints (permissions)
Zoltan: I got a lot of updates about writeProperty return
Daniel: ok I'll review
it
… next week call cancelled if nothing urgent
happen
<kaz> [adjourned]