Re: [Tracker] Zeitgeist ontology and Tracker

On Tue, 2011-03-22 at 21:15 +0100, Mikkel Kamstrup Erlandsen wrote:
Hi all,

There's been some back and forth about Zeitgeist/Tracker integration.
The key point in getting anything started in this direction is
figuring out the ontology business.

There has already been some work towards a solution[1]. We've already
fixed a few issues reported by Rob a while back, but the changes in
[1] were never discussed (see original ZG ontology in [2]). The
problem is that Rob's work contains some changes that are incompatible
with the original ontology, so it's not something we can adopt without
justifying it (will break our API and bring some troublesome data
migration work).

So, let's get that discussion we never had :-) If we *theoretically*
proposed the ZG ontology (as in [2], not [1]) for inclusion in
Tracker, what issues would you see?

While comparing the two, here are some examples:

o. zg: {} : In Tracker we don't allow brand specific namespaces. NEO is
   the namespace that we chose for this (New Event Ontology).

o. Those "Please do no instantiate directly, but use one of the sub
   classes." - like rules are not ok for us

o. zg:eventId : We don't allow such IDs in the ontology. And ID means
   that it's referring to something. A "something" is a rdfs:Resource.

   ps. If you want to use integral IDs in your framework, you can use
       tracker:id() on the resource

o. zg:timestamp rdfs:range xsd:long: xsd:integer is int64 in Tracker, I
   think we don't even support xsd:long as type atm

o. zg:hasSubject: must be nie:InformationElement as range

o. zg:hasActor: I think it should also be a nie:InformationElement as
   range, but in NEO we apparently didn't fix that. No idea why.

o. The rules for zg:hasActor are in conflict with our own .desktop miner

o. zg:hasEventManifestation: rdfs:type? What is that? rdf:type? In our
   fixed version we just removed this.

o. Probably a few more that I forgot


Philip Van Hoof
freelance software developer
Codeminded BVBA -

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]