TSC Meeting - May 14th, 2018

[darrelmiller]

NOTE: This is Monday at 9am PT
Zoom Meeting link: https://zoom.us/j/975841675

In order to give some more visibility into the topics we cover in the TSC meetings here is the planned Agenda for the next meeting. Hopefully this will allow people to plan to attend meetings for topics that they have an interest in. And for folks who cannot attend they can comment on this issue prior to the meeting. Feel free to suggest other potential agenda topics.

Proposed Agenda

Topic	Owner	Decision/NextStep
Find volunteer to record action items	@namdeirf
Review progress of work on official OAS JSON Schema	@webron	Tabled
Results of tag naming for draft-features proposals	@webron & @earth2marsh	Approved
Tag alternative-schemas proposal with newly minted tag	@OAI/tsc	Tabled till future meeting, to clarify wording. Other decision based on hosting of alternative schemas
Update on Bikeshed vs Respec voting +(GitHub Pages https celebration)	@OAI/tsc	The body chooses: Respec
Review issues with "review" tag Clarify allowEmptyValue #1573	@OAI/tsc	Tables #1573 seeking community feedback
Update on work related to specification conformance tests	@tedepstein

/cc @OAI/tsc Please add items as you see fit

[handrews]

To follow up from last week, I've been thinking some about Hyper-Schema + OAS best practices but nothing concrete to report yet and no new questions, so unless there's some other schema question for which I'm needed I'll likely skip the call this week. Hopefully @philsturgeon can make it :-) (tag! you're it!)

[philsturgeon]

I’m it!

…

-- Phil Sturgeon @philsturgeon

On May 13, 2018, at 14:13, Henry Andrews ***@***.***> wrote: To follow up from last week, I've been thinking some about Hyper-Schema + OAS best practices but nothing concrete to report yet and no new questions, so unless there's some other schema question for which I'm needed I'll likely skip the call this week. Hopefully @philsturgeon can make it :-) (tag! you're it!) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.