You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/digital-twins/concepts-ontologies-convert.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,9 @@ The sample is a .NET Core command-line application called **RdfToDtdlConverter**
50
50
51
51
You can get the sample here: [**RdfToDtdlConverter**](/samples/azure-samples/rdftodtdlconverter/digital-twins-model-conversion-samples/).
52
52
53
-
To download the code to your machine, hit the *Download ZIP* button underneath the title on the sample landing page. This will download a *ZIP* file under the name *RdfToDtdlConverter_sample_application_to_convert_RDF_to_DTDL.zip*, which you can then unzip and explore.
53
+
To download the code to your machine, select the **Browse code** button underneath the title on the sample page, which will take you to the GitHub repo for the sample. Select the **Code** button and **Download ZIP** to download the sample as a *.ZIP* file called *RdfToDtdlConverter-main.zip*. You can then unzip the file and explore the code.
54
+
55
+
:::image type="content" source="media/concepts-ontologies-convert/download-repo-zip.png" alt-text="Screenshot of the RdfToDtdlConverter repo on GitHub. The Code button is selected, producing a small dialog box where the Download ZIP button is highlighted." lightbox="media/concepts-ontologies-convert/download-repo-zip.png":::
54
56
55
57
You can use this sample to see the conversion patterns in context, and to have as a building block for your own applications performing model conversions according to your own specific needs.
Copy file name to clipboardExpand all lines: articles/digital-twins/concepts-ontologies-extend.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ In the DTDL-based RealEstateCore ontology, the Space hierarchy is used to define
29
29
30
30
A portion of the hierarchy looks like the diagram below.
31
31
32
-
:::image type="content" source="media/concepts-extending-ontologies/RealEstateCore-original.png" alt-text="Flow diagram illustrating part of the RealEstateCore space hierarchy. At the top level, there's an element called Space; it is connected by an 'extends' arrow down a level to Room; Room is connected by two 'extends' arrows down a level to ConferenceRoom and Office.":::
32
+
:::image type="content" source="media/concepts-ontologies-extend/RealEstateCore-original.png" alt-text="Flow diagram illustrating part of the RealEstateCore space hierarchy. At the top level, there's an element called Space; it is connected by an 'extends' arrow down a level to Room; Room is connected by two 'extends' arrows down a level to ConferenceRoom and Office.":::
33
33
34
34
For more information about the RealEstateCore ontology, see [*Concepts: Adopting industry-standard ontologies*](concepts-ontologies-adopt.md#realestatecore-smart-building-ontology).
35
35
@@ -52,7 +52,7 @@ To extend the industry ontology with this new concept, create a new interface th
52
52
53
53
After adding the focus room interface, the extended hierarchy shows the new room type.
54
54
55
-
:::image type="content" source="media/concepts-extending-ontologies/RealEstateCore-extended-1.png" alt-text="Flow diagram illustrating the RealEstateCore space hierarchy from above, with a new addition. At the bottom level with ConferenceRoom and Office, there is a new element called FocusRoom (also connected via an 'extends' arrow from Room)":::
55
+
:::image type="content" source="media/concepts-ontologies-extend/RealEstateCore-extended-1.png" alt-text="Flow diagram illustrating the RealEstateCore space hierarchy from above, with a new addition. At the bottom level with ConferenceRoom and Office, there is a new element called FocusRoom (also connected via an 'extends' arrow from Room)":::
56
56
57
57
### Add additional capabilities to existing interfaces
58
58
@@ -70,15 +70,15 @@ To extend the industry ontology, you create your own interfaces that extend from
70
70
71
71
After extending the portion of the hierarchy shown above, the extended hierarchy looks like the diagram below. Here the extended Space interface adds the `drawingId` property that will contain an ID that associates the digital twin with the 3D drawing. Additionally, the ConferenceRoom interface adds an "online" property that will contain the online status of the conference room. Through inheritance, the ConferenceRoom interface contains all capabilities from the RealEstateCore ConferenceRoom interface, as well as all capabilities from the extended Space interface.
72
72
73
-
:::image type="content" source="media/concepts-extending-ontologies/RealEstateCore-extended-2.png" alt-text="Flow diagram illustrating the extended RealEstateCore space hierarchy from above, with more new additions. Room now shares its level with a Space element, which connects with an 'extends' arrow down a level to a new Room element next to ConferenceRoom and Office. The new elements are connected to the existing ontology with more 'extends' relationships.":::
73
+
:::image type="content" source="media/concepts-ontologies-extend/RealEstateCore-extended-2.png" alt-text="Flow diagram illustrating the extended RealEstateCore space hierarchy from above, with more new additions. Room now shares its level with a Space element, which connects with an 'extends' arrow down a level to a new Room element next to ConferenceRoom and Office. The new elements are connected to the existing ontology with more 'extends' relationships.":::
74
74
75
75
## Using the extended space hierarchy
76
76
77
77
When you create digital twins using the extended Space hierarchy, each digital twin's model will be one from the extended Space hierarchy (not the original industry ontology) and will include all the capabilities from the industry ontology and the extended interfaces though interface inheritance.
78
78
79
79
Each digital twin's model will be an interface from the extended hierarchy, shown in the diagram below.
80
80
81
-
:::image type="content" source="media/concepts-extending-ontologies/ontology-with-models.png" alt-text="An excerpt from the extended RealEstateCore space hierarchy, including Space (top level), one Room (middle level), and ConferenceRoom, Office, and FocusRoom (lower level). Names of models are connected to each element (for instance, Room is connected to a model called Room101).":::
81
+
:::image type="content" source="media/concepts-ontologies-extend/ontology-with-models.png" alt-text="An excerpt from the extended RealEstateCore space hierarchy, including Space (top level), one Room (middle level), and ConferenceRoom, Office, and FocusRoom (lower level). Names of models are connected to each element (for instance, Room is connected to a model called Room101).":::
82
82
83
83
When querying for digital twins using the model ID (the `IS_OF_MODEL` operator), the model IDs from the extended hierarchy should be used. For example, `SELECT * FROM DIGITALTWINS WHERE IS_OF_MODEL('dtmi:com:example:Office;1')`.
0 commit comments