Mapping Ontologies For PGHD
Mapping Ontologies For PGHD
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
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:
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
Withings
In PROV-O, you can represent the attributes you mentioned using the following classes and properties:
1. **Distance**:
2. **Elevation**:
4. **Calories**:
5. **Total Calories**:
6. **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.
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.
```
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`
2. **totalCalorie**
- PROV-O: `prov:value`
3. **totalDistance**
- PROV-O: `prov:value`
4. **totalStrengthTime**
- PROV-O: `prov:Activity`
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.
|-------------------|----------------------|------------------------------|
| hr_average |- |- |
| hr_min |- |- |
| hr_max |- |- |
| hr_zone_0 |- |- |
| hr_zone_1 |- |- |
| hr_zone_2 |- |- |
| hr_zone_3 |- |- |
|- | totalHeight |- |
|- |- | goals : activeMinutes |
|- |- | goals : caloriesOut |
|- |- | goals : distance |
|- |- | goals : floors |
|- |- | goals : steps |
|- |- | summary : activeScore |
|- |- | summary : activityCalories |
|- |- | summary : caloriesEstimationMu |
|- |- | summary : caloriesBMR |
|- |- | summary : caloriesOut |
|- |- | summary : caloriesOutUnestimated |
|- |- | summary : elevation |
|- |- | summary : fairlyActiveMinutes |
|- |- | summary : floors |
|- |- | 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:
|-------------------|----------------------|------------------------------|--------------------------------------------|----------------
-------|-------------------------------|----------------------|
|- |- | summary : sedent