Re: [Tracker] trackerbird fixes



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Michael,

Our NMO ontology is indeed not the same as Nepomuk. That's because
Nepomuk's is incomplete.

More information here:

https://wiki.gnome.org/Projects/Tracker/Documentation/Examples/SPARQL/Email

Kind regards,

Philip

Michael Lipp schreef op 6/02/2014 19:33:
Hi Martyn,
If I query the tracker db for items of type nfo:Document,
however, I also get the emails. Could it be that the inheritance
relationships are implemented wrongly in the tracker db?

I wouldn't claim to have become an expert in such a short time, but
I think that the definition in data/ontoligies/34-nmo.ontology

nmo:Message a rdfs:Class ; rdfs:comment "A message. Could be an
email, instant messanging message, SMS message etc." ; 
rdfs:subClassOf nfo:TextDocument ; tracker:notify true .

simply doesn't comply with the nepomuk specification and is the
cause of the problem.

- Michael

_______________________________________________ tracker-list
mailing list tracker-list gnome org 
https://mail.gnome.org/mailman/listinfo/tracker-list


Alan Pater schreef op 12/02/2014 2:35:


- - git branch dwc-ontology
- - git checkout dwc-ontology
- - Write the ontology in our Turtle format. Call it 94-dwc.ontology
        - Ensure that nao:lastModified is correct in the
          tracker:Ontology stuff and that it's at the top of
          the file right underneath the @prefix lines.

- - Write a 94-dwc.description file
- - Put it in data/ontologies
- - Adapt Makefile.am (add to config_DATA)
- - make && make install
- - Restart tracker-store with -v 3, you should see your
  ontology being added and created.
- - Test thoroughly with tracker-sparql. Noticing that making
  changes afterwards is not always possible; depending on what
  kind of changes you make you might have to add ontology change
  coping infrastructure (which is a horror in complexity).
- - git add 94-dwc.description 94-dwc.ontology Makefile.am
- - git commit
- - git format-patch master

Kind regards,

Philip

Enigmail
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS+zhUAAoJEEP2NSGEz4aD5PYIALxZesPMmnIBxoZPo/bBKslk
x6yDjeqYKnKQv5AZ47Oj3w5StbU9IhQKvRQ/dEOffEXUQqgREBB8vLQzKLB1bZiC
XbCPlPSBXnQYjo2vkKERotLWFGJZBL8Pxcq231KI+5vdcLzBoso6rCzkBwsj5KVx
nyxBR4J6NwxelWQQGljlas9dU2a9J5jBAHCCm3Uq4X/Sy/lUgo/rD6djySef1fV4
1dho9aXRldPXnA+KLoGh9b5ti897akHXwzHeqDh0BMOisFoSeuEByH0RXmQnZD3O
dAWzjGegjIkWczDvbPnfONbgDKgK5CZRbIT3ie4WYGfQ4MBNVpV71CdRhvXNEZk=
=zLit
-----END PGP SIGNATURE-----


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