Here you can find a complete explanation of how to go from MIME to RDF:

http://live.gnome.org/Tracker/Documentation/Examples/SPARQL/Email


On Wed, 2010-08-18 at 18:16 +0200, Mildred Ki'Lya wrote:
> Hi,
> 
> I am in the process of writing an extractor for mbox files. My purpose
> is to use Tracker as an internal search engine for another application,
> and this application stores conversations in mbox files with specific
> headers I need to parse.
> 
> Additionally, it could be used to successfully search within e-mails
> when you don't use evolution.
> 
> 
> And, I have the following problems, I thought you guys could help me.
> 
> 
> First (but this isn't important at all), libmagic report mbox files as
> text/plain instead of application/mbox. So I have to make my extractor
> for the two mime types and filter afterwards.
> 
> 
> Then, I started looking at ontologies, and I had a hard time figuring
> everything out. I want to register both the mailbox and the messages
> within it.
> 
> I started out reading the NMO (Nepomuk Message Ontology) to find that
> there ware no relations between a nmo:Mailbox and a nmo:Email. I had to
> look at the NIE (Nepomuk Information Element) to construct the relations
> between my ontologies.
> 
> So, if I understood everything well, I should have something like:
> 
> 
> nmo:Mailbox -> nie:hasPart -> nmo:MailboxDataObject -> nie:interpretedAs
> -> nmo:Email
> 
> and of course
> 
> nmo:Email -> nie:isStoredAs -> nmo:MailboxDataObject -> nie:isPartOf ->
> nmo:Mailbox
> 
> It seems rather complex to me and I wanted to know if there was a
> simpler way to doing things.
> 
> Thanks,
> 
> 
> Mildred
> 
> 
> _______________________________________________
> tracker-list mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/tracker-list

-- 


Philip Van Hoof
freelance software developer
Codeminded BVBA - http://codeminded.be

_______________________________________________
tracker-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/tracker-list

Reply via email to