<?xml-stylesheet type="text/xsl" href="https://emersonexchange365.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>OPC .NET 3.0 is New Name for OPC&amp;#160;Xi</title><link>/services/b/implementbuild/posts/opc-net-3-0-is-new-name-for-opc-160-xi</link><description>In case you haven’t seen this news yet, the OPC Foundation has renamed OPC Xi to OPC .NET 3.0 (WCF). Let’s call it OPC .NET 3.0 for short. It’s the same client/server connectivity standard and functionality for the process industries that I’ve been describing</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator></channel></rss>