Re: [TF-LD] notes - 8 June 2018

Hi Kaz and all,

Sorry for not attending the meeting as I thought the meeting was cancelled and I also was travelling.  I would like to share my plan for some of the points you highlighted in bellow:

1. Integrated JSON-LD Frame into Thing directory: Victor and I discussed about this in recent F2F meetings, we're finishing the first implementation for this feature, we will create a PR for this this week so that Victor can review before the plugfest. 

2. For SHACL tooling  for TD, we're looking into providing a SHACL+GraphQL API/library for Thing Directory, it will not be ready for the plugfest, but I'll report the progress and implementation plans on the  Open Day.


Best regards, 

Danh 

On 11/06/2018, 08:11, "Kazuyuki Ashimura" <ashimura@w3.org> wrote:

    Hi all,
    
    Darko was not available and there were just Koster, McCool, Taki and
    myself during the LD call on June 8, so we didn't have an official
    call but had some chat as follows.
    
    Thanks a lot for taking these notes, Taki!
    
    Kazuyuki
    
    --- from here ---
    Present: Michael_Koster, Michael_McCool, Taki_Kamiya, Kaz_Ashimura
    Chair: Koster
    Scribe: Taki
    
    Koster: Originally on the agenda was:
      How to use external ontology such as semantic annotation using iotschema.org,
      and discussion on recommended patterns for using FoI (Feature of Interest).
    
    Koster: How JSON-LD Frame works.
      Has someone taken a look at it how it works exactly?
      If not, we need to have some to take a look at it closely.
    
    McCool: JSON-LD Playground.
      TD Validation is using JSON schema for syntactic checking.
      I already rewrote JSON schema halfway based on the latest TD draft spec.
      I encountered an issue.
      When importing external security schemes, validation needs to take
    that into account.
      Such as enumerated values. new scheme name needs to be allowed in
    enumeration, for example.
    
    
    Koster: WISHI telecon.
      WoT IG/WG exercises PlugFest according to our own plan.
      WISHI PlugFest uses WoT PlugFest as the starting point, and build
    research on top of it.
      With regards to on-line PlugFest, WISHI has assigned no action
    items. WISHI is volunteer-based activity.
      Next WISHI Face-to-Face meeting will be 14th-15th of July in Montreal.
    
    McCool: SHACL tooling.
      TD validation is also using SHACL for certain purposes.
      Not very clear about available toolset for processing/using SHACL.
      Is the toolset as powerful as those of JSON Schema?
      Some WoT members may be more knowledgeable on this, including Dave,
    Darko and Victor.
    Koster: schema.org, including iotschema.org is discussing to use shape
    constraints (SHACL).
      Tool development is part of the discussion.
    McCool: A practical approach is SHACL to JSON Schema generation. This
    is practical and useful.
      It should merge in all contexts, and generate JSON Schema.
    Koster: I also want to use OCF, ZigBee as well as iotschema.org definitions.
      JSON schema is mainly for validation payload.
      We can use RDF to describe OCF and generate JSON schema, for example.
      This kind of higher-level tooling is useful and important.
    McCool: There is a Korea F2F agenda item for discussing testing tools.
    Koster: We should also allocate time for discussing shapes validation.
    McCool: One hour testing tool discussion, and 15 minutes shapes
    validation discussion as part of it.
    Koster: That is good. Let's make sure to have it on agenda. Hopefully,
    Dahn can also join the meeting.
    
    McCool: Online PlugFest should also be an agenda point.
      When a light is on, how can we know about it?
      Device simulation is useful in this case.
    Koster: The idea of Digital Twin is also based on proxy and model.
    McCool: Semantic annotation can help simulation.
    Koster: Generic testing API for all TDs will also be useful.
    McCool: For example, when node.wot is run in testing mode, one way is
    to make it so that
      it automatically can turn on testing APIs such as for observability,
    controllability
      (such as triggering events, etc.).
    --- to here ---

Received on Thursday, 21 June 2018 09:49:58 UTC