Meeting minutes
Review minutes from last week
<kaz> July-30
Ege: Any comments?
… minutes are approved
review
Ege: Any questions about the publication schedule?
Issue # 2112, TD FPWD goals review
<kaz> TD Issue 2112 - TD 2.0 FPWD Goals
Ege: (reviews the features checklist)
… Is there anyone who wants to work on these items?
Issue #12, Registry plan
Kaz: One issue is how to deal with existing bindings that were created under the TD version 1
Ege: The question is whether the entries can be modified after they are registered
Kaz: Will check with PLH again
Ege: can someone take issue #13 to create the empty bindings table?
Normative content from the Architecture document
Ege: Toumura-san will do the work of copying normative content (assertions) from the Architecture document to the TD document
Ege: are there opinions on how we should do this?
Kaz: The style and policy for TD is a little different from the Architecture. we can first copy the text and than refine it later - we should be careful
Ege: we should make sure we preserve the intention and meaning, make sure there the normative content make sense
Ege: we need to create an issue for tracking
… maybe make a list first?
toumura: there are a lot of assertions, we should proceed step by step
Ege: (created issue #2120 to track this work)
TD PRs
PR # 2081
<kaz> TD PR 2081 - Make contentType optional in ExpectedResponse and AdditionalExpectedResponse classes
Ege: Makes content type optional
Jan: This issue came up in discovery
… some of the response codes that don't return payloads
… it also bears on the resuable connections
Ege: in TD 2.0 there will be a global default
Jan: would it be OK to remove now and add the default later?
Ege: it's OK
Jan: then I need to look at the impact of assertion violations
Ege: we can review again at the next call on August 20-21
Jan: I should be able to wrap it up by then
PR #2118
<kaz> TD PR 2118 - Binding Intro Reorganization
Ege: Explains the binding mechanism. There are no significant changes since last week
… content is from the previous Binding Template document
… does anyone need more time to review or have comments on the direction
… Any objection to merge after fixing a couple of nits
Kaz: for the future, we need to clarify the relationship between binding and profile mechanism
Ege: (adding a new issue for that, # 2121)
Binding PRs
PR #433
<kaz> Binding PR 434 - Retiring the main document
Ege: updates the current document to simply refer to the new document
… We discussed and the updated document needs to still have the regular respec intro content with an abstract
… I can finish by tomorrow
Kaz: it's more to be nicer for the readers
Daniel: can we set up a forwarding process?
Ege: it's not a simple forwarding
PR #432
<kaz> Binding PR 432 - Adapting to Registry and Binding Word Usage
Ege: removes the word "template"with explanation, from the existing binding documents
… mostly an editorial change
… we can merge after people have time to review
Registry PRs
PR #16 in the registry repo
<kaz> Registry PR 16 - Adding Ege Korkan to editors list
Ege: adds Ege to the editor list
… any comments? OK to merge?
… no comments, merged
PR # 18
<kaz> Registry PR 18 - Delete requirements.md
Ege: deleted the requirements.md document
… Daniel has moved all the content
Daniel: yes, everything is moved
Ege: no objections, merged
PR #19
<kaz> Registry PR 19 - Intro Refactor
Ege: refactors the introduction
Ege: any comments or need more time?
Daniel: small correction to the 2nd paragraph
Ege: (makes correction)
… merged
PR #17
<kaz> Registry PR 17 - refactor: reformat document
Ege: assertion text
Daniel: I can revert the changes for now
Ege: some of them can be moved to a new place
PR #20
<kaz> Registry PR 20 - Readme Alignment
Ege: aligns the README content
… is this OK with everyone?
… merged
Ege: AOB?
… adjourned