Meeting: August 13th, 2024 agenda

[earth2marsh]

Weekly meetings happen on Tuesdays

Time: 5pm GMT / 9am Pacific
Zoom: https://zoom.us/j/975841675, dial-in passcode: 763054

Accessibility & Etiquette

• Participants must abide by our Code-of-Conduct.
• Meetings are recorded for future reference, and for those who are not able to attend in-person.
• We invited challenges to language or behaviour that is harmful or not inclusive during this meeting.
• We look forward to your participation, but please consider these acts of etiquette:
  • Remain on mute when not speaking to prevent interruptions.
  • Blur your background to reduce visual distractions.
  • Use the Zoom meeting "Raise Hand" feature to notify the group when you wish to speak.

Blur My Background	Raise Hand

Agenda Structure

Topic	Owner	Decision/NextStep
Intros and governance meta-topics (5 mins)	SIG members	--
General discussion topics (list below)	SIG members	--
Wrap-up and seed the next agenda (5 mins)	SIG members	--

Whether attending or not, anyone can comment on this issue prior to the meeting to suggest topics or to add comments on planned topics or proposals.

[handrews]

Let's continue the data modeling discussion with high level thoughts on SDK vs HTTP interfaces. Background:

• July 30th agenda (we discussed all of this)
• Aug 6th agenda (we only discussed the very first bullet point group so far)

Here are the "for next week" comments from last week's agenda:

• Philosophical discussion about the relative importance of the HTTP-side interface vs the SDK-side interface
  • Is one more important? To whom?
  • How does this fit with how tools are currently written and used?
  • Background philosophical concept: consumer over producer (but consumer of HTTP or consumer of SDK?)
• Scope: XML and other less-common targets
  • many older / more slow-moving standards are still XML-centric
  • Extensibility? It's easier if we don't have to solve all target representation problems up front
  • Note the example of one schema mapping to many targets in the earlier comment- do we need this?
  • One SDK representatoin for multiple representation at the HTTP may make model-to-target mappings more clear
• Consider the use case groups (client, sever, tools- Gary to elaborate on distinctions) in the above comment for any specific data modeling features
  • We'll probably get back to this after the higher-level SDK/HTTP discussions resolve a bit

[earth2marsh]

We'll carry this over to next week!

[earth2marsh]

Today we began with some discussion of URI-encoding and why OpenAPI inherits opinions from its HTTP-orientation.

We then discussed how having an ontology and taxonomy might help organize the rest of the spec work (as well as helping us arrive at some common language!). I think @handrews has done some work in the last 6 months in this space? I also had started some draft definitions, and I walked through some of those. There was general support for more Moonwalk definitions, so please add suggestions and new words to define (and even definitions!) here.

Video has been posted.