<mkovatsc> Agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Agenda
<kaz> scribenick: nimura
<kaz> -> F2F201803/results registration result
Oracle host plugfest
place is 21 minutes from the hotel by subway
what is the network connectivity?
how about table?
Is it possible to shipping from the hotel?
30 people attends.
Plugfest would be 21 people
plan was 25 people and can prepare for that.
will attend 21 people for Saturday, 25 people for Sunday
<kaz> attendees per day
<kaz> (saturday 21; sunday 25)
possibility of shipping will be check with local attendee from Oracle
To have external guest access for network would be good
Guest access the network?
Check port restriction for Wi-Fi
Is SSH allowed?
hotel is already booked
the hotel in Thursday is full?
<mlagally> MLagally: I will clarify network capabilities
if you write e-mail for the hotel reservation, you can make the reservation.
<kaz> f2f wiki on the hotel
Kaz sent a request email today and got their response within 5 mins :)
approved the plugfest update.
<kaz> agenda input
we have a lot talk about security at the F2F logistics.
about remote participation, preference need to be check for example morning or afternoon.
we will talk about re-chartring the group on the admin day.
please make the hotel reservation.
Finding best term for all task force.
In TD and Binding call, talking about interaction or header option for how client find out staff.
current "form" is:
pro: no terminology conflicts
IETF and OCF also calls like that.
that is well known hyper media description.
Link: does not describe operation.
people think link is href or so though.
endpoint: Neither "link" nor "form"
define number of protocol
OCF endpoint is similar.
two endpoint in OCF.
conflict with other organization exist.
about binding:
no terminology conflict.
binding is sort of descriptive.
proposal is stick to "form"
no terminology conflict and fit for the concept of the element
if no objection, stick to "form"
this is re-thinking of TD...
Ok for TD chair point of view.
similar to form for machine
in the browser area.
this is machine readable version of form
"form" is make sense.
less conflict with other term.
"endpoint" was possible choice in the last week.
McCool: "form" is ok
<zkis> I would prefer "endpoint", but will leave it to the group/
if we realize the " form" is not good after the plugfest we can discuss and changing again.
RESOLUTION: use the term " form" for the TD element
Data schema: model class or so will be ready by Friday
TD document improves example.
Scripting API is also changing based on the TD work.
Security: target is March 10. new one will focus pragmatic aspect.
strawman doc will be ready by the F2F and discuss that.
One is simple authentication method.
Helpful to understand how node.wot deals those.
<kaz> [adjourned]