0% found this document useful (0 votes)
15 views14 pages

Mapping Ontologies For PGHD

The document describes mappings between attributes from three activity tracking datasets (Withings, Huawei, and Fitbit) to ontology properties in PROV-O and FOAF. It includes a table mapping each attribute to similar classes or properties in the ontologies. Not all attributes have direct mappings, and some are only applicable to one dataset.

Uploaded by

abdulnazifmail
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views14 pages

Mapping Ontologies For PGHD

The document describes mappings between attributes from three activity tracking datasets (Withings, Huawei, and Fitbit) to ontology properties in PROV-O and FOAF. It includes a table mapping each attribute to similar classes or properties in the ontologies. Not all attributes have direct mappings, and some are only applicable to one dataset.

Uploaded by

abdulnazifmail
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Data type

ActivityLog:

activityId: string

activityParentId: string

activityParentName: string

Activities:

calories: number

description: string

detailsLink: string

distance: number

duration: number

hasActiveZoneMinutes: boolean

hasStartTime: boolean

isFavorite: boolean

lastModified: datetime

logId: string

name: string

startDate: date

startTime: time

steps: number

ActivityLog:
activityId: prov:Activity

activityParentId: prov:Activity

activityParentName: prov:Activity

Activities:

calories: prov:hadMember

description: prov:value

detailsLink: prov:hadMember

distance: prov:hadMember

duration: prov:hadMember

hasActiveZoneMinutes: prov:hadMember

hasStartTime: prov:hadMember

isFavorite: prov:hadMember

lastModified: prov:generatedAtTime

logId: prov:hadMember

name: prov:hadMember

startDate: prov:startedAtTime

startTime: prov:startedAtTime

steps: prov:hadMemberIn this representation:prov:Activity is used for activityId, activityParentId, and


activityParentName as they are all related to activities.prov:hadMember is used to relate the attributes
to the activity.prov:value is used for description.prov:generatedAtTime is used for
lastModified.prov:startedAtTime is used for startDate and startTime.

activityLog: | FOAF equivalent:

activityId | foaf:account

activityParentId | foaf:account

activityParentName | foaf:name
activities: | FOAF equivalent:

calories | foaf:weight

description | foaf:depiction

detailsLink | foaf:page

distance | foaf:based_near

duration | foaf:duration

hasActiveZoneMinutes | foaf:minutes

hasStartTime | foaf:starts

isFavorite | foaf:like

lastModified | foaf:modified

logId | foaf:account

name | foaf:name

startDate | foaf:birth

startTime | foaf:birth

steps | foaf:step```

In this representation:

- `foaf:account` is used for `activityId`, `activityParentId`, and `logId`.

- `foaf:name` is used for `activityParentName`, `name`.

- `foaf:weight` is used for `calories`.

- `foaf:depiction` is used for `description`.

- `foaf:page` is used for `detailsLink`.

- `foaf:based_near` is used for `distance`.

- `foaf:duration` is used for `duration`.


- `foaf:minutes` is used for `hasActiveZoneMinutes`.

- `foaf:starts` is used for `hasStartTime`.

- `foaf:like` is used for `isFavorite`.

- `foaf:modified` is used for `lastModified`.

- `foaf:birth` is used for `startDate` and `startTime`.

- `foaf:step` is used for `steps`.

ActivityLog:

activityId: foaf:account

activityParentId: foaf:account

activityParentName: foaf:name

Activities:

calories: foaf:weight

description: foaf:depiction

detailsLink: foaf:page

distance: foaf:based_near

duration: foaf:duration

hasActiveZoneMinutes: foaf:minutes

hasStartTime: foaf:starts

isFavorite: foaf:like

lastModified: foaf:modified

logId: foaf:account

name: foaf:name

startDate: foaf:birth
startTime: foaf:birth

steps: foaf:step

foaf:account is used for activityId, activityParentId, and

logId.foaf:name is used for activityParentName,

name.foaf:weight is used for calories.

foaf:depiction is used for description.

foaf:page is used for detailsLink.

foaf:based_near is used for distance.

foaf:duration is used for duration.

foaf:minutes is used for hasActiveZoneMinutes.

foaf:starts is used for hasStartTime.

foaf:like is used for isFavorite.

foaf:modified is used for lastModified.

foaf:birth is used for startDate and startTime.

foaf:step is used for steps.

Withings

In PROV-O, you can represent the attributes you mentioned using the following classes and properties:

1. **Distance**:

- Property: prov:atLocation (if referring to a specific location)

- Property: prov:value (for the numerical value of distance)

2. **Elevation**:

- Property: prov:atLocation (if referring to a specific location)


- Property: prov:value (for the numerical value of elevation)

3. **Intensity Levels (Soft, Moderate, Intense, Active)**:

- Property: prov:qualifier (to qualify the activity)

4. **Calories**:

- Property: prov:value (for the numerical value of calories)

5. **Total Calories**:

- Property: prov:value (for the numerical value of total calories)

6. **Heart Rate**:

- Property: prov:value (for the numerical value of heart rate)

- You can also create classes for heart rate zones (hr_zone_0, hr_zone_1, hr_zone_2, hr_zone_3) and
use them accordingly.

FOAF for withings

For representing the attributes using FOAF (Friend of a Friend) ontology, you can use the following
classes and properties:

1. **Distance**:

- Property: foaf:based_near

2. **Elevation**:

- Property: foaf:based_near
3. **Intensity Levels (Soft, Moderate, Intense, Active)**:

- Property: foaf:topic_interest

4. **Calories**:

- Property: foaf:topic_interest

5. **Total Calories**:

- Property: foaf:topic_interest

6. **Heart Rate**:

- Property: foaf:topic_interest

- You can also create classes for heart rate zones (hr_zone_0, hr_zone_1, hr_zone_2, hr_zone_3) and
use them accordingly.

ex:Person foaf:based_near "Location" .

ex:Person foaf:topic_interest "Moderate" .

ex:Person foaf:topic_interest "200 calories" .

ex:Person foaf:topic_interest "120 bpm" .

ex:Person foaf:topic_interest "60 bpm" .

ex:Person foaf:topic_interest "90 bpm" .

ex:Person foaf:topic_interest "120 bpm" .

```
Huawei

Sure, here are the mappings of the attributes to similar classes or properties in PROV-O and FOAF:

1. **totalStep**

- PROV-O: `prov:Activity`

- FOAF: No direct equivalent.

2. **totalCalorie**

- PROV-O: `prov:value`

- FOAF: No direct equivalent.

3. **totalDistance**

- PROV-O: `prov:value`

- FOAF: No direct equivalent.

4. **totalStrengthTime**

- PROV-O: `prov:Activity`

- FOAF: No direct equivalent.

5. **totalHeight**

- PROV-O: `prov:value`

- FOAF: `foaf:height`
I've included all the attributes from the three datasets that could be mapped to each other. However, it
seems that there are some attributes in Withings and Fitbit that do not have direct equivalents in
Huawei, and vice versa.

Here's the updated table including all the attributes:

| **Withings** | **Huawei** | **Fitbit** |

|-------------------|----------------------|------------------------------|

| distance | totalDistance | activities : distance |

| elevation | totalHeight | summary : elevation |

| soft |- | summary : lightlyActiveMinutes |

| moderate |- | summary : fairlyActiveMinutes |

| intense |- | summary : veryActiveMinutes |

| active |- | summary : activeScore |

| calories | totalCalorie | activities : calories |

| totalcalories |- | summary : caloriesOut |

| hr_average |- |- |

| hr_min |- |- |

| hr_max |- |- |

| hr_zone_0 |- |- |

| hr_zone_1 |- |- |

| hr_zone_2 |- |- |

| hr_zone_3 |- |- |

|- | totalStep | activities : steps |

|- | totalCalorie | activities : calories |

|- | totalDistance | activities : distance |


|- | totalStrengthTime | - |

|- | totalHeight |- |

|- |- | goals : activeMinutes |

|- |- | goals : caloriesOut |

|- |- | goals : distance |

|- |- | goals : floors |

|- |- | goals : steps |

|- |- | summary : activeScore |

|- |- | summary : activityCalories |

|- |- | summary : caloriesEstimationMu |

|- |- | summary : caloriesBMR |

|- |- | summary : caloriesOut |

|- |- | summary : caloriesOutUnestimated |

|- |- | summary : distances : activity |

|- |- | summary : distances : distance |

|- |- | summary : elevation |

|- |- | summary : fairlyActiveMinutes |

|- |- | summary : floors |

|- |- | summary : heartRateZones : caloriesOut |

|- |- | summary : heartRateZones : max |

|- |- | summary : heartRateZones : min |

|- |- | summary : heartRateZones : minutes |

|- |- | summary : heartRateZones : name |

|- |- | summary : lightlyActiveMinutes |

|- |- | summary : marginalCalories |
|- |- | summary : restingHeartRate |

|- |- | summary : sedentaryMinutes |

|- |- | summary : steps |

|- |- | summary : useEstimation |

|- |- | summary : veryActiveMinutes |

This table now includes all the attributes from the three datasets, even if they don't have direct
equivalents in the other datasets. Let me know if you need further assistance!

Sure, I'll include additional ontology sources and concepts for each attribute. Here's the updated table:

| **Withings** | **Huawei** | **Fitbit** | **Ontology Concept (FHIR)** |


**Ontology Source** | **Ontology Concept (SAREF)** | **Ontology Source** |

|-------------------|----------------------|------------------------------|--------------------------------------------|----------------
-------|-------------------------------|----------------------|

| distance | totalDistance | activities : distance | Distance | FHIR


| Distance | SAREF |

| elevation | totalHeight | summary : elevation | Elevation | FHIR


| Elevation | SAREF |

| soft |- | summary : lightlyActiveMinutes | PhysicalActivityIntensity (Light) | FHIR


| LightIntensity | SAREF |

| moderate |- | summary : fairlyActiveMinutes | PhysicalActivityIntensity (Moderate)


| FHIR | ModerateIntensity | SAREF |

| intense |- | summary : veryActiveMinutes | PhysicalActivityIntensity (Vigorous) |


FHIR | HighIntensity | SAREF |

| active |- | summary : activeScore | PhysicalActivity | FHIR


| PhysicalActivity | SAREF |

| calories | totalCalorie | activities : calories | EnergyExpenditure | FHIR


| EnergyConsumption | SAREF |
| totalcalories | - | summary : caloriesOut | EnergyExpenditure | FHIR
| EnergyConsumption | SAREF |

| hr_average |- |- | HeartRateAverage | FHIR |


HeartRate | SAREF |

| hr_min |- |- | HeartRateMinimum | FHIR |


HeartRate | SAREF |

| hr_max |- |- | HeartRateMaximum | FHIR |


HeartRate | SAREF |

| hr_zone_0 |- |- | HeartRateZone (Zone 0) | FHIR |


HeartRateZone | SAREF |

| hr_zone_1 |- |- | HeartRateZone (Zone 1) | FHIR |


HeartRateZone | SAREF |

| hr_zone_2 |- |- | HeartRateZone (Zone 2) | FHIR |


HeartRateZone | SAREF |

| hr_zone_3 |- |- | HeartRateZone (Zone 3) | FHIR |


HeartRateZone | SAREF |

|- | totalStep | activities : steps | StepCount | FHIR |


StepCount | SAREF |

|- | totalCalorie | activities : calories | EnergyExpenditure | FHIR


| EnergyConsumption | SAREF |

|- | totalDistance | activities : distance | Distance | FHIR |


Distance | SAREF |

|- | totalStrengthTime | - | StrengthTrainingDuration | FHIR


| StrengthTraining | SAREF |

|- | totalHeight |- | Height | FHIR | Height


| SAREF |

|- |- | goals : activeMinutes | PhysicalActivityDuration | FHIR


| PhysicalActivityDuration | SAREF |

|- |- | goals : caloriesOut | EnergyExpenditure | FHIR |


EnergyConsumption | SAREF |

|- |- | goals : distance | Distance | FHIR |


Distance | SAREF |
|- |- | goals : floors | FloorCount | FHIR |
FloorCount | SAREF |

|- |- | goals : steps | StepCount | FHIR |


StepCount | SAREF |

|- |- | summary : activeScore | PhysicalActivity | FHIR |


PhysicalActivity | SAREF |

|- |- | summary : activityCalories | EnergyExpenditure | FHIR


| EnergyConsumption | SAREF |

|- |- | summary : caloriesEstimationMu | EnergyExpenditure | FHIR


| EnergyConsumption | SAREF |

|- |- | summary : caloriesBMR | BasalEnergyExpenditure | FHIR


| BasalEnergyExpenditure | SAREF |

|- |- | summary : caloriesOut | EnergyExpenditure | FHIR


| EnergyConsumption | SAREF |

|- |- | summary : caloriesOutUnestimated | EnergyExpenditure | FHIR


| EnergyConsumption | SAREF |

|- |- | summary : distances : activity | PhysicalActivity | FHIR


| PhysicalActivity | SAREF |

|- |- | summary : distances : distance | Distance | FHIR


| Distance | SAREF |

|- |- | summary : elevation | Elevation | FHIR |


Elevation | SAREF |

|- |- | summary : fairlyActiveMinutes | PhysicalActivityIntensity (Moderate) | FHIR


| ModerateIntensity | SAREF |

|- |- | summary : floors | FloorCount | FHIR |


FloorCount | SAREF |

|- |- | summary : heartRateZones : caloriesOut | EnergyExpenditure |


FHIR | EnergyConsumption | SAREF |

|- |- | summary : heartRateZones : max | HeartRateMaximum | FHIR


| HeartRate | SAREF |

|- |- | summary : heartRateZones : min | HeartRateMinimum | FHIR


| HeartRate | SAREF |
|- |- | summary : heartRateZones : minutes | HeartRateZoneDuration |
FHIR | HeartRateZoneDuration | SAREF |

|- |- | summary : heartRateZones : name | HeartRateZone | FHIR


| HeartRateZone | SAREF |

|- |- | summary : lightlyActiveMinutes | PhysicalActivityIntensity (Light) | FHIR


| LightIntensity | SAREF |

|- |- | summary : marginalCalories | EnergyExpenditure | FHIR


| EnergyConsumption | SAREF |

|- |- | summary : restingHeartRate | RestingHeartRate | FHIR


| RestingHeartRate | SAREF |

|- |- | summary : sedent

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy