Meeting: April 29th, 2025

[earth2marsh]

Weekly meetings happen on Tuesdays

Time: 5pm GMT / 9am Pacific
Zoom: https://zoom-lfx.platform.linuxfoundation.org/meeting/98869769538?password=d769f940-7da7-4de8-9fab-685a1cc8f33e

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.

[earth2marsh]

Topic: continue discussion from last week.

[earth2marsh]

Today we walked through Dan's straw-person for ADA interface for path-template-based signatures. This touched on:

• Considering one use case of what it takes to route incoming traffic to backend services
• That it seems shrewd to have priority as an disambiguator of last resort (assuming that there are always boundaries of ambiguity)
• The idea that you should be able to take the ADA and give you a clear answer on whether it can generate working code or not.
• That ADA should do the level of checking that any tooling should need
• ADA should make it easier for an application that reads an OAD to fail out when it hits something it cannot handle.
• Remember that vendors are used to disregarding parts of the spec that don't apply to them or appear too complicated to implement
• That DOM and ADA are not requirements for tooling. You could very well write a low-level parser that’s not concerned with anything DOM or ADA related. But when you are doing this, we strongly suggest you follow our DOM and ADA roadmap to maintain consistency across tooling. (Though if they want to demonstrate compliance some day, this may be necessary.)

[earth2marsh]

Video is available.