Feat/57/february 2026 newsletter

src/website/blog/2025-04-12-newsletter.md

@@ -0,0 +1,160 @@
+---
+slug: 2025-04-12-december-oai-newsletter
+publication-date: 2025-04-12
+author: Chris Wood
+---
+
+# OpenAPI Initiative Newsletter – December 2025
+
+Welcome to the OpenAPI Initiative (OAI) December 2025 newsletter! This is our
+last newsletter of 2025, and we'll be reflecting on what the community has
+accomplished this year as well as looking forward to 2026!
+
+### Events News
+
+We'll start this edition of the newsletter with Events news as our OpenAPI
+Conference at FOST, the conference formerly known as Apidays, starts December 9!
+This year the OAI Track has been promoted to a full subconference, with a
+complete agenda on December 11.
+
+Highlights of the full program at FOST include:
+
+- [Erik Wilde](https://www.linkedin.com/in/erikwilde/) and
+  [Frank Kilcommins](https://www.linkedin.com/in/frank-kilcommins/) wil be
+  running a workshop "API Management for the AI Era: Leveraging OpenAPI
+  Standards" (registration required) which gets to the heart of how you can
+  leverage OAI specifications for AI.
+
+- We are hosting an Executive Breakfast where you can learn more about what it
+  means to be an OAI member and meet members of the community. This is an
+  invite-only event, so watch your inbox!
+
+- Our subconference starts at 0915 on the Wednesday, and highlights include
+  What's New in OpenAPI 3.2
+  ([Lorna Mitchell](https://www.linkedin.com/in/lornajane/)), API Workflow
+  Testing and Mocking with a Single Arazzo Spec
+  ([Naresh Jain](https://www.linkedin.com/in/nareshjain/)), and Is OpenAPI still
+  relevant in the age of AI?
+  ([Emmanuel Paraskakis](https://www.linkedin.com/in/emmanuelparaskakis/)).
+
+2026 promises to be an exciting year and in bringing 2025 to close our OAI
+Ambassador and custodian of the OAI Track Erik Wilde puts the outlook for future
+events like this: "_For the past two years, OAI has actively fostered the
+OpenAPI community with organizing events at various events, most recently with
+our first OpenAPI Conference at API Days Paris. We plan on continuing these
+efforts in 2026, tentatively planning events in San Jose, Singapore, New York,
+London, Santa Clara, and Paris. If you're interested in APIs and OpenAPI, join
+us at one of these events in 2026! We also just launched our very own
+[conference site](https://conference.openapis.org/) so that going forward, you
+can find up-to-date information about all of our events in one place._"
+
+Our new conference and events website has been created to help highlight the
+work that OAI is doing bringing in-person events to the community, and will
+provide a complete picture of the agendas, talk and workshop abstracts, and
+speaker profiles in one place. Massive thanks here to
+[Pavel Kornev](https://www.linkedin.com/in/pavelkornev/), from OAI member SAP,
+who led the project with a clear vision for a cleaner, more modern experience,
+with [Juri Jatschmenow's](https://www.linkedin.com/in/jurijat/) outstanding
+development work bringing that vision to life. On his teams contributions, Pavel
+says: "_Designing the new OpenAPI Conference Paris 2025 landing page has been an
+exciting journey for our team. We’re both proud to contribute to the OpenAPI
+Initiative and thrilled to support an event that brings the community together.
+This is just the beginning — we’re looking forward to enhancing even more
+landing pages across the Initiative._"
+
+### Initiative News
+
+There’s been a enthusiastic reception to our OpenAPI Specification v3.2 release,
+with a great deal of coverage and interest from the community in the new
+features and capabilities. As a reminder, v3.2 provides a host of changes such
+as the refactored and improved
+[Tag Object](https://spec.openapis.org/oas/latest.html#tag-object), support for
+the `QUERY` HTTP Method, support for sequential and streaming data protocols,
+and additional Security Scheme features like OAuth 2.0 Device Authorization
+Flow. You can find out more in our
+[blog post](https://www.openapis.org/blog/2025/09/23/announcing-openapi-v3-2)),
+which includes links to key resource to help with upgrading to v3.2. Our
+[Ecosystem Spotlight](#ecosystem-spotlight) also provides resources from the
+community on what the v3.2 upgrade means.
+
+Completing v3.2 means we are now looking at what could appear in our next
+version and beyond, and the team is ramping up for further releases, with a view
+to v3.3 that covers improvements to Security Schemes and greater integration
+with MCP and AI protocols more generally. If you want to find out more, please
+checkout the Discussions on the OpenAPI Specification
+[repository](https://github.com/OAI/OpenAPI-Specification/discussions).
+
+Work has also started for an Arazzo Specification v1.1.0 release, with perhaps
+the most significant change being the addition of support for AsyncAPI. AsyncAPI
+support will provide the means to describe workflows for both HTTP-based and
+message-orientated APIs, providing a significant uplift to how Arazzo can
+describe sequences of API operations with different architectural styles and
+provide improved capabilities for calling sub-workflows. Other planned
+enhancements include improvements to JSONPath and XPath support, and a number of
+fixes identified since v1.0.1. You can find out more about the plans for v1.1.0
+[here](https://github.com/OAI/Arazzo-Specification/discussions/379).
+
+Overlay is also gearing up for a v1.1.0 release, with several features in the
+frame such as clarifications to format interoperability and a new Parameter
+Object in the frame. If you want to contribute or simply find out more about
+what's going on, head over to the
+[Overlay Specification repository](https://github.com/OAI/Overlay-Specification).
+
+### Ecosystem Spotlight
+
+We've already mentioned the release of v3.2 and we've had a great feedback from
+the community. Here's a few samples of what folks are saying.
+
+- [Dave Shanley](https://www.linkedin.com/in/daveshanley/) brought together a
+  really comprehensive [overview](https://quobix.com/articles/openapi-3.2/) of
+  all the new features of v3.2 ("_I love that new feature smell _") with plenty
+  of snippets showing exactly how to implement them.
+
+- [Anton Okolelov](https://www.linkedin.com/in/anton-okolelov/) also
+  [dug deep](https://medium.com/@okoanton/openapi-3-2-0-evolving-with-modern-api-patterns-9977972e9381)
+  in his overview, describing streaming support as "_a long overdue addition_".
+  He summarizes the value of v3.2 in this way: "_While no specification can
+  anticipate every future pattern, OpenAPI 3.2.0 demonstrates a willingness to
+  adapt to observed practices rather than dictating them. That’s a healthy
+  approach for any evolving standard._"
+
+- [Zaid Daba'een](https://www.linkedin.com/in/zaiddabaeen/) describes the update
+  as focusing "_...on the real pain points that show up when you scale: messy
+  docs, patchy auth support, and unclear streaming behavior._"
+
+For the contributors involved in the creation of v3.2, of which there was the
+greatest number yet in OpenAPI Specification versions, this level of validation
+is vital for the ongoing development of the OpenAPI Initiative Specifications.
+Getting great feedback - good and bad - which puts the new features in context
+are critical to address new features in future versions in earnest, and
+delivering what the OpenAPI, Arazzo, and Overlay communities really need.
+
+### Membership
+
+The work on the Conference website shows the power of the our community, in that
+a member organization helped bring an exciting new resource to life. We worked
+hard on revamping our member proposition this year, and next year we are hoping
+to bring exciting new features to life. If you are interest in becoming a
+member, head over to the
+[membership page](https://www.openapis.org/membershipjoin) on our website to
+find out more.
+
+### Finally
+
+Thank you for reading our newsletter. As always, we welcome suggestions on how
+we can improve it or bring you information that can help make the most of how
+you use specifications published by the OpenAPI Initiative.
+
+Please get in touch on the Outreach channel on Slack if you would like to work
+with us to tell your story, to feature in the Ecosystem Spotlight section, or
+get involved with any of the initiatives described above. We’d also like to hear
+from organizations, tooling makers, or community members for further reactions
+to our v3.2 release, and to share any stories in their adoption journey.
+
+Until next time, and happy holidays!
+
+Contributors: [Chris Wood](https://linkedin.com/in/sensiblewood),
+[Erik Wilde](https://www.linkedin.com/in/erikwilde/),
+[Pavel Kornev](https://www.linkedin.com/in/pavelkornev/),
+[Henry Andrews](https://github.com/handrews),
+[Lorna Mitchell](https://www.linkedin.com/in/lornajane/)

src/website/blog/2026-02-05-newsletter.md

@@ -0,0 +1,160 @@
+---
+slug: 2026-02-05-february-oai-newsletter
+publication-date: 2026-02-05
+author: Chris Wood
+---
+
+# OpenAPI Initiative Newsletter – February 2025
+
+Welcome to the OpenAPI Initiative (OAI) February 2025 newsletter!
+
+This is our first newsletter of 2026, and there is already plenty to share from
+the OAI community.
+
+### Initiative News
+
+We've made a great start to 2026 in the Overlay world with completion of version
+1.1.0 of the
+[Overlay Specification](https://spec.openapis.org/overlay/v1.1.0.html). Version
+1.1.0 brings several new features, including a new `copy` property for the
+Action Object, which can be used to copy or move an element in the OpenAPI
+document. This property is great for operations where you may already have a
+source-of-truth embedded in part of you API description, and want to use it
+across all operations. For example, you might implement a `default` Response
+Object and wish to copy it to all Operation responses for consistency for API
+consumers.
+
+Other improvements include the ability to `update` primitive values - strings,
+integers, and so on - rather than updating the parent object, making Overlay
+documents more concise and easier to manage. The specification has also been
+updated for full compliance with
+[RFC 9535](https://www.rfc-editor.org/rfc/rfc9535), to ensure tooling makers are
+creating Overlay tools through guidance that is fully compatible with the latest
+JSONPath standards.
+
+If you want know more on the upgrade path from v1.0.0 to v1.1.0 you can use this
+[helpful guide](https://learn.openapis.org/upgrading/overlay-v1.0-to-v1.1.html).
+As always, new versions of our specifications are nothing without our community
+of contributors, so a _*huge*_ thanks to [Vincent Biret](https://linkedin.com/),
+[Lorna Mitchell](https://linkedin.com/), [Ralf Handl](https://linkedin.com/),
+and [Michael Kistler](https://linkedin.com/) for contributions, reviews, and
+support.
+
+The
+[Moonwalk Special Interest Group](https://github.com/OAI/sig-moonwalk/discussions)
+(SIG) has also entered 2026 with a new focus. The SIG will continue to explore
+concepts that go beyond the current OpenAPI v3 Specification, with a particular
+focus in the first 6 months of 2026 on how OpenAPI relates to large language
+models (LLMs) as a new class of API clients. The groups aims to investigate what
+additional metadata or structural information might be needed in OpenAPI
+documents to make them more “agent-ready” for LLM use, including capability
+discovery and intent signaling. Several open questions are being posed,
+including around surfacing capabilities, grouping functionality for agents, and
+optimizing descriptions for LLM-based workflows. You can find the full scope of
+this initiative [here](https://github.com/OAI/sig-moonwalk/discussions/219).
+
+As always, initiatives as important as this do not create themselves (whatever
+the capabilities of AI), so the Moonwalk SIG is looking for new contributors and
+hosts to help in this important work.
+
+### Events News
+
+The end of last year saw our final event of the year, the Future of Software
+Technologies (FOST) - forever known as Apidays - Paris conference. The event
+attracted a huge number of delegates, speakers, and exhibiters, with APIs still
+obviously the key theme, but the role of AI, standards such as MCP, AI and
+agentic security, and the intersection between agents and APIs being key talking
+points throughout.
+
+OAI hosted our own sub-conference, hosted by
+[Erik Wilde](https://www.linkedin.com/in/erikwilde/) and
+[Frank Kilcommins](https://www.linkedin.com/in/frank-kilcommins/) with a stellar
+line-up from the OAI community and huge interest from the community with a
+packed conference room for most sessions. We saw speakers such as
+[Emmanuel Paraskakis](https://www.linkedin.com/in/emmanuelparaskakis/) talk
+about API design in the context of AI-based design workflows,
+[Marjukka Niinioja](https://www.linkedin.com/in/marjukkaniinioja/) describe how
+to embed OpenAPI into daily workflows using Lean principles to eliminate API
+delivery waste., and
+[Dimitri van Hees](https://www.linkedin.com/in/dimitrivanhees/) give an overview
+of the Dutch Government API developer portal and their OpenAPI-first approach
+for public sector APIs.
+
+This year we'll be keeping our focus on our successful partnership with FOST
+whilst continuing to develop new relationships with other conferences. To that
+end our first conference of the year is the OpenAPI Summit at
+[DeveloperWeek, San Jose](https://www.developerweek.com/conference/openapi-summit/),
+with a full day of speakers focusing on all things OAI and AI. We have
+[Henry Andrews](https://github.com/handrews) providing an overview of v3.2 of
+OpenAPI, [Sumit Amar](https://www.linkedin.com/in/samar/) focusing on using AI
+tools like Copilot and Cursor to automate API design, development, testing, and
+observability, and
+[Kuldeepak Angrish](https://www.linkedin.com/in/kuldeepakangrish/) and
+[Budha Bhattacharya](https://www.linkedin.com/in/budha-b/) discussing how API
+standards and governance create the foundation for AI-readiness before
+implementing LLMs or MCP. Head over to our dedicated
+[Events site](https://conference.openapis.org/) for more details.
+
+We also have Apidays Singapore, New York, and Munich - and of course Paris -
+already lined-up for this year. Stay tuned the newsletter and updated on our
+Events site and
+[LinkedIn page](https://www.linkedin.com/company/open-api-initiative) for
+details as they are finalized!
+
+### Ecosystem Spotlight: Jentic AI-Readiness Scorecard
+
+The Ecosystem Spotlight in this newsletter is provided by
+[Jentic](https://jentic.com), an OAI member who leverages both OpenAPI and
+Arazzo to provide deterministic and reliable agentic workflows.
+
+_As AI agents become first-class API consumers, a question emerges that linters
+can't answer: can an agent actually reason about this API, and use it safely?_
+
+_Jentic's AI-Readiness Scorecard addresses the gap between specification
+validity and machine usability. A syntactically correct OpenAPI document
+guarantees grammar conformance, not that an agent can interpret intent,
+construct valid requests, or handle errors gracefully. Developers compensate for
+ambiguity through trial and error; agents either halt or worse, proceed with
+confident but incorrect assumptions._
+
+_The scorecard evaluates APIs across six dimensions: foundational compliance,
+developer experience, AI interpretability, agent usability, security, and
+discoverability. Each dimension produces rich diagnostics that pinpoint exactly
+where improvements yield the highest gains for both human developers and AI
+agents. Analysis of 1,500+ APIs revealed consistent obstacles: missing server
+definitions, authentication buried in prose rather than the spec, sparse or
+contradictory examples, and broken schema references._
+
+_"AI systems don't just scan API descriptions; they must interpret, reason, and
+act on them reliably," notes Frank Kilcommins, Head of Enterprise Architecture
+at Jentic and co-author of the Arazzo Specification. "The scorecard provides
+concrete benchmarks and rich diagnostics on score breakdowns, so you know where
+you are and what investments will return the most reward. We're building
+automatic improvement capabilities leveraging the Overlay specification, helping
+teams move from insights to actionable fixes."_
+
+_You can learn more about the scoring framework, and/or try it for free with
+your own APIs at https://jentic.com/scorecard._
+
+### The Outlook for 2026
+
+2026 promises to be another exciting year for OAI, with the growing opportunity
+of specification updates, collaboration with industry verticals and software
+foundations who rely on OAI specifications, and the exploration into greater
+compatibility with AI and agentic tooling. As ever, we are always on the lookout
+for new members, so if you are thinking of getting involved becoming a member is
+one way of contributing to the work OAI does. Head over to the
+[membership page](https://www.openapis.org/membershipjoin) on our website to
+find out more.
+
+Thank you for reading our newsletter. As always, we welcome suggestions on how
+we can improve it or bring you information that can help make the most of how
+you use specifications published by OAI. Please get in touch on the
+[Outreach channel](https://open-api.slack.com/archives/C0KM0KXU6) on Slack if
+you would like to work with us to tell your story, to feature in the Ecosystem
+Spotlight section, or get involved with any of the initiatives described above.
+We’d really like to hear from organizations, tooling makers, or community
+members who have success stories to tell, so we can celebrate their successes on
+the blog.
+
+Until next time!