See also: IRC log
<kaz> scribenick: kaz
Darko: Matthias is not available today and asked me to chair the call today
Darko: is Bergi on the call?
(Bergi is not on the call)
<victor> https://github.com/bergos/wot-examples/
<inserted> scribenick: kaz
victor: Hydra examples
above
... also goes through the Current Practices document
-> http://w3c.github.io/wot/current-practices/wot-practices.html#td-examples Current Practices document
victor: Bergi defines events
<Yongjing> who's speaking now? i see Darko?
victor: GET, PUT, DELETE operations
<Yongjing> Why the WebEx shows Darko_Anicic?
victor: temperature sensor
<Yongjing> see, that's my problem...
victor: Hydra middleware recognizes any Hydra-based APIs
darko: not clear
... how to interact with events?
victor: he defines 3 other examples
<inserted> scribenick: Yongjing
darko: take temperature as example to explain?
<inserted> scribenick: kaz
victor: (goes through the
Hydra:supportedProperty examples)
... classes and Hydra properties
<inserted> scribenick: Yongjing
Daniel: missing aspects of protocols
victor: Hydra can map to abstract operations, e.g. GET, PUT
<inserted> scribenick: kaz
victor: mapping on protocols is quite obvious
<Yongjing> Daniel: need certain middleware?
michael: Hydra exposes underlying
REST-based mechanism
... Thing Description is a template
victor: serializable as RDF
michael: RDF is just one possible notation
<inserted> scribenick: Yongjing
victor: to get the temperature in Hydra, need to address resource, with serialized media type
<inserted> scribenick: kaz
victor: the Hydra client doesn't have to understand the media type
michael: we could have Hydra
Thing Description like our Thing Description
... I should join the discussion
victor: lacking modeling type
system
... link or actual resource
<inserted> scribenick: Yongjing
victor: resource should only have properties as literal or links to the resources
Michael: will take closer look into Hydra and have further discussion
<inserted> scribenick: kaz
darko: if we have one description
for temperature in one file
... and another file
... this would be definitely a hyperlink approach
victor: you can define
classes
... and all the temperature sensors will refer to the class
definition
... currently discussion on lifecycle
... interesting approach regarding this
... TD template
... if you recognize of URI of the class definition
michael: not only Thing Description for Hydra but some ontology for Hydra could be defined
<inserted> scribenick: Yongjing
michael: we can still use external ontologies
<inserted> scribenick: kaz
michael: interesting question on modeling ontology for Hydra
victor: everything should be
Hydra class
... if you want further semantic definition, you can include
Hydra class definition
michael: it has elegance to define everything within Hydra framework
victor: even for abstract
concept
... to me it's not flexible enough from semantic viewpoint
<inserted> scribenick: Yongjing
victor: it means every concept would be de-referencable, including abstraction concepts, that's not flexible
<kaz> Victor's pull request
<inserted> scribenick: kaz
victor: my pull request
above
... just a proposal
johannes: would suggest to merge this in unless any objections
darko: breakout session during
the next f2f?
... you can raise a proposal
victor: is Matthias available by the end of this week?
johannes: would ask the group about if it's OK to merge this proposal
(no objection)
yongjing: question about gh-pages branch
RESOLUTION: #299 can be merged, status remains as proposal to be discussed on TPAC
johannes: automatically available as a rendered HTML at some URL
kaz: the draft charter itself is
ok
... had discussions with candidate co-Chairs
... talking with W3M about the next step
... Jeff's suggestion is approving the WG charter today,
finalizing the co-Chair list by the end of Friday, and sending
out the AC review request on Monday
<inserted> scribenick: Yongjing
Johannes: anything preventing us
submit the WG charter?
... today?
Kaz: figure out the co-chair
arrangement by Fri
... final solution shall be ready by Monday
Kaz: will be another call on Friday about co-chair arrangement
Johannes: update info of the last joint call with oneM2M
<inserted> scribenick: kaz
yongjing: was there as the oneM2M
rep
... good discussion
... expecting another joint call maybe after TPAC
... also there will be the oneM2M meeting in Oct.
... working on liaison between oneM2M and W3C
kaz: please send a liaison letter to team-liaisons
yongjing: will happen after the Oct meeting
uday: can help you
... another question on the joint meeting with IRTF T2T
johannes: research group from
IRTF
... they're doing something quite similar to our work
... have been holding several joint meetings
... 2 days usually
... no registration fee
... announcement will be made on the mailinglist
... (shows Ari's message)
-> https://lists.w3.org/Archives/Public/public-wot-ig/2016Aug/0040.html Ari's message
<victor> send an email to t2trg-chairs@ietf.org if you attend
<DarkoAnicic> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_September_2016,_Portugal,_Lisbon#Agenda
-> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_September_2016,_Portugal,_Lisbon#Agenda TPAC agenda wiki
johannes: outreach and ad-hoc meetings
-> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_September_2016,_Portugal,_Lisbon#Outreach_and_Ad-hoc_meetings joint meetings
johannes: the slot for automotive?
kaz: still open, and to be discussed
victor: question on "breakout"?
darko: "breakout" means that the topic could be done as a breakout session
kaz: maybe we can start to define the initial time specific agenda based on those joint meetings
johannes: +1
<DarkoAnicic> Joint meeting with SDWG at TPAC: https://www.w3.org/2015/spatial/wiki/Meetings:F2F4 Tuesday 4pm
<inserted> scribenick: Yongjing
Kaz: no cable connection , maybe
we could use a converter between wifi and cable
connection
... cost will be evaluated
<inserted> scribenick: kaz
johannes: need to see if it's possible to bring that kind of converter
kaz: theoretically we can do that using a Linux PC
<inserted> scribenick: DarkoAnicic
Johannes: we should be prepared to work with no wire connection at the Demo/PlugFest
<dape> https://github.com/w3c/wot/blob/master/plugfest/2016-lisbon/TPAC-2016-Poster-Template.svg
<dape> see also https://www.w3.org/WoT/IG/wiki/F2F_meeting,_September_2016,_Portugal,_Lisbon_Demo
<DarkoAnicic> https://www.w3.org/WoT/IG/wiki/File:TPAC-2016-roll-up.jpg
dape: each demo leader is responsible to generate the poster
kaz: question on the "WoT"
logo
... Yingying, have you talked with the Marcomm Team about the
usage of the green "WoT" logo?
yingying: will hold a dedicated call for that
johannes: wondering if it would be problematic to have the logo
yingying: MarComm team requested
us to remove the WoT logo from W3C WoT Flyers.
... but need to check for this poster
johannes: when can we get the final statement?
yingying: will check after this call
johannes: maybe by Friday, can we get the conclusion?
yingying: will try
johannes: could show what the
API, servient, etc., are like
... Michael, can we work together?
... let's have another call with you later
can we set a deadline for the table status report?
uday: maybe you can talk with Matthias?
darko: offline discussion would be fine
dape: possibly could try a printing company in Lisbon
<DarkoAnicic> http://dx.doi.org/10.13140/RG.2.2.25758.13122
dape: or if we want to print it beforehand, we should finish it
<DarkoAnicic> Dave is not present today
kaz: need to check with
Dave
... got inquiries from some of the JP Members too
yongjing: I myself am also
included in this effort, and am wondering if W3C is happy to
consider this whitepaper as the one from W3C as a whole?
... rather than the one from those 4 individuals
... it's related to the usage of the W3C logo and the WoT logo
too
darko: Kaz will check with Dave
and other W3C Team
... any other questions?
(none)
[ adjourned ]