07:28:18 <RRSAgent> RRSAgent has joined #wot-td
07:28:18 <RRSAgent> logging to http://www.w3.org/2017/03/24-wot-td-irc
07:28:40 <yingying> yingying has joined #wot-td
07:29:45 <ohura> ohura has joined #wot-td
07:30:01 <kaz> Meeting: WoT WG - TD TF
07:30:15 <kaz> Chair: Sebastian
07:30:23 <McCool> McCool has joined #wot-td
07:30:34 <kaz> present+ Kaz_Ashimura, Sebastian_Kaebisch, Michael_McCool
07:30:48 <kaz> present+ Mari_Poveda
07:30:55 <kaz> s/Mari_/Maria_
07:31:14 <kaz> Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf
07:32:03 <mariapoveda> mariapoveda has joined #wot-td
07:32:55 <taki> taki has joined #wot-td
07:33:03 <dape> dape has joined #wot-td
07:33:40 <yingying> present+ Yingying_Chen
07:33:42 <McCool> present+
07:34:05 <dape> present+ Daniel_Peintner
07:35:22 <McCool> present+ Michael_McCool
07:35:36 <fernando> fernando has joined #wot-td
07:35:47 <kaz> present+ Dave_Raggett, Feng_Zhang, Fernando, Taki_Kamiya, Yongjing_Zhang
07:37:33 <kaz> s/Fernando/Fernando_Serena/
07:39:58 <kaz> -> https://www.w3.org/WoT/IG/wiki/ScribeList scribe list
07:40:09 <kaz> scribenick: taki
07:40:12 <taki> Scribe: TK
07:40:20 <taki> ScribeNick: taki
07:41:08 <kaz> topic: Logistics
07:41:10 <kaz> @@@
07:41:17 <taki> Sebastian: I am showing slides that I used in Santa Clara
07:41:33 <kaz> i/Sebastian/topic: TD model discussion/
07:42:04 <taki> Sebastian: JSON-LD is quite nice to describe thing description. Readable, and provides semantic anotation, actiona and event
07:42:23 <taki> Sebastian: We used thing description in plug fests. Very successful.
07:42:41 <kaz> -> https://www.w3.org/WoT/IG/wiki/images/9/9e/Td_model.pdf Sebastian's slides (Feb version)
07:43:08 <taki> Sebastian: It has a lot of restrictions. There are structure requirement, guidelines as to how it has to be difined and so on.
07:43:22 <McCool> q+
07:43:37 <taki> Sebastian: Web developer may want to use it as like JavaScripts.
07:43:50 <kaz> [ March version slides to be distributed? ]
07:43:59 <taki> Sebastian: What will be the best serialization formats?
07:44:25 <taki> Sebastian: In Santa Clara.What would like to see in TD?
07:44:50 <kaz> s/Clara.What/Clara, what/
07:45:14 <taki> Sebastian: Things name, interaction patterms (events, properties and actions). Names and datatypes.
07:45:44 <taki> Sebastian: and communication protocols. And most inportantly security aspects. Hooks to security.
07:45:56 <kaz> -> https://www.w3.org/2017/02/06-09-wot-minutes.html#day2-item03 discussion during the Santa Clara f2f meeting
07:46:00 <taki> Sebastian:  Most interesting part is semantics enrichment.
07:46:09 <kaz> s/inportantly/importantly/
07:46:24 <taki> Sebastian: I ha ve written down in the slides. We may need to have more.
07:46:27 <kaz> present+ Masato_Ohura
07:46:38 <kaz> rrsagent, make log public
07:46:42 <kaz> rrsagent, draft minutes
07:46:42 <RRSAgent> I have made the request to generate http://www.w3.org/2017/03/24-wot-td-minutes.html kaz
07:46:46 <taki> Sebastian: What is the first idea of thing descriptiion?
07:47:03 <taki> Sebastian: We have thing. Thing has name. and three kind of interections.
07:47:16 <taki> Sebastian: inputs and outputs.
07:47:35 <taki> Sebastian: not very professional representation but is a first step.
07:47:50 <taki> Sebastian: OCF and M2M. Dave can elavorate.
07:48:05 <dape> q?
07:48:18 <yingying_> yingying_ has joined #wot-td
07:48:59 <taki> DR: Property, action and events
07:49:09 <taki> DR: Everything is a thing
07:49:25 <taki> DR: Property, evnets and actions
07:49:34 <kaz> i|Property|-> @@dsr@@@ Dave's slides|
07:49:36 <taki> DR: types are importamt
07:50:00 <taki> DR: Application types. and combines thme together
07:50:22 <taki> DR: We need what metadata is required by a platform.
07:50:52 <taki> DR: Names is necessary. Structure, such as array. Collections. Links constraints.
07:50:58 <kaz> q?
07:51:01 <kaz> ack Mc
07:51:19 <taki> MC: Homogenious collection and non-homogenious collections
07:51:30 <taki> Sebastian: We can always reference JSON schema.
07:51:41 <taki> DR: I am talking about functional requirements.
07:52:03 <taki> DR: Actions. rquests and responses.
07:52:09 <kaz> s/Homogenious/Homogeneous/
07:52:15 <kaz> s/homogenious/homogeneous/
07:52:17 <taki> DR: Numbers, strings, booleans.
07:52:31 <kaz> s/rquests/requests/
07:52:48 <kaz> q+
07:52:52 <dape> q+
07:52:57 <taki> DR: strings. such as patterns.multi-lingual conetxts. Alternatives in laguagages.  enumerations
07:53:02 <taki> DR: unions
07:53:16 <taki> DR: un-homogenious is possible
07:53:28 <kaz> s/homogenious/homogeneous/
07:53:30 <taki> DR: vectors are helpful.
07:54:07 <taki> DR: metadata. such as location, owner
07:54:18 <taki> DR: serial number in echonets.
07:54:32 <taki> DR: only part description is possible.
07:54:57 <taki> DR: instance of a class, imports. Using RDF.
07:55:17 <kaz> q+ fernando
07:55:17 <taki> Fernando: Are there hierachies?
07:55:19 <kaz> ack fe
07:55:25 <taki> DR: Yes, it is useful.
07:55:32 <kaz> q+ mccool
07:55:36 <kaz> ack mccool
07:55:42 <taki> MC: Has to have names. URL. ie. human-readable label.
07:56:25 <kaz> q?
07:56:35 <taki> MC: Useful for data-modeling. Which ones are useful for TD?
07:56:55 <taki> MC: Short label vs. longer name. But unique label, we should specify.
07:57:08 <taki> DR: We need to make it expicit.
07:57:26 <taki> MC: Instance and Classes.
07:57:41 <taki> DR: This action is an istance of a class.
07:57:57 <kaz> s/istance/instance/
07:58:16 <taki> MC: I would vote for that. It is useful to have software that has model.
07:58:21 <kaz> q?
07:58:49 <dape> ack dape
07:59:06 <taki> MC: Streams
07:59:26 <taki> MC: Media streams and websockets.
07:59:42 <taki> MC: Implementations. Audio streams are important.
07:59:50 <dape> q?
07:59:59 <taki> MC: What does action means? We should be more specific
08:00:06 <taki> MC: As to what names mean
08:00:11 <kaz> s/means/mean/
08:00:26 <taki> Sebastian: We discussed what streams mean.
08:00:37 <taki> Sebastian: I do not know what is the current status
08:00:50 <taki> DR: I did not talk about streams
08:01:13 <taki> DR: property is updated. Where streams come from. All anout metadata.
08:01:35 <taki> MC: Sources and sync. flow of data. They are different from evnets.
08:01:45 <taki> MC: Events follow event model
08:02:20 <taki> MC: Streams is opaque. I am talking about this case.
08:02:22 <yychen__> yychen__ has joined #wot-td
08:02:34 <taki> DR: Blobs. We do not know what that is.
08:02:48 <kaz> q?
08:02:49 <taki> MC: Maybe video formats. Delegations.
08:02:51 <yongjing> yongjing has joined #wot-td
08:03:04 <taki> DR: Binary blobs with bute sequences.
08:03:13 <taki> MC: We can table this for now
08:03:27 <taki> Sebastian: We also have presentation by Maria
08:03:45 <taki> DR: Information model is important.
08:04:01 <taki> DR: Diagram needs to expterss choice and conjucntions.
08:04:45 <taki> Sebastian: This is mostly same as what I presented. Property. Request and response. I used input and output.
08:05:06 <taki> Sebastian: We should may be more concrete for TD>
08:05:16 <taki> Sebastian: We do not need to invent new.
08:05:34 <taki> DR: We need to make sure information madel matches requirements.
08:05:46 <yongjing> q+
08:05:51 <taki> DR: OneO2M, for example. We should drive by requirements.
08:06:32 <taki> Kaz: It seems to me that human kanguahe and mahcine-lamguahe part both exist.
08:06:52 <taki> DR: We need human-readable label. Desried by many platforms.
08:07:35 <dape> s/human kanguahe and mahcine-lamguahe/human language and machine-language
08:07:58 <taki> Kaz: TV vendors are interested in how to reuse WoT mechanisms. We need concrete mechanisms. We need to think about cencrete cases before thinnking about general ideas.
08:08:32 <taki> DR: We have standards, OCF and OneMM.
08:08:50 <taki> Kaz: We need to thinki about our own requirements.
08:08:59 <kaz> q?
08:09:01 <kaz> ack k
08:09:03 <kaz> ack y
08:09:11 <kaz> s/thinki/think/
08:09:25 <taki> YZ: TV use case. STreaming user case  is more convicing.
08:09:40 <taki> YZ: Action modeling is important.
08:09:42 <kaz> s/STreaming/Streaming/
08:09:51 <kaz> s/user case/use case/
08:10:09 <taki> Sebastian: Data input and putput make sense.
08:10:19 <kaz> s/putput/output/
08:10:32 <taki> Sebastian: We still have presentation from Maria
08:10:43 <taki> Sebastian: would you like to start?
08:11:07 <taki> MP: Can you see my slides?
08:11:18 <yongjing> what i said is IP-camera is more convincing than TV broadcast as an Web of Things use case :)
08:11:18 <taki> MP: I am going to present our model
08:11:26 <kaz> i/We still/topic: WoT ontology development - Maria/
08:11:34 <taki> MP: We are building ontology for vicinity projects.
08:11:56 <kaz> rrsagent, draft minutes
08:11:56 <RRSAgent> I have made the request to generate http://www.w3.org/2017/03/24-wot-td-minutes.html kaz
08:12:05 <taki> MP: We need to have ontologies for different domains. Buildings. etc.
08:12:28 <taki> MP: We rely on cross-domain ontologies. But we did not have WoT ontology.
08:12:58 <taki> MP: We put all requirements that came from your documents.
08:13:35 <taki> MP: Maintenance of ontologies. We are sharing ontologies in github public.
08:14:11 <taki> MP: We get requirements from your documents. We provide examples. We also looked at emails.
08:14:43 <taki> MP: In order to build ontology, we used protege.
08:15:20 <taki> MP: We can include actions. annotaions are pointing to standards.
08:15:45 <taki> MP: RDF. We are providing three different serializations.
08:16:19 <taki> MP: URI proivides content negotions.
08:17:18 <taki> MP: Properties are defined by URL
08:17:33 <taki> MP: We didn't include protege.
08:18:23 <taki> MP: If you want to adopt this ontology, we can rename it.
08:19:07 <taki> MP: We have thing. It has one more interaction pattern. Weitable? Required?
08:19:23 <taki> MP: properties can take input.
08:20:01 <taki> MP: Unit of measures, we already have ontologies for those.
08:20:16 <taki> MP: XML datatype. Dave proposed collections and lists.
08:20:26 <taki> MP: I have not addressed that.
08:21:09 <taki> MP: Vicinity use cases. SOme cases that uses end-points that i turn uses another end-points.
08:21:41 <taki> MP: Relations. We should with ISO standard.
08:22:08 <taki> MP: JSON to RDF model. Thing, isnsance and URI.
08:22:21 <taki> MP: We describe name.
08:22:45 <taki> MP: it is a triple. a data may lead to more that one triple.
08:23:11 <taki> MP: We could include int of measure and dataype.
08:23:32 <taki> MP: Next, you have to reference it.
08:23:53 <taki> MP: Unit of measure is also defined somewhere else.
08:24:58 <taki> MP: Scope. HTTP. Href, each has media type.
08:25:33 <taki> MP: You have all repositries.
08:26:32 <taki> MC: We should decide on one propocol. Whether it can support multiple mode.
08:26:50 <taki> DR: we need additional budger,
08:28:04 <taki> Sebastian: we need more clarificarions.
08:28:29 <dsr> dsr has joined #wot-td
08:28:32 <dsr> present+
08:28:41 <dsr> q+
08:29:08 <taki> MC: If we have classes, it would be easier.
08:30:02 <dsr> ack dsr
08:30:14 <taki> Sebastian: we snould dedine what kind of vacbulary.
08:31:41 <taki> DR: We need to broaden it. That's why I am suiporting kinked data iiceneses
08:31:59 <taki> Sebastian: Is it possible to join next meeting, Maria?
08:32:25 <taki> MP: Yes, I think so
08:32:44 <taki> Sebastian: I will send a list of questions.
08:33:30 <dsr> we shouldn’t talk about protocols in thing descriptions as that briding too many abstraction layers. Instead we should describe the metadata for the next layer down, i.e. for the IoT platforms. We also need to broaden the scope to encompas security, access control, privacy, service level agreements, and other terms and conditions.
08:33:44 <dsr> s/briding/bridging/
08:34:11 <taki> Sebastian: I like your ontology-based model.
08:34:25 <taki> Sebastian: I will list questions.
08:34:34 <taki> Sebastian: We discuss it next weel.
08:34:40 <taki> Sebastian: Are there more questions?
08:35:05 <taki> Sebastian: Thank you everyone. Dave and Maria. Have a nice day!
08:44:04 <kaz> [ adjourned ]
08:44:09 <kaz> rrsagent, draft minutes
08:44:09 <RRSAgent> I have made the request to generate http://www.w3.org/2017/03/24-wot-td-minutes.html kaz
09:28:31 <zkis> zkis has joined #wot-td
11:22:04 <Zakim> Zakim has left #wot-td