Meeting minutes
Agenda
Sebastian: couple of PRs and decide if we are ready for CR
… maybe we'll not have time to check the issues
… aob ?
… ok
minutes review
Sebastian: we talked about internationalization review
Sebastian: then we talked about directories
… and languages
… but the issue was forwarded to the Discovery TF
… regarding accessibility there were no specif issues for TD
… TAG review was positive
… IANA registration should be covered, we had a PR that is now merged
… there's a problem in the topics
… 6 and 7 sections can be merged in one
… then we had some PRs
… mostly related to semantics and context issues
… we fixed also read/writeOnly defaults in affordances
… do the minutes look good?
Jan: at the bottom there's some issues related to the scribe
Sebastian: yes probably kaz can fix it
… content-wise minutes approved
Wide review
Sebastian: I updated the questoinare, but no feedback
McCool: we exchanged some emails
… we should discuss it in the github issue no emails
Sebastian: internationalization is done
… TAG also almost done
… architecture is missing
… regarding IANA we now have also an entry about Thing Model
… added a ref to json pointers
McCool: also to TD registratoin?
Sebastian: no, we would need another PR
Daniel: about contact field we should use maybe team-wot
… not too specific
McCool: +1 for team-wot as long as it stays stable
Sebastian: regarding privacy
… we recieved comments
McCool: I updated architecture
… but it also applies to discovery
… TLS applies to everything that's why it has been added in architecture
… TLS is required for public URLs
… is optional for private networks
Lagally: should we recommend a certain version of TLS ?
McCool: it is a minor update but we can do it later
Lagally: do we mention tls in TD spec?
McCool: I think we should cite architecture
Sebastian: about identifiers
McCool: we should probably add an assertion about id rotation
… immutable IDs might be property affordances
… id can be used to track location
… or activity
Sebastian: I like the overview made by Michael
Lagally: tracking devices is inside monitoring use cases
… by definition
… probably we should distingish users and devices when it comes to tracking
McCool: yeah but it is tricky: devices can be used to track users
Sebastian: so you might to discuss a little more?
McCool: there's no standard way to rotate ids
… for discovery 2.0 we might include a notification system for id rotation
<Ege> I just wanted to say that for me, this is an issue for discovery and not TD
McCool: well maybe
… it is a good place to discuss the problem
… the rotation right now is "manual"
Cristiano: don't we have update events in TDDs?
McCool: yeah but you break the URL, but we can discuss futher next monday
Sebastian: ok moving on with reviews, no reaction on security
… but it seems they have a lot of requests
… let's wait
… maybe we can ask kaz
… discovery is WIP
McCool: it is because the explainer is still to be done
PRs
Sebastian: a lot in the pipeline
Lagally: I reviewed specific PRs
… mostly those related to normative changes
… it is very difficutl to review those
… they contain unrelated chages
… for example 1491 contains random changes
McCool: it happens mostly with index.html
… it is automatically generated
… that's why sometimes it changes
Sebastian: you should review the template.html
Lagally: I would like to focus just on the document
… I'm not interested in the low level details
Sebastian: what about using the preview?
Lagally: it hard to find normative keywords changes
… previews are not reliable
Sebastian: sadly we know about this issues
Lagally: but sometimes there might be content changes not just blank spaces
Ege: for example PR 1493
… this change keeps popping up
… added and removed
McCool: probably is the renderer that it gets confused
… with order of statement
… it might be a bug in the ontology
Lagally: why do we add the index.hmtl to PR?
Sebastian: to see the render version
Cristiano: the problem is well-known a lot of small details that need to be fixed...
… but likely the editors and me got used to the workflow and we can understand the changes
… still I agree that we should simplify
Sebastian: of course having an automatic buidling process helps to keep the ontology alligned
… we should talk about this when we set up a new document
issue 1487
https://
Ege: it removes the json schema inside the body of the main document
… it also caused merge conflicts
… it is an informative change
… also I'm removing the format keyword
… they all have problems
… not every jsonschema implement those
… added also an ed note
… we will need a link to teh static file
McCool: that was my comment
… not sure we should host in github
… the best place should be on w3c
Cristiano: agree
Ege: +1
Sebastian: yeah it should be done for all the other files
… e.g. ontology and context
… other standards used to have the schema in the body of the document
… but they were ment to be printed
… on paper
Jan: maybe the tm schema should go under the same treatment
Ege: I'm doing it
… probably we should have a table with links to all this documents
Sebastian: looks good to me
PR 1489
https://
Daniel: minor fix about respec
Sebastian: ok merged
subtopic 1491
https://
Sebastian: from ege, is about stating sync or async action in the TD body
… we have support for async actions in profile
Sebastian: any other changes?
McCool: what is the default?
Ege: no default
… no using a default we force people to use it
McCool: that clears the ambiguity
… but in 2.0 we should fix it
… in profile we should require it
Cristiano: what happen if I use sync false but I don't have a queryaction form?
Ege: you might expose the status in a property
… or you don't have a way to query what is happening
Cristiano: I'm not convinced about the name
Daniel: why are we shorting the name?
… what about synchronous?
<Zakim> dape, you wanted to naming
Cristiano: plus sync and async might be confusing for developers
Ege: yeah, maybe we can do an open call for better name
PR 1493
https://
Ege: move a statment to the right place
… and also put a new section with a explanation about the connection between data schema and operation
… this can be marked as informative
… no way to describe queryaction dataschema
… I also named the section
… previously was a big chunk of text
Sebastian: one section is missplaced
… I think it is nice to have this explainer
Ege: I marked the section as non-normative
Sebastian: I'm ok keeping it non-normative
Cristiano: +1
Sebastian: ok then PR accepted
… merged
PR 1494
https://
Sebastian: introducing a requirement for TMs to have @context
Jan: was arlready in the json schema?
Ege: yes
Sebastian: ok PR accepted
PR 1498
https://
Ege: didn't see Michael's comment, I'll update later
Jan: also ipr issues
McCool: it is updating a folder that was removed by me because it was confusing
PR 1499
https://
Sebastian: it removes a kind of process about how to evaluate the text direction
… it was there from 1.0
… but the internationalization review pinpointed a better approach
… now it links another document
… from w3c
McCool: I'm not seeing any assertions in the new document
Sebastian: the reason why is that I'm linking a note
McCool: that's why we copy it over
Sebastian: but it won't be normative
McCool: can we cite a non-normative document using an assertion?
Sebastian: we have to ask kaz
McCool: I would make it an assertion
Sebastian: PR not merged, let's continue the discussion
PR 1500
https://
Sebastian: it adds a note
… basically tm:fef might contains non-ASCII characters
McCool: json uses bit compatiiblity not ASCII
Sebastian: it was proposed
McCool: maybe URLs are more restrictive
Sebastian: ok PR approved
… merged
… ok we couldn't get all the PR merged
… we should postpone PR transition
… next week
… we are getting closer
McCool: still a lot of PRs
Sebastian: but we are not accepting new one
Ege: updated PR 1491
Sebastian: ok let's merge this
[adjourned]