# interoperability Published articles for interoperability. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Building cloud-native PACS on AWS DevFeed: [Building cloud-native PACS on AWS]() Original publisher: [Read original article]() Author: ManojKumar MV Published: 2026-09-17T15:21:06Z Content type: article Language: en Sources: [AWS Architecture Blog]() Topics: [Medical imaging](), [Cloud Architecture](), [Cloud](), [Amazon Web Services](), [Amazon S3](), [interoperability]() Tags: [advanced-300](), [amazon-s3](), [aws](), [capacity](), [capacity-planning](), [cloud-architecture](), [cloud-native](), [interoperability](), [medical-imaging](), [thought-leadership]() ### AI overview This article presents a hybrid cloud architecture for modernizing medical imaging infrastructure across multi-hospital networks. It describes centralizing PACS archives on AWS, supporting cross-facility interoperability, and using Amazon S3 storage tiers for cost and retention management at scale. ### Source excerpt A hybrid cloud architecture pattern for modernizing medical imaging on AWS. Learn how multi-hospital networks can centralize PACS archives, enable cross-facility interoperability, and use Amazon S3 storage tiers to manage cost and retention at scale. ## LF Energy Research Finds Open Source Software Can Deliver 2-5x Greater Net Value for Grid Operators DevFeed: [LF Energy Research Finds Open Source Software Can Deliver 2-5x Greater Net Value for Grid Operators]() Original publisher: [Read original article]() Author: andrewb@proximabiz.com (The Linux Foundation) Published: 2026-09-15T07:00:00Z Content type: news Language: en Sources: [Linux Foundation - Blog]() Topics: [Open Source](), [Software](), [cloud-infrastructure](), [digital sovereignty](), [interoperability](), [Simulation]() Tags: [ai-data-centers](), [case-studies](), [compare](), [cost](), [digital-sovereignty](), [framework](), [infrastructure](), [interoperability](), [linux-foundation](), [open-source](), [renewable-energy](), [report](), [research](), [september-2026](), [software](), [summit]() ### AI overview LF Energy reports that open source software can provide grid operators with 2-5 times greater net value than conventional software procurement. Its Open Source Benefit-Cost Framework evaluates total cost of ownership, risk exposure, strategic value, and societal impact using case studies and simulations. ### Source excerpt New benefit-cost framework gives utilities and regulators a standardized methodology to compare open source with conventional software procurement ## Mesa 26.3 RADV + RadeonSI Ready With DRM Format Modifiers For Older AMD GPUs DevFeed: [Mesa 26.3 RADV + RadeonSI Ready With DRM Format Modifiers For Older AMD GPUs]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-10T21:19:11Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [Wayland](), [interoperability](), [OpenGL](), [Git]() Tags: [amd](), [apis](), [desktop-linux](), [git](), [graphics](), [interoperability](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [performance](), [phoronix](), [phoronix-test-suite](), [ubuntu-benchmarks](), [ubuntu-hardware](), [vulkan]() ### AI overview Mesa 26.3 has merged the Mesa-side support needed for RADV and RadeonSI to use DRM format modifiers on older AMD GFX6 through GFX8 GPUs. The Linux 7.3 kernel cycle adds the corresponding AMDGPU support, enabling improved buffer-layout handling for tiling, compression, performance, and interoperability. ### Source excerpt Coming with Linux 7.3 is DRM format modifiers for GFX6 through GFX8 era GPUs covering the original Raddeon HD 7000 (GCN 1.0) graphics cards up through the Polaris and Fiji series. This work by Valve's Timur Kristóf is necessary for these older GPUs to support Vulkan-based Wayland compositors, better interoperability between OpenGL and Vulkan or other APis, compositors running on the Zink OpenGL-on-Vulkan driver implementation, and other benefits. Now merged for Mesa 26.3 is the RadeonSI and RADV user-space side support for making use of the format modifiers on these older GPUs... ## OIDC is a standard, identity providers are not DevFeed: [OIDC is a standard, identity providers are not]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-09T16:09:50Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [OpenID connect (OIDC)](), [interoperability](), [OAuth](), [JSON Web Tokens](), [Authentication]() Tags: [compatibility](), [interoperability](), [jwt](), [oauth](), [oidc](), [providers]() ### AI overview This article explains why generic OpenID Connect integrations often require provider-specific compatibility settings. It discusses differences in token-endpoint client authentication, including client secret basic, client secret POST, and private key JWT. ### Source excerpt Generic OIDC connections meet identity providers that read the same spec differently. Here are the per-connection compatibility settings we added, and why. ## Cisco and Axis Communications: Greater visibility, scalability, and incident management DevFeed: [Cisco and Axis Communications: Greater visibility, scalability, and incident management]() Original publisher: [Read original article]() Author: Jonathan Cohn Published: 2026-09-09T15:00:31Z Content type: news Language: en Sources: [Cisco Blogs]() Topics: [incident management](), [dashboards](), [interoperability](), [Security](), [Scalability](), [Cloud]() Tags: [boot](), [cisco-networking](), [cloud](), [encryption](), [incident-management](), [integration](), [interoperability](), [networking](), [security]() ### AI overview Cisco and Axis Communications are integrating Axis devices with Cisco Cloud Control through the Meraki dashboard. The integration gives IT and physical security teams centralized visibility into device health, firmware, patches, and connectivity while supporting secure, privacy-focused management across connected locations. ### Source excerpt Cisco and Axis Communications now allow managing Axis devices directly via the Meraki dashboard. This integration unifies IT and physical security, providing centralized visibility and simplified operations on a single, scalable platform. ## From AI Agent to Human Agent: ElevenLabs Call Handoffs with Twilio DevFeed: [From AI Agent to Human Agent: ElevenLabs Call Handoffs with Twilio]() Original publisher: [Read original article]() Author: Ricardo Bangueses Published: 2026-09-09T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Conversational AI](), [voice ai](), [interoperability]() Tags: [ai-agent](), [developer-insights](), [how-to](), [integration](), [interoperability](), [voice]() ### AI overview This tutorial explains how to integrate an ElevenLabs voice agent with Twilio Programmable Voice so the agent can escalate an active call to human-agent routing while preserving call control and useful context. The example uses Twilio Flex as the destination. ### Source excerpt Learn how to integrate an ElevenLabs voice agent with Twilio Programmable Voice for seamless AI-to-human call handoffs, preserving context and call control. ## Calling for Interop 2027 proposals DevFeed: [Calling for Interop 2027 proposals]() Original publisher: [Read original article]() Author: Patrick Brosset Published: 2026-09-03T16:09:17Z Content type: article Language: en Sources: [Microsoft Edge Blog]() Topics: [Interop2027](), [interoperability](), [Web platform](), [web-standards](), [Web Development]() Tags: [browsers](), [developer](), [interop](), [interop2027](), [interoperability](), [uncategorized](), [web-platform]() ### AI overview The article opens the proposal process for Interop 2027, inviting submissions that address inconsistent implementation of standards-based web-platform features across browsers. ### Source excerpt The Interop 2027 call for proposals is open, submit your ideas now! Over the past six years, the I The post Calling for Interop 2027 proposals appeared first on Microsoft Edge Blog. ## Test your custom elements and trust the results with Axe-core's support for ElementInternals DevFeed: [Test your custom elements and trust the results with Axe-core's support for ElementInternals]() Original publisher: [Read original article]() Author: Wilco Fiers Published: 2026-08-27T13:21:18Z Content type: article Language: en Sources: [Deque]() Topics: [Accessibility](), [axe-core](), [interoperability](), [Front end](), [browser](), [Angular](), [React](), [Vue.js](), [aria]() Tags: [a11y-for-developers](), [accessibility](), [angular](), [aria](), [axe-core](), [browser](), [compliance](), [frontend](), [interoperability](), [react](), [testing](), [vue](), [web-accessibility]() ### AI overview The article explains how custom elements and ElementInternals can standardize components across React, Angular, and Vue while allowing components to declare accessibility semantics. It highlights axe-core support for ElementInternals, enabling teams to test accessibility consistently across framework implementations and support compliance at enterprise scale. ### Source excerpt If you're a large enterprise organization with accessibility issues resulting from interoperability challenges, moving to ElementInternals is a savvy move. You can standardize, and safely test. And, with Axe-core now supporting ElementInternals, you can test those components and trust the results. The post Test your custom elements and trust the results with Axe-core's support for ElementInternals appeared first on Deque. ## Rust Function Overloading - Call for Experimentation DevFeed: [Rust Function Overloading - Call for Experimentation]() Original publisher: [Read original article]() Author: teor Published: 2026-08-19T00:00:00Z Content type: release Language: en Sources: [Inside Rust Blog]() Topics: [Rust](), [C++](), [Compiler](), [interoperability]() Tags: [c-plus-plus](), [compiler](), [interoperability](), [languages](), [rust](), [syntax]() ### AI overview The Rust Project is experimenting with function and method overloading for FFI bindings through the incomplete nightly "splat" compiler feature. The experiment aims to assess implementation complexity and improve interoperability with C++, while its design may change or be removed. ### Source excerpt In partnership with the Rust Foundation's Rust-C++ Interop Initiative, the Rust Project has been experimenting with function overloading for FFI bindings. This experiment is now at a stage where compiler and interop tool developers can start exploring function overloading. Stable Rust already supports a form of overloading using tuples and traits, but calling these overloaded functions looks strange, because the overloaded arguments have to be passed as a single tuple argument, like this: hypot((2.0, 3.0, 6.0)). Stable Rust also allows overloading of built-in operators with user-defined types, via traits like Add (the + operator) and Neg (the - value negation operator). We are running an unstable nightly Rust language experiment to answer questions like: How much overloading can we do with Rust's existing trait system? Could this help us call C++ from Rust ergonomically? In the tradition of yeet (to avoid bikeshedding), we are using basic syntax in the first stage of the experiment: the #[rustc_splat] attribute. Alternative syntaxes can be considered later, if the experiment generates useful outcomes. Experimental Function Overloading Rust nightly builds from 2026-07-31 onwards have experimental support for more ergonomic function and method overloading, using the incomplete "splat" compiler feature; if you're a compiler or interop tool developer, we encourage you to experiment with it! This experiment lets overloaded functions be called with separate arguments, like this: hypot(2.0, 3.0, 6.0). No double parentheses required! But type inference and type checking still happen as they would in a stable Rust overload. We are experimenting with splat to get a feel for the complexity of the implementation, and to see if it solves some language interoperability use cases. Like most Rust language experiments, this nightly feature has no RFC, and can change or be removed at any time. Experiment Design We expect the feature to change significantly in future, or to be replace ## Balancing Interoperability and Security in the Age of AI DevFeed: [Balancing Interoperability and Security in the Age of AI]() Original publisher: [Read original article]() Author: Eugene Liderman Published: 2026-08-05T01:00:00Z Content type: opinion Language: en Sources: [Security]() Topics: [AI Bots](), [AI Chat]() Tags: [ai](), [ai-agents](), [android](), [android-security](), [chatgpt](), [claude](), [interoperability](), [none](), [privacy](), [sandboxes](), [security]() ### AI overview The article argues that proposed EU interoperability measures for Android AI services could require user-downloaded AI agents to receive deep system access, weakening Android's security model. It calls for safeguards and cybersecurity consultation during implementation. ### Source excerpt Over the last six months, we have been engaging closely with the European Commission (EC) after they opened specification proceedings related to Android interoperability... ## Adapting open source practices to an AI-first world: A retrospective on 2025 DevFeed: [Adapting open source practices to an AI-first world: A retrospective on 2025]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-08-03T18:30:00Z Content type: article Language: en Sources: [Google Open Source Blog]() Topics: [Open Source](), [Google](), [A2A protocol](), [interoperability](), [GitHub](), [linux foundation](), [Protocol (disambiguation)](), [LLVM](), [Rust](), [vllm](), [gRPC](), [Kubernetes]() Tags: [2025](), [a2a](), [a2a-protocol](), [agents](), [ai](), [ai-agents](), [github](), [google-open-source](), [interoperability](), [kubernetes](), [linux](), [linux-foundation](), [open-source](), [report-card](), [retrospective](), [rust](), [security](), [vllm]() ### AI overview Google reviews Alphabet's 2025 open source activity, including employee and external contributions, collaboration on the Agent2Agent protocol, and the maintenance and launch of public repositories and tools. ### Source excerpt by Sophia Vargas, Google Open Source Even as AI adoption accelerates and transforms the global technology landscape, open source remains foundational to how Alphabet builds, uses, and collaborates on products for billions of users. Our commitment to open source remains broad and consistent, including sharing our work year-over-year, and reflecting on what we've learned. In 2025: Roughly 10% of Alphabet's full-time workforce actively contributed to open source projects. This contribution ratio has remained steady over the past five years, scaling to match our growth. These open source contributions are not just solely focused on Google. Our top projects by unique contributors at Alphabet include community-led projects such as LLVM, vLLM, Envoy, and Rust, as well as Google-initiated projects like Kubernetes, Apache Beam, and gRPC. In addition, Alphabet projects received commits from more than 20,000 non-Alphabet affiliated user accounts. Working together on emerging standards Open source communities continue to provide vital collaborative spaces to define emerging standards, ensuring the interoperability and extensibility for the next generation of technologies. In 2025, we worked with more than 50 partners on the Agent2Agent (A2A) protocol to enable AI agents to communicate with each other, securely exchange information, and coordinate actions on top of various enterprise platforms and applications. Within weeks of our initial announcement, Google donated the A2A project to the Linux Foundation as part of our long-standing commitment to develop "open, collaborative ecosystem - offering greater autonomy and multiplying productivity." Launching tools with transparency Open source licenses provide a framework for anyone to explore, test, fork and expand on our technologies. Over the last 15 years, Google has created more than 15,000 public repositories on GitHub. Today, Google continues to maintain more than 5,000 public repositories on GitHub, and more than 1,500 publi ## A big win for Android interoperability DevFeed: [A big win for Android interoperability]() Original publisher: [Read original article]() Author: Timothy Nibeaudeau Published: 2026-07-31T00:00:01Z Content type: article Language: en Sources: [Home Assistant]() Topics: [Android](), [interoperability](), [Home Assistant](), [Automation](), [Google]() Tags: [2026](), [android](), [automation](), [developer](), [eu](), [gemini](), [google](), [interoperability](), [news](), [privacy](), [self-hosted](), [voice]() ### AI overview The article describes the European Commission's July 16, 2026 decision under the Digital Markets Act requiring Alphabet to open eleven Android features to all assistants on equal terms. It presents the decision as a result of advocacy by the Open Home Foundation and a significant step toward Android interoperability, enabling capabilities such as always-on wake word detection, ambient sensor access, and screen automation for Home Assistant and other assistants. ### Source excerpt Something big just happened. As the Open Home Foundation's Android developer for Home Assistant, I was invited by the European Commission to consult on Android interoperability. On July 16, 2026, the Commission adopted a decision requiring Alphabet to open up eleven Android features -- including always-on wake word detection, ambient sensor access, and screen automation -- to all assistants, on equal terms. ## Stronger with every update: How we're making Chrome and the web safer in the AI Era DevFeed: [Stronger with every update: How we're making Chrome and the web safer in the AI Era]() Original publisher: [Read original article]() Author: Chrome Security Team Published: 2026-07-30T17:00:00Z Content type: article Language: en Sources: [Security]() Topics: [Chrome](), [Security](), [Vulnerabilities](), [Artificial Intelligence](), [Large Language Model](), [Fuzzing/Fuzz testing](), [Agent Harness](), [V8](), [JavaScript](), [interoperability](), [Resilience](), [Software]() Tags: [agent](), [ai](), [ai-models](), [bug](), [bugs](), [chrome](), [chrome-security](), [exploits](), [fuzzing](), [interoperability](), [javascript](), [none](), [resilience](), [security](), [vulnerabilities]() ### AI overview This article describes how Chrome's security teams use large language models, fuzzing, specialized research tools, and AI vulnerability-discovery agents to find and remediate security bugs more quickly. It highlights Big Sleep, an agent harness using Gemini, model interoperability, and a Chrome knowledge base built from CVEs and Git history. ### Source excerpt Video of Chrome logo turning into a shield ## Federated platforms: Scaling platform adoption in the enterprise DevFeed: [Federated platforms: Scaling platform adoption in the enterprise]() Original publisher: [Read original article]() Author: Johannes Rudolph Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [interoperability](), [Kubernetes](), [Cloud]() Tags: [cloud](), [enterprise](), [github-actions](), [interoperability](), [kubernetes](), [platform](), [platform-engineering](), [scale](), [sre](), [star-trek]() ### AI overview The article argues that scaling platform engineering in large enterprises is primarily a diplomatic challenge rather than a technical one. It uses Star Trek's Borg as a metaphor for centralized, tightly controlled platforms and presents federated platforms as a way to reduce political friction, improve interoperability, and turn resistant application teams into allies. ### Source excerpt Stop fighting for "total assimilation." Learn how the federated platform model uses Star Trek metaphors and diplomatic tactics to overcome political friction, enable interoperability, and successfully scale platform engineering in the enterprise by turning platform detractors into allies ## Get Ready: 2026 Python Packaging Council Nominations Opening Soon! DevFeed: [Get Ready: 2026 Python Packaging Council Nominations Opening Soon!]() Original publisher: [Read original article]() Author: Pradyun Gedam Published: 2026-07-23T00:00:00Z Content type: article Language: en Sources: [Python Insider]() Topics: [Python](), [interoperability](), [Maintainers]() Tags: [community](), [interoperability](), [maintainers](), [python](), [user-experience]() ### AI overview The Python Packaging Council's inaugural election opens for nominations on July 28, 2026, and closes on August 11. The council will guide interoperability specifications for building, distributing, and installing Python packages, while coordinating maintainers, the Python core team, and the wider community. ### Source excerpt The inaugural Python Packaging Council election nomination period opens on Tuesday, July 28th, 2:00 pm UTC and closes on Tuesday, August 11th, 2:00 pm UTC. ## Many Sovereignties, One Internet DevFeed: [Many Sovereignties, One Internet]() Original publisher: [Read original article]() Author: Hisham Ibrahim Published: 2026-07-15T07:09:49Z Content type: opinion Language: en Sources: [RIPE Labs]() Topics: [digital sovereignty](), [interoperability](), [Resilience](), [Internet]() Tags: [bgp](), [digital-sovereignty](), [governance](), [infrastructure](), [internet](), [interoperability](), [ipv6](), [policy](), [resilience](), [rpki](), [sovereignty-and-the-commons](), [standards]() ### AI overview The article proposes a "commons test" for evaluating digital sovereignty policies. It distinguishes strategies that expand choice, preserve interoperability, strengthen resilience and support participation from those that create dependencies and chokepoints. It argues that the Internet's technical coordination core should remain globally interoperable and should not be repurposed for broader national policy or political control. ### Source excerpt Digital sovereignty is not simply good or bad. The commons test offers a practical framework for assessing whether different strategies expand choice, preserve interoperability, strengthen resilience and support meaningful participation, or create new dependencies and chokepoints. ## Workshop Basel day one DevFeed: [Workshop Basel day one]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-07-14T20:25:28Z Content type: article Language: en Sources: [Daniel Stenberg]() Topics: [HTTP](), [networking](), [interoperability]() Tags: [http](), [http-workshop](), [interoperability](), [network](), [networking](), [quic](), [switzerland](), [web]() ### AI overview A report from the first day of the seventh HTTP workshop in Basel, Switzerland, covering discussions about extending REST and HTTP for state synchronization, Last-Modified header usage, HTTP usage data, and interoperability challenges. ### Source excerpt On this hot summer's day in Basel, Switzerland, the seventh HTTP workshop started. These events tend to work roughly the same way and the people in the room are also to large extent familiar and known since previous editions. Forty people in a meeting room, where we take turns in doing short talks on HTTP ... Continue reading Workshop Basel day one -> ## Agent interoperability: a complete explainer DevFeed: [Agent interoperability: a complete explainer]() Original publisher: [Read original article]() Author: Jeff Mills Published: 2026-07-14T00:00:00Z Content type: article Language: en Sources: [Redis Blog]() Topics: [AI Bots]() Tags: [agent](), [agents](), [ai](), [ai-agent](), [frameworks](), [integration](), [interoperability](), [tech-de](), [tools]() ### AI overview An explainer on enabling AI agents built with different frameworks to discover one another, share context, and delegate tasks without custom integrations. It outlines integration sprawl, duplicated work, brittle wiring, and fragmented context as consequences of poor interoperability. ### Source excerpt You built a research AI agent in the LangGraph framework. Another team shipped a customer-service agent in CrewAI. A third team wired up tools through the OpenAI Agents SDK. Now leadership asks: can these things work together? For most teams, the hone... ## Packaging Council Inaugural Election Dates DevFeed: [Packaging Council Inaugural Election Dates]() Original publisher: [Read original article]() Author: Pradyun Gedam Published: 2026-06-28T00:00:00Z Content type: news Language: en Sources: [Python Insider]() Topics: [Python](), [interoperability](), [Maintainers](), [Processes]() Tags: [2026](), [community](), [governance](), [interoperability](), [maintainers](), [python]() ### AI overview The Python Packaging Council is being established under PEP 772 to oversee packaging specifications and coordinate Python packaging efforts. Its inaugural five-member election will take place alongside the 2026 Python Software Foundation Board election, with staggered terms for elected members. ### Source excerpt A new Python Packaging Council (PPC) is being established, with their election of the inaugural PPC will be held in parallel to the 2026 PSF Board election. ## Four travel and hospitality trends from HITEC 2026 DevFeed: [Four travel and hospitality trends from HITEC 2026]() Original publisher: [Read original article]() Author: Andrew Beckmann Published: 2026-06-23T00:00:00Z Content type: article Language: en Sources: [Stripe Blog]() Topics: [AI Chat]() Tags: [ai](), [ai-agents](), [automation](), [conference](), [data](), [google](), [infrastructure](), [interoperability](), [operations](), [search]() ### AI overview The article reports HITEC 2026 trends in hospitality technology, focusing on the gap between AI investment and operational readiness. It also describes how AI-generated search answers are changing direct-booking strategies toward accurate, machine-readable property data. ### Source excerpt More than 6,000 hospitality executives and operators gathered in San Antonio last week for the HITEC conference. The big topic: whether the industry's AI investment is actually working. Across four days and over 50 meetings, four trends stood out. ## Open rails for agentic commerce at Open Source Summit North America 2026 DevFeed: [Open rails for agentic commerce at Open Source Summit North America 2026]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-06-16T23:16:03Z Content type: opinion Language: en Sources: [Google Open Source Blog]() Topics: [Artificial Intelligence](), [Open Source](), [systems](), [Protocol (disambiguation)]() Tags: [2026](), [agentic](), [agentic-commerce](), [ai](), [ai-agents](), [business](), [capabilities](), [checkout](), [consumer](), [e-commerce](), [features](), [fragmentation](), [integration](), [interoperability](), [open-source](), [open-standards](), [payment](), [platforms](), [shopping](), [standard](), [ucp](), [universal-commerce-protocol](), [workflows]() ### AI overview An article from Open Source Summit North America 2026 explains why agentic commerce may require shared, open rules and integrations. It presents Universal Commerce Protocol (UCP) as an open standard intended to let agents, businesses, consumer surfaces, and payment providers work together across shopping, checkout, fulfillment, and post-purchase flows. ### Source excerpt by Anurag Sinha, Universal Commerce Protocol (UCP) At Open Source Summit North America 2026, I shared why agentic commerce needs open rails. As AI agents become more capable, the shopping journey is shifting from "show me" to "help me." Instead of browsing, comparing, clicking, and checking out step by step, people can increasingly ask an agent to help them decide what to buy and, in some cases, complete the purchase. Industry forecasts suggest agentic shopping could account for roughly 10% to 25% of U.S. e-commerce by 2030 (Bain), which points to a meaningful shift in how digital commerce will work. Watch the full keynote here. Why shared rules matter That shift also exposes a challenge. Commerce is still highly fragmented. Different businesses, payment providers, and platforms operate with their own rules, workflows, and business logic. Every new surface adds more integration work. Every bespoke connection creates more complexity. And that fragmentation makes it harder for AI systems to understand and perform commerce actions consistently across businesses. A shared language lowers that barrier for everyone. A common language for agentic commerce That is the problem Universal Commerce Protocol (UCP) is designed to solve. We launched the Universal Commerce Protocol, or UCP, with industry leaders to establish an open standard for agentic commerce, built to work across the shopping journey. UCP creates a common language for agents and systems to operate together across consumer surfaces, businesses, and payment providers, so the ecosystem does not need a different bespoke integration for every new agent or platform. Just as importantly, UCP is designed for the real world. Every business has its own way of selling. Checkout, fulfillment, loyalty, policy logic, shipping, and post-purchase flows can vary widely between a local shop, a marketplace, and a large retailer. UCP is built to support that reality. A layered architecture for a shared commerce language UCP uses a ## A2A in Java: hands on Embabel DevFeed: [A2A in Java: hands on Embabel]() Original publisher: [Read original article]() Author: Aneshka Goyal Published: 2026-06-16T08:44:44Z Content type: tutorial Language: en Sources: [Amex GBT Technology]() Topics: [Embabel](), [A2A protocol](), [Java](), [Spring AI](), [Agent Framework](), [interoperability](), [Artificial Intelligence](), [Large Language Model]() Tags: [a2a](), [a2a-protocol](), [agent-framework](), [ai](), [embabel](), [interoperability](), [java](), [large-language-models-llms](), [software-engineering](), [spring-ai]() ### AI overview This hands-on article introduces A2A in Java and explores Embabel, a Java agent framework built on Spring AI. It explains how A2A enables interoperability among agents across languages, frameworks, vendors, and platforms, and describes Embabel's use of goal-oriented action planning with existing Java domain logic and structured code. ### Source excerpt Part 1: What is Embabel? A2A, or Agent-to-Agent Protocol, is an open standard (now under the Linux Foundation) that provides a common language for diverse AI agents to communicate, collaborate, and share tasks, enabling interoperability across different frameworks, vendors, and platforms. You can read more about A2A here. A2A makes agents framework and tech stack agnostic, which means agents developed in Python will be able to connect to other agents in Java or any other programming language of choice (given we have A2A protocol compliance). We currently have ADK (Python) and other Python specific frameworks that simplify the development of A2A compliant agents (as you'll read in this blog). This initiative explores creating a comparable Java-specific framework to enable building A2A-compliant agentic applications in Java. Brief about Spring AI Before learning about Embabel, it's important to discuss and know about Spring AI which provides the foundation for Embabel framework. The Spring AI project aims to streamline the development of applications that incorporate artificial intelligence functionality without unnecessary complexity. This project draws inspiration from notable Python projects, such as LangChain and LlamaIndex, but Spring AI isn't a direct port of those projects. The project was founded with the belief that the next wave of generative AI applications will not only be for Python developers but ubiquitous across many programming languages. Spring AI can be used without Embabel (or any other high level framework like ADK java) to create agents and agentic applications. For more info around how to use Spring AI, check out Part 1 and Part 2. What is Embabel? Embabel is an agent framework built on Spring AI, designed to integrate Large Language Models (LLMs) with existing domain logic and structured code in Java applications. It utilizes a Goal-Oriented Action Planning (GOAP) mechanism to allow agents to dynamically determine the sequence of actions needed ## Introducing glTF 2.1 with Complex Scenes DevFeed: [Introducing glTF 2.1 with Complex Scenes]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-06-11T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [3D](), [interoperability](), [Tooling](), [Streaming](), [Simulation]() Tags: [3d](), [announce](), [api](), [blog-glt](), [gltf](), [interoperability](), [release](), [streaming](), [tooling]() ### AI overview The Khronos 3D Formats Working Group announces plans for glTF 2.1, a focused and backward-compatible revision designed to support large, composed scenes. Proposed capabilities include multi-file scene graphs, spatial primitives, stable object IDs, progressive 3D streaming support, larger GLB files, and a formally deprecated multiple-scenes pattern. ### Source excerpt Since the release of glTF™ 2.0 in 2017, the format has matured into a rich ecosystem spanning mesh compression, texture optimization, 3D Gaussian splats, and more. Today, the Khronos® 3D Formats Working Group is excited to announce plans for glTF 2.1: a focused, backward-compatible revision of the core specification, built around a single motivation -- making glTF work as well for large, composed scenes as it already does for single assets. Every feature in this release addresses a real gap that today forces teams toward proprietary conventions, custom tooling, or workarounds that break interoperability. ## The Open Source Community is backing OpenEnv for Agentic RL DevFeed: [The Open Source Community is backing OpenEnv for Agentic RL]() Original publisher: [Read original article]() Author: ben burtenshaw; Joseph Spisak; Lysandre; Davide Testuggine; will brown; Joy Liu; Peyton Walters; Chris Wing; Daniel (Unsloth); Andrew Zhou Published: 2026-06-08T00:00:00Z Content type: release Language: en Sources: [Hugging Face - Blog]() Topics: [openenv](), [interoperability](), [Open Source](), [Artificial Intelligence](), [Machine learning]() Tags: [agentic](), [agents](), [ai](), [announcement](), [community](), [interoperability](), [open-source](), [releases](), [rl]() ### AI overview OpenEnv is becoming a more open, community-governed interoperability layer for training agents with reinforcement learning. It standardizes how RL environments are published, deployed, and consumed while allowing different models, harnesses, inference engines, and training libraries to work together. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. [Next page]()