Meeting minutes
topic PR
<kaz> PR 103 - TM smart coffee machine
McCool: pr 103 any comments?
Ege: what was about?
McCool: we renamed to jsonld to td.jsonld
… no other changes
… I assume that people will use also tm.jsonld
<kaz> PR 110 - Update TD suffixes
McCool: then 104 organized TD for geolocation and added a readme
<kaz> PR 104 - Update READMEs, Intel TDs, geolocation examples
McCool: then there's Sebastian's PR
… 111
<kaz> PR 111 - LwM2M Light Control ->SDF->TM->TD example
Sebastian: I transformed a SDF model to TM
… then I used it as base for another TM
… of course I provided also documentation about my process
McCool: file names are ok
… not sure relative URL is a valid in href field
cris: maybe the file scheme should work here
McCool: it could be taken from a website
… another comment is that unit field is odd
… it has a scale factor there
Koster: I have the same thing in my TDs for modbus
… I'd like to discuss it futher
… we discussed about this topic in OneDM
McCool: could you please create an issue this topic?
Koster: created a project issue
Sebastian: another discussion point is the usage of the required field in TMs
… I don't like the current solution
… in ediTDor this mess with the renderer
Koster: I think we should use a json pointer
McCool: I introduce json pointers also in links for geolocation.
<kaz> McCool shows his writeup on Geolocaton proposal (within wot-discovery PR 128)
McCool: we should also register json pointer as fragment identifier with IANA
cris: is that relative json pointer a valid url?
Koster: we think more on this issue
McCool: about previous issue rfc clearly says that there's no fragment indetifier registered for application/json
<kaz> McCool shows RFC6839
McCool: we have to override this spec to make this legal for json pointers
Koster: not sure
kaz: are you assuming that for our tests in PF to have a kind of proxy (or maybe the directory itself) that handles this fragment URLs?
McCool: I tried to describe a formal spec for geolocation so that it can be used in TDDs or other tools that we are building
McCool: other todo item is creating an SDF file for geolocation
<kaz> PR 100 - Project (2021-03 Plugfest): Geolocation
<kaz> PR 113 - fix format in TUM TDs
McCool: PR 113
Ege: minor change
McCool: can you describe your TDs?
Ege: there are a bunch of devices that are the same we used on last pf
McCool: I noticed that you used the format field for defining time stamp
… I think we should be more precise in the spec and describe our format for timestamps
Ege: I used a vocabulary that specify the format, we should be fine with that
… it might be even standard
McCool: we can look also at what SDF is doing
… let's create a document describing the best practices for time stamping.
McCool: philipp can you explain your project?
philipp: I just shared the link to my devices and described the issues that we encountered
McCool: ok thanks, then we have Ege
ege explaining WADE features
<kaz> Issue 107 - Project (2021-03 Plugfest): WADE (WoT API Development Environment)
Ege: the main new feature is the generation of mashup schemes
McCool: that's intresting let's schedule a time where you can describe this in depth
McCool: On Friday we'll do a final presentation with all the contributions
… then we have a project that involved me and koster
Koster: still need to test one of the tds with node-wot
… I am also working on a TD generator
McCool: is this aligned to what siemens is doing.
Koster: yes
McCool: what is the media type for your sdf files?
Koster: we don't have it
<kaz> Issue 108 - Project (2021-03): Create OneDM/SDF Semantic Annotation Examples
<kaz> Koster's switch-td.json
Koster: I'll at the URI expansion, it might mess with the context prefixes
Sebastian: does scaleMinimum coming from JSONSchema?
Koster: no it's from SDF
<kaz> modbus example
McCool: Sebastian, could you follow this example? about the scale
McCool: I like sdf approach
… just prototype stuff
Koster: the new terms were introduced to deal with the correct interpretation of values. JSONSchema just ignores them
McCool: next project is again from Ege
Ege: Marcus is testing TDs on this plugfest with our tool that evaluate the conformance with the spec
<kaz> Issue 112 - Project (2021-03 Plugfest): Node-RED integration
McCool: finally Node-RED integration from Toumura
<kaz> i|next project|Issue 109 - Project (2021-03 Plugfest): Conformance Testing via wot-testbench|
Toumura: I'm still working on this but I'll improve node-red generator with the latest finding in discovery task force.
<kaz> Issue 114 - Project (2021-03 Plugfest): Create several TMs and test Eclipse Edit{TD}or tool
<kaz> Issue 115 - Project (2021-03 Plugfest): Enable Thing Model support for the ediTDor
McCool: then we have the ediTDor tool.
Sebastian: we are using the ediTDor as an evaluation tool for TM experimentation
McCool: do you check the @type for tm validation?
Sebastian: not sure, it goes back to Felix
McCool: ok asking on the issue thread
McCool: closing the meeting, please continue the discussion on the slack channel.
<kaz> Projects so far
<kaz> [adjourned]