Meeting minutes
Minutes
<kaz> Mar-6
Cristiano: The last meeting we discussed PRs
… we'll discuss them as well
… doublecheck for DST changes
… <minutes check>
… minutes ok and approved
Daylight Saving
Schedule
<kaz> schedule
Cristiano: Deadline the 27th
… we'll call for a review
Issues
<cris_> wot-charter-drafts issue 84 - Should Scripting API be normative?
Cristiano: all editors commented on it
… the current opinion is to stay with the status quo: Stay on the Note track
… feedback welcome
Kaz: Please be aware of the difference between Normative Rec and Informative Note
… Notes are not endorsed by anybody., On the other hand, RECs are endorsed by the W3C as a whole.
… Technically, we can make the Scripting API a Note which says "These sections within this document are normative." However, it wouldn't really make any sense because nobody endorse that. So if we really want to make the Scripting API normative, it should be a W3C Recommendation.
Cristiano: We need to decide if we want to just explore and experiment or work on making a full Normative document
Luca: What is the aim Scripting API?
Cristiano: The original goal was to make the scripting API at the same level as the js runtime in the browsers
… we should see what is the goal
… either an experiment that can stay as Note or a runtime definition that has to be a Rec
new PR
PR 464
<cris_> PR 464 - Use biblio references for more URLs
Cristiano: using data-cite instead the full URLs
… renders fine, I'd merge it as-is
PR 461
<cris_> PR 461 - add undefined where missing in prose
Cristiano: Let's change from `null` to `{}`
… let's wait for Zoltan's approval
PR 462
<cris_> PR 462 - Update README.md with versioning information
Cristiano: Postponed to the next meeting
PR 463
<cris_> PR 463 - Fix internal slot in event handlers
Cristiano: it is still in draft, postponed till the next meeting
<kaz> [adjourned]