Skip to content

Commit 80f8c4a

Browse files
committed
Updated image name and reference to it
1 parent 0e8ff84 commit 80f8c4a

2 files changed

Lines changed: 1 addition & 1 deletion

File tree

learn-pr/wwl-data-ai/understand-fabric-iq-fundamentals/includes/4-understand-ontology-modeling-paradigm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Traditional database columns often vary: "temp," "temperature," "temp_reading,"
2828

2929
In ontology modeling, you define a standard property name like "Temperature" at the entity type level. When you bind to data, you map this property to whatever column name exists in your table - whether it's "temp," "temperature," or "body_temp." Tools querying the ontology always see the standardized "Temperature" property, regardless of the underlying column name.
3030

31-
:::image type="content" source="../media/vitalsign-properties.png" alt-text="Screenshot of VitalSign entity type showing properties including HeartRate, OxygenSaturation, RespiratoryRate, and Timestamp in Fabric IQ ontology editor." border="false":::
31+
:::image type="content" source="../media/vital-sign-properties.png" alt-text="Screenshot of VitalSign entity type showing properties including HeartRate, OxygenSaturation, RespiratoryRate, and Timestamp in Fabric IQ ontology editor." border="false":::
3232

3333
This VitalSign entity type shows standardized property names like HeartRate, OxygenSaturation, and RespiratoryRate. When bound to data, these properties map to the actual column names in the source table.
3434

learn-pr/wwl-data-ai/understand-fabric-iq-fundamentals/media/vitalsign-properties.png renamed to learn-pr/wwl-data-ai/understand-fabric-iq-fundamentals/media/vital-sign-properties.png

File renamed without changes.

0 commit comments

Comments
 (0)