 Warm welcome, please, for Ron Schultz. Thank you, Stephen. Thank you. I appreciate this opportunity to give you a brief synopsis of what the ODEP is all about. First of all, I'd like to highlight the fact that the open group's vision is boundless information flow. And obviously, to achieve that, an underlying capability is interoperability. In addition, the open group has making standards work as a tagline. I'd like to suggest that the ODEP, or open data element framework, is fundamentally a framework that enables making standards work. And so if you take nothing else away from this summary presentation, please take that away. Next slide. Okay. So I'll summarize what the problem is, how ODEP helps categorize concepts. And in summary there, I'm going to try and suggest that it is analogous to the periodic table. I'm going to give a brief example that was presented in Austin of how ODEP could be used to categorize information within the healthcare industry and then some of the benefits. Obviously, many people, especially the healthcare folks, will indicate that there are too many standards. And when you look across those standards, there are conflicting data. They don't establish common terminology across those standards. So there's a need for categorization. In the real world, you've got the elements found in the universe. And of course for that, you've got the periodic table. The periodic table helps you categorize all of the elements that we found in the universe. And it's essential because when you start combining things, you then end up with compounds, molecules and compounds. The data categorization system, I'd like to suggest that in the same way that you've got elements of the universe, you've got data elements within the enterprise. And so having a framework that can categorize data elements is essential to being able to use them and to analyze them. So a data categorization system should be able to use existing vocabularies. And that's where existing data standards, you should be able to use existing data standards. It provides a basic grammar for data descriptions. And it provides a consistent and repeatable method for data analysis and tagging. It should be consistent with your current implementation systems and use RDF. So the open data element framework provides an index and method for analyzing and tagging data elements. It's partially based on the previous standard known as UDF, but there are some substantial differences. For one thing, roles as well as object classes and properties will be available. And then the most significant difference is supporting plug-ins. So rather than a one size fits all, which is what UDF tried to be, ODF will take existing standards as plug-ins. And I'll highlight that here in a moment. Within the ODF, just a few, and there's no limit to how many plug-ins could be added to the ODF. But the United Nations had a standard product and services codes. And the United Nations also has types of units and measures known as REC20. In the healthcare area, you've got SNOMED and HL7 and ICD-10, ICD-11. And within the open group, they help create a federal health information model. There's many other standards out there, but there's EIA-36, which is config management of systems. And I'm going to suggest that all of these could be plug-ins to the ODF. At the Austin conference in July, I went through a detailed example of how the federal health information model has data element concepts in it and how those could be transformed into concepts that are easy for people to interpret. And going through the taxonomy, if you will, of the model itself, you've got, for example, health concern. It's a problem type and a diagnosis, and it has a date that it was diagnosed. And that's from the federal health information model. And that total concept, which, when you go through that model, can be represented by a unique identifier, which is similar to an IP address. A number dot number dot number is a way of representing that same concept with a unique ID that computers can respond to, whereas the human then would be able to read the words that make it understandable of what's there in the concept name. And so within the health care industry, there are some object classes and, for instance, various roles of persons. There's an object class called condition where you'd find things like diagnosis and symptoms and so forth. Processes for a medical procedure, product for the medical devices and drugs that might be prescribed. Events that might be relevant to the medical, such as a flood, earthquake, in other words, what happened that caused the problem. Enterprises, such as the insurance carrier and hospital and so forth. And substances that might be relevant to health care, dust, carbon monoxide. So those are the fundamental object classes that could all have plug-ins associated with them to deal with the health care industry. So some of the benefits of applying ODF to these concepts is that you can accommodate plug-ins from multiple, there really is no limit, existing data standards. So it's not competing with existing standards. It's a way of making existing standards work together. You want to know that you're in the health care that you're looking at ICD-10 code as opposed to an HL-7 code. And so that's given to you by the way the syntax is for the name as well as the ID of the ODF. So you've got an ODF name that's easily understood. It's just simply an English string or it can be any other language by the way. That ODF identifier can then be represented not only in English but in any other natural language. But that identifier would stay the same across all languages. And so the ODF identifier provides also an opportunity then to reduce the latency and bandwidth required of moving that information through the network. And then the ODF object classes provide a consistent starting point for categorizing information whether it's health care or any other domain. And that concludes my brief summary of the ODF. And I do want to point out that it was officially published in May of this year. So many people have asked what's ODF. I hadn't heard of it. Hopefully this satisfies that question.