# Open standards Published articles for Open standards. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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 ## Why Open Source May Not Always Work For IoT DevFeed: [Why Open Source May Not Always Work For IoT]() Original publisher: [Read original article]() Published: 2014-10-20T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Internet of things](), [Open Source](), [Internet](), [Software]() Tags: [iot](), [open-source](), [open-standards](), [standards](), [technology]() ### AI overview This opinion argues that Internet of Things systems should use small, componentized open standards while distinguishing open specifications from open source software. It maintains that both open-source and proprietary implementations can have a place in IoT, and uses HTTP and replaceable components as supporting examples. ### Source excerpt On Friday, Matt Asay wrote an article on readwrite about why the Internet of Things has to be open sourced that triggered a lot positive responses in my Twitter feed. I generally agree with what Matt had to say, but I found it unsettling that he conflates open source software with open specification. This distinction is important! There is a place for both open source and proprietary in the IoT and I believe that ignoring these differences will cause more harm than good. ## The Web at 25 DevFeed: [The Web at 25]() Original publisher: [Read original article]() Author: Brendan Eich Published: 2014-03-12T14:20:16Z Content type: opinion Language: en Sources: [Brendan Eich]() Topics: [Web](), [Internet](), [Open Source](), [systems]() Tags: [future](), [i](), [internet](), [interoperation](), [mozilla](), [open-source](), [open-standards](), [surveillance](), [uncategorized](), [web]() ### AI overview Brendan Eich reflects on the World Wide Web's 25th anniversary and considers how the Internet may change over the next 25 years. He argues that open systems, open standards, and open source will become increasingly important as computing becomes more personal and pervasive. ### Source excerpt The World Wide Web is 25 years old today. The Web is a big deal (as is the Internet on which it is built), I don't need to tell you! But I did have a few thoughts, solicited by a friend who asked "where [do] you think the future of the Internet will take us ... Continue reading "The Web at 25"