Meeting minutes
Logistics
<some discussions w.r.t low attendance>
Koster: We can think about a new timeslot if that works better for others
Minutes
<kaz> July-16
Ege: Any remark?
… none -> minutes are approved
<kaz> July-17
Ege: Any remark w.r.t Thursdays minutes?
… none -> minutes are approved
Editors for TD and Binding Registry
Ege: see w3c/
Ege: Discussion started a while ago
… discussion last week also
… Binding Registry doesn't have any editor
… current TD editors are no longer that active
… we talked about "author" role
… role is defined in https://
Ege: Editors do the maintenance work but not the creation of new content.
… Editors are responsible for the entire document
… Editor is not a creative role
… Authors are people creating significant new content
… like a new chapter
… Author is a creative role
… the product is still owned by the group
… Editors are only for the current version of a document
… If they stop being an editor for that, they are moved to "former editors"
… Authors stay in the document across versions if their contribution remains largely unchanged
… in case of JSON LD the version of the contribution is added
… we should regularly check the list of editors/authors
… should make clear, an entry into these lists is a "person + affiliation"
… e.g., the case for discovery spec and Farshid + Fraunhofer
… One person can have multiple roles
Ege: note that in IETF, our editor (definition used until now) is an author. RFC Editors are "professional editors" that are staff positions
… goal of today to make a proposal for the WG to discuss
Daniel: if we assume that this works, the policy about async process needs to be updated too right? We do not use author in the policy
Ege: w.r.t. async decision policy ... still editor has the decision... not the author
… editor needs to make sure nothing else breaks
… hence, the policy wouldn't change
<kaz> https://
Kaz: The WoT specification is generated by working group
… like the XML Signature WG policy above, probably we should clarify an additional policy
… to be discussed by the whole group
Ege: Next step would be turning into a policy?
Kaz: For today we think about it as draft policy
… can propose it to the whole group
… whole WG can make the decision
Ege: previous publications were done in the old mode
… wonder about implications and the current editors list (Sebastian, Michael)
Kaz: I am ok with any kind of policies if the whole group is ok
… but I'd suggest we clarify the policy first
… then talk to the former editors
… and decide which sections editors are moved to
Ege: Alright, will send mails
<kaz> (after clarifying the policy :)
Available PRs
TD PR 2109
<EgeKorkan> TD PR 2109 - Propose user story for XML data mapping
Ege: Daniel adds "XML data exchange"
… using user-story template
… it is about XML payload and validating data
… the reason why it is not possible right now, there is no 1:1 mapping betwen JSON schema and XML schema
Ege: I didn't see one comment
… proposal makes sense --> merging
Ege: Proposal looks good to me now
… FYI, OPEN API added new terms, see OAI/
… let's add it to "existing solution" section
Ege: no other comment, I think we can merge PR 2109
TD PR 2103
<kaz> TD PR 2103 - Initial Connection Improvements
Ege: no other PRs to look at right now
… maybe we can look at w3c/
Ege: it is about "Initial Connection"
Ege: default value must go in expanded form
… expanded form must not contain some terms in root level, like securityDefinitions etc
Ege: an expanded TD, some terms (like security, schema, ...) must not be used in form level
… local definitions take priority
… PR removes the examples sections from MD document
… the code part is also removed
… we said we do not provide code
… should be provided by implementations
… any objections/remarks?
… PR is available for a long time time
… would go ahead and merge
… merged PR 2103
Ege: other PRs are not yet ready
[adjourned]