Re: [TF-LD] minutes - 22 June 2018

On Tue, Jun 26, 2018 at 4:51 PM, tkamiya@us.fujitsu.com
<tkamiya@us.fujitsu.com> wrote:
> Thank you, Kaz.
>
> I noticed in the minutes "SSN SOSA" was wrongly spelled as "SSN saucer"...

Thanks a lot for your clarification, Taki!

I've just updated the HTML minutes accordingly:
  https://www.w3.org/2018/06/22-wot-minutes.html

Kazuyuki


>
>
> Taki Kamiya
> Fujitsu Laboratories of America
>
>
> -----Original Message-----
> From: Kazuyuki Ashimura [mailto:ashimura@w3.org]
> Sent: Monday, June 25, 2018 1:42 AM
> To: Public Web of Things IG <public-wot-ig@w3.org>
> Subject: [TF-LD] minutes - 22 June 2018
>
> available at:
>   https://www.w3.org/2018/06/22-wot-minutes.html
>
> also as text below.
>
> Thanks a lot for taking these minutes, Taki!
>
> Kazuyuki
>
> ---
>
>    [1]W3C
>
>       [1] http://www.w3.org/
>
>                                - DRAFT -
>
>                              WoT IG - TF-LD
>
> 22 Jun 2018
>
> Attendees
>
>    Present
>           DarkoAnicic, Kaz_Ashimura, Danh_Le_Phuoc, Darko_Anicic,
>           Michael_Koster, Taki_Kamiya, Aparna_Thuluva,
>           Victor_Charpenay
>
>    Regrets
>
>    Chair
>           Darko
>
>    Scribe
>           taki
>
> Contents
>
>      * [2]Topics
>          1. [3]Integrated JSON-LD Frame into Thing directory
>          2. [4]Feature of Interest pattern
>      * [5]Summary of Action Items
>      * [6]Summary of Resolutions
>      __________________________________________________________
>
>    <kaz> scribenick: taki
>
> Integrated JSON-LD Frame into Thing directory
>
>    <inserted> [7]Danh's slides
>
>       [7] https://drive.google.com/file/d/1VwUhZV7UiwMLG2-eBJYu2PMMagC2D7Bm/view?usp=sharing
>
>    Darko: We continue to discuss plugfest preparation.
>    ... work from Danh and victor.
>
>    Danh: Have been discussing query in thing directory.
>    ... sparql has some problems.
>    ... two solutions. using JSON-LD frame.
>    ... By the end of this week, we plan to make PR.
>    ... query for thing that provides temperatures by filtering
>    ... frame is simple. create JSON-LD frame query and send it.
>    ... to end point.
>    ... and it returns the partial document that contains data of
>    interest.
>    ... query is in JSON format.
>    ... you can modify the content on the fly based on templates.
>    ... you can create on-the-fly reversed property.
>    ... also implementing graphQL
>    ... query becomes even shorter with graphQL
>    ... GraphQL uses Shacl for validation.
>
>    Kaz: Can you send the presentation slide, Danh?
>
>    Danh: ok.
>
>    Koster: filtered lookup, I have been advocating. This can be a
>    solution. great.
>    ... GraphQL works under the hood.
>
>    Danh: We can also use this to other applications.
>    ... JSON-LD 1.1 frame, I believe is in the process of
>    standardization.
>
>    Koster: declarative filter is useful.
>
>    Darko: you don't need conversion.
>    ... This is better.
>    ... You can put recipe directly into query.
>
>    <DanhLePhuoc>
>    [8]https://www.topquadrant.com/graphql/graphql-shacl.html
>
>       [8] https://www.topquadrant.com/graphql/graphql-shacl.html
>
>    <victor> [9]https://www.topquadrant.com/graphql/directives.html
>
>       [9] https://www.topquadrant.com/graphql/directives.html
>
>    <victor> that's it, right?
>
>    <DanhLePhuoc> @Victor: yes, it is
>
>    Danh: I will present more on Open Day, including demo.
>
>    Darko: shapes validate data.
>
>    It automatically converted to sparql query.
>
>    Darko: what is the timeline?
>    ... will it be ready by plugfest?
>
>    Danh: JSON-frame work is on the way, this weekend, hopefully
>    can make PR.
>    ... Next week, people should be able to try it out.
>    ... I will also do test.
>
>    <Zakim> kaz, you wanted to ask if this information should be
>    included in the PlugFest preparation.md file (question after
>    the technical discussion)
>
>    Kaz: If this is expected to be provided by Plugfest, we should
>    provide some description. But it seems this is some of more
>    advanced features.
>    ... some WoT members are interested in this feature.
>
>    Darko: In the past, we created some slides (step1, step2, etc)
>    to explain sparql-based query.
>
>    Danh: I will follow the style.
>
>    Kaz: I should ask Koster (plugfest moderator) if it is
>    appropriate.
>
>    Koster: I agree with adding it.
>    ... How to use it, then how it is implemented.
>    ... Whatever we add, let's provide description.
>
>    Danh: You can use the same thing directory.
>
> Feature of Interest pattern
>
>    <inserted> [10]Aparna's slides
>
>      [10] https://github.com/w3c/wot/blob/master/linked-data/teleconferences/2018-06-30-Feature
> of Interest Pattern.pptx
>
>    Darko: let's proceed to next agenda item. Feature of Interest.
>    ... Aparna, can you show the current proposal?
>
>    Aparna: iotschema.org, FoI pattern is discussed.
>    ... FoI pattern came from SSN sauser.
>    ... FeatureOfInterest class.
>    ... capability is associated with featureofinterest
>    ... property is a property of FoI, etc.
>    ... Dataschema has actionOn association to Action.
>
>    Aparna showing TD example.
>
>    Aparna: pumpstatus "isPropertyOf" ... a FoI
>    ... DataSchema, description of data. Now it is a bit unclear
>    how to associate with FoI.
>
>    <Zakim> kaz, you wanted to ask Aparna (as well :) to provide
>    the slides
>
>    Koster: I created an example too. It is exactly the same.
>    ... I had the same question too.
>    ... we are in the same stage.
>    ... why we added triples instead of links. it is more
>    appropriate.
>    ... we need to add something to context to enable dataschema
>    FoI.
>    ... extension point, we will need to consider.
>    ... For now, directly adding to TD.
>    ... we can also add it into iotschema vocabulary.
>
>    Darko: with FoI, we are making a need for extra ontology to
>    derescribe your system. this is interesting.
>
>    Aparna: festoPA:pipe2 is it concept or instance
>
>    Koster: It is instance
>
>    Darko: there are two tanks and two pipes in the TD we are
>    making for plugfest.
>    ... festo-1, etc.
>
>    Danh: new pattern FoI, will it be iotschema or TD vocabulary?
>
>    Koster: iotschema vocabulary.
>
>    Darko: you can see the classes are in iot namespace.
>
>    Danh: FoI is new ? or are we just referencing SSN saucer?
>
>    Darko: FoI is aligned with SSN.
>    ... we did not take it as a whole from SSN.
>    ... we took a part of it.
>    ... event and observable relationship, for example. We adapted
>    to our pattern.
>
>    Koster: We integrated it into our capability pattern.
>
>    Danh: importing SSN as a whole may be too big. So it sounds
>    like a good solution.
>    ... we will need to pay more attention to alignment.
>
>    Danh and Koster discussing tooling including wol, RDFS, SHACL,
>    etc.
>
>    Kaz: We need more discussion during F2F.
>
>    Darko: We will provide TD for FestoPA.
>    ... Can query TD based on FoI.
>    ... using areas, doors, pipes.
>    ... I plan to attend the F2F remotely.
>
>    Koster: I will also add FoI in TD.
>    ... we should not block people from using it.
>
>    Kaz: It is better to document in preparation.md as
>    experimental. and if it's difficult, would be good to document
>    it within the result.md later.
>
>    Koster: we should inform the IG on how to use it.
>
>    Darko: I will describe in preparation.md.
>
>    Koster: Automotive use case is also interesting. I will contact
>    Benjamin and Soumya.
>
>    Darko: This is the last meeting before F2F.
>    ... Danh and I will add some description in preparation.md.
>
>    Kaz: Danh and Aparna, please send in slides.
>
>    <kaz> [adjourned]
>
> Summary of Action Items
>
> Summary of Resolutions
>
>    [End of minutes]
>      __________________________________________________________
>
>
>     Minutes formatted by David Booth's [11]scribe.perl version
>     1.152 ([12]CVS log)
>     $Date: 2018/06/25 08:38:28 $
>
>      [11] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
>      [12] http://dev.w3.org/cvsweb/2002/scribe/
>



-- 
Kaz Ashimura, W3C Staff Contact for WoT and M&E, W3C Project Team
Tel: +81 3 3516 2504

Received on Wednesday, 27 June 2018 19:28:39 UTC