Clarify ontology language

Author: baanders

articles/digital-twins/TOC.yml

@@ -27,7 +27,7 @@
   items:
   - name: DTDL models
     href: concepts-models.md
-  - name: Ontologies
+  - name: Industry ontologies
     items:
     - name: What is an ontology?
       href: concepts-ontologies.md

articles/digital-twins/concepts-ontologies-adopt.md

@@ -5,7 +5,7 @@ titleSuffix: Azure Digital Twins
 description: Learn about existing industry ontologies that can be adopted for Azure Digital Twins
 author: baanders
 ms.author: baanders # Microsoft employees only
-ms.date: 03/01/2022
+ms.date: 03/29/2023
 ms.topic: conceptual
 ms.service: digital-twins
 
@@ -17,7 +17,7 @@ ms.service: digital-twins
 
 # Adopting a DTDL industry ontology
 
-Microsoft has partnered with domain experts to create DTDL model sets based on industry standards, to help minimize reinvention and simplify solutions. This article presents the industry ontologies that are currently available. 
+Microsoft has partnered with domain experts to create DTDL model sets based on industry standards, to help minimize reinvention and simplify solutions. This article presents the DTDL industry ontologies that are currently available. 
 
 ## List of ontologies
 
@@ -34,4 +34,4 @@ Each ontology is focused on an initial set of models. You can contribute to the
 
 * Learn more about extending industry-standard ontologies to meet your specifications: [Extending industry ontologies](concepts-ontologies-extend.md).
 
-* Or, continue on the path for developing models based on ontologies: [Using ontology strategies in a model development path](concepts-ontologies.md#using-ontology-strategies-in-a-model-development-path).
+* Or, continue on the path for developing models based on ontologies: [Using ontology strategies in a model development path](concepts-ontologies.md#full-model-development-path).

articles/digital-twins/concepts-ontologies-convert.md

@@ -5,7 +5,7 @@ titleSuffix: Azure Digital Twins
 description: Understand the process of converting industry-standard models into DTDL for Azure Digital Twins
 author: baanders
 ms.author: baanders # Microsoft employees only
-ms.date: 02/28/2022
+ms.date: 03/05/2023
 ms.topic: conceptual
 ms.service: digital-twins
 
@@ -44,6 +44,8 @@ The following C# code snippet shows how an RDF model file is loaded into a graph
 
 ## Converter samples
 
+This section contains sample converter code for RDF and OWL converters, which can be extended for other schemas in the building industry. 
+
 ### RDF converter application 
 
 There's a sample application available that converts an RDF-based model file to [DTDL (version 2)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/DTDL.v2.md) for use by the Azure Digital Twins service. It has been validated for the [Brick](https://brickschema.org/ontology/) schema, and can be extended for other schemas in the building industry (such as [Building Topology Ontology (BOT)](https://w3c-lbd-cg.github.io/bot/), [Semantic Sensor Network](https://www.w3.org/TR/vocab-ssn/), or [buildingSmart Industry Foundation Classes (IFC)](https://technical.buildingsmart.org/standards/ifc/ifc-schema-specifications/)).
@@ -66,4 +68,4 @@ This converter was used to translate the [Real Estate Core Ontology](https://doc
 
 * Learn more about extending industry-standard ontologies to meet your specifications: [Extending industry ontologies](concepts-ontologies-extend.md).
 
-* Or, continue on the path for developing models based on ontologies: [Using ontology strategies in a model development path](concepts-ontologies.md#using-ontology-strategies-in-a-model-development-path).
+* Or, continue on the path for developing models based on ontologies: [Using ontology strategies in a model development path](concepts-ontologies.md#full-model-development-path).

articles/digital-twins/concepts-ontologies-extend.md

@@ -5,7 +5,7 @@ titleSuffix: Azure Digital Twins
 description: Learn about the reasons and strategies behind extending an ontology
 author: baanders
 ms.author: baanders # Microsoft employees only
-ms.date: 3/29/2022
+ms.date: 3/29/2023
 ms.topic: conceptual
 ms.service: digital-twins
 
@@ -17,11 +17,11 @@ ms.service: digital-twins
 
 # Extending ontologies 
 
-This article uses the [DTDL-based RealEstateCore ontology for smart buildings](https://github.com/Azure/opendigitaltwins-building) as the basis for examples of extending ontologies with new DTDL properties. The techniques described here are general, however, and can be applied to any part of a DTDL-based ontology with any DTDL capability (Telemetry, Property, Relationship, Component, or Command). 
+This article uses the [DTDL-based RealEstateCore ontology for smart buildings](https://github.com/Azure/opendigitaltwins-building) as the basis for examples of extending ontologies with new DTDL properties. The techniques described here are general, however, and can be applied to any part of a DTDL-based ontology with any DTDL capability (Telemetry, Property, Relationship, Component). 
 
-An industry-standard [ontology](concepts-ontologies.md), such as the DTDL-based [RealEstateCore](https://www.realestatecore.io/) ontology, is a great way to start building your IoT solution. Industry ontologies provide a rich set of base interfaces that are designed for your domain and engineered to work out of the box in Azure IoT services, such as Azure Digital Twins. 
+Microsoft's [industry-standard ontologies](concepts-ontologies-adopt.md), such as the DTDL-based [RealEstateCore](https://www.realestatecore.io/) ontology, are a great way to start building your IoT solution. Industry ontologies provide a rich set of base interfaces that are designed for your domain and engineered to work out of the box in Azure IoT services like Azure Digital Twins. 
 
-However, it's possible that your solution may have specific needs that aren't covered by the industry ontology. For example, you may want to link your digital twins to 3D models stored in a separate system. In this case, you can extend one of these ontologies to add your own capabilities while keeping all the benefits of the original ontology.
+However, it's possible that your solution may have specific needs that aren't covered by the industry ontology. For example, you may want to link your digital twins to 3D models stored in a separate system. In this case, you can extend one of these ontologies to add your own capabilities while keeping all the [benefits of the original ontology](concepts-ontologies.md).
 
 ## RealEstateCore space hierarchy 
 
@@ -40,11 +40,11 @@ Sometimes your solution has specific needs that aren't covered by the industry o
 In this article, we discuss two different cases where extending the ontology's hierarchy is useful: 
 
 * Adding new interfaces for concepts not in the industry ontology. 
-* Adding extra properties (or relationships, components, telemetry, or commands) to existing interfaces.
+* Adding extra Properties (or Relationships, Components, and Telemetry) to existing interfaces.
 
 ### Add new interfaces for new concepts 
 
-In this case, you want to add interfaces for concepts needed for your solution but that aren't present in the industry ontology. For example, if your solution has other types of rooms that aren't represented in the DTDL-based RealEstateCore ontology, then you can add them by extending directly from the RealEstateCore interfaces. 
+In this case, you want to add interfaces for concepts needed for your solution that aren't present in the industry ontology. For example, if your solution has other types of rooms that aren't represented in the DTDL-based RealEstateCore ontology, then you can add them by extending directly from the RealEstateCore interfaces. 
 
 The example below presents a solution that needs to represent "focus rooms," which aren't present in the RealEstateCore ontology. A focus room is a small space designed for people to focus on a task for a couple hours at a time. 
 
@@ -56,7 +56,7 @@ After adding the focus room interface, the extended hierarchy shows the new room
 
 ### Add extra capabilities to existing interfaces 
 
-In this case, you want to add more properties (or relationships, components, telemetry, or commands) to interfaces that are in the industry ontology.
+In this case, you want to add more Properties (or Relationships, Components, and Telemetry) to interfaces that are in the industry ontology.
 
 In this section, you'll see two examples: 
 * If you're building a solution that displays 3D drawings of spaces that you already have in an existing system, you might want to associate each digital twin to its 3D drawing (by ID) so that when the solution displays information about the space, it can also retrieve the 3D drawing from the existing system. 
@@ -175,4 +175,4 @@ The DTDL for the extended interfaces, limited to the portion discussed above, wo
 
 ## Next steps
 
-Continue on the path for developing models based on ontologies: [Using ontology strategies in a model development path](concepts-ontologies.md#using-ontology-strategies-in-a-model-development-path).
+Continue on the path for developing models based on ontologies: [Using ontology strategies in a model development path](concepts-ontologies.md#full-model-development-path).

articles/digital-twins/concepts-ontologies.md

@@ -5,7 +5,7 @@ titleSuffix: Azure Digital Twins
 description: Learn about digital twin ontologies, how they're used in Azure Digital Twins, and how these DTDL ontologies can be used for modeling in the context of certain industries.
 author: baanders
 ms.author: baanders # Microsoft employees only
-ms.date: 02/28/2022
+ms.date: 04/05/2023
 ms.topic: conceptual
 ms.service: digital-twins
 ms.custom: engagement-fy23
@@ -20,17 +20,19 @@ ms.custom: engagement-fy23
 
 This article describes the concept of industry ontologies and how they can be used within the context of Azure Digital Twins.
 
-The vocabulary of an Azure Digital Twins solution is defined using [models](concepts-models.md), which describe the types of entities that exist in your environment. An *ontology* is a set of models for a given domain, like manufacturing, building structures, IoT systems, smart cities, energy grids, web content, and more.
+The vocabulary of an Azure Digital Twins solution is defined using [models](concepts-models.md), which describe the types of entities that exist in your environment. An *ontology* is a set of models that comprehensively describe a given domain, like manufacturing, building structures, IoT systems, smart cities, energy grids, web content, and more.
 
-Sometimes, when your solution is tied to a particular industry, it can be easier and more effective to start with a set of models for that industry that already exist, instead of authoring your own model set from scratch. This article explains more about using pre-existing industry ontologies for your Azure Digital Twins scenarios, including strategies for using the ontologies that are available today.
+When you author a model set from scratch that is complete and describes a domain, you're creating your own ontology. Sometimes, however, when modeling standards for an industry already exist, it can be easier and more effective to lean on that existing ontology instead of creating the ontology from scratch yourself. 
 
-## Using ontologies for Azure Digital Twins
+The articles in this section explain more about using pre-existing industry ontologies for your Azure Digital Twins scenarios, including what ontologies are available today, and the different strategies for turning industry standards into ontologies for use in Azure Digital Twins.
 
-Ontologies provide a great starting point for digital twin solutions. They encompass a set of domain-specific models and relationships between entities for designing, creating, and parsing a digital twin graph. Ontologies enable solution developers to begin a digital twins solution from a proven starting point, and focus on solving business problems. The ontologies provided by Microsoft are also designed to be easily extensible, so that you can customize them for your solution. 
+## Using existing ontologies for Azure Digital Twins
 
-Also, using these ontologies in your solutions can set them up for more seamless integration between different partners and vendors, because ontologies can provide a common vocabulary across solutions.
+Microsoft has created several [open-source DTDL ontologies](concepts-ontologies-adopt.md) built on widely adopted industry standards. You can use these model sets out-of-the-box in your solutions, or [extend the ontologies](concepts-ontologies-extend.md) with your own additions for a customized solution.
 
-Because models in Azure Digital Twins are represented in [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/DTDL.v2.md), ontologies for use with Azure Digital Twins are also written in DTDL. 
+Either way, existing industry ontologies provide a great starting point for digital twin solutions. They encompass a set of domain-specific models and relationships between entities for designing, creating, and parsing a digital twin graph. Industry ontologies enable solution developers to begin a digital twins solution from a proven starting point, and focus on solving business problems. The industry ontologies provided by Microsoft are also designed to be easily extensible, so that you can customize them for your solution. Because models in Azure Digital Twins are represented in [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/DTDL.v2.md), ontologies for use with Azure Digital Twins are also written in DTDL.
+
+Using these ontologies in your solutions can also set them up for more seamless integration between different partners and vendors, because ontologies can provide a common vocabulary across solutions.
 
 Here are some other benefits to using industry-standard DTDL ontologies as schemas for your twin graphs:
 * Harmonization of software components, documentation, query libraries, and more
@@ -40,15 +42,16 @@ Here are some other benefits to using industry-standard DTDL ontologies as schem
 
 ## Strategies for integrating ontologies
 
-There are three possible strategies for integrating industry-standard ontologies with DTDL. You can pick the one that works best for you depending on your needs:
+Here are the main strategies for integrating existing industry-standard ontologies with DTDL for use in Azure Digital Twins. Choose the one that works best for you, depending on how closely the existing materials for your industry already match your solution.
 
 | Strategy | Description | Resources |
 | --- | --- | --- |
-| Adopt | You can start your solution with an open-source DTDL ontology that has been built on widely adopted industry standards. You can either use these model-sets out-of-the-box, or extend them with your own additions for a customized solution. | [Adopting&nbsp;industry&nbsp;standard ontologies](concepts-ontologies-adopt.md)<br><br>[Extending&nbsp;ontologies](concepts-ontologies-extend.md) |
-| Convert | If you already have existing models represented in another standard format, you can convert them to DTDL to use them with Azure Digital Twins. | [Converting&nbsp;ontologies](concepts-ontologies-convert.md)<br><br>[Extending&nbsp;ontologies](concepts-ontologies-extend.md) |
-| Author | You can always develop your own custom DTDL models from scratch, using any applicable industry standards as inspiration. | [DTDL models](concepts-models.md) |
+| Adopt | You can jump-start your solution by adopting one of Microsoft's open-source DTDL ontologies that has been built on widely accepted industry standards. If the ontologies contain all the models you need, you can take these model sets as they are and use them out-of-the-box. | [Adopting&nbsp;industry&nbsp;standard ontologies](concepts-ontologies-adopt.md) |
+| Extend | If an existing DTDL ontology has most, but not all, of the models you need in your solution, you can extend the ontology with your own additions to create a customized ontology. | [Adopting&nbsp;industry&nbsp;standard ontologies](concepts-ontologies-adopt.md)<br><br>[Extending&nbsp;ontologies](concepts-ontologies-extend.md) |
+| Convert | If you already have existing models represented in another standard industry format, you can convert them to DTDL to use them with Azure Digital Twins. | [Converting&nbsp;ontologies](concepts-ontologies-convert.md) |
+| Author | You can always develop your own custom DTDL ontologies from scratch, using any applicable industry standards as inspiration. | [DTDL models](concepts-models.md) |
 
-### Using ontology strategies in a model development path
+### Full model development path
 
 No matter which strategy you choose for integrating an ontology into Azure Digital Twins, you can follow the complete path below to guide you through creating and uploading your ontology as DTDL models.