Zeitgeist Framework

Symbollic Access of the Datamodel

Registered by Mikkel Kamstrup Erlandsen

We should use the content- and source types defined in zeitgeist/datamodel.py throughout Zeitgeist, never use string constants defined inside each logger class.

Blueprint information

Status:
Complete
Approver:
Seif Lotfy
Priority:
Essential
Drafter:
Mikkel Kamstrup Erlandsen
Direction:
Approved
Assignee:
None
Definition:
Obsolete
Series goal:
Accepted for 0.3
Implementation:
Implemented
Milestone target:
milestone icon 0.3.0
Started by
Mikkel Kamstrup Erlandsen
Completed by
Markus Korn

Related branches

Sprints

Whiteboard

If the source or content are not of the defined types then we should give out an error and reject insertion of the data.

-----------------------------------------------------------------------------
How will 3rd party loggers (which don't have types defined in datamodel.py) handle this? --Natan

 * We will publish a full ontology, linking to Nepomuk and defining any missing pieces. With time we will also provide a client library in C/GObject, that expose all useful definitions -- Mikkel

-----------------------------------------

Markus: closed the bug, a symbolic datamodel is already implemented, if it is not used everywhere it is a bug, and we should handle it as such and file a bugreport.

(?)

Work Items

Nearby

This blueprint contains Public information 
Everyone can see this information.