I don't have an example per se, but the standard dwells on use of xml for use in SoC builders so IP from all vendors can be picked up by each other's tools. It does not affect the designer, only the tool. When the internet started, different systems could not communicate until XML came along and the analogous situation exists among the SoC builders.
This is wonderful news and for me, it's a definite 'green shoot' for recovery from lingering effects of the Great Recession. So companies are better able to look at long term solutions for IP Reuse. Work slowed down on the deployment of IP-XACT in 2009 and 2010, and those who were able to soldier on with this effort (and their sponsor firms) deserve congratulations for keeping the cause alive!
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.