1. Tracker Feeds representation
In the set of Tracker-Nepomuk ontologies, MFO (maemo feeds ontology) can be used to represent feeds.
1.1. Mapping
As a reminder, when you are looking for the right property in the ontology:
- Check if the specific class has a property for it
- If not, check the superclass, and its superclasses and so on
- If there is no property in the ontology for that information, ask to the tracker developers. Or it is missing in the ontology, or that information shouldn't be in tracker at all.
It seems that some field translations into ontology properties can be confusing, so here is a table defining a mapping. Note that FeedMessage and FeedChannel should also be a nfo:RemoteDataObject instance.
1.1.1. For feeds
Property |
Ontology property |
Comments |
title |
nie:title |
|
updatedTime |
mfo:updatedTime |
is used to store a local timestamp of feed channel |
contentLastModified |
nie:contentLastModified |
remote time is stored using this |
Feed Url |
nie:url |
|
1.1.2. For feeds settings
Property |
Ontology property |
updateInterval |
mfo:updateInterval |
downloadPath |
mfo:downloadPath |
subscription Time |
nie:contentCreated (in the feed!) |
1.1.3. For messages
Property |
Ontology property |
Comments |
title |
nie:title |
|
content |
nie:plainTextContent |
|
isRead |
nmo:isRead |
Inherited from nmo:Message |
published time |
nie:contentCreated |
|
downloaded time |
mfo:downloadedTime |
nmo:receivedDate inherited from nmo:Message can (should) be used too (or instead?) |
message url |
nie:url |
The original post url |
Parent Feed |
|