From - Wed Oct  4 18:54:16 2006
X-Account-Key: account3
X-UIDL: 0000ed56033dd35e
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:33996 "EHLO
	lists-outbound.sourceforge.net") by ps11.test.onet.pl with ESMTP
	id <S1007234AbWJDQwG>; Wed, 4 Oct 2006 18:52:06 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP id A388B126A9
	for <antoni_mylka@poczta.onet.pl>; Wed,  4 Oct 2006 09:52:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
From:	aperture-devel-request@lists.sourceforge.net
To:	antoni_mylka@poczta.onet.pl
Subject: confirm c6989dd83a4acb9a0ebecff87c309211496a8e4d
Reply-To: aperture-devel-request@lists.sourceforge.net
Message-ID: <mailman.0.1159980721.9332.aperture-devel@lists.sourceforge.net>
Date:	Wed, 04 Oct 2006 09:52:01 -0700
Precedence: bulk
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
List-Id: <aperture-devel.lists.sourceforge.net>
X-List-Administrivia: yes
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Mailing list subscription confirmation notice for mailing list
Aperture-devel

We have received a request from 10.3.1.94 for subscription of your
email address, "antoni_mylka@poczta.onet.pl", to the
aperture-devel@lists.sourceforge.net mailing list.  To confirm that
you want to be added to this mailing list, simply reply to this
message, keeping the Subject: header intact.  Or visit this web page:

    https://lists.sourceforge.net/lists/confirm/aperture-devel/c6989dd83a4acb9a0ebecff87c309211496a8e4d


Or include the following line -- and only the following line -- in a
message to aperture-devel-request@lists.sourceforge.net:

    confirm c6989dd83a4acb9a0ebecff87c309211496a8e4d

Note that simply sending a `reply' to this message should work from
most mail readers, since that usually leaves the Subject: line in the
right form (additional "Re:" text in the Subject: is okay).

If you do not wish to be subscribed to this list, please simply
disregard this message.  If you think you are being maliciously
subscribed to the list, or have any other questions, send them to
aperture-devel-owner@lists.sourceforge.net.

From - Wed Oct  4 19:03:25 2006
X-Account-Key: account3
X-UIDL: 0000ed56033dd7fc
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:24806 "EHLO
	lists-outbound.sourceforge.net") by ps26.test.onet.pl with ESMTP
	id <S4817394AbWJDRCf>; Wed, 4 Oct 2006 19:02:35 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP id 29E6D1224D
	for <antoni_mylka@poczta.onet.pl>; Wed,  4 Oct 2006 10:02:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Aperture-devel@lists.sourceforge.net mailing list reminder
From:	aperture-devel-bounces@lists.sourceforge.net
To:	antoni_mylka@poczta.onet.pl
X-No-Archive: yes
Message-ID: <mailman.0.1159981339.13301.aperture-devel@lists.sourceforge.net>
Date:	Wed, 04 Oct 2006 10:02:19 -0700
Precedence: bulk
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
List-Id: <aperture-devel.lists.sourceforge.net>
X-List-Administrivia: yes
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

You, or someone posing as you, has requested a password reminder for
your membership on the mailing list
aperture-devel@lists.sourceforge.net.  You will need this password in
order to change your membership options (e.g. do you want regular
delivery or digest delivery), and having this password makes it easier
for you to unsubscribe from the mailing list.

You are subscribed with the address: antoni_mylka@poczta.onet.pl

Your Aperture-devel password is: kochanaalinka

To make changes to your membership options, log in and visit your
options web page:

    https://lists.sourceforge.net/lists/options/aperture-devel/antoni_mylka%40poczta.onet.pl


You can also make such changes via email by sending a message to:

    aperture-devel-request@lists.sourceforge.net

with the text "help" in the subject or body.  The automatic reply will
contain more detailed instructions.

Questions or comments?  Please send them to the Aperture-devel mailing
list administrator at aperture-devel-owner@lists.sourceforge.net.

From - Thu Oct  5 15:13:58 2006
X-Account-Key: account3
X-UIDL: 0000ed56033de5be
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:19419 "EHLO
	lists-outbound.sourceforge.net") by ps12.test.onet.pl with ESMTP
	id <S494991AbWJDQyr>; Wed, 4 Oct 2006 18:54:47 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP id 14FD0FEA9
	for <antoni_mylka@poczta.onet.pl>; Wed,  4 Oct 2006 09:54:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Welcome to the "Aperture-devel" mailing list
From:	aperture-devel-request@lists.sourceforge.net
To:	antoni_mylka@poczta.onet.pl
X-No-Archive: yes
Message-ID: <mailman.0.1159980881.10528.aperture-devel@lists.sourceforge.net>
Date:	Wed, 04 Oct 2006 09:54:41 -0700
Precedence: bulk
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
List-Id: <aperture-devel.lists.sourceforge.net>
X-List-Administrivia: yes
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Welcome to the Aperture-devel@lists.sourceforge.net mailing list!

To post to this list, send your email to:

  aperture-devel@lists.sourceforge.net

General information about the mailing list is at:

  https://lists.sourceforge.net/lists/listinfo/aperture-devel

If you ever want to unsubscribe or change your options (eg, switch to
or from digest mode, change your password, etc.), visit your
subscription page at:

  https://lists.sourceforge.net/lists/options/aperture-devel/antoni_mylka%40poczta.onet.pl


You can also make such adjustments via email by sending a message to:

  Aperture-devel-request@lists.sourceforge.net

with the word `help' in the subject or body (don't include the
quotes), and you will get back a message with instructions.

You must know your password to change your options (including changing
the password, itself) or to unsubscribe.  It is:

  kochanaalinka

Normally, Mailman will remind you of your lists.sourceforge.net
mailing list passwords once every month, although you can disable this
if you prefer.  This reminder will also include instructions on how to
unsubscribe or change your account options.  There is also a button on
your options page that will email your current password to you.

From - Thu Oct  5 15:13:57 2006
X-Account-Key: account3
X-UIDL: 0000ed56033de1f5
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:59622 "EHLO
	lists-outbound.sourceforge.net") by ps15.test.onet.pl with ESMTP
	id <S6371102AbWJDRDx>; Wed, 4 Oct 2006 19:03:53 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP id B42EA12065
	for <antoni_mylka@poczta.onet.pl>; Wed,  4 Oct 2006 10:03:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Aperture-devel@lists.sourceforge.net mailing list reminder
From:	aperture-devel-bounces@lists.sourceforge.net
To:	antoni_mylka@poczta.onet.pl
X-No-Archive: yes
Message-ID: <mailman.0.1159981428.13661.aperture-devel@lists.sourceforge.net>
Date:	Wed, 04 Oct 2006 10:03:48 -0700
Precedence: bulk
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
List-Id: <aperture-devel.lists.sourceforge.net>
X-List-Administrivia: yes
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

You, or someone posing as you, has requested a password reminder for
your membership on the mailing list
aperture-devel@lists.sourceforge.net.  You will need this password in
order to change your membership options (e.g. do you want regular
delivery or digest delivery), and having this password makes it easier
for you to unsubscribe from the mailing list.

You are subscribed with the address: antoni_mylka@poczta.onet.pl

Your Aperture-devel password is: kochanaalinka

To make changes to your membership options, log in and visit your
options web page:

    https://lists.sourceforge.net/lists/options/aperture-devel/antoni_mylka%40poczta.onet.pl


You can also make such changes via email by sending a message to:

    aperture-devel-request@lists.sourceforge.net

with the text "help" in the subject or body.  The automatic reply will
contain more detailed instructions.

Questions or comments?  Please send them to the Aperture-devel mailing
list administrator at aperture-devel-owner@lists.sourceforge.net.

From - Mon Oct  9 18:08:19 2006
X-Account-Key: account3
X-UIDL: 0000ed56034ba39d
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:897 "EHLO
	lists-outbound.sourceforge.net") by ps28.test.onet.pl with ESMTP
	id <S2245883AbWJIPFq>; Mon, 9 Oct 2006 17:05:46 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 4FF26160DA; Mon,  9 Oct 2006 08:05:45 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GWwhI-0007BE-Hy for aperture-devel@lists.sourceforge.net;
	Mon, 09 Oct 2006 08:05:40 -0700
Received: from www4.aduna.biz ([66.98.176.99] helo=mail.aduna.biz)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GWwhJ-0000OE-40
	for aperture-devel@lists.sourceforge.net;
	Mon, 09 Oct 2006 08:05:41 -0700
Received: (qmail 19084 invoked from network); 9 Oct 2006 17:05:31 +0200
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna.biz with (DHE-RSA-AES256-SHA encrypted) SMTP;
	9 Oct 2006 17:05:31 +0200
Message-ID: <452A6537.1030309@aduna-software.com>
Date:	Mon, 09 Oct 2006 17:05:27 +0200
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <452A03DB.3020705@dfki.de> <452A168F.7010108@aduna-software.com>
	<452A5832.2080801@dfki.de>
In-Reply-To: <452A5832.2080801@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Antoni Mylka <Antoni.Mylka@dfki.de>
Subject: Re: [Aperture-devel] New Aperture Developer
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Leo Sauermann wrote:
> I would go for DC and other popular vocabs as well.
> 
> note we have a wikipage to discuss these things here:
> https://gnowsis.opendfki.de/wiki/ApertureDiscussion
> 
> if you have any ideas about DC, add them here:
> https://gnowsis.opendfki.de/wiki/ApertureDiscussion#Vocabulary:useDCinsteadofdata

I have made some notes during the last weeks, I'll add them here soon.

> I would keep the RDFContainer. Its a good thing. I would only build it 
> on top of RDF2GO, so that it can be used on both jena and sesame.
> https://gnowsis.opendfki.de/wiki/ApertureDiscussion#RDFContainerbasedonRDF2GO

I see. I'm still considering this, not sure whether it's a good approach:

pros:

- bindings for various RDF stores that we get for free

cons:

- is RDF2GO still using java.net.URIs? That would mean a lot of 
conversions that are potentially not necessary, e.g. when using a Sesame 
Repository: org.openrdf.model.URIs get translated to java.net.URIs and 
back to org.openrdf.model.URIs.

- RDFContainer lacks full RDF graph access. A simple getStatements 
method with a subject parameter would solve this though. I've also read 
comments by Gunnar about having to cast RDFContainer to 
SesameRDFContainer in code he wrote, I guess he had the same problem?

>> Once we have completed this move, we might also look at the AccessData 
>> API.
>> [snip]
> hm, I would think that using an rdfgraph here is overkill.
> I always thought we can implement the AccessData interface on top of the 
> store you are actually crawling to.

That's what I did with RepositoryAccessData. It wraps a Repository, 
which *can* be the same as used by the CrawlerHandler.

I'm already using this code in AutoFocus, which has dramatically 
improved the memory requirements of WebCrawler. This crawler used to 
keep the entire hypertext graph in main memory. Both the AccessData and 
the CrawlerHandler use the same Repository, using contexts to keep 
information separate (you really want to enforce that AccessData only 
reads and writes its own data).

However, the AccessData API limits the data that it can hold to simple 
key-value pairs, with the exception of the notion of "referred IDs", 
which are used for indicating links, nested objects, etc. Whenever you 
have some other graph-like data, you cannot store it properly in the 
AccessData, unless you're willing to encode multiple values in a single 
string. Also, the value is often a primitive value but can also be 
another URI (e.g. a redirectsTo property between two URLs). Right now 
these URIs are stored as literals by RepositoryAccessData.


Regards,

Chris
--

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct  9 18:08:19 2006
X-Account-Key: account3
X-UIDL: 0000ed56034ba735
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:54678 "EHLO
	lists-outbound.sourceforge.net") by ps10.test.onet.pl with ESMTP
	id <S100827472AbWJIPKv>; Mon, 9 Oct 2006 17:10:51 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 67CA616074; Mon,  9 Oct 2006 08:10:49 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GWwmE-000847-Fb for aperture-devel@lists.sourceforge.net;
	Mon, 09 Oct 2006 08:10:46 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GWwmE-0003Jz-6p
	for aperture-devel@lists.sourceforge.net;
	Mon, 09 Oct 2006 08:10:47 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k99FARWR012281; Mon, 9 Oct 2006 17:10:27 +0200
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p1+Sun/8.11.4) with ESMTP id
	k99FARv21299; Mon, 9 Oct 2006 17:10:27 +0200 (MEST)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k99FAQwf021725; Mon, 9 Oct 2006 17:10:26 +0200 (CEST)
Message-ID: <452A6646.10207@dfki.de>
Date:	Mon, 09 Oct 2006 17:09:58 +0200
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <452A03DB.3020705@dfki.de>
	<452A168F.7010108@aduna-software.com>	<452A5832.2080801@dfki.de>
	<452A6537.1030309@aduna-software.com>
In-Reply-To: <452A6537.1030309@aduna-software.com>
X-Spam-Score: 0.1 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.1 HTML_30_40             BODY: Message is 30% to 40% HTML
	0.0 HTML_MESSAGE           BODY: HTML included in message
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] New Aperture Developer
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2120612111=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============2120612111==
Content-Type: multipart/alternative;
	boundary="------------040000070900080702060605"

This is a multi-part message in MIME format.
--------------040000070900080702060605
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Es begab sich aber da Christiaan Fluit zur rechten Zeit 09.10.2006 17:05 
folgendes schrieb:
> Leo Sauermann wrote:
>   
>> I would go for DC and other popular vocabs as well.
>>
>> note we have a wikipage to discuss these things here:
>> https://gnowsis.opendfki.de/wiki/ApertureDiscussion
>>
>> if you have any ideas about DC, add them here:
>> https://gnowsis.opendfki.de/wiki/ApertureDiscussion#Vocabulary:useDCinsteadofdata
>>     
>
> I have made some notes during the last weeks, I'll add them here soon.
>
>   
>> I would keep the RDFContainer. Its a good thing. I would only build it 
>> on top of RDF2GO, so that it can be used on both jena and sesame.
>> https://gnowsis.opendfki.de/wiki/ApertureDiscussion#RDFContainerbasedonRDF2GO
>>     
>
> I see. I'm still considering this, not sure whether it's a good approach:
>
> pros:
>
> - bindings for various RDF stores that we get for free
>
> cons:
>
> - is RDF2GO still using java.net.URIs? That would mean a lot of 
> conversions that are potentially not necessary, e.g. when using a Sesame 
> Repository: org.openrdf.model.URIs get translated to java.net.URIs and 
> back to org.openrdf.model.URIs.
>   
we are contiously ranting about this to Max and finally he has changed 
his mind... I think its ok in the latest version


> - RDFContainer lacks full RDF graph access. A simple getStatements 
> method with a subject parameter would solve this though. I've also read 
> comments by Gunnar about having to cast RDFContainer to 
> SesameRDFContainer in code he wrote, I guess he had the same problem?
>
>   
and exactly that would be solved by RDF2GO, where you would have a 
proper model with all methods you need. (including querying, whatever)


>>> Once we have completed this move, we might also look at the AccessData 
>>> API.
>>> [snip]
>>>       
>> hm, I would think that using an rdfgraph here is overkill.
>> I always thought we can implement the AccessData interface on top of the 
>> store you are actually crawling to.
>>     
>
> That's what I did with RepositoryAccessData. It wraps a Repository, 
> which *can* be the same as used by the CrawlerHandler.
>
> I'm already using this code in AutoFocus, which has dramatically 
> improved the memory requirements of WebCrawler. This crawler used to 
> keep the entire hypertext graph in main memory. Both the AccessData and 
> the CrawlerHandler use the same Repository, using contexts to keep 
> information separate (you really want to enforce that AccessData only 
> reads and writes its own data).
>
> However, the AccessData API limits the data that it can hold to simple 
> key-value pairs, with the exception of the notion of "referred IDs", 
> which are used for indicating links, nested objects, etc. Whenever you 
> have some other graph-like data, you cannot store it properly in the 
> AccessData, unless you're willing to encode multiple values in a single 
> string. Also, the value is often a primitive value but can also be 
> another URI (e.g. a redirectsTo property between two URLs). Right now 
> these URIs are stored as literals by RepositoryAccessData.
>
>
> Regards,
>
> Chris
> --
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------040000070900080702060605
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Es begab sich aber da Christiaan Fluit zur rechten Zeit 09.10.2006
17:05 folgendes schrieb:
<blockquote cite="mid452A6537.1030309@aduna-software.com" type="cite">
  <pre wrap="">Leo Sauermann wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">I would go for DC and other popular vocabs as well.

note we have a wikipage to discuss these things here:
<a class="moz-txt-link-freetext" href="https://gnowsis.opendfki.de/wiki/ApertureDiscussion">https://gnowsis.opendfki.de/wiki/ApertureDiscussion</a>

if you have any ideas about DC, add them here:
<a class="moz-txt-link-freetext" href="https://gnowsis.opendfki.de/wiki/ApertureDiscussion#Vocabulary:useDCinsteadofdata">https://gnowsis.opendfki.de/wiki/ApertureDiscussion#Vocabulary:useDCinsteadofdata</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I have made some notes during the last weeks, I'll add them here soon.

  </pre>
  <blockquote type="cite">
    <pre wrap="">I would keep the RDFContainer. Its a good thing. I would only build it 
on top of RDF2GO, so that it can be used on both jena and sesame.
<a class="moz-txt-link-freetext" href="https://gnowsis.opendfki.de/wiki/ApertureDiscussion#RDFContainerbasedonRDF2GO">https://gnowsis.opendfki.de/wiki/ApertureDiscussion#RDFContainerbasedonRDF2GO</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I see. I'm still considering this, not sure whether it's a good approach:

pros:

- bindings for various RDF stores that we get for free

cons:

- is RDF2GO still using java.net.URIs? That would mean a lot of 
conversions that are potentially not necessary, e.g. when using a Sesame 
Repository: org.openrdf.model.URIs get translated to java.net.URIs and 
back to org.openrdf.model.URIs.
  </pre>
</blockquote>
we are contiously ranting about this to Max and finally he has changed
his mind... I think its ok in the latest version<br>
<br>
<br>
<blockquote cite="mid452A6537.1030309@aduna-software.com" type="cite">
  <pre wrap="">
- RDFContainer lacks full RDF graph access. A simple getStatements 
method with a subject parameter would solve this though. I've also read 
comments by Gunnar about having to cast RDFContainer to 
SesameRDFContainer in code he wrote, I guess he had the same problem?

  </pre>
</blockquote>
and exactly that would be solved by RDF2GO, where you would have a
proper model with all methods you need. (including querying, whatever)<br>
<br>
<br>
<blockquote cite="mid452A6537.1030309@aduna-software.com" type="cite">
  <pre wrap=""></pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">Once we have completed this move, we might also look at the AccessData 
API.
[snip]
      </pre>
    </blockquote>
    <pre wrap="">hm, I would think that using an rdfgraph here is overkill.
I always thought we can implement the AccessData interface on top of the 
store you are actually crawling to.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
That's what I did with RepositoryAccessData. It wraps a Repository, 
which *can* be the same as used by the CrawlerHandler.

I'm already using this code in AutoFocus, which has dramatically 
improved the memory requirements of WebCrawler. This crawler used to 
keep the entire hypertext graph in main memory. Both the AccessData and 
the CrawlerHandler use the same Repository, using contexts to keep 
information separate (you really want to enforce that AccessData only 
reads and writes its own data).

However, the AccessData API limits the data that it can hold to simple 
key-value pairs, with the exception of the notion of "referred IDs", 
which are used for indicating links, nested objects, etc. Whenever you 
have some other graph-like data, you cannot store it properly in the 
AccessData, unless you're willing to encode multiple values in a single 
string. Also, the value is often a primitive value but can also be 
another URI (e.g. a redirectsTo property between two URLs). Right now 
these URIs are stored as literals by RepositoryAccessData.


Regards,

Chris
--

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT &amp; business topics through brief surveys -- and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&amp;p=sourceforge&amp;CID=DEVDEV</a>
_______________________________________________
Aperture-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aperture-devel@lists.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listinfo/aperture-devel</a>
  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
____________________________________________________
DI Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------040000070900080702060605--


--===============2120612111==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--===============2120612111==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============2120612111==--


From - Mon Oct  9 18:08:20 2006
X-Account-Key: account3
X-UIDL: 0000ed56034bbe46
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:43208 "EHLO
	lists-outbound.sourceforge.net") by ps17.test.onet.pl with ESMTP
	id <S5302679AbWJIOKk>; Mon, 9 Oct 2006 16:10:40 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id BF8D613A4B; Mon,  9 Oct 2006 07:10:38 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GWvpz-0001cN-C9 for aperture-devel@lists.sourceforge.net;
	Mon, 09 Oct 2006 07:10:35 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GWvpv-000127-Dm
	for aperture-devel@lists.sourceforge.net;
	Mon, 09 Oct 2006 07:10:36 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k99EANTR004060; Mon, 9 Oct 2006 16:10:23 +0200
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p1+Sun/8.11.4) with ESMTP id
	k99EANv17975; Mon, 9 Oct 2006 16:10:23 +0200 (MEST)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k99EALHh018878; Mon, 9 Oct 2006 16:10:22 +0200 (CEST)
Message-ID: <452A5832.2080801@dfki.de>
Date:	Mon, 09 Oct 2006 16:09:54 +0200
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <452A03DB.3020705@dfki.de> <452A168F.7010108@aduna-software.com>
In-Reply-To: <452A168F.7010108@aduna-software.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Antoni Mylka <Antoni.Mylka@dfki.de>
Subject: Re: [Aperture-devel] New Aperture Developer
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Hi guys,

Es begab sich aber da Christiaan Fluit zur rechten Zeit 09.10.2006 11:29 
folgendes schrieb:
> Related to this we might also update Aperture's own ontology for 
> describing crawling results. Right now we have our own Data namespace. 
> We could consider switching to Dublin core and other properly 
> standardized namespaces. As of yet I don't have a clear view of all 
> the pros and cons of such a move, but we should decide on this before 
> we can make a beta or final Aperture release.
I would go for DC and other popular vocabs as well.

note we have a wikipage to discuss these things here:
https://gnowsis.opendfki.de/wiki/ApertureDiscussion

if you have any ideas about DC, add them here:
https://gnowsis.opendfki.de/wiki/ApertureDiscussion#Vocabulary:useDCinsteadofdata



>
>> 3. Create a bibtex extractor. We will use a bibtex2rdf converter. He
>> would like to have me alter  it work with rdf2go library. Now it works
>> directly with jena and the archive is almost 8 MB large. With rdf2go we
>> should be able to reduce the dependencies. Leo hopes to make it a
>> sourceforge (or opendfki) project. He has already sent an email to the
>> author.
>
> Sounds cool as well.
>
>> 4. Migrate the entire aperture to the RDF2Go Framework.
>
> Ah, you're bravely targeting Aperture's holy grail ;)
>
> There have been several discussions already on RDF2GO vs. 
> RDFContainer. Both APIs have their pros and cons. At the moment I'm a 
> mild proponent of this switch, although I do have a few reservations 
> (from the back of my head: the use of java.net.URIs - requires 
> parsing, the lack of dedicated methods for handling common Java types 
> (ints, Dates, etc.) and the lack of a notion of a described URI). 
> Probably nothing that can't be solved, but stuff we need to think 
> carefully about to prevent us from having to revisit this issue once 
> we start to add support for the next DataSource or Extractor.
I would keep the RDFContainer. Its a good thing. I would only build it 
on top of RDF2GO, so that it can be used on both jena and sesame.
https://gnowsis.opendfki.de/wiki/ApertureDiscussion#RDFContainerbasedonRDF2GO


>
> Therefore, before you start migrating, I would suggest you to write a 
> proposal to the Aperture devel mailing in which you explain how you 
> plan to work around these issues. See the mailing list archive for 
> past discussions, they should provide you with some background info.
yes, thats a good idea. To get things discussed, use the mailinglist, to 
write "agreed way" down, use the wiki.

>
> Just to prevent any misunderstandings, please know that I don't want 
> to obstruct the move to RDF2GO, it's just that there are some useful 
> aspects of RDFContainer that didn't happen by accident and that need 
> to be revisited now.
>
we should keep rdfcontainer but base it on rdf2go.

> Once we have completed this move, we might also look at the AccessData 
> API. FYI: an AccessData instance is hold to keep track of information 
> needed by a Crawler in order to be able to incrementally crawl a 
> source. While working on the WebCrawler recently, I noticed that it 
> would make my life simpler if this were also an RDF graph. Perhaps the 
> new RDF2GO stuff can be used there as well?
>
hm, I would think that using an rdfgraph here is overkill.
I always thought we can implement the AccessData interface on top of the 
store you are actually crawling to.

Store s = new Store()
Class X implements AccessData and CrawlerHander {

 x.getAccessDate... (uri)
{ return s.getStatement(uri, dc:modified, null).getObject()
}

x.onNewObject(object)
{
   object.data.add(uri, dc:modified, new Date())
   s.store(object)
}
}

==== this means: the store is both the rdf store for the crawled stuff 
and keeps the access dates, as part of the stored metadata.


>
> Good luck with your work,
thx, thats something which always helps

Leo

>
> Chris
> -- 


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Oct 19 00:03:20 2006
X-Account-Key: account3
X-UIDL: 0000ed56036a5282
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:39611 "EHLO
	lists-outbound.sourceforge.net") by ps25.test.onet.pl with ESMTP
	id <S4935663AbWJROQe>; Wed, 18 Oct 2006 16:16:34 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id BFD7413129; Wed, 18 Oct 2006 07:16:01 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GaCCx-0006I2-NS for aperture-devel@lists.sourceforge.net;
	Wed, 18 Oct 2006 07:15:47 -0700
Received: from www4.aduna.biz ([66.98.176.99] helo=mail.aduna.biz)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GaCCu-0004YL-Ci
	for aperture-devel@lists.sourceforge.net;
	Wed, 18 Oct 2006 07:15:48 -0700
Received: (qmail 4191 invoked from network); 18 Oct 2006 16:15:36 +0200
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna.biz with (DHE-RSA-AES256-SHA encrypted) SMTP;
	18 Oct 2006 16:15:36 +0200
Message-ID: <45363700.7000006@aduna-software.com>
Date:	Wed, 18 Oct 2006 16:15:28 +0200
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] handling of symbolic links, redirections, etc.
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Hello all,

I just ran into a situation with FileSystemCrawler/FileAccessor and I'm 
wondering about your opinion on this.

When crawling the /usr dir on a Linux system, I noticed that the 
resulting set of objects also contains files from /var, /etc, /opt, etc. 
This is caused by FileAccessor resolving each File to its canonical 
File, which resolves symbolic links, among other things. When a file 
path contains a symbolic link, the resulting DataObject will have a 
different URI than what the FileSystemCrawler asked from the FileAccessor.

First, I believe you should be aware of this behaviour. As far as I 
know, this will only occur on Linux and MacOS X.

Furthermore, I'm still wondering what the optimal crawling strategy 
would be for such cases:

Option 1: Just crawl these symbolically linked files and folders and 
accept that you have many DataObjects lying outside your configured root 
folders.

Option 2: The other extreme: ignore symbolic links, recognizable by the 
fact that the absolute and canonical paths of such Files differ. The 
idea would be that you are just crawling them in the wrong location.

Option 3: Only crawl them when the canonical File has one of the root 
folders as ancestor (e.g. when crawling /url, /url/foo --> /usr/foo/bar 
is crawled, /url/foo --> /etc/foo is not). Possible in various variants, 
e.g. do you use the root folders as is or do you also determine their 
canonical Files? Makes a difference when your root folder already 
contains a symbolic link.

Option 4: Let FileAccessor use File.getAbsolutePath instead of 
File.getCanonicalPath and accept that some files will be crawled 
multiple times when they can be reached through multiple paths. Note 
that in this situation entire folder trees may be crawled twice or more! 
It takes one clumsy symbolic link to expand your domain gigantically.

At first sight options 2 and 3 don't seem that bad but they may still 
produce counter-intuitive results. The problem is that file systems let 
you use such "virtual" file names without any visible difference in 
behaviour with canonical file names. Compare this for example to URL 
redirections, where it is always made explicit to end users that they 
are being redirected (your browser's address bar mentions the resolved 
"canonical URL", not the one that you typed in or clicked on). 
Consequently, it may for example happen that people will not be able to 
scan their /home/username dir just because /home points to somewhere 
else in the file system.

For this reason, option 4 may still be very reasonable. Another benefit 
is that the URIs of the reported DataObjects may be more recognizable 
for end users (again consider the /home example).

Summarizing, I believe that the current behaviour is strictly speaking 
correct and reflects the complexity of the file system, but may be 
counter-intuitive to end users. What to do, what to do...

Of course, we could make the behaviour configurable and let the 
integrator decide (who may even decide to make it configurable for the 
end user), but perhaps someone knows of an attractive option 5.

There is also another theoretical problem, whose solution depends on the 
strategy chosen above: symbolic links can be used to create circular 
paths, leading to infinitely deep folder trees.

When crawling with an AccessData instance you will probably not notice 
this as these files will seem to be unchanged the second time they are 
accessed (this only works because we resolve to the canonical File and 
therefore check the same path for being known), except that the initial 
crawl will unexpectedly report unchanged objects. Without an AccessData 
instance to use and without maximum depth restrictions the 
FileSystemCrawler will get into an infinite loop.

A note about URL redirections: the behaviour of WebCrawler is currently 
that redirections are always followed and that, if a URL falls inside 
the DomainBoundaries, the URL that it redirects to is considered to fall 
inside the boundaries as well. Only the links starting from that page 
will be checked against the DomainBoundaries again. Just so you know.


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Fri Oct 20 22:59:39 2006
X-Account-Key: account3
X-UIDL: 0000ed560371bfbb
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:16061 "EHLO
	lists-outbound.sourceforge.net") by ps26.test.onet.pl with ESMTP
	id <S4934341AbWJTSib>; Fri, 20 Oct 2006 20:38:31 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 3CFF812784; Fri, 20 Oct 2006 11:38:14 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GazFy-0002i7-Ut for aperture-devel@lists.sourceforge.net;
	Fri, 20 Oct 2006 11:38:10 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GazFz-0001Oy-G5
	for aperture-devel@lists.sourceforge.net;
	Fri, 20 Oct 2006 11:38:12 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9KIc4iZ032539 for <aperture-devel@lists.sourceforge.net>;
	Fri, 20 Oct 2006 20:38:04 +0200
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9KIc4M07138 for <aperture-devel@lists.sourceforge.net>;
	Fri, 20 Oct 2006 20:38:04 +0200 (MEST)
Received: from [192.168.41.103] (gast-4113.kl.dfki.de [192.168.41.103])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9KIc3Kk006578 for <aperture-devel@lists.sourceforge.net>;
	Fri, 20 Oct 2006 20:38:03 +0200 (CEST)
Message-ID: <4539178E.5050703@dfki.uni-kl.de>
Date:	Fri, 20 Oct 2006 20:38:06 +0200
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Report
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

I have finished the IcalCrawler. It implements the icaltzd ontology 
created by Dan Connoly. I based my work on the following materials:

The output of the fromIcal.py script by Dan Connoly
	http://www.w3.org/2002/12/cal/fromIcal.py
The rdf-ical examples
	http://www.w3.org/2002/12/cal/test/
The RDF Calendaring page in the ESW Wiki
	http://esw.w3.org/topic/RdfCalendar

The mapping of ical elements that weren't mentioned in the above sources 
  is my invention. This 'ontology' is in itself incomplete. It is 
automatically generated from the ontology document. Many properties 
don't have their ranges specified (that is those that introduce blank 
nodes). I did my best to my rdf output conform with icaltzd but I didn't 
check it in any automatic way.

The mapping is documented in the javadocs for the IcalCrawler class. I 
welcome any comments pertaining the code and the documentation.

The part responsible for incremental crawling creates for each 
DataObject a concatenation of all it's properties, their values and 
datatypes in one long string. Then a SHA1 hash value of this string is 
computed. This hash value is stored in the AccessData and later compared 
with subsequent ones to determine if a given object has been changed or 
not. Such a general approach proved necessary since there is no other 
sure way to do it. There are iCalendar files generated by various 
applications that don't have either the LAST-MODIFIED or SEQUENCE 
values. This process may be detrimental to the performance of the 
application. If this is an issue, I may try to optimize it.

I implemented the comments of Christiaan. The lines are now 110 
characters wide. The license files have been added. ExampleIcalCrawler 
has been moved to examples. A new IcalDataSource class has been 
introduced (in the source rdfs ontology, in the DATASOURCE_GEN class and 
as a separate IcalDataSource.java class).

There are 64 tests in TestIcalCrawler and 5 more in 
TestIcalCrawlerIncremental. I have changed the classes so that now they 
use the getSystemResourceAsStream() and generate a temporary file in the 
directory returned by
URL tempFileDirectory = ClassLoader.getSystemResource(".");
I hope it will help, if not, please let me know.

Leo asked me some time ago to remove the umlauts from the source files. 
I did it. I made a version tag called ApertureBeforeRemovingUmlauts. If 
there are any problems, it should be possible to return the repository 
to the previous state.

Now I begin with the migration of aperture to the RDF2Go framework.

Antoni Mylka
Antoni.Mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Sat Oct 21 23:35:29 2006
X-Account-Key: account3
X-UIDL: 0000ed560374ac33
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:14225 "EHLO
	lists-outbound.sourceforge.net") by ps21.test.onet.pl with ESMTP
	id <S6195706AbWJUQcE>; Sat, 21 Oct 2006 18:32:04 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 2C5FB12EA1; Sat, 21 Oct 2006 09:31:48 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GbJlB-0002iQ-Bp for aperture-devel@lists.sourceforge.net;
	Sat, 21 Oct 2006 09:31:45 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GbJlB-0000Vr-PL
	for aperture-devel@lists.sourceforge.net;
	Sat, 21 Oct 2006 09:31:46 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9LGUfxp023034 for <aperture-devel@lists.sourceforge.net>;
	Sat, 21 Oct 2006 18:30:41 +0200
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9LGUeM06626 for <aperture-devel@lists.sourceforge.net>;
	Sat, 21 Oct 2006 18:30:40 +0200 (MEST)
Received: from [192.168.41.103] (gast-4113.kl.dfki.de [192.168.41.103])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9LGUeIT024355 for <aperture-devel@lists.sourceforge.net>;
	Sat, 21 Oct 2006 18:30:40 +0200 (CEST)
Message-ID: <453A4B32.8030801@dfki.uni-kl.de>
Date:	Sat, 21 Oct 2006 18:30:42 +0200
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] New RDF2Go Branch
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

I ask for permission to make a branch in the CVS repository to work on 
the RDF2Go version without interrupting others. As far as I can see 
there is little activity in the aperture source tree at the moment. I 
think I would be able to merge all changes to the main trunk with my 
branch immediately as they come. That would (theoretically) facilitate 
the eventual big merge of the RDF2Go version into the main trunk.

I identified following issues that will have to be resolved:
* RDF2Go lacks the ability to set ID's for blank nodes. The Model
   interface has a generateBlankNode() method. The Sesame2 driver does
   a default createBNode() call, which creates a BNode with the default
   ID (that is node1, node2, node3 etc...) It may cause problems with
   merging, and force us to use random uris.
* it also lacks simple searching functionality with
   getStatements(Subject,Predicate,Object) methods. e.g. in the
   RDF container with have a getAll(URI property) method that operates
   via a getStatements(describedUri,property,null ... ) call. In RDF2Go
   it would have to be a SPARQL query. I will have to implement the
   this simple search functionality myself.
* the getValue() method in the literal interface returns a concatenation
   of "value" ^^ "datatype". This is an arbitrary choice. I will have to
   introduce some kind of a getLabel method that would return the value
   itself, without the datatype. (Maybe a wrapper, or an inherited class)

As far as I can see, none of those issues would make it impossible to 
use RDF2Go. I would proceed as follows:

1. Update the RDFContainer interface to use RDF2Go URIS, Nodes etc...
2. Write the RDF2GoRDFContainer implementation, that operates on a 
RDF2Go model. It would use a Sesame Model implementation by default, but 
would also provide a constructor that would enable the user to pass in 
an arbitrary model implementation (backed by any RDF store supported by 
RDF2Go). This implementation would come with TestCases.
3. Then I would systematically rewrite the crawlers and other classes 
where the RDFContainer is used. For every rewritten aperture class, I 
would rewrite the corresponding testCase. It should go mechanically.

The latest CVS Head version imports classes from Sesame 378 times and 
contains 136 tests. I understand that the goal is to completely 
eliminate the dependency on Sesame and to make all tests pass in the new 
version. The number of remaining sesame imports and the number of tests 
the new version will pass - will be indicators of my progress.

Antoni Mylka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Sat Oct 21 23:35:29 2006
X-Account-Key: account3
X-UIDL: 0000ed560374b02e
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:60077 "EHLO
	lists-outbound.sourceforge.net") by ps8.test.onet.pl with ESMTP
	id <S4874196AbWJUQk7>; Sat, 21 Oct 2006 18:40:59 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id ACBB31371F; Sat, 21 Oct 2006 09:40:58 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GbJu4-0003iX-U9 for aperture-devel@lists.sourceforge.net;
	Sat, 21 Oct 2006 09:40:56 -0700
Received: from uranus.svr3-speedyservers.com ([193.189.74.29])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GbJu5-00084W-Bo
	for aperture-devel@lists.sourceforge.net;
	Sat, 21 Oct 2006 09:40:58 -0700
Received: from p508821f5.dip0.t-ipconnect.de ([80.136.33.245]
	helo=[192.168.178.27])
	by uranus.svr3-speedyservers.com with esmtpa (Exim 4.52)
	id 1GbJu1-0000GV-TT; Sat, 21 Oct 2006 17:40:54 +0100
Message-ID: <453A4D8F.5020602@dfki.de>
Date:	Sat, 21 Oct 2006 18:40:47 +0200
From:	Gunnar Aastrand Grimnes <gunnar.grimnes@dfki.de>
User-Agent: Thunderbird 3.0a1 (Macintosh/20060417)
MIME-Version: 1.0
To:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
References: <453A4B32.8030801@dfki.uni-kl.de>
In-Reply-To: <453A4B32.8030801@dfki.uni-kl.de>
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - uranus.svr3-speedyservers.com
X-AntiAbuse: Original Domain - lists.sourceforge.net
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - dfki.de
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>,
	Max Voelkel <max@xam.de>
Subject: Re: [Aperture-devel] New RDF2Go Branch
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Hey Antoni,

I only have a few minutes so I can't check these issues, so just a quick
note!

Keep in mind that rdf2go is in no way fixed, if you have serious
problems (which you seem to have) or suggestions it can be changed!

I CC'd Max Voelkel, the main rdf2go developer, on this email.
Max: Do you have any comments?

- Gunnar

Antoni Mylka wrote:
> I ask for permission to make a branch in the CVS repository to work on 
> the RDF2Go version without interrupting others. As far as I can see 
> there is little activity in the aperture source tree at the moment. I 
> think I would be able to merge all changes to the main trunk with my 
> branch immediately as they come. That would (theoretically) facilitate 
> the eventual big merge of the RDF2Go version into the main trunk.
> 
> I identified following issues that will have to be resolved:
> * RDF2Go lacks the ability to set ID's for blank nodes. The Model
>    interface has a generateBlankNode() method. The Sesame2 driver does
>    a default createBNode() call, which creates a BNode with the default
>    ID (that is node1, node2, node3 etc...) It may cause problems with
>    merging, and force us to use random uris.
> * it also lacks simple searching functionality with
>    getStatements(Subject,Predicate,Object) methods. e.g. in the
>    RDF container with have a getAll(URI property) method that operates
>    via a getStatements(describedUri,property,null ... ) call. In RDF2Go
>    it would have to be a SPARQL query. I will have to implement the
>    this simple search functionality myself.
> * the getValue() method in the literal interface returns a concatenation
>    of "value" ^^ "datatype". This is an arbitrary choice. I will have to
>    introduce some kind of a getLabel method that would return the value
>    itself, without the datatype. (Maybe a wrapper, or an inherited class)
> 
> As far as I can see, none of those issues would make it impossible to 
> use RDF2Go. I would proceed as follows:
> 
> 1. Update the RDFContainer interface to use RDF2Go URIS, Nodes etc...
> 2. Write the RDF2GoRDFContainer implementation, that operates on a 
> RDF2Go model. It would use a Sesame Model implementation by default, but 
> would also provide a constructor that would enable the user to pass in 
> an arbitrary model implementation (backed by any RDF store supported by 
> RDF2Go). This implementation would come with TestCases.
> 3. Then I would systematically rewrite the crawlers and other classes 
> where the RDFContainer is used. For every rewritten aperture class, I 
> would rewrite the corresponding testCase. It should go mechanically.
> 
> The latest CVS Head version imports classes from Sesame 378 times and 
> contains 136 tests. I understand that the goal is to completely 
> eliminate the dependency on Sesame and to make all tests pass in the new 
> version. The number of remaining sesame imports and the number of tests 
> the new version will pass - will be indicators of my progress.
> 
> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel

-- 
Gunnar Aastrand Grimnes
gunnar.grimnes [AT] dfki.de

DFKI GmbH
Knowledge Management
Erwin-Schroedinger-Strasse
D-67663 Kaiserslautern
Germany

Office: +49 631 205 3438
Mobile: +49 177 277 4397



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 23 00:00:41 2006
X-Account-Key: account3
X-UIDL: 0000ed5603782b43
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:27075 "EHLO
	lists-outbound.sourceforge.net") by ps20.test.onet.pl with ESMTP
	id <S5331516AbWJVVys>; Sun, 22 Oct 2006 23:54:48 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id D065112703; Sun, 22 Oct 2006 14:52:56 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GblFT-0005SE-Hj for aperture-devel@lists.sourceforge.net;
	Sun, 22 Oct 2006 14:52:53 -0700
Received: from smtp9.poczta.onet.pl ([213.180.130.49])
	by mail.sourceforge.net with esmtp (Exim 4.44) id 1GblFS-00084e-U4
	for aperture-devel@lists.sourceforge.net;
	Sun, 22 Oct 2006 14:52:52 -0700
Received: from p54A6EE18.dip.t-dialin.net ([84.166.238.24]:23718 "EHLO
	[192.168.1.120]") by ps9.test.onet.pl with ESMTP
	id <S4933406AbWJVVuR>; Sun, 22 Oct 2006 23:50:17 +0200
Message-ID: <453BE7E7.6010804@poczta.onet.pl>
Date:	Sun, 22 Oct 2006 23:51:35 +0200
From:	=?ISO-8859-2?Q?Antoni_My=B3ka?= <antoni_mylka@poczta.onet.pl>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Value Factory problem
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

RDF2Go doesn't have the handy concept of ValueFactory. Every Model is in 
itself a ValueFactory (has methods like createURI, createPlainLiteral, 
createDatatypeLiteral). There is no getStatement method but the only 
available StatementImpl constructor takes the model as an argument. It 
is possible to use URIImpl, DatatypeLiteralImpl, PlainLiteralImpl 
without the Model, but BlankNodes and Statements cannot be created 
without it.

There are three solutions:

1. Use the underlying model:
BlankNode bNode = ((Model)rdfContainer.getModel()).createBlankNode();
Statement statement = new StatementImpl((Model)rdfContainer.getModel(),
	subject,predicate,object);

Pros: simple, no changes necessary
Cons: Ugly. Severly limits the genericity of RDFContainer. It would only 
work as a wrapper around the rdf2go model. It would be impossible to 
build our own SesameRdfContainer, JenaRdfContainer etc. It may not be an 
issue though. After all rdf2go is exactly about NOT having to write 
JenaRDFContainer...

2. introduce our own concept of ValueFactory and add some 
getValueFactory method to the RDF container. This value factory would 
operate on the underlying Model and would return uris, blank nodes, 
literals and statements.

Pros: elegant solution. Doesn't exclude the possibility of having the 
RDFContainer work with something else than a RDF2Go Model. We could 
implement the translation to and from rdf2go interfaces by ourselves and 
have RDFContainer work with any implementation we like. (even though in 
such case an rdf2go driver might be a better solution)

Cons: change in the RDFContainer interface.

3. add the ValueFactory functionality to the RDFContainer itself.
pros: definitely more elegant than the first
cons: bloating the RDFContainer interface

I would adopt the second one.

Antoni Mylka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 23 12:27:39 2006
X-Account-Key: account3
X-UIDL: 0000ed560379e124
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from mailgate1.uni-kl.de ([131.246.120.5]:64676 "EHLO
	mailgate1.uni-kl.de") by ps11.test.onet.pl with ESMTP
	id <S1464220AbWJWJ1T>; Mon, 23 Oct 2006 11:27:19 +0200
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de [131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id k9N8qCLx029595;
	Mon, 23 Oct 2006 10:52:15 +0200
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id k9N8q2M25296;
	Mon, 23 Oct 2006 10:52:02 +0200 (MEST)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id k9N8q0O2025717;
	Mon, 23 Oct 2006 10:52:00 +0200 (CEST)
Message-ID: <453C827C.50109@dfki.de>
Date:	Mon, 23 Oct 2006 10:51:08 +0200
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	=?UTF-8?B?QW50b25pIE15xYJrYQ==?= <antoni_mylka@poczta.onet.pl>
CC:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Value Factory problem
References: <453BE7E7.6010804@poczta.onet.pl>
In-Reply-To: <453BE7E7.6010804@poczta.onet.pl>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: leo.sauermann@dfki.de
X-ZA0: unknown (-1,0)
Status:   

Hi Antoni,

I go for 2, but please note:
rdf2go is already the Abstraction!

we don't need another abstraction on top of rdf2go, thats and 
abstraction of an abstraction, which is typical Java complication we 
don't need ;-)

We won't provide any other implementation of RDFContainer anymore 
besides the RDF2GO one, thats the idea of RDF2Go -it should wrap all the 
others and take away this work from us and push it to rdf2go.

If ValueFactory is an interface provided by rdf2go, implemented by 
rdf2go's model, then
I would say to publish the valuefactory to the rdfcontainer:
interface rdfcontainer {...

public org.rdf2go.ValueFactory getValueFactory();

}

greetings
Leo

Es begab sich aber da Antoni Myłka zur rechten Zeit 22.10.2006 23:51 
folgendes schrieb:
> RDF2Go doesn't have the handy concept of ValueFactory. Every Model is in 
> itself a ValueFactory (has methods like createURI, createPlainLiteral, 
> createDatatypeLiteral). There is no getStatement method but the only 
> available StatementImpl constructor takes the model as an argument. It 
> is possible to use URIImpl, DatatypeLiteralImpl, PlainLiteralImpl 
> without the Model, but BlankNodes and Statements cannot be created 
> without it.
>
> There are three solutions:
>
> 1. Use the underlying model:
> BlankNode bNode = ((Model)rdfContainer.getModel()).createBlankNode();
> Statement statement = new StatementImpl((Model)rdfContainer.getModel(),
> 	subject,predicate,object);
>
> Pros: simple, no changes necessary
> Cons: Ugly. Severly limits the genericity of RDFContainer. It would only 
> work as a wrapper around the rdf2go model. It would be impossible to 
> build our own SesameRdfContainer, JenaRdfContainer etc. It may not be an 
> issue though. After all rdf2go is exactly about NOT having to write 
> JenaRDFContainer...
>
> 2. introduce our own concept of ValueFactory and add some 
> getValueFactory method to the RDF container. This value factory would 
> operate on the underlying Model and would return uris, blank nodes, 
> literals and statements.
>
> Pros: elegant solution. Doesn't exclude the possibility of having the 
> RDFContainer work with something else than a RDF2Go Model. We could 
> implement the translation to and from rdf2go interfaces by ourselves and 
> have RDFContainer work with any implementation we like. (even though in 
> such case an rdf2go driver might be a better solution)
>
> Cons: change in the RDFContainer interface.
>
> 3. add the ValueFactory functionality to the RDFContainer itself.
> pros: definitely more elegant than the first
> cons: bloating the RDFContainer interface
>
> I would adopt the second one.
>
> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


From - Mon Oct 23 12:27:39 2006
X-Account-Key: account3
X-UIDL: 0000ed560379e36b
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:26598 "EHLO
	lists-outbound.sourceforge.net") by ps5.test.onet.pl with ESMTP
	id <S3418644AbWJWJfQ>; Mon, 23 Oct 2006 11:35:16 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 009AA12BA4; Mon, 23 Oct 2006 02:35:01 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GbwCw-0000pN-23 for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 02:34:58 -0700
Received: from www4.aduna.biz ([66.98.176.99] helo=mail.aduna.biz)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GbwCw-00059w-Ra
	for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 02:34:59 -0700
Received: (qmail 29255 invoked from network); 23 Oct 2006 11:34:51 +0200
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna.biz with (DHE-RSA-AES256-SHA encrypted) SMTP;
	23 Oct 2006 11:34:51 +0200
Message-ID: <453C8CB8.2080007@aduna-software.com>
Date:	Mon, 23 Oct 2006 11:34:48 +0200
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
References: <4539178E.5050703@dfki.uni-kl.de>
In-Reply-To: <4539178E.5050703@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Report
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Antoni Mylka wrote:
> The part responsible for incremental crawling creates for each 
> DataObject a concatenation of all it's properties, their values and 
> datatypes in one long string. Then a SHA1 hash value of this string is 
> computed. [...] This process may be detrimental to the performance of the 
> application. If this is an issue, I may try to optimize it.

IMO the main purpose of incremental crawling has always been to optimize 
crawling performance by preventing unnecessary file processing, 
retrieval of resources over a network, etc. as much as possible.

There are some beneficial side effects such as the ability to report to 
users how much/which part of their domain has changed, but when this 
actually hurts performance, I don't believe it's worth the cost.

Furthermore, incremental crawling is always hard and error-prone to code 
because of reliance on information that's not always available or 
reliable, the division between Crawler and DataAccessor that can get in 
the way, etc.

Therefore, I wouldn't mind if you change this later on to support 
non-incremental crawling only.

> There are 64 tests in TestIcalCrawler and 5 more in 
> TestIcalCrawlerIncremental. I have changed the classes so that now they 
> use the getSystemResourceAsStream() and generate a temporary file in the 
> directory returned by
> URL tempFileDirectory = ClassLoader.getSystemResource(".");
> I hope it will help, if not, please let me know.

I still have problems running the unit tests and I spent some time 
figuring out why. Here's what I found.

First of all, the FileReader created by IcalCrawler.crawlIcalFile is not 
closed. Consequently, the assertTrue(File.delete) on the temporary Ical 
file fails. I strongly suspect that this only occurs on Windows, I 
believe other platforms do allow you to delete open files, which may 
explain why you do not see this error. I would advise you to close the 
FileReader in the finally clause of the try that creates it, so that you 
are sure it will always be invoked, especially when crawling is aborted 
because of an exception.

BTW: shouldn't crawlCalendar be invoked within the try block? Now you 
risk invoking it when creation of the FileReader has failed. A nice unit 
test might therefore be to feed it some invalid input (e.g. a 
non-existing file) and ensure that crawling does not result in an 
exception at the point where you invoke crawler.crawl(). This might also 
be a good idea for the other crawler unit tests.

Furthermore, I do not understand the ClassLoader.getSystemResource(".") 
trick. What is the idea behind this? Why not use File.createTempFile? I 
suspect that your approach may even load to locations where you cannot 
even store a file, e.g. when running the unit tests from a jar file.

I would also recommend invoking .deleteOnExit on the temporary files. 
The assert on file.delete remains to be a good idea but deleteOnExit 
ensures that, when this file cannot be deleted, your temp directory 
won't be filled with temporary files that are never deleted.

Finally, note that you can use IOUtil.writeStream(InputStream, File), 
which you can use to simply your createTempFile method.


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 23 12:27:39 2006
X-Account-Key: account3
X-UIDL: 0000ed560379f5e9
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:19353 "EHLO
	lists-outbound.sourceforge.net") by ps6.test.onet.pl with ESMTP
	id <S6331362AbWJWJvK>; Mon, 23 Oct 2006 11:51:10 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 95BC31254B; Mon, 23 Oct 2006 02:51:08 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GbwSV-0002Je-G4 for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 02:51:03 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GbwST-0003cs-Gg
	for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 02:51:04 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9N9ot1s013155; Mon, 23 Oct 2006 11:50:55 +0200
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9N9osM28880; Mon, 23 Oct 2006 11:50:54 +0200 (MEST)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9N9oqYX029159; Mon, 23 Oct 2006 11:50:53 +0200 (CEST)
Message-ID: <453C9048.2030307@dfki.de>
Date:	Mon, 23 Oct 2006 11:50:00 +0200
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <45363700.7000006@aduna-software.com>
In-Reply-To: <45363700.7000006@aduna-software.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] handling of symbolic links, redirections, etc.
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Funny, we had the same problem this week when Heinz Kirchmann, one of 
our Software Engineers crawled test data.

I would go for 2:
'Don't crawl symbolic links at all'

and optionally switch to 1: follow symlinks.

The problem only appears on UNIX systems, and people on these systems 
know what symlinks are, they make them intentionally, so it should be ok.
I am inspired there by ususal command line options on UNIX tools, so for 
example RSYNC has this "follow symlinks" option, same with RM I think, 
and TAR, etc. I would do the same with aperture. I don't know how the 
pathnames look like then, but I won't go for 4 where only the absolute 
names are given.

Keep it simple?

regards
Leo

Es begab sich aber da Christiaan Fluit zur rechten Zeit 18.10.2006 16:15 
folgendes schrieb:
> Hello all,
>
> I just ran into a situation with FileSystemCrawler/FileAccessor and I'm 
> wondering about your opinion on this.
>
> When crawling the /usr dir on a Linux system, I noticed that the 
> resulting set of objects also contains files from /var, /etc, /opt, etc. 
> This is caused by FileAccessor resolving each File to its canonical 
> File, which resolves symbolic links, among other things. When a file 
> path contains a symbolic link, the resulting DataObject will have a 
> different URI than what the FileSystemCrawler asked from the FileAccessor.
>
> First, I believe you should be aware of this behaviour. As far as I 
> know, this will only occur on Linux and MacOS X.
>
> Furthermore, I'm still wondering what the optimal crawling strategy 
> would be for such cases:
>
> Option 1: Just crawl these symbolically linked files and folders and 
> accept that you have many DataObjects lying outside your configured root 
> folders.
>
> Option 2: The other extreme: ignore symbolic links, recognizable by the 
> fact that the absolute and canonical paths of such Files differ. The 
> idea would be that you are just crawling them in the wrong location.
>
> Option 3: Only crawl them when the canonical File has one of the root 
> folders as ancestor (e.g. when crawling /url, /url/foo --> /usr/foo/bar 
> is crawled, /url/foo --> /etc/foo is not). Possible in various variants, 
> e.g. do you use the root folders as is or do you also determine their 
> canonical Files? Makes a difference when your root folder already 
> contains a symbolic link.
>
> Option 4: Let FileAccessor use File.getAbsolutePath instead of 
> File.getCanonicalPath and accept that some files will be crawled 
> multiple times when they can be reached through multiple paths. Note 
> that in this situation entire folder trees may be crawled twice or more! 
> It takes one clumsy symbolic link to expand your domain gigantically.
>
> At first sight options 2 and 3 don't seem that bad but they may still 
> produce counter-intuitive results. The problem is that file systems let 
> you use such "virtual" file names without any visible difference in 
> behaviour with canonical file names. Compare this for example to URL 
> redirections, where it is always made explicit to end users that they 
> are being redirected (your browser's address bar mentions the resolved 
> "canonical URL", not the one that you typed in or clicked on). 
> Consequently, it may for example happen that people will not be able to 
> scan their /home/username dir just because /home points to somewhere 
> else in the file system.
>
> For this reason, option 4 may still be very reasonable. Another benefit 
> is that the URIs of the reported DataObjects may be more recognizable 
> for end users (again consider the /home example).
>
> Summarizing, I believe that the current behaviour is strictly speaking 
> correct and reflects the complexity of the file system, but may be 
> counter-intuitive to end users. What to do, what to do...
>
> Of course, we could make the behaviour configurable and let the 
> integrator decide (who may even decide to make it configurable for the 
> end user), but perhaps someone knows of an attractive option 5.
>
> There is also another theoretical problem, whose solution depends on the 
> strategy chosen above: symbolic links can be used to create circular 
> paths, leading to infinitely deep folder trees.
>
> When crawling with an AccessData instance you will probably not notice 
> this as these files will seem to be unchanged the second time they are 
> accessed (this only works because we resolve to the canonical File and 
> therefore check the same path for being known), except that the initial 
> crawl will unexpectedly report unchanged objects. Without an AccessData 
> instance to use and without maximum depth restrictions the 
> FileSystemCrawler will get into an infinite loop.
>
> A note about URL redirections: the behaviour of WebCrawler is currently 
> that redirections are always followed and that, if a URL falls inside 
> the DomainBoundaries, the URL that it redirects to is considered to fall 
> inside the boundaries as well. Only the links starting from that page 
> will be checked against the DomainBoundaries again. Just so you know.
>
>
> Chris
> --
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 23 12:27:40 2006
X-Account-Key: account3
X-UIDL: 0000ed56037a08d8
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:4836 "EHLO
	lists-outbound.sourceforge.net") by ps7.test.onet.pl with ESMTP
	id <S3119899AbWJWKV5>; Mon, 23 Oct 2006 12:21:57 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id F155BFCD5; Mon, 23 Oct 2006 03:21:50 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GbwwF-000579-Ms for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 03:21:47 -0700
Received: from www4.aduna.biz ([66.98.176.99] helo=mail.aduna.biz)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GbwwG-0002nE-G3
	for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 03:21:48 -0700
Received: (qmail 30544 invoked from network); 23 Oct 2006 12:21:42 +0200
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna.biz with (DHE-RSA-AES256-SHA encrypted) SMTP;
	23 Oct 2006 12:21:42 +0200
Message-ID: <453C97B3.3060900@aduna-software.com>
Date:	Mon, 23 Oct 2006 12:21:39 +0200
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
References: <453A4B32.8030801@dfki.uni-kl.de>
In-Reply-To: <453A4B32.8030801@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] New RDF2Go Branch
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Antoni Mylka wrote:
> I ask for permission to make a branch in the CVS repository to work on 
> the RDF2Go version without interrupting others. As far as I can see 
> there is little activity in the aperture source tree at the moment. I 
> think I would be able to merge all changes to the main trunk with my 
> branch immediately as they come. That would (theoretically) facilitate 
> the eventual big merge of the RDF2Go version into the main trunk.

Sounds good to me! I'm not much of a versioning hero myself (I pretty 
much always live on the trunk or whatever the latest code is called in 
your scm of choice) but there surely are others at DFKI or Aduna who can 
advise you on how to organize this in the best way.

> * it also lacks simple searching functionality with
>    getStatements(Subject,Predicate,Object) methods. e.g. in the
>    RDF container with have a getAll(URI property) method that operates
>    via a getStatements(describedUri,property,null ... ) call. In RDF2Go
>    it would have to be a SPARQL query. I will have to implement the
>    this simple search functionality myself.

Gunnar already said it: RDF2Go may be extended to accommodate this. 
Using SPARQL for this sounds like a rather heavy mechanism.

> 1. Update the RDFContainer interface to use RDF2Go URIS, Nodes etc...
> 2. Write the RDF2GoRDFContainer implementation, that operates on a 
> RDF2Go model. It would use a Sesame Model implementation by default, but 
> would also provide a constructor that would enable the user to pass in 
> an arbitrary model implementation (backed by any RDF store supported by 
> RDF2Go).

If your goal is to remove the dependency on Sesame Repositories 
altogether, why not only have the second constructor?

And how about using org.openrdf.model.URIs instead of java.net.URIs in 
the RDF2Go APIs? Think you can get to change? Primary reasons for 
introducing our own URI API in Sesame were (if I remember correctly):

- java.net.URI performs some heavy URI parsing operations which 
considerably hurts performance when dealing with URI-centric data such 
as RDF.

- At that time java.net.URI also did not correctly parse all valid URIs. 
In the heterogeneous kind of environments where Aperture is typically 
applied I'm sure this will certainly lead to problems someday somewhere. 
Perhaps the parsing behaviour has been corrected by now, perhaps not 
(Sun is very conservative in order to preserve backwards compatability).

- Introducing our own API allows us to put URI in a hierarchy of 
interfaces so that it also implements Resource and Value.

IMHO the use of the other org.openrdf.model interfaces such as Resource 
and Value in RDF2Go also make much sense, rather than using e.g. 
java.lang.Object to model values in statements. I can imagine some 
resistance from the RDF2Go developers though, not in the least because 
RDF2Go aims to unify access to a lot of RDF stores and the use of Sesame 
APIs in its core may give users a different *perception* on how 
storage-neutral it really is. Let me know if this is an issue and we can 
be of some assistance in this matter.


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 23 14:26:33 2006
X-Account-Key: account3
X-UIDL: 0000ed56037a1c31
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from www4.aduna.biz ([66.98.176.99]:40416 "EHLO mail.aduna.biz")
	by ps9.test.onet.pl with ESMTP id <S4822658AbWJWK6d>;
	Mon, 23 Oct 2006 12:58:33 +0200
Received: (qmail 31640 invoked from network); 23 Oct 2006 12:59:54 +0200
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
  by www4.aduna.biz with (DHE-RSA-AES256-SHA encrypted) SMTP; 23 Oct 2006 12:59:54 +0200
Message-ID: <453CA0A7.4010300@aduna-software.com>
Date:	Mon, 23 Oct 2006 12:59:51 +0200
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	=?UTF-8?B?QW50b25pIE15xYJrYQ==?= <antoni_mylka@poczta.onet.pl>
CC:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Value Factory problem
References: <453BE7E7.6010804@poczta.onet.pl>
In-Reply-To: <453BE7E7.6010804@poczta.onet.pl>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: christiaan.fluit@aduna-software.com
X-ZA0: unknown (-1,0)
Status:   

Antoni Myłka wrote:
> RDF2Go doesn't have the handy concept of ValueFactory. Every Model is in 
> itself a ValueFactory (has methods like createURI, createPlainLiteral, 
> createDatatypeLiteral). There is no getStatement method but the only 
> available StatementImpl constructor takes the model as an argument. It 
> is possible to use URIImpl, DatatypeLiteralImpl, PlainLiteralImpl 
> without the Model, but BlankNodes and Statements cannot be created 
> without it.

I guess you refer to the code in the RDF2Go trunk? I don't see them in 
the online javadocs.

> There are three solutions:
[snip]

I'm having some trouble overseeing this all, I don't really have a clear 
view of all the consequences of these strategies.

I agree with Leo that RDF2Go should be the abstraction of the RDF store 
and his solution sounds fine to me. I believe the idea was that 
RDFContainer would always work on an RDF2Go Model, so that Crawlers etc. 
finally are able to access the full RDF graph, without exception. 
Therefore I'm not so thrilled by "Doesn't exclude the possibility of 
having the RDFContainer work with something else than a RDF2Go Model".

Just an informative note: right now I use my own specialized 
RDFContainer implementation in AutoFocus, tuned towards its specific 
needs. In the new architecture that would probably be an 
AutoFocus-specific org.ontoware.rdf2go.Model implementation, right? As 
long as that remains possible without breaking anything, I'm quite 
satisfied :)


Chris
--

From - Mon Oct 23 14:26:34 2006
X-Account-Key: account3
X-UIDL: 0000ed56037a2952
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:6306 "EHLO
	lists-outbound.sourceforge.net") by ps25.test.onet.pl with ESMTP
	id <S4822625AbWJWLY3>; Mon, 23 Oct 2006 13:24:29 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id E1C9AF9A8; Mon, 23 Oct 2006 04:23:53 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GbxuI-0002is-Es for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 04:23:50 -0700
Received: from www4.aduna.biz ([66.98.176.99] helo=mail.aduna.biz)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GbxuH-0003Uz-1Z
	for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 04:23:51 -0700
Received: (qmail 32081 invoked from network); 23 Oct 2006 13:23:42 +0200
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna.biz with (DHE-RSA-AES256-SHA encrypted) SMTP;
	23 Oct 2006 13:23:42 +0200
Message-ID: <453CA63B.3060706@aduna-software.com>
Date:	Mon, 23 Oct 2006 13:23:39 +0200
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Leo Sauermann <leo.sauermann@dfki.de>
References: <45363700.7000006@aduna-software.com> <453C9048.2030307@dfki.de>
In-Reply-To: <453C9048.2030307@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] handling of symbolic links, redirections, etc.
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Leo Sauermann wrote:
> I would go for 2: 'Don't crawl symbolic links at all'
> 
> and optionally switch to 1: follow symlinks.
> 
> The problem only appears on UNIX systems, and people on these systems
>  know what symlinks are, they make them intentionally, so it should
> be ok. I am inspired there by ususal command line options on UNIX
> tools, so for example RSYNC has this "follow symlinks" option, same
> with RM I think, and TAR, etc. I would do the same with aperture.

Sounds very reasonable. I'll create an issue for it in the bug tracker 
and change the behaviour somewhere in the next weeks (have to finish an 
AutoFocus beta release first, for which this is not a big issue).

I'm still wondering whether this is something for the FileSystemCrawler
or the FileAccessor to handle. It feels like a crawling property but it 
can be more conveniently handled by the FileAccessor so that it prevents 
the construction of the data object with all its metadata in the first 
place. However, there is no mechanism to communicate this back to the 
Crawler. Just returning "null" already has a specific semantics, namely 
that the object has not been modified.

Furthermore, throwing DataObjects away in the Crawler without reporting 
them first through one of the CrawlerHandler methods gives me a Sesame 
warning for every DataObject as the temporary Repository in its 
RDFContainer is not properly disposed of. RDFContainer has no method for 
  disposing it and the CrawlerHandler never gets a signal that the 
retrieved RDFContainer is thrown away. The same problem also occurs in 
WebCrawler. Any ideas? Perhaps CrawlerHandler should be extended with a 
method to "push back" unused RDFContainers? Or RDFContainer should have 
a close/dispose method? It's not that much of a big deal but now that 
we're revising that part of the API anyway, this is a good time to discuss.

> I don't know how the pathnames look like then, but I won't go for 4
> where only the absolute names are given.

Agreed.

Guess today's an Aperture day for me :)


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 23 16:29:34 2006
X-Account-Key: account3
X-UIDL: 0000ed56037a5e52
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:35205 "EHLO
	lists-outbound.sourceforge.net") by ps1.test.onet.pl with ESMTP
	id <S7463107AbWJWNQe>; Mon, 23 Oct 2006 15:16:34 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 873D8F9C0; Mon, 23 Oct 2006 05:46:14 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GbzC0-0001yB-8r for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 05:46:12 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GbzBw-0004pR-P8
	for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 05:46:13 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9NCjvZR010811; Mon, 23 Oct 2006 14:45:57 +0200
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9NCjuM08180; Mon, 23 Oct 2006 14:45:56 +0200 (MEST)
Received: from [192.168.41.103] (gast-4113.kl.dfki.de [192.168.41.103])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9NCjtvG003601; Mon, 23 Oct 2006 14:45:56 +0200 (CEST)
Message-ID: <453CB984.50800@dfki.uni-kl.de>
Date:	Mon, 23 Oct 2006 14:45:56 +0200
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <453BE7E7.6010804@poczta.onet.pl>
	<453CA0A7.4010300@aduna-software.com>
In-Reply-To: <453CA0A7.4010300@aduna-software.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgate1.uni-kl.de id
	k9NCjvZR010811
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Value Factory problem
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Q2hyaXN0aWFhbiBGbHVpdCBuYXBpc2HFgihhKToKPiBBbnRvbmkgTXnFgmthIHdyb3RlOgo+PiBS
REYyR28gZG9lc24ndCBoYXZlIHRoZSBoYW5keSBjb25jZXB0IG9mIFZhbHVlRmFjdG9yeS4gRXZl
cnkgTW9kZWwgaXMgCj4+IGluIGl0c2VsZiBhIFZhbHVlRmFjdG9yeSAoaGFzIG1ldGhvZHMgbGlr
ZSBjcmVhdGVVUkksIAo+PiBjcmVhdGVQbGFpbkxpdGVyYWwsIGNyZWF0ZURhdGF0eXBlTGl0ZXJh
bCkuIFRoZXJlIGlzIG5vIGdldFN0YXRlbWVudCAKPj4gbWV0aG9kIGJ1dCB0aGUgb25seSBhdmFp
bGFibGUgU3RhdGVtZW50SW1wbCBjb25zdHJ1Y3RvciB0YWtlcyB0aGUgCj4+IG1vZGVsIGFzIGFu
IGFyZ3VtZW50LiBJdCBpcyBwb3NzaWJsZSB0byB1c2UgVVJJSW1wbCwgCj4+IERhdGF0eXBlTGl0
ZXJhbEltcGwsIFBsYWluTGl0ZXJhbEltcGwgd2l0aG91dCB0aGUgTW9kZWwsIGJ1dCAKPj4gQmxh
bmtOb2RlcyBhbmQgU3RhdGVtZW50cyBjYW5ub3QgYmUgY3JlYXRlZCB3aXRob3V0IGl0Lgo+IAo+
IEkgZ3Vlc3MgeW91IHJlZmVyIHRvIHRoZSBjb2RlIGluIHRoZSBSREYyR28gdHJ1bms/IEkgZG9u
J3Qgc2VlIHRoZW0gaW4gCj4gdGhlIG9ubGluZSBqYXZhZG9jcy4KPiAKCkkgZGlkbid0IG1lYW4g
aXQgbGl0ZXJhbGx5LiBUaGVyZSBpcyBubyBzdWNoIHRoaW5nIGFzIGEgVmFsdWVGYWN0b3J5IGlu
IApSREYyR28uIEkgbWVhbiB0aGF0IHRoZSBmdW5jdGlvbmFsaXR5IG9mIGEgU2VzYW1lIFZhbHVl
RmFjdG9yeSAodGhhdCBpcyAKY3JlYXRpbmcgaW1wbGVtZW50YXRpb24gc3BlY2lmaWMgTGl0ZXJh
bHMsIFVSSXMsIEJsYW5rTm9kZXMgYW5kIApTdGF0ZW1lbnRzKSBpcyBpbmNsdWRlZCBpbiB0aGUg
TW9kZWwgaW50ZXJmYWNlLiBJdCBjb3VsZCBiZSB1c2VkIApkaXJlY3RseSwgYnV0IEkgdGhpbmsg
dGhhdCBpbnRyb2R1Y2luZyBzb21lIHNvcnQgb2YgYSB3cmFwcGVyIGFyb3VuZCAKdGhlc2UgY3Jl
YXRpb24gbWV0aG9kcyBtaWdodCBiZSBjb252ZW5pZW50LiBGb3IgZXhhbXBsZSB3ZSBjb3VsZCBo
YXZlIAp0aGUgY3JlYXRlTGl0ZXJhbCBtZXRob2RzIGZvciBhbGwgcHJpbWl0aXZlIHR5cGVzIHRo
YXQgd291bGQgcmV0dXJuIApEYXRhdHlwZUxpdGVyYWxzIHdpdGggYXBwcm9wcmlhdGUgWFNEIGRh
dGF0eXBlLgoKSW4gbXkgY3VycmVudCB3b3JrICh0aGF0IGlzIGR1cmluZyBsYXN0IHRocmVlIGRh
eXMpIEkgaW50cm9kdWNlIGxvdHMgb2YgCnJkZkNvbnRhaW5lci5nZXRWYWx1ZUZhY3RvcnkoKS5j
cmVhdGVMaXRlcmFsKCJibGFoIGJsYWggYmxhaCIpOyAKY29uc3RydWN0cy4gVGhlIHF1ZXN0aW9u
IGlzIG9ubHkgaWYgd2Ugc2hvdWxkIHVzZSB0aGUgVmFsdWVGYWN0b3J5IChhcyAKYWJvdmUpIG9y
IG5vdCBhbmQgYWRkIHRob3NlIGNyZWF0ZS4uLiBtZXRob2RzIHRvIHRoZSBSREZDb250YWluZXIg
CmludGVyZmFjZSwgZm9yIGV4YW1wbGU6CgpMaXRlcmFsIGxpdGVyYWwgPSByZGZDb250YWluZXIu
Y3JlYXRlTGl0ZXJhbCgiYmxhaCBibGFoIGJsYWgiKTsuCgptYXliZSB0aGlzIGV4cGFuc2lvbiBv
ZiByZGZDb250YWluZXIgaW50ZXJmYWNlIHdvdWxkbid0IGJlIHRoYXQgYmFkIAphZnRlciBhbGwg
Oi0pLgoKQXMgTGVvIHdyb3RlIGluIGhpcyBlbWFpbCwgSSB3aWxsIGNvbnRpbnVlIHdpdGggZ2V0
VmFsdWVGYWN0b3J5KCkuLi4gCmFwcHJvYWNoLiBJIHdhbnRlZCB0byBtYWtlIGFzIGxpdHRsZSBj
aGFuZ2VzIGFzIHBvc3NpYmxlLiBUaGUgClJERkNvbnRhaW5lciBpcyB0aGUgY2VudHJhbCBpbnRl
cmZhY2Ugb2YgdGhlIGVudGlyZSBmcmFtZXdvcmsuIEkgZGlkbid0IAp3YW50IHRvIGFkZCAxMiBj
cmVhdGVTb21ldGhpbmcuLiBtZXRob2RzIHRvIGl0IHdpdGhvdXQgZGlzY3Vzc2luZyBpdCAKd2l0
aCB0aGUgZXhlY3V0aXZlcyBmaXJzdC4gSSBjYW4gZG8gaXQgYXQgYW55IG1vbWVudCBpZiB5b3Ug
Y2hhbmdlIHlvdXIgCm1pbmQuCgpBbnRvbmkgTXlsa2EKYW50b25pLm15bGthQGRma2kudW5pLWts
LmRlCgoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQpVc2luZyBUb21jYXQgYnV0IG5lZWQgdG8gZG8gbW9yZT8g
TmVlZCB0byBzdXBwb3J0IHdlYiBzZXJ2aWNlcywgc2VjdXJpdHk/CkdldCBzdHVmZiBkb25lIHF1
aWNrbHkgd2l0aCBwcmUtaW50ZWdyYXRlZCB0ZWNobm9sb2d5IHRvIG1ha2UgeW91ciBqb2IgZWFz
aWVyCkRvd25sb2FkIElCTSBXZWJTcGhlcmUgQXBwbGljYXRpb24gU2VydmVyIHYuMS4wLjEgYmFz
ZWQgb24gQXBhY2hlIEdlcm9uaW1vCmh0dHA6Ly9zZWwuYXMtdXMuZmFsa2FnLm5ldC9zZWw/Y21k
PWxuayZraWQ9MTIwNzA5JmJpZD0yNjMwNTcmZGF0PTEyMTY0MgpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXwpBcGVydHVyZS1kZXZlbCBtYWlsaW5nIGxpc3QK
QXBlcnR1cmUtZGV2ZWxAbGlzdHMuc291cmNlZm9yZ2UubmV0Cmh0dHBzOi8vbGlzdHMuc291cmNl
Zm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL2FwZXJ0dXJlLWRldmVsCg==

From - Mon Oct 23 18:20:15 2006
X-Account-Key: account3
X-UIDL: 0000ed56037aac86
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:11424 "EHLO
	lists-outbound.sourceforge.net") by ps4.test.onet.pl with ESMTP
	id <S3621823AbWJWPNk>; Mon, 23 Oct 2006 17:13:40 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 0372916043; Mon, 23 Oct 2006 08:11:36 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gc1Sd-0000g7-KD for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 08:11:31 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gc1SZ-0001hD-IX
	for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 08:11:32 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9NFBLYF019816; Mon, 23 Oct 2006 17:11:21 +0200
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9NFBLM16761; Mon, 23 Oct 2006 17:11:21 +0200 (MEST)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9NFBJDM017492; Mon, 23 Oct 2006 17:11:19 +0200 (CEST)
Message-ID: <453CDB62.4080504@dfki.de>
Date:	Mon, 23 Oct 2006 17:10:26 +0200
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
References: <453BE7E7.6010804@poczta.onet.pl>	<453CA0A7.4010300@aduna-software.com>
	<453CB984.50800@dfki.uni-kl.de>
In-Reply-To: <453CB984.50800@dfki.uni-kl.de>
X-Spam-Score: 0.6 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.5 HTML_20_30             BODY: Message is 20% to 30% HTML
	0.0 HTML_TITLE_EMPTY       BODY: HTML title contains no text
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>,
	Christiaan Fluit <christiaan.fluit@aduna-software.com>
Subject: Re: [Aperture-devel] Value Factory problem
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2093244961=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============2093244961==
Content-Type: multipart/alternative;
	boundary="------------010909000300070302030100"

This is a multi-part message in MIME format.
--------------010909000300070302030100
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgate1.uni-kl.de id
	k9NFBLYF019816

Hi all,

ok, if RDF2Go has not a separate valuefactory (which is bad, but we can=20
live with it), I don't see a solution at hand.
For sure, the RDFContainer wraps one resource, and creating literal=20
values with datatypes could be handled in the way similar to now:
RDFContainer.add....(property, boolean bool)
and many more, where you create statements.

I would say that we ask rdf2go to provide a valuefactory interface -=20
these guys love abstractions anyway - and see what they say.
Antoni - could you check how this can be done in rdf2go in an=20
intelligent way and write a mail to them?
we will get all mails from the rdf2go mailinglist also on the aperture=20
list, so no need to copy it here.

greetings
Leo


Es begab sich aber da Antoni Mylka zur rechten Zeit 23.10.2006 14:45=20
folgendes schrieb:
> Christiaan Fluit napisa=C5=82(a):
>  =20
>> Antoni My=C5=82ka wrote:
>>    =20
>>> RDF2Go doesn't have the handy concept of ValueFactory. Every Model is=
=20
>>> in itself a ValueFactory (has methods like createURI,=20
>>> createPlainLiteral, createDatatypeLiteral). There is no getStatement=20
>>> method but the only available StatementImpl constructor takes the=20
>>> model as an argument. It is possible to use URIImpl,=20
>>> DatatypeLiteralImpl, PlainLiteralImpl without the Model, but=20
>>> BlankNodes and Statements cannot be created without it.
>>>      =20
>> I guess you refer to the code in the RDF2Go trunk? I don't see them in=
=20
>> the online javadocs.
>>
>>    =20
>
> I didn't mean it literally. There is no such thing as a ValueFactory in=
=20
> RDF2Go. I mean that the functionality of a Sesame ValueFactory (that is=
=20
> creating implementation specific Literals, URIs, BlankNodes and=20
> Statements) is included in the Model interface. It could be used=20
> directly, but I think that introducing some sort of a wrapper around=20
> these creation methods might be convenient. For example we could have=20
> the createLiteral methods for all primitive types that would return=20
> DatatypeLiterals with appropriate XSD datatype.
>
> In my current work (that is during last three days) I introduce lots of=
=20
> rdfContainer.getValueFactory().createLiteral("blah blah blah");=20
> constructs. The question is only if we should use the ValueFactory (as=20
> above) or not and add those create... methods to the RDFContainer=20
> interface, for example:
>
> Literal literal =3D rdfContainer.createLiteral("blah blah blah");.
>
> maybe this expansion of rdfContainer interface wouldn't be that bad=20
> after all :-).
>
> As Leo wrote in his email, I will continue with getValueFactory()...=20
> approach. I wanted to make as little changes as possible. The=20
> RDFContainer is the central interface of the entire framework. I didn't=
=20
> want to add 12 createSomething.. methods to it without discussing it=20
> with the executives first. I can do it at any moment if you change your=
=20
> mind.
>
> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de
>
>
> -----------------------------------------------------------------------=
--
> Using Tomcat but need to do more? Need to support web services, securit=
y?
> Get stuff done quickly with pre-integrated technology to make your job =
easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron=
imo
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>
>  =20


--=20
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann=20
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------010909000300070302030100
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgate1.uni-kl.de id
	k9NFBLYF019816

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"=
>
  <title></title>
</head>
<body bgcolor=3D"#ffffff" text=3D"#000000">
Hi all,<br>
<br>
ok, if RDF2Go has not a separate valuefactory (which is bad, but we can
live with it), I don't see a solution at hand.<br>
For sure, the RDFContainer wraps one resource, and creating literal
values with datatypes could be handled in the way similar to now:<br>
RDFContainer.add....(property, boolean bool)<br>
and many more, where you create statements.<br>
<br>
I would say that we ask rdf2go to provide a valuefactory interface -
these guys love abstractions anyway - and see what they say.<br>
Antoni - could you check how this can be done in rdf2go in an
intelligent way and write a mail to them?<br>
we will get all mails from the rdf2go mailinglist also on the aperture
list, so no need to copy it here.<br>
<br>
greetings<br>
Leo<br>
<br>
<br>
Es begab sich aber da Antoni Mylka zur rechten Zeit 23.10.2006 14:45
folgendes schrieb:
<blockquote cite=3D"mid453CB984.50800@dfki.uni-kl.de" type=3D"cite">
  <pre wrap=3D"">Christiaan Fluit napisa=C5=82(a):
  </pre>
  <blockquote type=3D"cite">
    <pre wrap=3D"">Antoni My=C5=82ka wrote:
    </pre>
    <blockquote type=3D"cite">
      <pre wrap=3D"">RDF2Go doesn't have the handy concept of ValueFactor=
y. Every Model is=20
in itself a ValueFactory (has methods like createURI,=20
createPlainLiteral, createDatatypeLiteral). There is no getStatement=20
method but the only available StatementImpl constructor takes the=20
model as an argument. It is possible to use URIImpl,=20
DatatypeLiteralImpl, PlainLiteralImpl without the Model, but=20
BlankNodes and Statements cannot be created without it.
      </pre>
    </blockquote>
    <pre wrap=3D"">I guess you refer to the code in the RDF2Go trunk? I d=
on't see them in=20
the online javadocs.

    </pre>
  </blockquote>
  <pre wrap=3D""><!---->
I didn't mean it literally. There is no such thing as a ValueFactory in=20
RDF2Go. I mean that the functionality of a Sesame ValueFactory (that is=20
creating implementation specific Literals, URIs, BlankNodes and=20
Statements) is included in the Model interface. It could be used=20
directly, but I think that introducing some sort of a wrapper around=20
these creation methods might be convenient. For example we could have=20
the createLiteral methods for all primitive types that would return=20
DatatypeLiterals with appropriate XSD datatype.

In my current work (that is during last three days) I introduce lots of=20
rdfContainer.getValueFactory().createLiteral("blah blah blah");=20
constructs. The question is only if we should use the ValueFactory (as=20
above) or not and add those create... methods to the RDFContainer=20
interface, for example:

Literal literal =3D rdfContainer.createLiteral("blah blah blah");.

maybe this expansion of rdfContainer interface wouldn't be that bad=20
after all :-).

As Leo wrote in his email, I will continue with getValueFactory()...=20
approach. I wanted to make as little changes as possible. The=20
RDFContainer is the central interface of the entire framework. I didn't=20
want to add 12 createSomething.. methods to it without discussing it=20
with the executives first. I can do it at any moment if you change your=20
mind.

Antoni Mylka
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:antoni.mylka@dfki.un=
i-kl.de">antoni.mylka@dfki.uni-kl.de</a>


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job ea=
sier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim=
o
<a class=3D"moz-txt-link-freetext" href=3D"http://sel.as-us.falkag.net/se=
l?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D121642">http://sel.as-us.falk=
ag.net/sel?cmd=3Dlnk&amp;kid=3D120709&amp;bid=3D263057&amp;dat=3D121642</=
a>
_______________________________________________
Aperture-devel mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Aperture-devel@lists=
.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.sourceforge.net/=
lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listin=
fo/aperture-devel</a>

  </pre>
</blockquote>
<br>
<br>
<pre class=3D"moz-signature" cols=3D"72">--=20
____________________________________________________
DI Leo Sauermann       <a class=3D"moz-txt-link-freetext" href=3D"http://=
www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a>=20
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class=3D"moz-txt-link-abbreviated" href=3D=
"mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------010909000300070302030100--


--===============2093244961==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--===============2093244961==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============2093244961==--


From - Mon Oct 23 18:20:15 2006
X-Account-Key: account3
X-UIDL: 0000ed56037ab657
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:40409 "EHLO
	lists-outbound.sourceforge.net") by ps1.test.onet.pl with ESMTP
	id <S8510570AbWJWPZg>; Mon, 23 Oct 2006 17:25:36 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 05DF012A93; Mon, 23 Oct 2006 08:25:33 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gc1g8-0003Uw-RA for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 08:25:29 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gc1g4-0006XV-Mm
	for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 08:25:29 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9NFPEbe029857; Mon, 23 Oct 2006 17:25:14 +0200
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9NFPDM17310; Mon, 23 Oct 2006 17:25:13 +0200 (MEST)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9NFPBle018310; Mon, 23 Oct 2006 17:25:12 +0200 (CEST)
Message-ID: <453CDEA3.6020509@dfki.de>
Date:	Mon, 23 Oct 2006 17:24:19 +0200
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <45363700.7000006@aduna-software.com> <453C9048.2030307@dfki.de>
	<453CA63B.3060706@aduna-software.com>
In-Reply-To: <453CA63B.3060706@aduna-software.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] handling of symbolic links, redirections, etc.
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Es begab sich aber da Christiaan Fluit zur rechten Zeit 23.10.2006 13:23 
folgendes schrieb:
> Leo Sauermann wrote:
>> I would go for 2: 'Don't crawl symbolic links at all'
>>
>> and optionally switch to 1: follow symlinks.
>>
>> The problem only appears on UNIX systems, and people on these systems
>>  know what symlinks are, they make them intentionally, so it should
>> be ok. I am inspired there by ususal command line options on UNIX
>> tools, so for example RSYNC has this "follow symlinks" option, same
>> with RM I think, and TAR, etc. I would do the same with aperture.
>
> Sounds very reasonable. I'll create an issue for it in the bug tracker 
> and change the behaviour somewhere in the next weeks (have to finish 
> an AutoFocus beta release first, for which this is not a big issue).
>
> I'm still wondering whether this is something for the FileSystemCrawler
> or the FileAccessor to handle. It feels like a crawling property but 
> it can be more conveniently handled by the FileAccessor so that it 
> prevents the construction of the data object with all its metadata in 
> the first place. However, there is no mechanism to communicate this 
> back to the Crawler. Just returning "null" already has a specific 
> semantics, namely that the object has not been modified.
I wouldn't put it in accessor. If the configuration of the filesystem 
datasource is "follow symlinks or not", then it only influences the 
crawler, not the accessor.

>
> Furthermore, throwing DataObjects away in the Crawler without 
> reporting them first through one of the CrawlerHandler methods gives 
> me a Sesame warning for every DataObject as the temporary Repository 
> in its RDFContainer is not properly disposed of. RDFContainer has no 
> method for  disposing it and the CrawlerHandler never gets a signal 
> that the retrieved RDFContainer is thrown away. The same problem also 
> occurs in WebCrawler. Any ideas? Perhaps CrawlerHandler should be 
> extended with a method to "push back" unused RDFContainers? Or 
> RDFContainer should have a close/dispose method? It's not that much of 
> a big deal but now that we're revising that part of the API anyway, 
> this is a good time to discuss.
RDFContainer should have a close() method, thats what would be the right 
thing.
with the switch to RDF2go, this will be interesting anyway.


>
>> I don't know how the pathnames look like then, but I won't go for 4
>> where only the absolute names are given.
>
> Agreed.
>
> Guess today's an Aperture day for me :)
oh yeah, many e-mails

>
>
> Chris
> -- 


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 23 18:20:15 2006
X-Account-Key: account3
X-UIDL: 0000ed56037ab770
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from mailgate1.uni-kl.de ([131.246.120.5]:41362 "EHLO
	mailgate1.uni-kl.de") by ps8.test.onet.pl with ESMTP
	id <S4985758AbWJWP1c>; Mon, 23 Oct 2006 17:27:32 +0200
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de [131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id k9NFRALw031085;
	Mon, 23 Oct 2006 17:27:10 +0200
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id k9NFRAM17343;
	Mon, 23 Oct 2006 17:27:10 +0200 (MEST)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id k9NFR85K018392;
	Mon, 23 Oct 2006 17:27:08 +0200 (CEST)
Message-ID: <453CDF18.2010500@dfki.de>
Date:	Mon, 23 Oct 2006 17:26:16 +0200
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
CC:	=?UTF-8?B?QW50b25pIE15xYJrYQ==?= <antoni_mylka@poczta.onet.pl>,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Value Factory problem
References: <453BE7E7.6010804@poczta.onet.pl> <453CA0A7.4010300@aduna-software.com>
In-Reply-To: <453CA0A7.4010300@aduna-software.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: leo.sauermann@dfki.de
X-ZA0: unknown (-1,0)
Status:   

Es begab sich aber da Christiaan Fluit zur rechten Zeit 23.10.2006 12:59 
folgendes schrieb:
> Just an informative note: right now I use my own specialized 
> RDFContainer implementation in AutoFocus, tuned towards its specific 
> needs. In the new architecture that would probably be an 
> AutoFocus-specific org.ontoware.rdf2go.Model implementation, right? As 
> long as that remains possible without breaking anything, I'm quite 
> satisfied :)
>   
I would say so.

If we need to optimise the in-memory representation of RDF, packing a 
"simple as bread" RDF implementation underneath RDF2Go would be the way 
to go, that helps everyone in the community and motivates reuse.

Leo



>
> Chris
> --
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


From - Tue Oct 24 09:56:55 2006
X-Account-Key: account3
X-UIDL: 0000ed56037f4a80
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:27055 "EHLO
	lists-outbound.sourceforge.net") by ps19.test.onet.pl with ESMTP
	id <S8027379AbWJWKoj>; Mon, 23 Oct 2006 12:44:39 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 67D3D12BD6; Mon, 23 Oct 2006 03:44:24 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GbxI5-0007WP-7u for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 03:44:21 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GbxI3-0002ob-Rd
	for aperture-devel@lists.sourceforge.net;
	Mon, 23 Oct 2006 03:44:22 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9NAiDoI018729; Mon, 23 Oct 2006 12:44:13 +0200
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9NAiDM01609; Mon, 23 Oct 2006 12:44:13 +0200 (MEST)
Received: from [192.168.41.103] (gast-4113.kl.dfki.de [192.168.41.103])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9NAiCDx027857; Mon, 23 Oct 2006 12:44:12 +0200 (CEST)
Message-ID: <453C9CFD.4020809@dfki.uni-kl.de>
Date:	Mon, 23 Oct 2006 12:44:13 +0200
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <453A4B32.8030801@dfki.uni-kl.de>
	<453C97B3.3060900@aduna-software.com>
In-Reply-To: <453C97B3.3060900@aduna-software.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] New RDF2Go Branch
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Christiaan Fluit wrote:
> And how about using org.openrdf.model.URIs instead of java.net.URIs in 
> the RDF2Go APIs? 

They have introduced their own org.ontoware.rdf2go.model.node.URI class. 
This would solve the problem as far as interfaces are concerned. There 
is some room for discussion on the implementation side though. They use 
java.net.URI's internally to perform validation. This validation can be 
turned off, either by using the non-validating 
URIImpl.createURIWithoutChecking method or turning the log level to 
something above debug (curious solution as far as I'm concerned...)

public static URI create(String uriString) throws ModelException {
   if (log.isDebugEnabled()) {
     // check URI: applying strict and not 100% correct URI validation
     try {
       new java.net.URI(uriString);
     } catch (URISyntaxException e) {
       throw new ModelException(e);
     }
   }
   return new URIImpl(uriString);
}

Antoni Mylka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Tue Oct 24 11:38:54 2006
X-Account-Key: account3
X-UIDL: 0000ed56037fae30
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:51916 "EHLO
	lists-outbound.sourceforge.net") by ps28.test.onet.pl with ESMTP
	id <S2252317AbWJXJ1b>; Tue, 24 Oct 2006 11:27:31 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 4F29E12633; Tue, 24 Oct 2006 02:27:29 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GcIZB-0004BN-Tz for aperture-devel@lists.sourceforge.net;
	Tue, 24 Oct 2006 02:27:26 -0700
Received: from www4.aduna.biz ([66.98.176.99] helo=mail.aduna.biz)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GcIZB-00088A-M6
	for aperture-devel@lists.sourceforge.net;
	Tue, 24 Oct 2006 02:27:27 -0700
Received: (qmail 6341 invoked from network); 24 Oct 2006 11:27:19 +0200
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna.biz with (DHE-RSA-AES256-SHA encrypted) SMTP;
	24 Oct 2006 11:27:19 +0200
Message-ID: <453DDC73.7010204@aduna-software.com>
Date:	Tue, 24 Oct 2006 11:27:15 +0200
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <453DD823.5060009@dfki.uni-kl.de>
In-Reply-To: <453DD823.5060009@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Update Exception
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Antoni Mylka wrote:
> The RDFContainer methods throw UpdateException. This UpdateException 
> class is in the org.semanticdesktop.aperture.rdf.sesame package. I ask 
> for permission to move it to org.semanticdesktop.aperture.rdf. After all 
> it's a generic class thrown by all rdfcontainers regardless of their 
> implementation.

I actually was surprised to see that it wasn't already there, so I'm 
fine with this change.


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Tue Oct 24 15:54:14 2006
X-Account-Key: account3
X-UIDL: 0000ed560380525f
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:2197 "EHLO
	lists-outbound.sourceforge.net") by ps17.test.onet.pl with ESMTP
	id <S6081463AbWJXJJJ>; Tue, 24 Oct 2006 11:09:09 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 12377FC3F; Tue, 24 Oct 2006 02:09:00 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GcIHI-0002RJ-Sg for aperture-devel@lists.sourceforge.net;
	Tue, 24 Oct 2006 02:08:57 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GcIHI-0005BH-BA
	for aperture-devel@lists.sourceforge.net;
	Tue, 24 Oct 2006 02:08:57 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9O98psa023804 for <aperture-devel@lists.sourceforge.net>;
	Tue, 24 Oct 2006 11:08:53 +0200
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9O98pM04326 for <aperture-devel@lists.sourceforge.net>;
	Tue, 24 Oct 2006 11:08:51 +0200 (MEST)
Received: from [192.168.41.103] (gast-4113.kl.dfki.de [192.168.41.103])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9O98nbo008481 for <aperture-devel@lists.sourceforge.net>;
	Tue, 24 Oct 2006 11:08:50 +0200 (CEST)
Message-ID: <453DD823.5060009@dfki.uni-kl.de>
Date:	Tue, 24 Oct 2006 11:08:51 +0200
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Update Exception
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

The RDFContainer methods throw UpdateException. This UpdateException 
class is in the org.semanticdesktop.aperture.rdf.sesame package. I ask 
for permission to move it to org.semanticdesktop.aperture.rdf. After all 
it's a generic class thrown by all rdfcontainers regardless of their 
implementation.

I did this in my branch, but it seems that cvs doesn't handle deletions 
in branches too well. I deleted it from the branch, but it also 
disappeared in the main trunk. I readded it to the trunk and it 
reappeared in the branch... This solution would solve the problem once 
and for all... Or maybe I'm missing something.

Antoni Mylka
Antoni.Mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Oct 26 15:59:50 2006
X-Account-Key: account3
X-UIDL: 0000ed560387c204
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:6802 "EHLO
	lists-outbound.sourceforge.net") by ps18.test.onet.pl with ESMTP
	id <S5852106AbWJZKK6>; Thu, 26 Oct 2006 12:10:58 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id D00E513966; Thu, 26 Oct 2006 03:10:56 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gd2CG-0003uz-SU for aperture-devel@lists.sourceforge.net;
	Thu, 26 Oct 2006 03:10:49 -0700
Received: from www4.aduna.biz ([66.98.176.99] helo=www4.aduna-software.com)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gd2CG-0006YJ-Km
	for aperture-devel@lists.sourceforge.net;
	Thu, 26 Oct 2006 03:10:49 -0700
Received: (qmail 26538 invoked from network); 26 Oct 2006 12:10:40 +0200
Received: from 5353a894.cable.casema.nl (HELO ?83.83.168.148?) (83.83.168.148)
	by www4.aduna.biz with (DHE-RSA-AES256-SHA encrypted) SMTP;
	26 Oct 2006 12:10:40 +0200
Message-ID: <4540899E.8090001@aduna-software.com>
Date:	Thu, 26 Oct 2006 12:10:38 +0200
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <4539178E.5050703@dfki.uni-kl.de>
	<453C8CB8.2080007@aduna-software.com>
In-Reply-To: <453C8CB8.2080007@aduna-software.com>
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	1.0 FORGED_RCVD_HELO       Received: contains a forged HELO
Subject: Re: [Aperture-devel] Report
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Hi Antoni,

Christiaan Fluit wrote:
> First of all, the FileReader created by IcalCrawler.crawlIcalFile is not 
> closed. [...] BTW: shouldn't crawlCalendar be invoked within the try block? Now you 
> risk invoking it when creation of the FileReader has failed. 

I see that you added closing of the FileReader but that CrawlCalender is 
still invoked outside the try clause, which will definitely lead to 
NullPointerExceptions when the reader cannot be opened.

I don't mind fixing this myself but I don't like changing other peoples 
code without notice, especially when that code is still under active 
development. The same applies to the unit tests, which still fail for 
me. Just say so when you don't mind me changing them, I can fix those 
unit tests in 5 mins.

> Finally, note that you can use IOUtil.writeStream(InputStream, File), 
> which you can use to simply your createTempFile method.

Don't know what I was drinking when I wrote this but I meant that you 
can use IOUtil.writeStream to simplify createTempFile :)


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Oct 26 15:59:50 2006
X-Account-Key: account3
X-UIDL: 0000ed560387ef71
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:49052 "EHLO
	lists-outbound.sourceforge.net") by ps8.test.onet.pl with ESMTP
	id <S4876395AbWJZL2i>; Thu, 26 Oct 2006 13:28:38 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id CCF5113323; Thu, 26 Oct 2006 04:28:29 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gd3PO-0002gy-Ht for aperture-devel@lists.sourceforge.net;
	Thu, 26 Oct 2006 04:28:26 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gd3PP-0003nx-3c
	for aperture-devel@lists.sourceforge.net;
	Thu, 26 Oct 2006 04:28:27 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9QBSC6h015003; Thu, 26 Oct 2006 13:28:12 +0200
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9QBSBM03613; Thu, 26 Oct 2006 13:28:11 +0200 (MEST)
Received: from [192.168.31.133] (pc-3113 [192.168.31.133])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9QBS9rO018924; Thu, 26 Oct 2006 13:28:09 +0200 (CEST)
Message-ID: <45409C45.9040508@dfki.de>
Date:	Thu, 26 Oct 2006 13:30:13 +0200
From:	Gunnar Aastrand Grimnes <gunnar.grimnes@dfki.de>
User-Agent: Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version: 1.0
To:	Gunnar Aastrand Grimnes <gunnar.grimnes@dfki.de>
References: <454097E3.2060806@dfki.de>
In-Reply-To: <454097E3.2060806@dfki.de>
X-Enigmail-Version: 0.94.0.0
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	kirchmann@dfki.uni-kl.de,
	Aperture Developers <aperture-devel@lists.sourceforge.net>,
	reuschling@dfki.uni-kl.de
Subject: Re: [Aperture-devel] IMAP crawler braks on MH type folders
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

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

Update - i checked this - and the incorrect values are actually from JavaMail,
so it's not aperture's fault.

I will contact the JavaMail people...

- - Gunnar

Gunnar Aastrand Grimnes wrote:
> We just came across an interesting problem with the aperture ImapCrawler.
> 
> Some people here have MH type IMAP folders, meaning that instead of:
> 
> ~user/Mail/Mailinglists/Protege
> 
> being one looong file with all the emails concatenated, we have
> 
> ~user/Mail/Mailinglists/Protege/ as a folder and
> ~user/Mail/Mailinglists/Protege/1
> ~user/Mail/Mailinglists/Protege/2
> ~user/Mail/Mailinglists/Protege/3
> ....
> 
> for the emails... this breaks the imap crawler good and proper. Attached is a
> single email from this folder, and the RDF generated from it... not how the
> sender, subject, etc. are all wrong.
> 
> Has anyone seen anything like this?
> 
> I will try to investigate whether it's the JavaMail api that gives us broken
> values, or whether we are broken ourselves. This might not happen till next week
> though.
> 
- --
Gunnar Aastrand Grimnes
gunnar.grimnes [AT] dfki.de

DFKI GmbH
Knowledge Management
Erwin-Schroedinger-Strasse
D-67663 Kaiserslautern
Germany

Office: +49 631 205 3438
Mobile: +49 177 277 4397


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFQJxFfD15aMgAOfcRAjCMAJ99Pgre6HhgMDEaoag6QgQpQMLJNQCfZpiR
e396ru1yhA3BAnzwrTC45KE=
=Ix/k
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Oct 26 15:59:51 2006
X-Account-Key: account3
X-UIDL: 0000ed5603881b7d
X-Mozilla-Status: 0001
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:3040 "EHLO
	lists-outbound.sourceforge.net") by ps20.test.onet.pl with ESMTP
	id <S4916749AbWJZLxS>; Thu, 26 Oct 2006 13:53:18 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 86A11FEA8; Thu, 26 Oct 2006 04:22:03 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gd3J9-00023p-O5 for aperture-devel@lists.sourceforge.net;
	Thu, 26 Oct 2006 04:22:00 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gd3J8-0006lQ-1k
	for aperture-devel@lists.sourceforge.net;
	Thu, 26 Oct 2006 04:22:00 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9QBLe0E009814 for <aperture-devel@lists.sourceforge.net>;
	Thu, 26 Oct 2006 13:21:40 +0200
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9QB9SM02603; Thu, 26 Oct 2006 13:09:28 +0200 (MEST)
Received: from [192.168.31.133] (pc-3113 [192.168.31.133])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9QB9QbI018058; Thu, 26 Oct 2006 13:09:26 +0200 (CEST)
Message-ID: <454097E3.2060806@dfki.de>
Date:	Thu, 26 Oct 2006 13:11:31 +0200
From:	Gunnar Aastrand Grimnes <gunnar.grimnes@dfki.de>
User-Agent: Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed; boundary="------------020000090503020404030105"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	kirchmann@dfki.uni-kl.de, reuschling@dfki.uni-kl.de
Subject: [Aperture-devel] IMAP crawler braks on MH type folders
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--------------020000090503020404030105
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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

We just came across an interesting problem with the aperture ImapCrawler.

Some people here have MH type IMAP folders, meaning that instead of:

~user/Mail/Mailinglists/Protege

being one looong file with all the emails concatenated, we have

~user/Mail/Mailinglists/Protege/ as a folder and
~user/Mail/Mailinglists/Protege/1
~user/Mail/Mailinglists/Protege/2
~user/Mail/Mailinglists/Protege/3
....

for the emails... this breaks the imap crawler good and proper. Attached is a
single email from this folder, and the RDF generated from it... not how the
sender, subject, etc. are all wrong.

Has anyone seen anything like this?

I will try to investigate whether it's the JavaMail api that gives us broken
values, or whether we are broken ourselves. This might not happen till next week
though.

- --
Gunnar Aastrand Grimnes
gunnar.grimnes [AT] dfki.de

DFKI GmbH
Knowledge Management
Erwin-Schroedinger-Strasse
D-67663 Kaiserslautern
Germany

Office: +49 631 205 3438
Mobile: +49 177 277 4397


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFQJfifD15aMgAOfcRApdbAJ0SD7NZOO7fd0cWj2ji+tmjOIEd1gCg5iRB
bwIXCYl2lk8e9Evu9ryOASU=
=Rsiy
-----END PGP SIGNATURE-----

--------------020000090503020404030105
Content-Type: text/plain;
 name="email.n3"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="email.n3"


@prefix _3: <http://aperture.semanticdesktop.org/ontology/data#>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.

 <imap://reuschling@serv-3100/Mail%2fmisc%2fProtege%2f1/1> a _3:DataObject,
         _3:Email;
     _3:byteSize "2388"^^<http://www.w3.org/2001/XMLSchema#int>;
     _3:characterSet "iso-8859-1";
     _3:contentMimeType "text/plain";
     _3:date "2006-04-18T12:54:39"^^<http://www.w3.org/2001/XMLSchema#dateTime>;
     _3:from <email:reuschling@serv-3100.kl.dfki.de>;
     _3:mimeType "message/rfc822";
     _3:partOf <imap://reuschling@serv-3100/Mail%2fmisc%2fProtege%2f1;TYPE=LIST>;
     _3:subject "/home/reuschling/Mail/misc/Protege/1". 

 <email:reuschling@serv-3100.kl.dfki.de> a _3:Agent;
     _3:emailAddress "reuschling@serv-3100.kl.dfki.de". 

 <imap://reuschling@serv-3100/Mail%2fmisc%2fProtege%2f1;TYPE=LIST> a _3:DataObject,
         _3:FolderDataObject;
     _3:name "1";
     _3:partOf <imap://reuschling@serv-3100/Mail%2fmisc%2fProtege;TYPE=LIST>. 

 <imap://reuschling@serv-3100/Mail%2fmisc%2fProtege;TYPE=LIST> a _3:DataObject,
         _3:FolderDataObject;
     _3:name "Protege";
     _3:partOf <imap://reuschling@serv-3100/Mail%2fmisc;TYPE=LIST>;
     _3:rootFolderOf <urn:test:exampleimapsource>. 
--------------020000090503020404030105
Content-Type: text/plain;
 name="protegeemail.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="protegeemail.txt"

Delivery-Date: Tue, 18 Apr 2006 12:54:39 +0200
Received: from dfki-2203.dfki.uni-kl.de (gate-3114 [192.168.31.254])
	by serv-3100.kl.dfki.de (8.12.10+Sun/8.12.10) with ESMTP id k3IAsdha019623
	for <reuschling@serv-3100.kl.dfki.de>; Tue, 18 Apr 2006 12:54:39 +0200 (CEST)
Received: from mailgate2.uni-kl.de (isg-2202.kl.dfki.de [192.168.22.192])
	by dfki-2203.dfki.uni-kl.de (8.11.7p1+Sun/8.11.4) with ESMTP id k3IAsd322006
	for <reuschling@dfki.uni-kl.de>; Tue, 18 Apr 2006 12:54:40 +0200 (MEST)
Received: from smtp3.Stanford.EDU (smtp3.Stanford.EDU [171.67.16.138])
	by mailgate2.uni-kl.de (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id k3IAsaN8031423
	for <reuschling@dfki.uni-kl.de>; Tue, 18 Apr 2006 12:54:38 +0200
Received: from crg-gw.Stanford.EDU (crg-gw.Stanford.EDU [171.65.32.201])
	by smtp3.Stanford.EDU (8.12.11/8.12.11) with ESMTP id k3IAsZeG022625
	for <reuschling@dfki.uni-kl.de>; Tue, 18 Apr 2006 03:54:35 -0700
Received: (from web@localhost)
	by crg-gw.Stanford.EDU (8.11.5/8.11.5) id k3IAsZP05519;
	Tue, 18 Apr 2006 03:54:35 -0700 (PDT)
Date: Tue, 18 Apr 2006 03:54:35 -0700 (PDT)
From: Web Administrator <web@SMI.Stanford.EDU>
Message-Id: <200604181054.k3IAsZP05519@crg-gw.Stanford.EDU>
To: reuschling@dfki.uni-kl.de
Subject: Welcome to Protege!

Thank you for registering your copy of Protege. We would 
like to welcome you as a new member of the Protege user community and 
we hope that you find the tool useful and enjoy working with it.

If you have questions or comments about the tool, we encourage you to
post them to the protege-discussion mailing list. There is a large
community of users subscribed to this list and they may be able to
answer your questions. If your questions are about OWL or the
OWL plugin, then we ask you to post your questions to the protege-owl mailing list.

We also maintain a wiki page with a list of projects that used Protege.
http://protege.cim3.net/cgi-bin/wiki.pl?ProjectsThatUseProtege
If you use Protege in your project we would like for you to
add a wiki page containing a brief description of your project and
perhaps a link directly to your project's web site.

Thanks again.

The Protege Team

--------------020000090503020404030105
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--------------020000090503020404030105
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--------------020000090503020404030105--


From - Fri Oct 27 07:59:15 2006
X-Account-Key: account3
X-UIDL: 0000ed560389f046
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:58063 "EHLO
	lists-outbound.sourceforge.net") by ps9.test.onet.pl with ESMTP
	id <S5143902AbWJZSSI>; Thu, 26 Oct 2006 20:18:08 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 6F12E138A8; Thu, 26 Oct 2006 10:50:21 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gd9Mx-0007Bg-BP for aperture-devel@lists.sourceforge.net;
	Thu, 26 Oct 2006 10:50:19 -0700
Received: from brmea-mail-1.sun.com ([192.18.98.31])
	by mail.sourceforge.net with esmtp (Exim 4.44) id 1Gd9Mw-00079j-6R
	for aperture-devel@lists.sourceforge.net;
	Thu, 26 Oct 2006 10:50:20 -0700
Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k9QHncRL021394; Thu, 26 Oct 2006 11:49:39 -0600 (MDT)
Received: from nissan.sfbay.sun.com (vpn-129-150-12-251.SFBay.Sun.COM
	[129.150.12.251])
	by sfbaymail2sca.sfbay.sun.com (8.13.6+Sun/8.12.10/ENSMAIL,v2.2) with
	ESMTP id k9QHnYGN024748; Thu, 26 Oct 2006 10:49:34 -0700 (PDT)
Received: from [192.168.1.4] (dell [192.168.1.4])
	by nissan.sfbay.sun.com (8.13.7+Sun/8.13.7) with ESMTP id
	k9QHgcRW026395; Thu, 26 Oct 2006 10:42:38 -0700 (PDT)
Message-ID: <4540F606.7060300@sun.com>
Date:	Thu, 26 Oct 2006 10:53:10 -0700
From:	Bill Shannon <bill.shannon@sun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To:	Gunnar Aastrand Grimnes <gunnar.grimnes@dfki.de>
References: <45409E3B.2050109@dfki.de>
In-Reply-To: <45409E3B.2050109@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	javamail@sun.com,
	Aperture Developers <aperture-devel@lists.sourceforge.net>,
	reuschling@dfki.uni-kl.de, Heinz.Kirchmann@dfki.de
Subject: Re: [Aperture-devel] incorrect subject (and maybe other fields)
 when crawling MH types folders
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Gunnar Aastrand Grimnes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi JavaMail developers!,
> 
> I work on aperture, a framework for extracting RDF meta-data from "things" - one
> of these being IMAP mail servers, and we just came across a curious problem:
> 
> Some people here have MH type IMAP folders, meaning that instead of:
> 
> ~user/Mail/Mailinglists/Protege
> 
> being one looong file with all the emails concatenated, we have
> 
> ~user/Mail/Mailinglists/Protege/ as a folder and messages in separate files:
> ~user/Mail/Mailinglists/Protege/1
> ~user/Mail/Mailinglists/Protege/2
> ~user/Mail/Mailinglists/Protege/3
> ....
> 
> Crawling this folder and extracting the first message, the real subject is
> "Welcome to Protege!", but Message.getSubject() gives us back
> "/home/grimnes/Mail/test/Protege/1", i.e the path on disk to the mail file.
> 
> The sender is also incorrect.
> 
> We use JavaMail 1.4 and IMAP server is UW imapd 2004.352
> 
> Any ideas why this happens?

This is really more of a UW IMAP question, so you might want to ask that
mailing list.  Including the protocol trace from JavaMail would help
explain the problem.

I believe the problem is that UW IMAP expects files to be in mbox format.
What you're running into here is a "mailbox" in MH format.  In MH format,
a directory corresponds to a mailbox and a file corresponds to an
individual message.  If you open those files and treat them like mbox
format mailboxes, you're not going to get the view you expect.

UW IMAP does support MH format mailboxes, but I believe you have to use
a name such as #mh/Mailinglists/Protege.  I don't know how, or if, you
can access another user's MH-format mailboxes.  If you can't figure it
out from the UW IMAP docs, try the UW IMAP mailing list.

Hope that helps.


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Fri Oct 27 09:49:14 2006
X-Account-Key: account3
X-UIDL: 0000ed56038a78e6
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:7342 "EHLO
	lists-outbound.sourceforge.net") by ps25.test.onet.pl with ESMTP
	id <S5308795AbWJZLgt>; Thu, 26 Oct 2006 13:36:49 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id B8266EC19; Thu, 26 Oct 2006 04:36:41 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gd3XL-0003OK-Aq for aperture-devel@lists.sourceforge.net;
	Thu, 26 Oct 2006 04:36:39 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gd3XI-00037c-2r
	for aperture-devel@lists.sourceforge.net;
	Thu, 26 Oct 2006 04:36:37 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9QBaWeg021072; Thu, 26 Oct 2006 13:36:32 +0200
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9QBaWM04041; Thu, 26 Oct 2006 13:36:32 +0200 (MEST)
Received: from [192.168.31.133] (pc-3113 [192.168.31.133])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9QBaUxp019286; Thu, 26 Oct 2006 13:36:30 +0200 (CEST)
Message-ID: <45409E3B.2050109@dfki.de>
Date:	Thu, 26 Oct 2006 13:38:35 +0200
From:	Gunnar Aastrand Grimnes <gunnar.grimnes@dfki.de>
User-Agent: Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version: 1.0
To:	javamail@sun.com
X-Enigmail-Version: 0.94.0.0
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>,
	reuschling@dfki.uni-kl.de, Heinz.Kirchmann@dfki.de
Subject: [Aperture-devel] incorrect subject (and maybe other fields) when
 crawling MH types folders
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

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

Hi JavaMail developers!,

I work on aperture, a framework for extracting RDF meta-data from "things" - one
of these being IMAP mail servers, and we just came across a curious problem:

Some people here have MH type IMAP folders, meaning that instead of:

~user/Mail/Mailinglists/Protege

being one looong file with all the emails concatenated, we have

~user/Mail/Mailinglists/Protege/ as a folder and messages in separate files:
~user/Mail/Mailinglists/Protege/1
~user/Mail/Mailinglists/Protege/2
~user/Mail/Mailinglists/Protege/3
....

Crawling this folder and extracting the first message, the real subject is
"Welcome to Protege!", but Message.getSubject() gives us back
"/home/grimnes/Mail/test/Protege/1", i.e the path on disk to the mail file.

The sender is also incorrect.

We use JavaMail 1.4 and IMAP server is UW imapd 2004.352

Any ideas why this happens?

Any help is appreciated!

Thanks,
- --
Gunnar Aastrand Grimnes
gunnar.grimnes [AT] dfki.de

DFKI GmbH
Knowledge Management
Erwin-Schroedinger-Strasse
D-67663 Kaiserslautern
Germany

Office: +49 631 205 3438
Mobile: +49 177 277 4397


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFQJ46fD15aMgAOfcRAvZ9AKC+DkvHt3d3jefrsSD/CSFCCevtWgCeOUPa
4vXiU9gwQNd/nze/1QtwNCk=
=LlSd
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Fri Oct 27 16:09:49 2006
X-Account-Key: account3
X-UIDL: 0000ed56038b2de7
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:62116 "EHLO
	lists-outbound.sourceforge.net") by ps27.test.onet.pl with ESMTP
	id <S4874969AbWJ0Lgn>; Fri, 27 Oct 2006 13:36:43 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 276C71249B; Fri, 27 Oct 2006 01:17:08 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GdMtl-0005fr-R9 for aperture-devel@lists.sourceforge.net;
	Fri, 27 Oct 2006 01:17:05 -0700
Received: from uranus.svr3-speedyservers.com ([193.189.74.29])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GdMtl-0004lr-BZ
	for aperture-devel@lists.sourceforge.net;
	Fri, 27 Oct 2006 01:17:06 -0700
Received: from p54a69bbc.dip0.t-ipconnect.de ([84.166.155.188]
	helo=[192.168.178.20])
	by uranus.svr3-speedyservers.com with esmtpa (Exim 4.52)
	id 1GdMtd-0003Nz-5r; Fri, 27 Oct 2006 09:16:57 +0100
Message-ID: <4541CF3A.6060405@dfki.de>
Date:	Fri, 27 Oct 2006 10:19:54 +0100
From:	Gunnar AAstrand Grimnes <gunnar.grimnes@dfki.de>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To:	Bill Shannon <bill.shannon@sun.com>
References: <45409E3B.2050109@dfki.de> <4540F606.7060300@sun.com>
In-Reply-To: <4540F606.7060300@sun.com>
X-Enigmail-Version: 0.94.0.0
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - uranus.svr3-speedyservers.com
X-AntiAbuse: Original Domain - lists.sourceforge.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dfki.de
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	javamail@sun.com,
	Aperture Developers <aperture-devel@lists.sourceforge.net>,
	reuschling@dfki.uni-kl.de, Heinz.Kirchmann@dfki.de
Subject: Re: [Aperture-devel] incorrect subject (and maybe other fields)
 when crawling MH types folders
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

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

Excellent! We've tested it, and specifying #mh/Mailinglists/Protege as
the folder makes it behave as expected.

I wonder if there is any way to detect this, and not expect the end-user
to know, hmm...

Thanks for a quick and helpful response Bill!

- - Gunnar


Bill Shannon wrote:
> Gunnar Aastrand Grimnes wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi JavaMail developers!,
>>
>> I work on aperture, a framework for extracting RDF meta-data from "things" - one
>> of these being IMAP mail servers, and we just came across a curious problem:
>>
>> Some people here have MH type IMAP folders, meaning that instead of:
>>
>> ~user/Mail/Mailinglists/Protege
>>
>> being one looong file with all the emails concatenated, we have
>>
>> ~user/Mail/Mailinglists/Protege/ as a folder and messages in separate files:
>> ~user/Mail/Mailinglists/Protege/1
>> ~user/Mail/Mailinglists/Protege/2
>> ~user/Mail/Mailinglists/Protege/3
>> ....
>>
>> Crawling this folder and extracting the first message, the real subject is
>> "Welcome to Protege!", but Message.getSubject() gives us back
>> "/home/grimnes/Mail/test/Protege/1", i.e the path on disk to the mail file.
>>
>> The sender is also incorrect.
>>
>> We use JavaMail 1.4 and IMAP server is UW imapd 2004.352
>>
>> Any ideas why this happens?
> 
> This is really more of a UW IMAP question, so you might want to ask that
> mailing list.  Including the protocol trace from JavaMail would help
> explain the problem.
> 
> I believe the problem is that UW IMAP expects files to be in mbox format.
> What you're running into here is a "mailbox" in MH format.  In MH format,
> a directory corresponds to a mailbox and a file corresponds to an
> individual message.  If you open those files and treat them like mbox
> format mailboxes, you're not going to get the view you expect.
> 
> UW IMAP does support MH format mailboxes, but I believe you have to use
> a name such as #mh/Mailinglists/Protege.  I don't know how, or if, you
> can access another user's MH-format mailboxes.  If you can't figure it
> out from the UW IMAP docs, try the UW IMAP mailing list.
> 
> Hope that helps.
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFQc86fD15aMgAOfcRAvjzAJ0b/w8aLbWiWzYLORx/vsHz7PCpUwCfT/y/
kkBRAF5txqEMmxPPOCEFAQM=
=5yi4
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Sat Oct 28 11:25:25 2006
X-Account-Key: account3
X-UIDL: 0000ed56038bd7a7
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:23013 "EHLO
	lists-outbound.sourceforge.net") by ps25.test.onet.pl with ESMTP
	id <S4881209AbWJ0RSL>; Fri, 27 Oct 2006 19:18:11 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 2947E13A7D; Fri, 27 Oct 2006 10:18:08 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GdVLI-0001kA-U6 for aperture-devel@lists.sourceforge.net;
	Fri, 27 Oct 2006 10:18:04 -0700
Received: from uranus.svr3-speedyservers.com ([193.189.74.29])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GdVLI-0005E7-4q
	for aperture-devel@lists.sourceforge.net;
	Fri, 27 Oct 2006 10:18:06 -0700
Received: from p54a69bbc.dip0.t-ipconnect.de ([84.166.155.188]
	helo=[192.168.178.20])
	by uranus.svr3-speedyservers.com with esmtpa (Exim 4.52)
	id 1GdVLF-00068M-Mb; Fri, 27 Oct 2006 18:18:01 +0100
Message-ID: <45424E03.9040303@dfki.de>
Date:	Fri, 27 Oct 2006 19:20:51 +0100
From:	Gunnar AAstrand Grimnes <gunnar.grimnes@dfki.de>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
References: <45423D68.8040606@dfki.uni-kl.de>
In-Reply-To: <45423D68.8040606@dfki.uni-kl.de>
X-Enigmail-Version: 0.94.0.0
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - uranus.svr3-speedyservers.com
X-AntiAbuse: Original Domain - lists.sourceforge.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dfki.de
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Report - 27.10.2006
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

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

Well done!

 I can rewrite the appleaddressbook crawler to use rdf2go classes and
test it when I get back next friday.
To create the temp model the crawler would also need to get a
modelfactory somehow... hmm. Maybe this could be exposed in the
rdfcontainer interface?

- - Gunnar

Antoni Mylka wrote:
> So, more or less the first stage of migration seems to be nearing 
> completion. Here is a short summary of what has been done, what remains 
> to be done and what issues arose in the process..
> 
> -----------------------------------------------------------------------------
> 
> Translation issues:
> 
> RDFContainer
> 
> changed the interfaces to their RDF2Go Equivalents
> getModel returns an RDFModel, not a generic Object
> getValueFactory returns a ValueFactory
> 
> Creation of values and statements
> 
> There are three ways to create values (URIS, Literals, BlankNodes and 
> Statements)
> * using the model interface directly
> * using a value factory
> * using ModelUtil static methods (which are exactly the same as those in the
>    valueFactory, but accept a model as their first argument).
> 
> The rest is more of a mechanical process.
> * changing imports
> * changing new URIImpl into URIImpl.createURIWithoutChecking
> * changing new LiteralImpl into ModelUtil.createLiteral, or
>    rdfContainer.getValueFactory().createLiteral
> 
> 
> -----------------------------------------------------------------------------
> 
> Implementation independence issues:
> 
> There are three goals I tried to pursue.
> 
> 1. Core aperture should depend only on rdf2go.jar (that is
> no class from the core aperture should use any concrete model 
> implementation, since that
> would introduce a dependency on that particular implementation).
> 
> 2. The tests may depend on ModelSesameImpl (but not on org.openrdf ... 
> classes)
> 
> 3. From the concrete Node implementations only URIImpl can be used 
> directly in aperture code. It is impossible to prevent it, since it 
> causes chicken-and-egg type problems e.g. with constructing 
> rdfContainers. All other values are to be created with the aid of a 
> model instance (either directly or through a valuefactory or through a 
> ModelUtil).
> 
> This is broken in:
> 
> The AppleAddressBookCrawler. It uses a temporary model. Invokes a
> createSimpleModel() method. That uses ModelImplSesame Originally it was 
> in RepositoryUtil class. I moved it to the AppleAddressBookCrawler for
> the dependency issues to be better visible.
> 
> The RDF2GoRDFContainer itself. If the user doesn't provide a model - it 
> creates a default ModelImplSesame model. I did some searching around the 
> code. The only place within core architecture classes those constructors 
> are used is the RDF2GoRDFContainer factory. The factory itself is used 
> in other parts of the code but no class creates it. If removing this 
> dependency is a concern, I would suggest a following solution.
> 
> 1. Have RDF2GoRDFContainer accept a Model from outside. Don't provide 
> any default implementation.
> 
> 2. Ask Benjamin to create a ModelImplSesameFactory. (I'm actually 
> surprised it isn't there).
> 
> 3. Create a constructor for RDF2GoRDFContainerFactory that accepts an 
> instance of the ModelFactory interface. (it is possible since as I said 
> no aperture class creates instances of RDFContainerFactory, and the 
> DEFAULT_FACTORY static field is never used in aperture).
> 
> 4. Use the ModelFactory in newInstance and  and getRDFContainer
> 
> 5. Remove the DEFAULT_FACTORY field.
> 
> This might break applications that use aperture. It's hard for me to 
> estimate what would be the costs of such a change.
> (every RDFContainerFactory creation would need an
> instance of ModelFactory, DEFAULT_FACTORY couldn't be used).
> 
> -----------------------------------------------------------------------------
> 
> URI Validation
> 
> Leo is right that a malformed URI is usually an indication of a bug on 
> our side that should be found and removed. Nevertheless if a Schema for 
> some input file format states that some elements from the input should 
> be represented as URIs in the RDF output - we should be prepared for 
> situations where an input file can contain arbitrary strings that should 
> be interpreted as 'URIS' The solution to ignore DataObjects with faulty 
> URIs is simple and clear, It cannot be implemented with java.net.URI, 
> since a simple string without spaces is accepted. I do insist that we 
> need a general way to validate URI's from the input... a checkURI method 
> in the Model interface would be sufficient. It has been proposed
> on the RDF2Go devel list independetly by me, and by Mr. Richard Cyganiak.
> 
> In reply to this discussion Max Volkel changed a single comment in the 
> Model interface, from
> 
> /** @return a new URI from the given String */
> 
> to
> 
> /** The model must create URIs it would accept itself.
>      @return a new URI from the given String */
> 
> This is clearly NOT a solution, because in current implementation the
> validation is to be employed when a log level is high enough. We can't
> build an application that will be robust only if debug log level is 
> enabled...
> 
> -------------------------------------------------------------------------------
> 
> Other issues:
> 
> ...outlook.OutlookResource
> 
> Contains references to the ICAL ontology. May I switch it to ICALTZD 
> ontology?
> 
> Untestable classes...
> 
> ...outlook.TestOutlookCrawlAll
> ...outlook.TestOutlookCrawler
> ...addressbook.AppleAddressbookCrawlerTest
> 
> Couldn't test it since I don't have Outlook and Apple Addressbook...
> 
> -----------------------------------------------------------------------------
> 
> Obsolete classes - had to be rewritten...
> 
> RepositoryAccessData - replaced by ModelAccessData
> 
> Since rdf2go doesn't support contexts directly it would be up to the 
> user of ModelAccessData, to provide a model implementation that would 
> use an appropriate context (if necessary)
> 
> SesameRDFContainer - replaced by RDF2GoRDFContainer
> SesameRDFContainerFactory - replaced by RDF2GoRDFContainerFactory
> 
> RepositoryUtil - methods from this class have been included in ModelUtil
> 
> I have also rewritten the ConfigurationUtil.get/set domain boundaries 
> and the VocabularyWriter, so they don't use SERQL queries anymore.
> 
> -----------------------------------------------------------------------------
> RDF2Go Bugs...
> 
> Something's wrong with the reading part... I have sent an email to the 
> RDF2Go devel
> mailing list. This exception occurs in the VocabularyWriter and in 
> ThunderbirdCrawlerTest
> 
> The ModelImplSesame constructor was wrong...
> 
> There are deadlocks...
> 
> There seems to be no implementation of ModelSet in the Sesame2 driver. 
> Or maybe I don't understand how to use it... I couldn't find any 
> documentation for the ModelFactory.getModelSet(Properties p). What 
> properties could go there?
> 
> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFQk4DfD15aMgAOfcRAgECAKDhnYZ7laSbuqS/UzWf0/Z307vmRQCg4r9G
2otqsGuuAziRFuf0fxY/j5w=
=fB8+
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Sat Oct 28 11:25:28 2006
X-Account-Key: account3
X-UIDL: 0000ed56038c9910
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:45524 "EHLO
	lists-outbound.sourceforge.net") by ps27.test.onet.pl with ESMTP
	id <S5113921AbWJ0RKc>; Fri, 27 Oct 2006 19:10:32 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 3770212120; Fri, 27 Oct 2006 10:10:27 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GdVDr-0000zm-Om for aperture-devel@lists.sourceforge.net;
	Fri, 27 Oct 2006 10:10:24 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GdVDm-0001Wy-5v
	for aperture-devel@lists.sourceforge.net;
	Fri, 27 Oct 2006 10:10:23 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9RH9wqA026326 for <aperture-devel@lists.sourceforge.net>;
	Fri, 27 Oct 2006 19:10:04 +0200
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9RH9wM04762 for <aperture-devel@lists.sourceforge.net>;
	Fri, 27 Oct 2006 19:09:58 +0200 (MEST)
Received: from [192.168.41.101] (gast-4111.kl.dfki.de [192.168.41.101])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9RH9vLh003513 for <aperture-devel@lists.sourceforge.net>;
	Fri, 27 Oct 2006 19:09:57 +0200 (CEST)
Message-ID: <45423D68.8040606@dfki.uni-kl.de>
Date:	Fri, 27 Oct 2006 19:10:00 +0200
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Report - 27.10.2006
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

So, more or less the first stage of migration seems to be nearing 
completion. Here is a short summary of what has been done, what remains 
to be done and what issues arose in the process..

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

Translation issues:

RDFContainer

changed the interfaces to their RDF2Go Equivalents
getModel returns an RDFModel, not a generic Object
getValueFactory returns a ValueFactory

Creation of values and statements

There are three ways to create values (URIS, Literals, BlankNodes and 
Statements)
* using the model interface directly
* using a value factory
* using ModelUtil static methods (which are exactly the same as those in the
   valueFactory, but accept a model as their first argument).

The rest is more of a mechanical process.
* changing imports
* changing new URIImpl into URIImpl.createURIWithoutChecking
* changing new LiteralImpl into ModelUtil.createLiteral, or
   rdfContainer.getValueFactory().createLiteral


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

Implementation independence issues:

There are three goals I tried to pursue.

1. Core aperture should depend only on rdf2go.jar (that is
no class from the core aperture should use any concrete model 
implementation, since that
would introduce a dependency on that particular implementation).

2. The tests may depend on ModelSesameImpl (but not on org.openrdf ... 
classes)

3. From the concrete Node implementations only URIImpl can be used 
directly in aperture code. It is impossible to prevent it, since it 
causes chicken-and-egg type problems e.g. with constructing 
rdfContainers. All other values are to be created with the aid of a 
model instance (either directly or through a valuefactory or through a 
ModelUtil).

This is broken in:

The AppleAddressBookCrawler. It uses a temporary model. Invokes a
createSimpleModel() method. That uses ModelImplSesame Originally it was 
in RepositoryUtil class. I moved it to the AppleAddressBookCrawler for
the dependency issues to be better visible.

The RDF2GoRDFContainer itself. If the user doesn't provide a model - it 
creates a default ModelImplSesame model. I did some searching around the 
code. The only place within core architecture classes those constructors 
are used is the RDF2GoRDFContainer factory. The factory itself is used 
in other parts of the code but no class creates it. If removing this 
dependency is a concern, I would suggest a following solution.

1. Have RDF2GoRDFContainer accept a Model from outside. Don't provide 
any default implementation.

2. Ask Benjamin to create a ModelImplSesameFactory. (I'm actually 
surprised it isn't there).

3. Create a constructor for RDF2GoRDFContainerFactory that accepts an 
instance of the ModelFactory interface. (it is possible since as I said 
no aperture class creates instances of RDFContainerFactory, and the 
DEFAULT_FACTORY static field is never used in aperture).

4. Use the ModelFactory in newInstance and  and getRDFContainer

5. Remove the DEFAULT_FACTORY field.

This might break applications that use aperture. It's hard for me to 
estimate what would be the costs of such a change.
(every RDFContainerFactory creation would need an
instance of ModelFactory, DEFAULT_FACTORY couldn't be used).

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

URI Validation

Leo is right that a malformed URI is usually an indication of a bug on 
our side that should be found and removed. Nevertheless if a Schema for 
some input file format states that some elements from the input should 
be represented as URIs in the RDF output - we should be prepared for 
situations where an input file can contain arbitrary strings that should 
be interpreted as 'URIS' The solution to ignore DataObjects with faulty 
URIs is simple and clear, It cannot be implemented with java.net.URI, 
since a simple string without spaces is accepted. I do insist that we 
need a general way to validate URI's from the input... a checkURI method 
in the Model interface would be sufficient. It has been proposed
on the RDF2Go devel list independetly by me, and by Mr. Richard Cyganiak.

In reply to this discussion Max Volkel changed a single comment in the 
Model interface, from

/** @return a new URI from the given String */

to

/** The model must create URIs it would accept itself.
     @return a new URI from the given String */

This is clearly NOT a solution, because in current implementation the
validation is to be employed when a log level is high enough. We can't
build an application that will be robust only if debug log level is 
enabled...

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

Other issues:

...outlook.OutlookResource

Contains references to the ICAL ontology. May I switch it to ICALTZD 
ontology?

Untestable classes...

...outlook.TestOutlookCrawlAll
...outlook.TestOutlookCrawler
...addressbook.AppleAddressbookCrawlerTest

Couldn't test it since I don't have Outlook and Apple Addressbook...

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

Obsolete classes - had to be rewritten...

RepositoryAccessData - replaced by ModelAccessData

Since rdf2go doesn't support contexts directly it would be up to the 
user of ModelAccessData, to provide a model implementation that would 
use an appropriate context (if necessary)

SesameRDFContainer - replaced by RDF2GoRDFContainer
SesameRDFContainerFactory - replaced by RDF2GoRDFContainerFactory

RepositoryUtil - methods from this class have been included in ModelUtil

I have also rewritten the ConfigurationUtil.get/set domain boundaries 
and the VocabularyWriter, so they don't use SERQL queries anymore.

-----------------------------------------------------------------------------
RDF2Go Bugs...

Something's wrong with the reading part... I have sent an email to the 
RDF2Go devel
mailing list. This exception occurs in the VocabularyWriter and in 
ThunderbirdCrawlerTest

The ModelImplSesame constructor was wrong...

There are deadlocks...

There seems to be no implementation of ModelSet in the Sesame2 driver. 
Or maybe I don't understand how to use it... I couldn't find any 
documentation for the ModelFactory.getModelSet(Properties p). What 
properties could go there?

Antoni Mylka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Sat Oct 28 18:07:05 2006
X-Account-Key: account3
X-UIDL: 0000ed56038ecae3
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:12934 "EHLO
	lists-outbound.sourceforge.net") by ps16.test.onet.pl with ESMTP
	id <S1677462AbWJ1Nco>; Sat, 28 Oct 2006 15:32:44 +0200
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 1D2B1E07F; Sat, 28 Oct 2006 06:32:43 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GdoIi-0006YN-2l for aperture-devel@lists.sourceforge.net;
	Sat, 28 Oct 2006 06:32:40 -0700
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GdoIg-00033M-HS
	for aperture-devel@lists.sourceforge.net;
	Sat, 28 Oct 2006 06:32:41 -0700
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9SDWWNZ016345 for <aperture-devel@lists.sourceforge.net>;
	Sat, 28 Oct 2006 15:32:33 +0200
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9SDWWM29440 for <aperture-devel@lists.sourceforge.net>;
	Sat, 28 Oct 2006 15:32:32 +0200 (MEST)
Received: from [192.168.41.101] (gast-4111.kl.dfki.de [192.168.41.101])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9SDWVgR004693 for <aperture-devel@lists.sourceforge.net>;
	Sat, 28 Oct 2006 15:32:31 +0200 (CEST)
Message-ID: <45435BF3.8020003@dfki.uni-kl.de>
Date:	Sat, 28 Oct 2006 15:32:35 +0200
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] A commit to the RDF2GO branch
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

It seems that I forgot to make a commit yesterday. I did it now...
I also did some work on the classes from Example directory

The package org.sematicdesktop.aperture.examples.fileinspector has
been left as it is. It uses the LiteralClipper class, that implements
the RDFHandler interface. There is no equivalent in RDF2Go. That's
why i have a question:

Do we need to migrate this example to RDF2Go, (and think up some way
to implement the LiteralClipper functionality) or to leave it as it is,
with direct references to sesame and adjust it to changes in sesame
interface from the newest source?

All in all.
The TestAll test suite contains 136 tests now. The TestFileSystemCrawler 
halts in a deadlock. All other tests pass. (At least on my machine).
The examples don't seem to work for the time being... I'll fix it.

Antoni Mylka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 30 14:31:31 2006
X-Account-Key: account3
X-UIDL: 0000ed5603949ca3
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:50401 "EHLO
	lists-outbound.sourceforge.net") by ps8.test.onet.pl with ESMTP
	id <S4872526AbWJ3LNT>; Mon, 30 Oct 2006 12:13:19 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id EC196FC7E; Mon, 30 Oct 2006 02:45:11 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GeUdh-0003mK-0d for aperture-devel@lists.sourceforge.net;
	Mon, 30 Oct 2006 02:45:09 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GeUdZ-0004GL-Sz
	for aperture-devel@lists.sourceforge.net;
	Mon, 30 Oct 2006 02:45:04 -0800
Received: (qmail 29873 invoked from network); 30 Oct 2006 11:44:52 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	30 Oct 2006 11:44:52 +0100
Message-ID: <4545D7A1.9040502@aduna-software.com>
Date:	Mon, 30 Oct 2006 11:44:49 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45423D68.8040606@dfki.uni-kl.de>
In-Reply-To: <45423D68.8040606@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Report - 27.10.2006
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Antoni Mylka wrote:
> 1. Core aperture should depend only on rdf2go.jar
> 
> 2. The tests may depend on ModelSesameImpl (but not on org.openrdf ... 
> classes)
> 
> 3. From the concrete Node implementations only URIImpl can be used 
> directly in aperture code.

Sounds all good to me.

> The RDF2GoRDFContainer itself. If the user doesn't provide a model - it 
> creates a default ModelImplSesame model. I did some searching around the 
> code. The only place within core architecture classes those constructors 
> are used is the RDF2GoRDFContainer factory. The factory itself is used 
> in other parts of the code but no class creates it. If removing this 
> dependency is a concern, I would suggest a following solution.

We are not using this factory in Aduna code, I'm not sure about others.

The whole idea about all those factories and registries everywhere is to 
support a dynamic system based on e.g. OSGi where there are as little 
assumptions as possible about which implementation classes are used, in 
which order things are initialized and even make runtime changes to the 
setup possible.

As we still make little use of this architecture, perhaps remove it for 
now and introduce a better version as soon as we fully know/agree on 
what "better" means?

> 1. Have RDF2GoRDFContainer accept a Model from outside. Don't provide 
> any default implementation.
> 
> 2. Ask Benjamin to create a ModelImplSesameFactory. (I'm actually 
> surprised it isn't there).
> 
> 3. Create a constructor for RDF2GoRDFContainerFactory that accepts an 
> instance of the ModelFactory interface. (it is possible since as I said 
> no aperture class creates instances of RDFContainerFactory, and the 
> DEFAULT_FACTORY static field is never used in aperture).
> 
> 4. Use the ModelFactory in newInstance and  and getRDFContainer
> 
> 5. Remove the DEFAULT_FACTORY field.

The typical OSGi-like setup that we use is to let the factory (in this 
case the RDF2GORDFContainerFactory) have all configuration info stored 
in its attributes. It gets this info through set methods that are 
invoked by whoever creates these factories (static code, an OSGi 
BundleActivator, some configuration file setup mechanism, etc).

This way the invocation of the factory's get/createNew/whatever method 
is often parameterless. This ensures that future API changes have as few 
consequences as possible and that configuration code needed by a 
specific factory are only reflected by the set/get methods of that 
factory, not by the artifact-producing methods.

> Leo is right that a malformed URI is usually an indication of a bug on 
> our side that should be found and removed.

I'm comfortable with URI checking as long as it's optional. With this I 
don't mean that it should depend on a log level whether checks are done 
or not, but that the API should be constructed in such a way that a 
developer can choose whether to use a safe and sound approach or play it 
dirty. A method to explicitly check URIs is an example of such an 
approach, as is for example org.openrdf.model's approach where you can 
easily introduce your own URI implementation transparently, that does as 
much or as little checking as you want.

  > RepositoryAccessData - replaced by ModelAccessData
> 
> Since rdf2go doesn't support contexts directly it would be up to the 
> user of ModelAccessData, to provide a model implementation that would 
> use an appropriate context (if necessary)

Perhaps leave this class out altogether and reserve some time in the 
future to revisit the AccessData API altogether?

Given recent work on the crawler implementations I really had the 
feeling that we would benefit from being able to use RDF to store access 
data. Of course AccessData can also have a getModel method but I think 
we should consider whether we really need an AccessData on top of a
model or instead give it such a model directly. IMO AccessData does not 
provide an added value over an RDF Model in the way RDFContainer does.


All in all: good work!

Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 30 14:31:33 2006
X-Account-Key: account3
X-UIDL: 0000ed560394d7dc
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:28813 "EHLO
	lists-outbound.sourceforge.net") by ps6.test.onet.pl with ESMTP
	id <S6267033AbWJ3NHC>; Mon, 30 Oct 2006 14:07:02 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 5D1D5126E2; Mon, 30 Oct 2006 05:07:00 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GeWqu-00005h-4e for aperture-devel@lists.sourceforge.net;
	Mon, 30 Oct 2006 05:06:56 -0800
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GeWqs-0004Qs-I9
	for aperture-devel@lists.sourceforge.net;
	Mon, 30 Oct 2006 05:06:57 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9UD6g25024634 for <aperture-devel@lists.sourceforge.net>;
	Mon, 30 Oct 2006 14:06:42 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9UD6gM11803; Mon, 30 Oct 2006 14:06:42 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9UD6esU020536; Mon, 30 Oct 2006 14:06:40 +0100 (CET)
Message-ID: <4545F8D2.8070909@dfki.de>
Date:	Mon, 30 Oct 2006 14:06:26 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
References: <45435BF3.8020003@dfki.uni-kl.de>
In-Reply-To: <45435BF3.8020003@dfki.uni-kl.de>
X-Spam-Score: 3.9 (+++)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	3.9 URIBL_SC_SURBL Contains an URL listed in the SC SURBL blocklist
	[URIs: falkag.net]
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] A commit to the RDF2GO branch
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Es begab sich aber da Antoni Mylka zur rechten Zeit 28.10.2006 15:32 
folgendes schrieb:
> It seems that I forgot to make a commit yesterday. I did it now...
> I also did some work on the classes from Example directory
>
> The package org.sematicdesktop.aperture.examples.fileinspector has
> been left as it is. It uses the LiteralClipper class, that implements
> the RDFHandler interface. There is no equivalent in RDF2Go. That's
> why i have a question:
>
> Do we need to migrate this example to RDF2Go, (and think up some way
> to implement the LiteralClipper functionality) or to leave it as it is,
> with direct references to sesame and adjust it to changes in sesame
> interface from the newest source?
>
> All in all.
> The TestAll test suite contains 136 tests now. The TestFileSystemCrawler 
> halts in a deadlock. All other tests pass. (At least on my machine).
> The examples don't seem to work for the time being... I'll fix it.
>   

It would be good to have an example that is easy to show, something like 
the example window.
we have somewhere an example frame that shows a file selection dialog 
and then extracts all metadata from this peticular file.
That is needed to show developers how Aperture works!

also, another example would be great, again consisting of Swing window 
and some backend, that allows to create a lucene index.
This would require the Lucene jar, though, but we may consider adding it 
to the CVS for showing the capabilities.
(In a distribution, we could then remove these parts, making them optional)

I would love to make a distro this week, before ISWC :-)

is this possible?


> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 30 14:39:37 2006
X-Account-Key: account3
X-UIDL: 0000ed560394e8b2
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:37764 "EHLO
	lists-outbound.sourceforge.net") by ps21.test.onet.pl with ESMTP
	id <S6223094AbWJ3Ngi>; Mon, 30 Oct 2006 14:36:38 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id CB4C9FFC5; Mon, 30 Oct 2006 05:36:36 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GeXJZ-0002wq-Sx for aperture-devel@lists.sourceforge.net;
	Mon, 30 Oct 2006 05:36:34 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GeXJY-0005CJ-Hn
	for aperture-devel@lists.sourceforge.net;
	Mon, 30 Oct 2006 05:36:35 -0800
Received: (qmail 2218 invoked from network); 30 Oct 2006 14:36:23 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	30 Oct 2006 14:36:23 +0100
Message-ID: <4545FFD2.1060301@aduna-software.com>
Date:	Mon, 30 Oct 2006 14:36:18 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45435BF3.8020003@dfki.uni-kl.de> <4545F8D2.8070909@dfki.de>
In-Reply-To: <4545F8D2.8070909@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] A commit to the RDF2GO branch
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Leo Sauermann wrote:
> It would be good to have an example that is easy to show, something like 
> the example window.
> we have somewhere an example frame that shows a file selection dialog 
> and then extracts all metadata from this peticular file.
> That is needed to show developers how Aperture works!

Just launch 
org.semanticdesktop.aperture.examples.fileinspector.FileInspectorFrame. 
The distribution also contains fileinspector.bat/.sh scripts.

  > I would love to make a distro this week, before ISWC :-)
> 
> is this possible?

I don't see why not. I assume you want to base this on the current 
trunk, i.e. exclude the new rdf2go stuff for now, right? The only thing 
that needs to happen before a release is fixing the ICal unit tests. I 
can help you out here if necessary. Tasks such as Javadoc cleanup etc. 
are also nice but not show stoppers for an alpha release IMO.

BTW: I see some generics creeping into the AccessData API. Is this 
intentional? I thought the plan was to keep the APIs based on 1.4 for 
now? I'm fine with switching to 1.5 but just would like to get this 
straight.

I'm especially concerned because in my experience proper application of 
generics in APIs is often far from trivial. Using generics in 
implementations is often not that difficult; if it compiles and runs 
correctly, its usually ok. For APIs you need to think ahead much more 
and solutions that look perfectly fine at first later turn out to be 
incorrect.


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Oct 30 16:57:10 2006
X-Account-Key: account3
X-UIDL: 0000ed5603950352
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:46751 "EHLO
	lists-outbound.sourceforge.net") by ps3.test.onet.pl with ESMTP
	id <S3425498AbWJ3OW4>; Mon, 30 Oct 2006 15:22:56 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 18C3C12594; Mon, 30 Oct 2006 06:22:52 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GeY2I-0007Hw-RH for aperture-devel@lists.sourceforge.net;
	Mon, 30 Oct 2006 06:22:48 -0800
Received: from mailgate1.uni-kl.de ([131.246.120.5])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GeY2G-0001q4-LE
	for aperture-devel@lists.sourceforge.net;
	Mon, 30 Oct 2006 06:22:48 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	k9UEMEG7021221; Mon, 30 Oct 2006 15:22:15 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	k9UEM2M17042; Mon, 30 Oct 2006 15:22:02 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	k9UEM0ms025171; Mon, 30 Oct 2006 15:22:00 +0100 (CET)
Message-ID: <45460A7B.3080301@dfki.de>
Date:	Mon, 30 Oct 2006 15:21:47 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <45423D68.8040606@dfki.uni-kl.de>
	<4545D7A1.9040502@aduna-software.com>
In-Reply-To: <4545D7A1.9040502@aduna-software.com>
X-Spam-Score: 0.5 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.5 HTML_20_30             BODY: Message is 20% to 30% HTML
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Report - 27.10.2006
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0586212141=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============0586212141==
Content-Type: multipart/alternative;
	boundary="------------080903070900050204060302"

This is a multi-part message in MIME format.
--------------080903070900050204060302
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi guys

Es begab sich aber da Christiaan Fluit zur rechten Zeit 30.10.2006 11:44 
folgendes schrieb:
>> The RDF2GoRDFContainer itself. If the user doesn't provide a model - it 
>> creates a default ModelImplSesame model. I did some searching around the 
>> code. The only place within core architecture classes those constructors 
>> are used is the RDF2GoRDFContainer factory. The factory itself is used 
>> in other parts of the code but no class creates it. If removing this 
>> dependency is a concern, I would suggest a following solution.
>>     
>
> We are not using this factory in Aduna code, I'm not sure about others.
>
> The whole idea about all those factories and registries everywhere is to 
> support a dynamic system based on e.g. OSGi where there are as little 
> assumptions as possible about which implementation classes are used, in 
> which order things are initialized and even make runtime changes to the 
> setup possible.
>
> As we still make little use of this architecture, perhaps remove it for 
> now and introduce a better version as soon as we fully know/agree on 
> what "better" means?
>   
About the OSGI thing:

one of the next tasks on DFKI side will be to wrap Aperture into a 
Nepomuk interface for datawrappers,
and to bundle it as OSGI service using the Eclipse plugin concept, with 
Bundelactivators, etc.
There will also be a service then running, with configuration etc.

Anyone has experience how to handle configuration the "right way" in OSGI?

I am not concerned about the factories, but more on:
A) where to store config values (file, database, config file inside the 
bundle?)
B) how to change config values (through interface, is there a 
"configuration" bundle?)
C) how to make a gui that uses B to change A
D) how to make an activator that reads A, perhaps through B?
E) or is it all dependent on a "service" bundle, that wrapps another 
bundle and provides A,B,C,D for application environment X where it runs. 
For example, one for Nepomuk, one for Autofocus

greetings
Leo


>   
>> 1. Have RDF2GoRDFContainer accept a Model from outside. Don't provide 
>> any default implementation.
>>
>> 2. Ask Benjamin to create a ModelImplSesameFactory. (I'm actually 
>> surprised it isn't there).
>>
>> 3. Create a constructor for RDF2GoRDFContainerFactory that accepts an 
>> instance of the ModelFactory interface. (it is possible since as I said 
>> no aperture class creates instances of RDFContainerFactory, and the 
>> DEFAULT_FACTORY static field is never used in aperture).
>>
>> 4. Use the ModelFactory in newInstance and  and getRDFContainer
>>
>> 5. Remove the DEFAULT_FACTORY field.
>>     
>
> The typical OSGi-like setup that we use is to let the factory (in this 
> case the RDF2GORDFContainerFactory) have all configuration info stored 
> in its attributes. It gets this info through set methods that are 
> invoked by whoever creates these factories (static code, an OSGi 
> BundleActivator, some configuration file setup mechanism, etc).
>
> This way the invocation of the factory's get/createNew/whatever method 
> is often parameterless. This ensures that future API changes have as few 
> consequences as possible and that configuration code needed by a 
> specific factory are only reflected by the set/get methods of that 
> factory, not by the artifact-producing methods.
>
>   
>> Leo is right that a malformed URI is usually an indication of a bug on 
>> our side that should be found and removed.
>>     
>
> I'm comfortable with URI checking as long as it's optional. With this I 
> don't mean that it should depend on a log level whether checks are done 
> or not, but that the API should be constructed in such a way that a 
> developer can choose whether to use a safe and sound approach or play it 
> dirty. A method to explicitly check URIs is an example of such an 
> approach, as is for example org.openrdf.model's approach where you can 
> easily introduce your own URI implementation transparently, that does as 
> much or as little checking as you want.
>
>   > RepositoryAccessData - replaced by ModelAccessData
>   
>> Since rdf2go doesn't support contexts directly it would be up to the 
>> user of ModelAccessData, to provide a model implementation that would 
>> use an appropriate context (if necessary)
>>     
>
> Perhaps leave this class out altogether and reserve some time in the 
> future to revisit the AccessData API altogether?
>
> Given recent work on the crawler implementations I really had the 
> feeling that we would benefit from being able to use RDF to store access 
> data. Of course AccessData can also have a getModel method but I think 
> we should consider whether we really need an AccessData on top of a
> model or instead give it such a model directly. IMO AccessData does not 
> provide an added value over an RDF Model in the way RDFContainer does.
>
>
> All in all: good work!
>
> Chris
> --
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------080903070900050204060302
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi guys<br>
<br>
Es begab sich aber da Christiaan Fluit zur rechten Zeit 30.10.2006
11:44 folgendes schrieb:
<blockquote cite="mid4545D7A1.9040502@aduna-software.com" type="cite">
  <blockquote type="cite">
    <pre wrap="">The RDF2GoRDFContainer itself. If the user doesn't provide a model - it 
creates a default ModelImplSesame model. I did some searching around the 
code. The only place within core architecture classes those constructors 
are used is the RDF2GoRDFContainer factory. The factory itself is used 
in other parts of the code but no class creates it. If removing this 
dependency is a concern, I would suggest a following solution.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
We are not using this factory in Aduna code, I'm not sure about others.

The whole idea about all those factories and registries everywhere is to 
support a dynamic system based on e.g. OSGi where there are as little 
assumptions as possible about which implementation classes are used, in 
which order things are initialized and even make runtime changes to the 
setup possible.

As we still make little use of this architecture, perhaps remove it for 
now and introduce a better version as soon as we fully know/agree on 
what "better" means?
  </pre>
</blockquote>
About the OSGI thing:<br>
<br>
one of the next tasks on DFKI side will be to wrap Aperture into a
Nepomuk interface for datawrappers,<br>
and to bundle it as OSGI service using the Eclipse plugin concept, with
Bundelactivators, etc.<br>
There will also be a service then running, with configuration etc.<br>
<br>
Anyone has experience how to handle configuration the "right way" in
OSGI?<br>
<br>
I am not concerned about the factories, but more on:<br>
A) where to store config values (file, database, config file inside the
bundle?)<br>
B) how to change config values (through interface, is there a
"configuration" bundle?)<br>
C) how to make a gui that uses B to change A<br>
D) how to make an activator that reads A, perhaps through B?<br>
E) or is it all dependent on a "service" bundle, that wrapps another
bundle and provides A,B,C,D for application environment X where it
runs. For example, one for Nepomuk, one for Autofocus<br>
<br>
greetings<br>
Leo<br>
<br>
<br>
<blockquote cite="mid4545D7A1.9040502@aduna-software.com" type="cite">
  <pre wrap="">
  </pre>
  <blockquote type="cite">
    <pre wrap="">1. Have RDF2GoRDFContainer accept a Model from outside. Don't provide 
any default implementation.

2. Ask Benjamin to create a ModelImplSesameFactory. (I'm actually 
surprised it isn't there).

3. Create a constructor for RDF2GoRDFContainerFactory that accepts an 
instance of the ModelFactory interface. (it is possible since as I said 
no aperture class creates instances of RDFContainerFactory, and the 
DEFAULT_FACTORY static field is never used in aperture).

4. Use the ModelFactory in newInstance and  and getRDFContainer

5. Remove the DEFAULT_FACTORY field.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
The typical OSGi-like setup that we use is to let the factory (in this 
case the RDF2GORDFContainerFactory) have all configuration info stored 
in its attributes. It gets this info through set methods that are 
invoked by whoever creates these factories (static code, an OSGi 
BundleActivator, some configuration file setup mechanism, etc).

This way the invocation of the factory's get/createNew/whatever method 
is often parameterless. This ensures that future API changes have as few 
consequences as possible and that configuration code needed by a 
specific factory are only reflected by the set/get methods of that 
factory, not by the artifact-producing methods.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Leo is right that a malformed URI is usually an indication of a bug on 
our side that should be found and removed.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I'm comfortable with URI checking as long as it's optional. With this I 
don't mean that it should depend on a log level whether checks are done 
or not, but that the API should be constructed in such a way that a 
developer can choose whether to use a safe and sound approach or play it 
dirty. A method to explicitly check URIs is an example of such an 
approach, as is for example org.openrdf.model's approach where you can 
easily introduce your own URI implementation transparently, that does as 
much or as little checking as you want.

  &gt; RepositoryAccessData - replaced by ModelAccessData
  </pre>
  <blockquote type="cite">
    <pre wrap="">Since rdf2go doesn't support contexts directly it would be up to the 
user of ModelAccessData, to provide a model implementation that would 
use an appropriate context (if necessary)
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Perhaps leave this class out altogether and reserve some time in the 
future to revisit the AccessData API altogether?

Given recent work on the crawler implementations I really had the 
feeling that we would benefit from being able to use RDF to store access 
data. Of course AccessData can also have a getModel method but I think 
we should consider whether we really need an AccessData on top of a
model or instead give it such a model directly. IMO AccessData does not 
provide an added value over an RDF Model in the way RDFContainer does.


All in all: good work!

Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
<a class="moz-txt-link-freetext" href="http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642">http://sel.as-us.falkag.net/sel?cmd=lnk&amp;kid=120709&amp;bid=263057&amp;dat=121642</a>
_______________________________________________
Aperture-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aperture-devel@lists.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listinfo/aperture-devel</a>
  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
____________________________________________________
DI Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------080903070900050204060302--


--===============0586212141==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--===============0586212141==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============0586212141==--


From - Mon Oct 30 16:57:11 2006
X-Account-Key: account3
X-UIDL: 0000ed560395119a
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:22414 "EHLO
	lists-outbound.sourceforge.net") by ps24.test.onet.pl with ESMTP
	id <S4829758AbWJ3Oue>; Mon, 30 Oct 2006 15:50:34 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id DC3D4EC9C; Mon, 30 Oct 2006 06:50:00 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GeYSb-0001NF-Au for aperture-devel@lists.sourceforge.net;
	Mon, 30 Oct 2006 06:49:57 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GeYSX-0000u1-Vb
	for aperture-devel@lists.sourceforge.net;
	Mon, 30 Oct 2006 06:49:58 -0800
Received: (qmail 4504 invoked from network); 30 Oct 2006 15:49:35 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	30 Oct 2006 15:49:35 +0100
Message-ID: <454610FB.4040201@aduna-software.com>
Date:	Mon, 30 Oct 2006 15:49:31 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45423D68.8040606@dfki.uni-kl.de>	<4545D7A1.9040502@aduna-software.com>
	<45460A7B.3080301@dfki.de>
In-Reply-To: <45460A7B.3080301@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Report - 27.10.2006
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Leo Sauermann wrote:
> About the OSGI thing:
> 
> one of the next tasks on DFKI side will be to wrap Aperture into a 
> Nepomuk interface for datawrappers,
> and to bundle it as OSGI service using the Eclipse plugin concept, with 
> Bundelactivators, etc.
> There will also be a service then running, with configuration etc.
> 
> Anyone has experience how to handle configuration the "right way" in OSGI?

 From your words I get the impression that you think of Aperture as a 
single OSGi service, right?

I have no practical experience with OSGi yet (Herko does), I only know 
some theoretical bits. I've written documentation about it a while ago 
to explain the rationale for all these factories and registries in 
Aperture, see http://aperture.sourceforge.net/tutorial/architecture.html.

The idea is that every core functionality (e.g. extracting metadata, 
crawling a source or identifying a stream's MIME type) becomes a single 
service. A registry for that service keeps track of all available 
factories, each factory representing a single implementation of that 
servive. Each factory has as associated BundleActivator that registers 
the factory with the registry. Special dependency management code inside 
these BundleActivators guarantee that "things" are initialized in the 
correct order and with the correct information.

Each service implementation, factory and BundleActivator are packaged in 
a bundle. This is a jar file whose manifest has an entry identifying the 
BundleActivator.

What's left then is a mechanism for listing the available bundles. I 
believe this mechanism is dependent on the OSGi runtime that you use, 
e.g. Equinox, Knoplerfish, etc.

That's about my knowledge of OSGi.


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov  1 12:16:24 2006
X-Account-Key: account3
X-UIDL: 0000ed56039a98fa
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:64962 "EHLO
	lists-outbound.sourceforge.net") by ps7.test.onet.pl with ESMTP
	id <S3114027AbWKAEAT>; Wed, 1 Nov 2006 05:00:19 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id BBB7113311; Tue, 31 Oct 2006 20:00:17 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gf7Gw-0001oJ-8X for aperture-devel@lists.sourceforge.net;
	Tue, 31 Oct 2006 20:00:14 -0800
Received: from smtp1.rz.uni-karlsruhe.de ([129.13.185.217] ident=Debian-exim)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gf7Gu-0005rn-2W
	for aperture-devel@lists.sourceforge.net;
	Tue, 31 Oct 2006 20:00:15 -0800
Received: from ontoware.org (aifbontoware.aifb.uni-karlsruhe.de
	[172.22.131.111])
	by smtp1.rz.uni-karlsruhe.de with esmtp (Exim 4.50 #1)
	id 1Gf7Go-0007jI-M4; Wed, 01 Nov 2006 05:00:06 +0100
Received: from [127.0.0.1] (helo=aifbontoware.aifb.uni-karlsruhe.de)
	by ontoware.org with esmtp (Exim 4.63)
	(envelope-from <mailman-bounces@ontoware.org>) id 1Gf7Go-00042I-9m
	for aperture-devel@lists.sourceforge.net;
	Wed, 01 Nov 2006 05:00:06 +0100
MIME-Version: 1.0
From:	mailman-owner@ontoware.org
To:	aperture-devel@lists.sourceforge.net
X-No-Archive: yes
Message-ID: <mailman.31.1162353602.15351.mailman@ontoware.org>
Date:	Wed, 01 Nov 2006 05:00:02 +0100
Precedence: bulk
X-BeenThere: mailman@ontoware.org
X-Mailman-Version: 2.1.7
X-List-Administrivia: yes
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.2 NO_REAL_NAME           From: does not include a real name
	1.0 FORGED_RCVD_HELO       Received: contains a forged HELO
Subject: [Aperture-devel] ontoware.org mailing list memberships reminder
X-BeenThere: aperture-devel@lists.sourceforge.net
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a reminder, sent out once a month, about your ontoware.org
mailing list memberships.  It includes your subscription info and how
to use it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ontoware.org) containing just
the word 'help' in the message body, and an email message will be sent
to you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ontoware.org.  Thanks!

Passwords for aperture-devel@lists.sourceforge.net:

List                                     Password // URL
----                                     --------  
rdf2go-devel@ontoware.org                esdukaan  
http://ontoware.org/mailman/options/rdf2go-devel/aperture-devel%40lists.sourceforge.net

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov  2 13:17:12 2006
X-Account-Key: account3
X-UIDL: 0000ed56039f60ae
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:29142 "EHLO
	lists-outbound.sourceforge.net") by ps7.test.onet.pl with ESMTP
	id <S3170098AbWKBLe2>; Thu, 2 Nov 2006 12:34:28 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 969B912DCD; Thu,  2 Nov 2006 03:34:16 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gfapp-0001MI-PK for aperture-devel@lists.sourceforge.net;
	Thu, 02 Nov 2006 03:34:13 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gfapn-0000Wo-IC
	for aperture-devel@lists.sourceforge.net;
	Thu, 02 Nov 2006 03:34:14 -0800
Received: (qmail 2152 invoked from network); 2 Nov 2006 12:34:02 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.13?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	2 Nov 2006 12:34:02 +0100
Message-ID: <4549D7AD.1060300@aduna-software.com>
Date:	Thu, 02 Nov 2006 12:34:05 +0100
From:	Herko ter Horst <herko.ter.horst@aduna-software.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45423D68.8040606@dfki.uni-kl.de>	<4545D7A1.9040502@aduna-software.com>	<45460A7B.3080301@dfki.de>	<454610FB.4040201@aduna-software.com>
	<4549C2DC.4040801@dfki.de>
In-Reply-To: <4549C2DC.4040801@dfki.de>
X-Enigmail-Version: 0.94.0.0
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI stuff
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Leo, all,

> Ho guys,
> 
> well, you can do it fine-grained or simple.

Why not both? :)

> The main use for OSGI and Aperture will be (in my view):
> * you have an application, say a web application or a data integration
> server
> * you already have about 10 bundles for: logging, web, database, user
> interface, another database ...
> * you want to add aperture to USE IT for your existing app

This is one use case, perhaps you are right it is common, however, the
way we envisioned it - and the reason for the all the factories and
registries - is based on a number of use cases we encountered with our
clients.

This is a situation where we have a base product (Metadata Server, based
on Aperture and Sesame) that contains bundles for several common file
formats, etc (in other words: Aperture in its default configuration).
What we want to be able to do is dynamically add client-specific file
formats, add or replace metadata extractors, maybe even remove certain
extractors or fileformats for security reasons, etc.

This would a prime reason to use an OSGi-based approach with
fine-grained bundles. OSGi provides the ability to dynamically load,
unload and update bundles, the fine-grained approach allows us to
control precisely what is available.

> So - installing aperture should be simple as installing Log4j - which is
> one bundle - or any http server - which is one bundle

I don't really think this is a fair comparison. Logging is a
well-defined single-purpose service, as is providing HTTP
connectivity(*). Providing metadata access, crawling and extraction
services for many different file types, access methods and crawling
strategies is not nearly as simple.

> I would go for simple :KISS-keep it simple

I agree, it should be as simple as possible... but not simpler.

> I would go for this layout:
> * one bundle "org.semanticdesktop.aperture" conatining all the core
> services: Crawlers, Extractors, Mimetype stuff, Accessors, everything -
> they host a registry service available via OSGI to register crawlers,
> datasources, ..... but do not add them
> * one bundle "org.semanticdesktop.aperture.coredatasources" for all our
> core crawlers, extractors, accessor implementations. All of them in ONE
> bundle - ease of install and they aren't that big anyway

This is fine for some purposes, but not for all. I would also like to
see the possibility for a more fine-grained approach.

> * if anybody writes an additional crawler or so - another bundle (for
> Bibtex, for example) "org.blub.bibtext.aperturedatasource"
> 
> THEN !!!!
> you need another bundle that does the actual crawling from aperture into
> your existing database.
> * a bundle that uses all above bundles to regularly crawl:
> "com.myproject.aperturesynchroniserimpl.dependingonmydatabase"
> 
> adding a bundle for each crawler, extractor, mimetype is in my eyes
> stupid - you will end up with a hundred bundles and don'T know which is
> compatible with which, updates, etc.... too hard to manage.

This is why it is very important to provide a stable API defined in
terms of interfaces, which I think we have now.

I have no problem providing Aperture in one or two bundles, as long as
there is also the possibility to create the fine-grained bundles.


(*) Simple HTTP connectivity may be one bundle, but you only have to
look at the number of modules in Apache httpd to know that it isn't
always that simple.

Cheers,

Herko ter Horst
Senior Software Engineer
-- 
Aduna - Guided Exploration
www.aduna-software.com

Prinses Julianaplein 14-b
3817 CS Amersfoort
The Netherlands
+31-33-4659987 (office)

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov  2 16:33:53 2006
X-Account-Key: account3
X-UIDL: 0000ed56039f9baa
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:5036 "EHLO
	lists-outbound.sourceforge.net") by ps14.test.onet.pl with ESMTP
	id <S1058215AbWKBKFr>; Thu, 2 Nov 2006 11:05:47 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id AB72412126; Thu,  2 Nov 2006 02:05:37 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GfZS1-0001RO-U6 for aperture-devel@lists.sourceforge.net;
	Thu, 02 Nov 2006 02:05:34 -0800
Received: from mailgw3.uni-kl.de ([131.246.120.222])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GfZRz-0006Y5-TI
	for aperture-devel@lists.sourceforge.net;
	Thu, 02 Nov 2006 02:05:35 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw3.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kA2A5NCN001459; Thu, 2 Nov 2006 11:05:23 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kA2A5NM17571; Thu, 2 Nov 2006 11:05:23 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kA2A5KN6017875; Thu, 2 Nov 2006 11:05:21 +0100 (CET)
Message-ID: <4549C2DC.4040801@dfki.de>
Date:	Thu, 02 Nov 2006 11:05:16 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <45423D68.8040606@dfki.uni-kl.de>	<4545D7A1.9040502@aduna-software.com>	<45460A7B.3080301@dfki.de>
	<454610FB.4040201@aduna-software.com>
In-Reply-To: <454610FB.4040201@aduna-software.com>
X-Spam-Score: 0.5 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.5 HTML_20_30             BODY: Message is 20% to 30% HTML
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] OSGI stuff
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0057186557=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============0057186557==
Content-Type: multipart/alternative;
	boundary="------------020409030101050308050902"

This is a multi-part message in MIME format.
--------------020409030101050308050902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ho guys,

well, you can do it fine-grained or simple.

The main use for OSGI and Aperture will be (in my view):
* you have an application, say a web application or a data integration 
server
* you already have about 10 bundles for: logging, web, database, user 
interface, another database ...
* you want to add aperture to USE IT for your existing app

So - installing aperture should be simple as installing Log4j - which is 
one bundle - or any http server - which is one bundle

I would go for simple :KISS-keep it simple

I would go for this layout:
* one bundle "org.semanticdesktop.aperture" conatining all the core 
services: Crawlers, Extractors, Mimetype stuff, Accessors, everything - 
they host a registry service available via OSGI to register crawlers, 
datasources, ..... but do not add them
* one bundle "org.semanticdesktop.aperture.coredatasources" for all our 
core crawlers, extractors, accessor implementations. All of them in ONE 
bundle - ease of install and they aren't that big anyway
* if anybody writes an additional crawler or so - another bundle (for 
Bibtex, for example) "org.blub.bibtext.aperturedatasource"

THEN !!!!
you need another bundle that does the actual crawling from aperture into 
your existing database.
* a bundle that uses all above bundles to regularly crawl: 
"com.myproject.aperturesynchroniserimpl.dependingonmydatabase"

adding a bundle for each crawler, extractor, mimetype is in my eyes 
stupid - you will end up with a hundred bundles and don'T know which is 
compatible with which, updates, etc.... too hard to manage.



the last bit is the code  that would glue aperture to autofocus or the ams.

greets
Leo

Es begab sich aber da Christiaan Fluit zur rechten Zeit 30.10.2006 15:49 
folgendes schrieb:
> Leo Sauermann wrote:
>   
>> About the OSGI thing:
>>
>> one of the next tasks on DFKI side will be to wrap Aperture into a 
>> Nepomuk interface for datawrappers,
>> and to bundle it as OSGI service using the Eclipse plugin concept, with 
>> Bundelactivators, etc.
>> There will also be a service then running, with configuration etc.
>>
>> Anyone has experience how to handle configuration the "right way" in OSGI?
>>     
>
>  From your words I get the impression that you think of Aperture as a 
> single OSGi service, right?
>
> I have no practical experience with OSGi yet (Herko does), I only know 
> some theoretical bits. I've written documentation about it a while ago 
> to explain the rationale for all these factories and registries in 
> Aperture, see http://aperture.sourceforge.net/tutorial/architecture.html.
>
> The idea is that every core functionality (e.g. extracting metadata, 
> crawling a source or identifying a stream's MIME type) becomes a single 
> service. A registry for that service keeps track of all available 
> factories, each factory representing a single implementation of that 
> servive. Each factory has as associated BundleActivator that registers 
> the factory with the registry. Special dependency management code inside 
> these BundleActivators guarantee that "things" are initialized in the 
> correct order and with the correct information.
>
> Each service implementation, factory and BundleActivator are packaged in 
> a bundle. This is a jar file whose manifest has an entry identifying the 
> BundleActivator.
>
> What's left then is a mechanism for listing the available bundles. I 
> believe this mechanism is dependent on the OSGi runtime that you use, 
> e.g. Equinox, Knoplerfish, etc.
>
> That's about my knowledge of OSGi.
>
>
> Chris
> --
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------020409030101050308050902
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ho guys,<br>
<br>
well, you can do it fine-grained or simple.<br>
<br>
The main use for OSGI and Aperture will be (in my view):<br>
* you have an application, say a web application or a data integration
server<br>
* you already have about 10 bundles for: logging, web, database, user
interface, another database ...<br>
* you want to add aperture to USE IT for your existing app<br>
<br>
So - installing aperture should be simple as installing Log4j - which
is one bundle - or any http server - which is one bundle<br>
<br>
I would go for simple :KISS-keep it simple<br>
<br>
I would go for this layout:<br>
* one bundle "org.semanticdesktop.aperture" conatining all the core
services: Crawlers, Extractors, Mimetype stuff, Accessors, everything -
they host a registry service available via OSGI to register crawlers,
datasources, ..... but do not add them<br>
* one bundle "org.semanticdesktop.aperture.coredatasources" for all our
core crawlers, extractors, accessor implementations. All of them in ONE
bundle - ease of install and they aren't that big anyway<br>
* if anybody writes an additional crawler or so - another bundle (for
Bibtex, for example) "org.blub.bibtext.aperturedatasource"<br>
<br>
THEN !!!!<br>
you need another bundle that does the actual crawling from aperture
into your existing database.<br>
* a bundle that uses all above bundles to regularly crawl:
"com.myproject.aperturesynchroniserimpl.dependingonmydatabase"<br>
<br>
adding a bundle for each crawler, extractor, mimetype is in my eyes
stupid - you will end up with a hundred bundles and don'T know which is
compatible with which, updates, etc.... too hard to manage.<br>
<br>
<br>
<br>
the last bit is the code&nbsp; that would glue aperture to autofocus or the
ams.<br>
<br>
greets<br>
Leo<br>
<br>
Es begab sich aber da Christiaan Fluit zur rechten Zeit 30.10.2006
15:49 folgendes schrieb:
<blockquote cite="mid454610FB.4040201@aduna-software.com" type="cite">
  <pre wrap="">Leo Sauermann wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">About the OSGI thing:

one of the next tasks on DFKI side will be to wrap Aperture into a 
Nepomuk interface for datawrappers,
and to bundle it as OSGI service using the Eclipse plugin concept, with 
Bundelactivators, etc.
There will also be a service then running, with configuration etc.

Anyone has experience how to handle configuration the "right way" in OSGI?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
 From your words I get the impression that you think of Aperture as a 
single OSGi service, right?

I have no practical experience with OSGi yet (Herko does), I only know 
some theoretical bits. I've written documentation about it a while ago 
to explain the rationale for all these factories and registries in 
Aperture, see <a class="moz-txt-link-freetext" href="http://aperture.sourceforge.net/tutorial/architecture.html">http://aperture.sourceforge.net/tutorial/architecture.html</a>.

The idea is that every core functionality (e.g. extracting metadata, 
crawling a source or identifying a stream's MIME type) becomes a single 
service. A registry for that service keeps track of all available 
factories, each factory representing a single implementation of that 
servive. Each factory has as associated BundleActivator that registers 
the factory with the registry. Special dependency management code inside 
these BundleActivators guarantee that "things" are initialized in the 
correct order and with the correct information.

Each service implementation, factory and BundleActivator are packaged in 
a bundle. This is a jar file whose manifest has an entry identifying the 
BundleActivator.

What's left then is a mechanism for listing the available bundles. I 
believe this mechanism is dependent on the OSGi runtime that you use, 
e.g. Equinox, Knoplerfish, etc.

That's about my knowledge of OSGi.


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
<a class="moz-txt-link-freetext" href="http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642">http://sel.as-us.falkag.net/sel?cmd=lnk&amp;kid=120709&amp;bid=263057&amp;dat=121642</a>
_______________________________________________
Aperture-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aperture-devel@lists.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listinfo/aperture-devel</a>
  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
____________________________________________________
DI Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------020409030101050308050902--


--===============0057186557==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--===============0057186557==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============0057186557==--


From - Fri Nov  3 08:38:23 2006
X-Account-Key: account3
X-UIDL: 0000ed5603a0379b
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:26242 "EHLO
	lists-outbound.sourceforge.net") by ps23.test.onet.pl with ESMTP
	id <S4880201AbWKBRr4>; Thu, 2 Nov 2006 18:47:56 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 76C5F13516; Thu,  2 Nov 2006 09:47:53 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GfgfN-0005mL-EB for aperture-devel@lists.sourceforge.net;
	Thu, 02 Nov 2006 09:47:50 -0800
Received: from mailgw3.uni-kl.de ([131.246.120.222])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GfgfK-0008WA-Kf
	for aperture-devel@lists.sourceforge.net;
	Thu, 02 Nov 2006 09:47:50 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw3.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kA2HleAl013351 for <aperture-devel@lists.sourceforge.net>;
	Thu, 2 Nov 2006 18:47:40 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kA2HldM13702 for <aperture-devel@lists.sourceforge.net>;
	Thu, 2 Nov 2006 18:47:39 +0100 (MET)
Received: from [192.168.41.96] (gast-4106.kl.dfki.de [192.168.41.96])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kA2Hlb78015481 for <aperture-devel@lists.sourceforge.net>;
	Thu, 2 Nov 2006 18:47:37 +0100 (CET)
Message-ID: <454A2F34.1030904@dfki.de>
Date:	Thu, 02 Nov 2006 18:47:32 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Aperture 2006.1 alpha 3 RELEASED
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

We are pleased to announce the third alpha release of the Aperture 
framework.
The most notable feature in this release is a new IcalCrawler. It works 
with
iCal files generated by many calendaring applications (Apple iCal, 
Korganizer,
Lotus Notes ...). It uses a ical-rdf mapping developed by the W3C Rdf
Calendaring group. Apart from that there are numerous small improvements 
and
bugfixes. The tutorial has been expanded with more code examples and UML
diagrams to facilitate learning for new users.

This the last release before the switch to the RDF2Go framework.
(The curious can already examine the RDF2Go branch in the cvs).

Aperture 2006.1-alpha-3 can be downloaded from here:
http://sourceforge.net/project/showfiles.php?group_id=150969&package_id=166878&release_id=460471

What's new in alpha-3?

- new IcalCrawler

- added MIME type detection for many formats:

- improved MIME type detection of MHTML files (web archives)

- introduced HtmlParserUtil, containing large parts of the HtmlExtractor
  implementation, as HTML (fragments) may occur in other document types
  as well (e.g. saved mails, see MimeExtractor)

- added ThreadedExtractorWrapper class, for catching and interrupting
  hanging Extractors

- added RepositoryAccessData, an AccessData implementation storing its
  information in a Repository

- added ability to specify a port number for an IMAP source

- set target platform to Java 5

Leo Sauermann
Christiaan Fluit
Gunnar Grimnes
Antoni Mylka

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Fri Nov  3 17:07:44 2006
X-Account-Key: account3
X-UIDL: 0000ed5603a3aeb4
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:20958 "EHLO
	lists-outbound.sourceforge.net") by ps22.test.onet.pl with ESMTP
	id <S4833762AbWKCOfM>; Fri, 3 Nov 2006 15:35:12 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 2F4F5FFC5; Fri,  3 Nov 2006 06:35:11 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gg07i-0002Qh-KI for aperture-devel@lists.sourceforge.net;
	Fri, 03 Nov 2006 06:34:22 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gg07g-0002h1-2z
	for aperture-devel@lists.sourceforge.net;
	Fri, 03 Nov 2006 06:34:23 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kA3EY9xh014767; Fri, 3 Nov 2006 15:34:10 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kA3EY9M15489; Fri, 3 Nov 2006 15:34:09 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kA3EY7EA007969; Fri, 3 Nov 2006 15:34:07 +0100 (CET)
Message-ID: <454B5359.4000608@dfki.de>
Date:	Fri, 03 Nov 2006 15:34:01 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	gnowsis-dev@lists.opendfki.de, semantic-web@w3.org,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Announcement: Gnowsis Semantic Desktop 0.9.2
	released
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

The DFKI Knowledge Management lab is proud to release Gnowsis version 0.9.2

Gnowsis is a tool for realising a Semantic Desktop - a desktop where all
your data is inter-linked and related. Gnowsis gives you a tool for 
structuring
your data as well as your thoughts! This release is part of the Nepomuk
project, providing a prototype implementation of some core services.

Gnowsis has a range of features for helping you manage your personal 
information:

* Integration with Aperture for easy integration of the data in the 
applications
      you already use on your desktop! This release is based on the 
Aperture Framework
      Release 3, for more information about aperture see 
http://aperture.sourceforge.net

* A new approach to personal information management. We call it your PIMO.
* Integration with the Semantic Wiki Kaukolu, see 
http://kaukoluwiki.opendfki.de
   for information
* goodies for developers: AJAX support with XML/RPC
* Quick and easy full-text searching of all your data using Lucene.


Additional new added in this release include:

* Web2.0 Goodies: bookmarklets for tagging pages and creating things, 
geo tagging of PIMO Locations and showing these on a google-map, showing 
creation and modification of PIMO things on a Simile Timeline
* Many additional data-sources, both from aperture, and some additional 
web2.0
   sites, such as flickr, bibsonomy and del.icio.us!
* Support for PIMO synchronisation over SSH
* Many many bug fixes and minor enhancement


Download gnowsis here:

http://www.gnowsis.org/Download

And for additional information see

* http://www.gnowsis.org
* http://gnowsis.opendfki.de

Contributors to this release include Malte Kiesel, Benjamin Horack, Dominik
Heim, Sebastian Weber, Gunnar Aastrand Grimnes, Leo Sauermann, Antoni Mylka

-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Sat Nov  4 15:17:00 2006
X-Account-Key: account3
X-UIDL: 0000ed5603a40c6e
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:18336 "EHLO
	lists-outbound.sourceforge.net") by ps2.test.onet.pl with ESMTP
	id <S1422649AbWKCQtX>; Fri, 3 Nov 2006 17:49:23 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 0477913711; Fri,  3 Nov 2006 08:49:22 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gg2EI-0000tz-NB for aperture-devel@lists.sourceforge.net;
	Fri, 03 Nov 2006 08:49:18 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gg2EG-0005CB-A0
	for aperture-devel@lists.sourceforge.net;
	Fri, 03 Nov 2006 08:49:19 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kA3Gn5cV006312; Fri, 3 Nov 2006 17:49:05 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kA3Gn5M22819; Fri, 3 Nov 2006 17:49:05 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kA3Gn3mG013768; Fri, 3 Nov 2006 17:49:03 +0100 (CET)
Message-ID: <454B72F8.9000601@dfki.de>
Date:	Fri, 03 Nov 2006 17:48:56 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	gnowsis-dev@lists.opendfki.de, semantic-web@w3.org,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Announcement: Gnowsis Semantic Desktop 0.9.2
	released - update
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

The DFKI Knowledge Management lab is proud to release Gnowsis version 0.9.2

UPDATE:
we have some videos where you can see how gnowsis looks at the moment,
watch here:

GNOWSIS Videos
http://gnowsis.opendfki.de/wiki/GnowsisUsage


Gnowsis is a tool for realising a Semantic Desktop - a desktop where all
your data is inter-linked and related. Gnowsis gives you a tool for
structuring
your data as well as your thoughts! This release is part of the Nepomuk
project, providing a prototype implementation of some core services.

Gnowsis has a range of features for helping you manage your personal
information:

* Integration with Aperture for easy integration of the data in the
applications
      you already use on your desktop! This release is based on the
Aperture Framework
      Release 3, for more information about aperture see
http://aperture.sourceforge.net

* A new approach to personal information management. We call it your PIMO.
* Integration with the Semantic Wiki Kaukolu, see
http://kaukoluwiki.opendfki.de
   for information
* goodies for developers: AJAX support with XML/RPC
* Quick and easy full-text searching of all your data using Lucene.


Additional new added in this release include:

* Web2.0 Goodies: bookmarklets for tagging pages and creating things,
geo tagging of PIMO Locations and showing these on a google-map, showing
creation and modification of PIMO things on a Simile Timeline
* Many additional data-sources, both from aperture, and some additional
web2.0
   sites, such as flickr, bibsonomy and del.icio.us!
* Support for PIMO synchronisation over SSH
* Many many bug fixes and minor enhancement


Download gnowsis here:

http://www.gnowsis.org/Download

And for additional information see

* http://www.gnowsis.org
* http://gnowsis.opendfki.de

Contributors to this release include Malte Kiesel, Benjamin Horack, Dominik
Heim, Sebastian Weber, Gunnar Aastrand Grimnes, Leo Sauermann, Antoni Mylka

-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Nov  6 13:15:28 2006
X-Account-Key: account3
X-UIDL: 0000ed5603acd8e6
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:12691 "EHLO
	lists-outbound.sourceforge.net") by ps7.test.onet.pl with ESMTP
	id <S4159219AbWKFMOr>; Mon, 6 Nov 2006 13:14:47 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 038C7125E0; Mon,  6 Nov 2006 04:14:45 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gh3NB-0003Di-LZ for aperture-devel@lists.sourceforge.net;
	Mon, 06 Nov 2006 04:14:41 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gh3N8-0007DQ-53
	for aperture-devel@lists.sourceforge.net;
	Mon, 06 Nov 2006 04:14:42 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kA6CERHj000841 for <aperture-devel@lists.sourceforge.net>;
	Mon, 6 Nov 2006 13:14:28 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kA6CERM27011 for <aperture-devel@lists.sourceforge.net>;
	Mon, 6 Nov 2006 13:14:27 +0100 (MET)
Received: from [192.168.41.94] (gast-4104.kl.dfki.de [192.168.41.94])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kA6CEQDI009315 for <aperture-devel@lists.sourceforge.net>;
	Mon, 6 Nov 2006 13:14:27 +0100 (CET)
Message-ID: <454F2723.8040809@dfki.uni-kl.de>
Date:	Mon, 06 Nov 2006 13:14:27 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Progress Report - BibTex crawler - OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

We had the release, time to think about the future.

RDF2Go Branch

The lockTracking branch in the Sesame2 doesn't compile. I included the 
changes in my working copy of the main trunk. Having done this - I 
adjusted the RDF2Go Sesame2 driver to work with this code (and generate 
lock tracking messages). It seems to work, all tests seem to pass. Right 
now I work with a self-made sesame2 onejar (current trunk + 
lockTracking) and a self-made ModelImplSesame version.

TODO:

1. Take care of proper closing of all rdf models. The underlying sesame2 
implementation uses a sesameConnection. It has to be properly closed. 
Max Volkel included the open() and close() methods in the model 
interface. Benjamin Hartman implemented them in ModelImplSesame. I must 
take a look at this and see what problems would it pose in the current 
aperture architecture.

2. Remove the default RDFContainerConstructor, add a constructor to the 
RDF2GoRDFContainerFactory to make it use a ModelFactory. Remove the 
DEFAULT_FACTORY field. Goal: remove the dependency on ModelImplSesame 
(an indirectly on sesame itself) from the core aperture jar.

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

BibTeX Crawler

I did some investigation into available solutions. Apart from the 
converter made by Wolf Siberski there is one by Peter Haase and Bjorn 
Schnitzler from AIFB. It uses the same java-bib BibTeX parser. It's 
advantage is that it is GPL. It's disadvantage is that it is really 
crappy. Works with string concatenation, generates ugly XML, creates 
URIs for all resources by concatenating some magic hard-coded prefix:

swap://urn.jxta.uuid-59616261646162614A7874615032503319973678153643E581589E1EC4A2ED4E03.jxta

with a hash and some integer. I guess that trying to convert it to use 
RDF2Go would be more unnerving than it's worth. The other option is to 
use the java-bib to create our own crawler from scratch - and use the 
experience from the ical crawler, they would be similar in many respects.

Wolf Siberski uses vocabulary from dc and vcard - standarized 
namespaces. His mapping is configurable though, there is no set 
ontology. The uris to bibtex-specific elements are taken from some 
non-existent namespace (Configurable in a properties-file).

Haase and Schitzler use vocabulary from the SWRC ontology.

"
The SWRC (Semantic Web for Research Communities) is an ontology for 
modeling entities of research communities such as persons, 
organisations, publications (bibliographic metadata) and their 
relationships. It is used in numerous applications and projects 
including the AIFB portal, Bibster and the SemIPort project.

More details about the modeling of the SWRC ontology can be found in:
York Sure, Stephan Bloehdorn, Peter Haase, Jens Hartmann, Daniel Oberle. 
The SWRC Ontology - Semantic Web for Research Communities. In 
Proceedings of the 12th Portuguese Conference on Artificial Intelligence 
(EPIA 2005). Springer, Covilha, Portugal, December 2005.
"

This seems more reasonable as far as I'm concerned...

I would like to hear the decision...

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

OSGI

I must admit that I'm completely new to OSGI. So if I am to implement 
the code, that would enable aperture to be used as a set of OSGI bundles 
- it would be easier for me to know the decision concerning the level of 
granularity...

Below are exceprts from the discussion between Leo and Herko.

 > > Ho guys,
 > >
 > > well, you can do it fine-grained or simple.

 > Why not both?  :)

What would it mean 'both' - two editions? aperture-fine-grained.zip and 
aperture-coarse-grained.zip ?????

 > > The main use for OSGI and Aperture will be (in my view):
 > > * you have an application, say a web application or a data
 > >   integration server
 > > * you already have about 10 bundles for: logging, web, database,
 > >   user interface, another database ...
 > > * you want to add aperture to USE IT for your existing app

 > This is one use case, perhaps you are right it is common, however, the
 > way we envisioned it - and the reason for the all the factories and
 > registries - is based on a number of use cases we encountered with our
 > clients.

...

 > the fine-grained approach allows us to control precisely what is
 > available.

...

 > > I would go for simple :KISS-keep it simple

 > I agree, it should be as simple as possible... but not simpler.

Leo proposed the folowing layout:
* org.sematingdesktop.aperture
     - core crawlers
     - extractors
     - mimetype identification
     - accessors
     - registries for the above
     - this bundle would contain the interfaces
* org.semanticdesktop.coredatasources
     - implementations for the above services
* additional bundles for non-core crawlers etc...
* additional bundles for the transfer of data into a user-provided
   database. (That would mean a bundle for every CrawlerHandler??)
   That would mean that the user would have to provide this one...

That is: first bundle for intefaces, second for implementations ????

 > This is fine for some purposes, but not for all. I would also like to
 > see the possibility for a more fine-grained approach.

Could you provide some more specific suggestions?

 > This is why it is very important to provide a stable API defined in
 > terms of interfaces, which I think we have now.

 > I have no problem providing Aperture in one or two bundles, as long as
 > there is also the possibility to create the fine-grained bundles.

Should I try to support two layouts? E.g. create ant tasks, that would 
create releases in both versions?

I'll dig into OSGi. I hope I will my questions weren't completely 
nonsense. :-)

Antoni Mylka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Nov  6 14:48:45 2006
X-Account-Key: account3
X-UIDL: 0000ed5603ad0b65
X-Mozilla-Status: 0003
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:35283 "EHLO
	lists-outbound.sourceforge.net") by ps21.test.onet.pl with ESMTP
	id <S6252074AbWKFNpu>; Mon, 6 Nov 2006 14:45:50 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 66DA313222; Mon,  6 Nov 2006 05:45:43 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gh4nF-0003Ie-7q for aperture-devel@lists.sourceforge.net;
	Mon, 06 Nov 2006 05:45:41 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gh4n7-0007xN-2p
	for aperture-devel@lists.sourceforge.net;
	Mon, 06 Nov 2006 05:45:35 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kA6DjQl6021277 for <aperture-devel@lists.sourceforge.net>;
	Mon, 6 Nov 2006 14:45:26 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kA6DjPM02244 for <aperture-devel@lists.sourceforge.net>;
	Mon, 6 Nov 2006 14:45:26 +0100 (MET)
Received: from [192.168.41.94] (gast-4104.kl.dfki.de [192.168.41.94])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kA6DjPLg012211 for <aperture-devel@lists.sourceforge.net>;
	Mon, 6 Nov 2006 14:45:25 +0100 (CET)
Message-ID: <454F3C76.5060307@dfki.uni-kl.de>
Date:	Mon, 06 Nov 2006 14:45:26 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

I began to introduce the calls to model.close to the tests. It turns out 
that the sequence of invocations that is used most often is:

dataObject.getMetadata().getModel().close();
dataObject.dispose();

Just a design consideration. It has been made necessary by the new 
sesameConnection concept. Do we consider this acceptable or do we try 
to work around it?

Obviously automatically closing the model in dispose() is a bad idea. 
The dispose() method was conceived to close the InputStreams (or other 
system resources). Not to block the access to rdf metadata. On the other 
hand in this architecture remembering to close every Model may be 
difficult (e.g. a dataObject has two models:
dataObject.getMetadata().getModel() and
dataObject.getDataSource().getConfiguration().getModel() and both will 
have to be closed).

Antoni Mylka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Tue Nov  7 17:42:22 2006
X-Account-Key: account3
X-UIDL: 0000ed5603b12010
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:28871 "EHLO
	lists-outbound.sourceforge.net") by ps22.test.onet.pl with ESMTP
	id <S4892752AbWKGQTw>; Tue, 7 Nov 2006 17:19:52 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 609F113487; Tue,  7 Nov 2006 08:19:50 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GhTfX-00028R-Fo for aperture-devel@lists.sourceforge.net;
	Tue, 07 Nov 2006 08:19:23 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GhTfV-00036a-Rx
	for aperture-devel@lists.sourceforge.net;
	Tue, 07 Nov 2006 08:19:24 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kA7GJ9CK019471 for <aperture-devel@lists.sourceforge.net>;
	Tue, 7 Nov 2006 17:19:09 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kA7GJ9C23515 for <aperture-devel@lists.sourceforge.net>;
	Tue, 7 Nov 2006 17:19:09 +0100 (MET)
Received: from [192.168.41.94] (gast-4104.kl.dfki.de [192.168.41.94])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kA7GJ7Xk019152 for <aperture-devel@lists.sourceforge.net>;
	Tue, 7 Nov 2006 17:19:08 +0100 (CET)
Message-ID: <4550B1FF.2030400@dfki.uni-kl.de>
Date:	Tue, 07 Nov 2006 17:19:11 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F3C76.5060307@dfki.uni-kl.de>
In-Reply-To: <454F3C76.5060307@dfki.uni-kl.de>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kA7GJ9CK019471
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

QW50b25pIE15bGthIG5hcGlzYcWCKGEpOgo+IEkgYmVnYW4gdG8gaW50cm9kdWNlIHRoZSBjYWxs
cyB0byBtb2RlbC5jbG9zZSB0byB0aGUgdGVzdHMuIEl0IHR1cm5zIG91dCAKPiB0aGF0IHRoZSBz
ZXF1ZW5jZSBvZiBpbnZvY2F0aW9ucyB0aGF0IGlzIHVzZWQgbW9zdCBvZnRlbiBpczoKPiAKPiBk
YXRhT2JqZWN0LmdldE1ldGFkYXRhKCkuZ2V0TW9kZWwoKS5jbG9zZSgpOwo+IGRhdGFPYmplY3Qu
ZGlzcG9zZSgpOwo+IAo+IEp1c3QgYSBkZXNpZ24gY29uc2lkZXJhdGlvbi4gSXQgaGFzIGJlZW4g
bWFkZSBuZWNlc3NhcnkgYnkgdGhlIG5ldyAKPiBzZXNhbWVDb25uZWN0aW9uIGNvbmNlcHQuIERv
IHdlIGNvbnNpZGVyIHRoaXMgYWNjZXB0YWJsZSBvciBkbyB3ZSB0cnkgCj4gdG8gd29yayBhcm91
bmQgaXQ/Cj4gCgpJIGZpbmlzaGVkIGl0LiBOb3cgYWxsIHRlc3RzIHJ1biBzbW9vdGhseS4gTm8g
d2FybmluZ3MuIEl0IGhhcyBiZWVuIGRvbmUgCndpdGggc29tZSBzdHJhaW4gdGhvdWdoLiBJbnN0
ZWFkIG9mIGNhbGxpbmcgb2JqZWN0LmRpc3Bvc2UoKSwgYWxsIHRlc3RzIApjYWxsIGEgbWV0aG9k
IHRoYXQgbG9va3MgbGlrZSB0aGlzOgoKcHJvdGVjdGVkIHZvaWQgZGlzcG9zZURhdGFPYmplY3Qo
RGF0YU9iamVjdCBvYmplY3QpIHsKICAgaWYgKG9iamVjdC5nZXREYXRhU291cmNlKCkgIT0gbnVs
bCAmJgogICAgICAgb2JqZWN0LmdldERhdGFTb3VyY2UoKS5nZXRDb25maWd1cmF0aW9uKCkgIT0g
bnVsbCAmJgogICAgICAgb2JqZWN0LmdldERhdGFTb3VyY2UoKS5nZXRDb25maWd1cmF0aW9uKCku
Z2V0TW9kZWwoKSAhPSBudWxsKSB7CiAgICAgb2JqZWN0LmdldERhdGFTb3VyY2UoKS5nZXRDb25m
aWd1cmF0aW9uKCkuZ2V0TW9kZWwoKS5jbG9zZSgpOwogICB9CiAgIGlmIChvYmplY3QuZ2V0TWV0
YWRhdGEoKSAhPSBudWxsICYmCiAgICAgICBvYmplY3QuZ2V0TWV0YWRhdGEoKS5nZXRNb2RlbCgp
ICE9IG51bGwpIHsKICAgICAgb2JqZWN0LmdldE1ldGFkYXRhKCkuZ2V0TW9kZWwoKS5jbG9zZSgp
OwogICB9CQkKICAgb2JqZWN0LmRpc3Bvc2UoKTsKfQoKT2J2aW91c2x5IHRoaXMgaXMgY3JhcC4g
VGhlIGlzc3VlIG9mIGNsb3NpbmcgbW9kZWxzIGNhbGxzIGZvciBzb21lIApzZXJpb3VzIGFyY2hp
dGVjdHVyYWwgY29uc2lkZXJhdGlvbi4gUmlnaHQgbm93IG1vZGVsIGlzIGluY2x1ZGVkIGJ5IApE
YXRhT2JqZWN0IChhcyBtZXRhZGF0YSkgYW5kIGJ5IERhdGFTb3VyY2UgKGFzIGNvbmZpZ3VyYXRp
b24pLiBUbyBtYWtlIAp0aGluZ3Mgd29yc2UgRGF0YU9iamVjdCBlbmNhcHN1bGF0ZXMgdGhlIERh
dGFTb3VyY2UuIEN1cnJlbnRseSB3ZSBoYXZlIAp0byBjbG9zZSBpdCBhbGwgc2VwYXJhdGVseS4K
ClRoZSBjdXJpb3VzIHRoaW5nIGlzIHRoYXQgTW9kZWxJbXBsU2VzYW1lIGNsb3NlcyB0aGUgY29u
bmVjdGlvbiBvbiAKZmluYWxpemF0aW9uIGJ1dCB0aGUgd2FybmluZ3MgYXJlIHN0aWxsIHByaW50
ZWQuIEl0IHNlZW1zIHRoYXQgdGhlIEdDIApkb2VzIHNvbWUgbWFnaWMgd2hlbiBjaG9vc2luZyB0
aGUgb3JkZXIgb2Ygb2JqZWN0cyB0byBiZSBkZXN0cm95ZWQuCgoxLiBsZWF2ZSBpdCBhcyBpdCBp
cyBhbmQgbGV0IHRoZSB1c2VyIGRlYWwgd2l0aCBpdC4KMi4gTGVhdmUgaXQgYXMgaXQgaXMgYW5k
IHdyaXRlIG91ciBvd24gd3JhcHBlciBhcm91bmQgbW9kZWwgdGhhdCB3b3VsZCAKaW1wbGVtZW50
IGFsbCBtZXRob2RzIGFzCm1vZGVsLm9wZW4oKTsKc29tZXJlc3VsdCA9IG1vZGVsLmRvU3RoKGFy
ZzEsIC4uLiwgYXJnTik7Cm1vZGVsLmNsb3NlKCk7XAozLiBXZSBjb3VsZCB0aGVuIGNoYW5nZSB0
aGUgRGF0YVNvdXJjZSBpbnRlcmZhY2UgdG8gc3RhdGUgdGhhdCBpdCBjYW4gCm9ubHkgYmUgY29u
ZmlndXJlZCB3aXRoIHRoaXMgd3JhcHBlci4gKE5vdCB3aXRoIGEgZ2VuZXJpYyBSREZDb250YWlu
ZXIpLiAKSXQgd291bGRuJ3QgY2hhbmdlIHRvbyBtdWNoLCBidXQgaXQgd291bGQgZ3VhcmFudGVl
LCB0aGF0IHNpbXBsZSAKY29uZmlndXJhdGlvbiBlbGVtZW50cyB3b24ndCBuZWVkIGV4cGxpY2l0
IGNsb3NpbmcuCjQuID8/Pz8/Pz8/CgpBbnRvbmkgTXlsa2EKYW50b25pLm15bGthQGRma2kudW5p
LWtsLmRlCgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tClVzaW5nIFRvbWNhdCBidXQgbmVlZCB0byBkbyBtb3Jl
PyBOZWVkIHRvIHN1cHBvcnQgd2ViIHNlcnZpY2VzLCBzZWN1cml0eT8KR2V0IHN0dWZmIGRvbmUg
cXVpY2tseSB3aXRoIHByZS1pbnRlZ3JhdGVkIHRlY2hub2xvZ3kgdG8gbWFrZSB5b3VyIGpvYiBl
YXNpZXIKRG93bmxvYWQgSUJNIFdlYlNwaGVyZSBBcHBsaWNhdGlvbiBTZXJ2ZXIgdi4xLjAuMSBi
YXNlZCBvbiBBcGFjaGUgR2Vyb25pbW8KaHR0cDovL3NlbC5hcy11cy5mYWxrYWcubmV0L3NlbD9j
bWQ9bG5rJmtpZD0xMjA3MDkmYmlkPTI2MzA1NyZkYXQ9MTIxNjQyCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCkFwZXJ0dXJlLWRldmVsIG1haWxpbmcgbGlz
dApBcGVydHVyZS1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKaHR0cHM6Ly9saXN0cy5zb3Vy
Y2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vYXBlcnR1cmUtZGV2ZWwK

From - Wed Nov  8 17:06:38 2006
X-Account-Key: account3
X-UIDL: 0000ed5603b46811
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:10152 "EHLO
	lists-outbound.sourceforge.net") by ps24.test.onet.pl with ESMTP
	id <S4824557AbWKHQDE>; Wed, 8 Nov 2006 17:03:04 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id D35BC12973; Wed,  8 Nov 2006 07:44:10 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GhpZr-0003SY-0U for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 07:42:59 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GhpZp-0002QS-8q
	for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 07:43:00 -0800
Received: (qmail 23283 invoked from network); 8 Nov 2006 16:42:48 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	8 Nov 2006 16:42:48 +0100
Message-ID: <4551FAF4.5080309@aduna-software.com>
Date:	Wed, 08 Nov 2006 16:42:44 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F3C76.5060307@dfki.uni-kl.de>
In-Reply-To: <454F3C76.5060307@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Antoni Mylka wrote:
> I began to introduce the calls to model.close to the tests. It turns out 
> that the sequence of invocations that is used most often is:
> 
> dataObject.getMetadata().getModel().close();
> dataObject.dispose();
> 
> Just a design consideration. It has been made necessary by the new 
> sesameConnection concept. Do we consider this acceptable or do we try 
> to work around it?

Not just because of the sesameConnection, in Sesame 2 alpha 3 the 
MemoryStore also printed a warning when you didn't close it (which I 
find awkward for an in-memory representation, but ok).

> Obviously automatically closing the model in dispose() is a bad idea. 
> The dispose() method was conceived to close the InputStreams (or other 
> system resources). Not to block the access to rdf metadata. On the other 
> hand in this architecture remembering to close every Model may be 
> difficult (e.g. a dataObject has two models:
> dataObject.getMetadata().getModel() and
> dataObject.getDataSource().getConfiguration().getModel() and both will 
> have to be closed).

I think I have an idea. Forgive me for being rather elaborate (again!), 
I just want to make sure we don't talk about different issues here.

The CrawlerHandler is responsible for producing the RDFContainers used 
in DataObjects. Each RDFContainer now operates on top of some kind of 
RDF store. In the new architecture this will be an RDFContainer 
operating on a RDF2Go model containing some kind of store. As only the 
CrawlerHandler knows what store is used, whether it's a single instance 
or one instance per RDFContainer, whether it needs to be closed, flushed 
or whatever, I believe it is the CrawlerHandler's responsibility to make 
sure that this happens.

The problem with this approach is that the CrawlerHandler may not know 
when is the appropriate time. One could argue that once the Crawler 
invokes an objectNew or objectChanged method on that same 
CrawlerHandler, the CrawlerHandler can do this by itself at the end of 
this method. This is what we do right now in AutoFocus and it works well 
enough, although we occasionally get a warning from a MemoryStore being 
garbage collected because we didn't do a shutdown on it.

The problem in general is that sometimes RDFContainers are requested 
from the CrawlerHandler but they are never returned, wrapped in a 
DataObject. This happens for example because halfway during processing 
the Crawler decides that it should not report the resource it is 
processing (think redirections, symbolic links and all other sorts of 
things that may make the Crawler change his mind). The warnings 
mentioned above are caused by WebCrawlers throwing away retrieved 
RDFContainers - at that time there was no dispose I could use.

Therefore I think that the best approach is not to do a 
dataObject.getMetadata().getModel().close but instead give RDFContainer 
a dispose method. The semantics of this method is that an application 
can say: I do no longer want to use this object. Similar to 'close' but 
without the possibility to 'reopen'. The CrawlerHandler implementation 
can then provide RDFContainer instances that do a shutdown on a 
MemoryStore in case each of these RDFContainers has its own MemoryStore 
and do nothing in the dispose() when it operates on a shared store. Note 
that for simplicity I'm still talking in terms of the old architecture 
here, I'm not sure whether in the new architecture only the store could 
be shared or also the RDF2Go Model encapsulating it.

I think this approach is also good object-oriented programming: the 
RDFContainer holds the model and should therefore invoke its methods, 
you should only extract the Model and operate on it directly when 
RDFContainer's API lacks functionality for your needs and when you 
absolutely know what you will get back. DataObjects themselves don't so 
they should only use the RDFContainer API, giving the producer of the 
RDFContainer the possibility to intervene by choice of implementation class.

I would propose a similar construction for DataSources and their 
configuration models: they should just dispose() their RDFContainers. 
What happens then is to be decided by whoever instantiates these 
RDFContainers: they should choose an RDFContainer implementation 
suitable for the kind of underlying storage. The config.dispose() may 
close the underlying store or it may not, but this should be of no 
concern to the DataSources themselves.

Does this solve your problem?


Chris
--


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov  8 18:15:21 2006
X-Account-Key: account3
X-UIDL: 0000ed5603b46c68
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:13013 "EHLO
	lists-outbound.sourceforge.net") by ps4.test.onet.pl with ESMTP
	id <S3630596AbWKHQJ4>; Wed, 8 Nov 2006 17:09:56 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id DC82213C06; Wed,  8 Nov 2006 08:09:30 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GhpzU-0006EP-D1 for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 08:09:28 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GhpzP-0003Vi-4w
	for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 08:09:26 -0800
Received: (qmail 24142 invoked from network); 8 Nov 2006 17:09:14 +0100
Received: from ip22-165-208-87.adsl2.versatel.nl (HELO ?192.168.1.6?)
	(87.208.165.22)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	8 Nov 2006 17:09:13 +0100
Message-ID: <45520125.7080904@aduna-software.com>
Date:	Wed, 08 Nov 2006 17:09:09 +0100
From:	Arjohn Kampman <arjohn.kampman@aduna-software.com>
Organization: Aduna BV
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F3C76.5060307@dfki.uni-kl.de>
	<4551FAF4.5080309@aduna-software.com>
In-Reply-To: <4551FAF4.5080309@aduna-software.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Christiaan Fluit wrote:
> Antoni Mylka wrote:
>> I began to introduce the calls to model.close to the tests. It turns out 
>> that the sequence of invocations that is used most often is:
>>
>> dataObject.getMetadata().getModel().close();
>> dataObject.dispose();
>>
>> Just a design consideration. It has been made necessary by the new 
>> sesameConnection concept. Do we consider this acceptable or do we try 
>> to work around it?
> 
> Not just because of the sesameConnection, in Sesame 2 alpha 3 the 
> MemoryStore also printed a warning when you didn't close it (which I 
> find awkward for an in-memory representation, but ok).

Note that memory stores are not necessarily volatile, they can use data
files for persistence.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov  8 18:15:22 2006
X-Account-Key: account3
X-UIDL: 0000ed5603b46d8f
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:48061 "EHLO
	lists-outbound.sourceforge.net") by ps30.test.onet.pl with ESMTP
	id <S3070498AbWKHQGI>; Wed, 8 Nov 2006 17:06:08 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 1B82E13DEB; Wed,  8 Nov 2006 08:06:06 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GhpwA-0005hh-CN for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 08:06:02 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Ghpw7-0006m4-V3
	for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 08:06:03 -0800
Received: (qmail 23920 invoked from network); 8 Nov 2006 17:05:42 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	8 Nov 2006 17:05:42 +0100
Message-ID: <45520052.5000204@aduna-software.com>
Date:	Wed, 08 Nov 2006 17:05:38 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F2723.8040809@dfki.uni-kl.de>	<4551F000.5020009@aduna-software.com>
	<4551F7C7.2080602@aduna-software.com>
In-Reply-To: <4551F7C7.2080602@aduna-software.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Progress Report - BibTex crawler - OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Arjohn Kampman wrote:
> Further, MIT's Simile project has a number of RDFizers, one of which
> transforms BibTEX to RDF. Might be worth investigating:
> http://simile.mit.edu/RDFizers/

Actually I see a lot more interesting RDFizers, e.g. Java (bytecode) to 
RDF, Javadoc to RDF, Jira to RDF, Subversion to RDF, ... Maybe we could 
see if we can reuse more of their stuff or cooperate on writing some 
extraction libraries?

Stefano: are you still on this list? I see your name appearing in 
several Readme's.

The RDFizer projects differ a lot in structure: some are neatly 
organized Maven projects, others are just Perl scripts. Some may 
therefore be used directly, others would need to be ported or adapted to 
fit.


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov  9 08:39:02 2006
X-Account-Key: account3
X-UIDL: 0000ed5603b4a11e
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:5319 "EHLO
	lists-outbound.sourceforge.net") by ps8.test.onet.pl with ESMTP
	id <S5441403AbWKHRqA>; Wed, 8 Nov 2006 18:46:00 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id BE42C13CDB; Wed,  8 Nov 2006 09:45:58 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GhrUp-0000vb-Jr for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 09:45:55 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GhrUo-0001Ov-Ds
	for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 09:45:56 -0800
Received: (qmail 26563 invoked from network); 8 Nov 2006 18:45:40 +0100
Received: from 5353a894.cable.casema.nl (HELO ?83.83.168.148?) (83.83.168.148)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	8 Nov 2006 18:45:39 +0100
Message-ID: <455217BF.6010908@aduna-software.com>
Date:	Wed, 08 Nov 2006 18:45:35 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F3C76.5060307@dfki.uni-kl.de> <4550B1FF.2030400@dfki.uni-kl.de>
In-Reply-To: <4550B1FF.2030400@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Antoni Mylka wrote:
> protected void disposeDataObject(DataObject object) {
>    if (object.getDataSource() != null &&
>        object.getDataSource().getConfiguration() != null &&
>        object.getDataSource().getConfiguration().getModel() != null) {
>      object.getDataSource().getConfiguration().getModel().close();
>    }
>    if (object.getMetadata() != null &&
>        object.getMetadata().getModel() != null) {
>       object.getMetadata().getModel().close();
>    }		
>    object.dispose();
> }
> 
> Obviously this is crap.

I overlooked this mail when I answered the previous one. I agree that 
this is not a desirable situation.

I believe the solution I proposed would fix this:

- disposeDataObject could be made unnecessary by simply invoking 
object.dispose, whose implementation should invoke metadata.dispose(), 
if it has such an RDFContainer - perhaps the DataObject API mandates 
that there always is an RDFContainer, can't remember.

- depending on the RDFContainer implementation class, the underlying 
Model may or may not be closed. This however is the concern of the 
CrawlerHandler producing these RDFContainers, as it is this handler that 
decides what kind of Models are used, whether they are shared, etc.

- I don't believe DataObject should invoke dataSource.dispose(), that's 
the responsibility of whoever manages the DataSources, including the 
RDFContainers that they internally use. It's only in your unit test that 
these two objects are created and destroyed together, in applications 
DataSources often have a very different life cycle than DataObjects.

Does this help?


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov  9 15:47:28 2006
X-Account-Key: account3
X-UIDL: 0000ed5603b75987
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:60141 "EHLO
	lists-outbound.sourceforge.net") by ps27.test.onet.pl with ESMTP
	id <S4846228AbWKIO1F>; Thu, 9 Nov 2006 15:27:05 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id C5BB414000; Thu,  9 Nov 2006 06:27:02 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiArd-0006ei-Vq for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 06:26:46 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiArc-0003RG-II
	for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 06:26:47 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kA9EQQt5024990; Thu, 9 Nov 2006 15:26:27 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kA9EHMY18709; Thu, 9 Nov 2006 15:17:23 +0100 (MET)
Received: from [192.168.41.94] (gast-4104.kl.dfki.de [192.168.41.94])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kA9EHLJB012047; Thu, 9 Nov 2006 15:17:21 +0100 (CET)
Message-ID: <45533875.30002@dfki.uni-kl.de>
Date:	Thu, 09 Nov 2006 15:17:25 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F3C76.5060307@dfki.uni-kl.de>
	<4551FAF4.5080309@aduna-software.com>
In-Reply-To: <4551FAF4.5080309@aduna-software.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kA9EQQt5024990
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Q2hyaXN0aWFhbiBGbHVpdCBuYXBpc2HFgihhKToKPiBJIHRoaW5rIEkgaGF2ZSBhbiBpZGVhLiBG
b3JnaXZlIG1lIGZvciBiZWluZyByYXRoZXIgZWxhYm9yYXRlIChhZ2FpbiEpLCAKPiBJIGp1c3Qg
d2FudCB0byBtYWtlIHN1cmUgd2UgZG9uJ3QgdGFsayBhYm91dCBkaWZmZXJlbnQgaXNzdWVzIGhl
cmUuCgpJIGNlcnRhaW5seSBkb24ndCBtaW5kIDotKQoKPiAKPiBUaGVyZWZvcmUgSSB0aGluayB0
aGF0IHRoZSBiZXN0IGFwcHJvYWNoIGlzIG5vdCB0byBkbyBhIAo+IGRhdGFPYmplY3QuZ2V0TWV0
YWRhdGEoKS5nZXRNb2RlbCgpLmNsb3NlIGJ1dCBpbnN0ZWFkIGdpdmUgUkRGQ29udGFpbmVyIAo+
IGEgZGlzcG9zZSBtZXRob2QuIFRoZSBzZW1hbnRpY3Mgb2YgdGhpcyBtZXRob2QgaXMgdGhhdCBh
biBhcHBsaWNhdGlvbiAKPiBjYW4gc2F5OiBJIGRvIG5vIGxvbmdlciB3YW50IHRvIHVzZSB0aGlz
IG9iamVjdC4gU2ltaWxhciB0byAnY2xvc2UnIGJ1dCAKPiB3aXRob3V0IHRoZSBwb3NzaWJpbGl0
eSB0byAncmVvcGVuJy4gVGhlIENyYXdsZXJIYW5kbGVyIGltcGxlbWVudGF0aW9uIAo+IGNhbiB0
aGVuIHByb3ZpZGUgUkRGQ29udGFpbmVyIGluc3RhbmNlcyB0aGF0IGRvIGEgc2h1dGRvd24gb24g
YSAKPiBNZW1vcnlTdG9yZSBpbiBjYXNlIGVhY2ggb2YgdGhlc2UgUkRGQ29udGFpbmVycyBoYXMg
aXRzIG93biBNZW1vcnlTdG9yZSAKPiBhbmQgZG8gbm90aGluZyBpbiB0aGUgZGlzcG9zZSgpIHdo
ZW4gaXQgb3BlcmF0ZXMgb24gYSBzaGFyZWQgc3RvcmUuIE5vdGUgCj4gdGhhdCBmb3Igc2ltcGxp
Y2l0eSBJJ20gc3RpbGwgdGFsa2luZyBpbiB0ZXJtcyBvZiB0aGUgb2xkIGFyY2hpdGVjdHVyZSAK
PiBoZXJlLCBJJ20gbm90IHN1cmUgd2hldGhlciBpbiB0aGUgbmV3IGFyY2hpdGVjdHVyZSBvbmx5
IHRoZSBzdG9yZSBjb3VsZCAKPiBiZSBzaGFyZWQgb3IgYWxzbyB0aGUgUkRGMkdvIE1vZGVsIGVu
Y2Fwc3VsYXRpbmcgaXQuCgouLi4KCj4gSSB3b3VsZCBwcm9wb3NlIGEgc2ltaWxhciBjb25zdHJ1
Y3Rpb24gZm9yIERhdGFTb3VyY2VzIGFuZCB0aGVpciAKPiBjb25maWd1cmF0aW9uIG1vZGVsczog
dGhleSBzaG91bGQganVzdCBkaXNwb3NlKCkgdGhlaXIgUkRGQ29udGFpbmVycy4gCj4gV2hhdCBo
YXBwZW5zIHRoZW4gaXMgdG8gYmUgZGVjaWRlZCBieSB3aG9ldmVyIGluc3RhbnRpYXRlcyB0aGVz
ZSAKPiBSREZDb250YWluZXJzOiB0aGV5IHNob3VsZCBjaG9vc2UgYW4gUkRGQ29udGFpbmVyIGlt
cGxlbWVudGF0aW9uIAo+IHN1aXRhYmxlIGZvciB0aGUga2luZCBvZiB1bmRlcmx5aW5nIHN0b3Jh
Z2UuIFRoZSBjb25maWcuZGlzcG9zZSgpIG1heSAKPiBjbG9zZSB0aGUgdW5kZXJseWluZyBzdG9y
ZSBvciBpdCBtYXkgbm90LCBidXQgdGhpcyBzaG91bGQgYmUgb2Ygbm8gCj4gY29uY2VybiB0byB0
aGUgRGF0YVNvdXJjZXMgdGhlbXNlbHZlcy4KPiAKPiBEb2VzIHRoaXMgc29sdmUgeW91ciBwcm9i
bGVtPwoKU28uLi4KCjEuIEFkZCBhIGRpc3Bvc2UoKSBtZXRob2QgdG8gdGhlIFJERkNvbnRhaW5l
ciBpbnRlcmZhY2UuIERvY3VtZW50IGl0IAp0aGF0IHVzaW5nIHRoZSBSREZDb250YWluZXIgYWZ0
ZXIgdGhlIGNhbGwgdG8gZGlzcG9zZSgpIGlzIGZvcmJpZGRlbiBhcyAKdW5leHBlY3RlZCByZXN1
bHRzIG1heSBvY2N1ci4KCjIuIEhhdmUgRGF0YU9iamVjdC5kaXNwb3NlKCkgaW52b2tlIG1ldGFk
YXRhLmRpc3Bvc2UoKS4KCkludHJvZHVjZSB0aGUgY29uY2VwdCBvZiBhIE1vZGVsIGJlaW5nIG93
bmVkIGJ5IHRoZSBjb250YWluZXIgdnMuCm1vZGVsIGJlaW5nIHNoYXJlZCBiZXR3ZWVuIGNvbnRh
aW5lcnMuIFdlIGNvdWxkIGFkZCB0d28gYWRkaXRpb25hbAptZXRob2RzIGlzTW9kZWxTaGFyZWQg
dnMuIHNldE1vZGVsU2hhcmVkLiBBbHNvLCB3ZSBjb3VsZCBwcm92aWRlCmFuIGFkZGl0aW9uYWwg
cGFyYW1ldGVyIGluIHRoZSBjb25zdHJ1Y3RvcnMuIFRoZSBpbXBsZW1lbnRhdGlvbgpjb3VsZCB1
c2UgdGhpcyBwYXJhbWV0ZXIgdG8gZGV0ZXJtaW5lIGlmIGEgbW9kZWwgc2hvdWxkIGJlIGNsb3Nl
ZApvbiBkaXBvc2FsIG9yIG5vdAoKV2UgaGF2ZSB0byBjb25zaWRlciBmb3VyIGNhc2VzLgoKMS4g
TXVsdGlwbGUgQ29udGFpbmVycywgTXVsdGlwbGUgTW9kZWxzLCBNdWx0aXBsZSBSZXBvc2l0b3Jp
ZXMKMi4gTXVsdGlwbGUgQ29udGFpbmVycywgTXVsdGlwbGUgTW9kZWxzLCBTaW5nbGUgUmVwb3Np
dG9yeQozLiBNdWx0aXBsZSBDb250YWluZXJzLCBTaW5nbGUgTW9kZWwKNC4gU2luZ2xlIENvbnRh
aW5lciByZXR1cm5lZCBtdWx0aXBsZSB0aW1lcy4KCjEuIENsb3NlIHRoZSBtb2RlbCBvbiBkaXBv
c2FsIChvYnZpb3VzbHkpCjIuIENsb3NlIHRoZSBtb2RlbCBvbiBkaXNwb3NhbC4gVGhpcyB3b3Vs
ZCBpbXBseSBtdWx0aXBsZSBjb25uZWN0aW9ucyB0byAKdGhlIHNhbWUgcmVwb3NpdG9yeS4KMyY0
ICAgRG9uJ3QgY2xvc2UgdGhlIG1vZGVsIG9uIGRpc3Bvc2FsCgpJIGNvbnNpZGVyZWQgaGF2aW5n
IHRoZSBSREYyR29SREZDb250YWluZXIgdGhyb3cgYW4gCklsbGVnYWxTdGF0ZUV4Y2VwdGlvbiBp
ZiBpdCB3b3VsZCBiZSB1c2VkIGFmdGVyIGJlaW5nIGRpc3Bvc2VkLiBJdCBpcyAKbm90IGEgZ29v
ZCBpZGVhIHRob3VnaCBpZiB3ZSBhY2NlcHQgdGhlIDR0aCBjYXNlLgoKV2UgY291bGQgbWFrZSBp
dCBjbGVhcmVyIGJ5IGhhdmluZyB0d28gc3ViY2xhc3NlcyBvZiBSREYyR29SREZDb250YWluZXIg
Ci0gU2hhcmVkTW9kZWxSREZDb250YWluZXIgYW5kIEV4Y2x1c2l2ZU1vZGVsUkRGQ29udGFpbmVy
LiBUaGUgZmlyc3Qgb25lIAp3b3VsZCBzZXQgdGhlIGlzTW9kZWxTaGFyZWQgdG8gdHJ1ZSBhbmQg
b3ZlcnJpZGUgdGhlIHNldHRlciAoYW5kIG1ha2UgCnRoZSBvdmVycmlkZW4gc2V0dGVyIGZpbmFs
KSwgdGhlIHNlY29uZCBvbmUgd291bGQgc2V0IHRoZSBpc01vZGVsU2hhcmVkIAp0byBmYWxzZSBh
bmQgbGlrZXdpc2Ugb3ZlcnJpZGUgdGhlIHNldHRlciAoYW5kIG1ha2UgaXQgZmluYWwpLgoKV2Ug
Y291bGQgaW50cm9kdWNlIGEgRGF0YVNvdXJjZS5kaXNwb3NlKCkgbWV0aG9kIHRoYXQgd291bGQg
YmUgYSAKY29udmVuaWVuY2Ugd3JhcHBlciBmb3IgY29uZmlndXJhdGlvbi5jbG9zZSgpLiBCdXQg
RGF0YU9iamVjdC5kaXNwb3NlKCkgCndvdWxkIE5PVCBpbnZva2UgaXQuCgpJZiBJIGdldCB0aGUg
Z3JlZW4gbGlnaHQsIEkgY291bGQgaW1wbGVtZW50IGl0IHJpZ2h0IGF3YXkuIFRoZW4gSSB3b3Vs
ZCAKbW9kaWZ5IHRoZSB0ZXN0cyBhbmQgZXhhbXBsZXMgdG8gdXNlIHRoaXMgYXBwcm9hY2guIEFm
dGVyIHRoYXQgd2UgY291bGQgCm1ha2UgYSBtZXJnZS4gSSBhZGp1c3RlZCBhbGwgUmVwb3NpdG9y
eS11c2luZyBjbGFzc2VzIHRvIHRoZSBuZXcgc2VzYW1lIAppbnRlcmZhY2UuIFJpZ2h0IG5vdyBh
bGwgY2xhc3NlcyBmcm9tIHRoZSBSREYyR28gYnJhbmNoIGNvbXBpbGUgCnBlcmZlY3RseSwgU2Vz
YW1lUkRGQ29udGFpbmVyIGJlY2FtZSBhIGNvbnZlbmllbmNlIHdyYXBwZXIgYXJvdW5kIGEgCk1v
ZGVsSW1wbFNlc2FtZSwgKGFjdHVhbGx5IGEgd3JhcHBlciBhcm91bmQgYSBSREYyR29SREZDb250
YWluZXIgdGhhdCBpbiAKdHVybnMgd3JhcHMgYSBNb2RlbEltcGxTZXNhbWUgOi0pICkuIFJlcG9z
aXRvcnlVdGlsIHNlZW1zIHRvIHdvcmssIHNvIApkb2VzIFJlcG9zaXRvcnlBY2Nlc3NEYXRhIHRo
ZSBmaWxlaW5zcGVjdG9yIGV4YW1wbGVzIHdvcmsgdG9vLgoKQW50b25pIE15bGthCmFudG9uaS5t
eWxrYUBkZmtpLnVuaS1rbC5kZQoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQpVc2luZyBUb21jYXQgYnV0IG5l
ZWQgdG8gZG8gbW9yZT8gTmVlZCB0byBzdXBwb3J0IHdlYiBzZXJ2aWNlcywgc2VjdXJpdHk/Ckdl
dCBzdHVmZiBkb25lIHF1aWNrbHkgd2l0aCBwcmUtaW50ZWdyYXRlZCB0ZWNobm9sb2d5IHRvIG1h
a2UgeW91ciBqb2IgZWFzaWVyCkRvd25sb2FkIElCTSBXZWJTcGhlcmUgQXBwbGljYXRpb24gU2Vy
dmVyIHYuMS4wLjEgYmFzZWQgb24gQXBhY2hlIEdlcm9uaW1vCmh0dHA6Ly9zZWwuYXMtdXMuZmFs
a2FnLm5ldC9zZWw/Y21kPWxuayZraWQ9MTIwNzA5JmJpZD0yNjMwNTcmZGF0PTEyMTY0MgpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpBcGVydHVyZS1kZXZl
bCBtYWlsaW5nIGxpc3QKQXBlcnR1cmUtZGV2ZWxAbGlzdHMuc291cmNlZm9yZ2UubmV0Cmh0dHBz
Oi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL2FwZXJ0dXJlLWRldmVsCg==

From - Fri Nov 10 10:20:58 2006
X-Account-Key: account3
X-UIDL: 0000ed5603b7ce6c
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:59063 "EHLO
	lists-outbound.sourceforge.net") by ps7.test.onet.pl with ESMTP
	id <S7307141AbWKIPau>; Thu, 9 Nov 2006 16:30:50 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 437F213F2E; Thu,  9 Nov 2006 07:30:49 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiBqV-0004Od-Uf for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 07:29:40 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiBqV-0005JA-8L
	for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 07:29:40 -0800
Received: (qmail 22021 invoked from network); 9 Nov 2006 16:29:28 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	9 Nov 2006 16:29:28 +0100
Message-ID: <45534957.30401@aduna-software.com>
Date:	Thu, 09 Nov 2006 16:29:27 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Announcement: Aduna AutoFocus 4.0 Beta 2 released
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Hello all,

We are happy to announce the release of AutoFocus 4.0 Beta 2.

 From the product page: "Aduna AutoFocus helps you to search and find 
information on your PC, network disks, mail boxes, websites and Aduna 
Metadata Server sources. It scans all places where you expect valuable 
information and provides powerful means for retrieving that information. 
The important difference with other search tools is that AutoFocus 
presents the search results using Cluster Maps. In these maps you can 
see how files, web pages or emails are related to your question."

This release succeeds AutoFocus 2006.3 Beta 1; we have changed from a 
year-based version number system to a regular "major.minor" version 
number. It is based on Aperture 2006.1 alpha 3 and Sesame 2.0 alpha 3.

New in this release:

* A completely revised user interface.

* Facet highlighting to help you inspect and drill down on search results.

* Keyword search options, allowing you to specify what parts of the 
documents should be searched on.

* A lot of bug fixes and improvements throughout the application, many 
of which made possible because of the feedback on the AutoFocus forum 
(http://www.aduna-software.net/forum/forums/show/2.page) or via the 
feedback email alias (feedback@aduna-software.com).

Visit http://www.aduna-software.org/projects/x/iw for more detailed 
release notes and download links.

Visit http://www.aduna-software.com/downloads/demos/autofocus-intro.html 
for a Flash-based Guided Tour.

We are looking forward to hear about your experiences with this new 
release. The final AutoFocus 4.0 release is scheduled for December 2006.


Kind regards,

Christiaan Fluit
-- 
Aduna - Guided Exploration
www.aduna-software.com

Prinses Julianaplein 14-b
3817 CS Amersfoort
The Netherlands
+31-33-4659987 (office)

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Fri Nov 10 10:20:58 2006
X-Account-Key: account3
X-UIDL: 0000ed5603b7d588
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:54701 "EHLO
	lists-outbound.sourceforge.net") by ps26.test.onet.pl with ESMTP
	id <S4841482AbWKIRl6>; Thu, 9 Nov 2006 18:41:58 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 813E7127BB; Thu,  9 Nov 2006 08:16:17 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiCWz-0000xk-RW for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 08:13:33 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiCWv-0002OZ-Gy
	for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 08:13:32 -0800
Received: (qmail 23101 invoked from network); 9 Nov 2006 17:13:14 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	9 Nov 2006 17:13:14 +0100
Message-ID: <45535399.5070600@aduna-software.com>
Date:	Thu, 09 Nov 2006 17:13:13 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F3C76.5060307@dfki.uni-kl.de>
	<4551FAF4.5080309@aduna-software.com>
	<45533875.30002@dfki.uni-kl.de>
In-Reply-To: <45533875.30002@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Antoni Mylka wrote:
> So...
> 
> 1. Add a dispose() method to the RDFContainer interface. Document it 
> that using the RDFContainer after the call to dispose() is forbidden as 
> unexpected results may occur.

Yes.

> 2. Have DataObject.dispose() invoke metadata.dispose().

Yes.

> Introduce the concept of a Model being owned by the container vs.
> model being shared between containers. We could add two additional
> methods isModelShared vs. setModelShared. Also, we could provide
> an additional parameter in the constructors. The implementation
> could use this parameter to determine if a model should be closed
> on diposal or not

Introduce the concept where? In which API?

I mainly see this as something for the CrawlerHandler implementor to 
worry about, although I can understand that you want to offer basic 
RDFContainer implementations ready for general use. I wouldn't add any 
methods related to shared or unshared underlying models in 
RDFContainer's API if that's what you propose. I believe this should be 
entirely transparent and encapsulated by the implementing class.

> ...
> 4. Single Container returned multiple times.
> ...
> I considered having the RDF2GoRDFContainer throw an 
> IllegalStateException if it would be used after being disposed. It is 
> not a good idea though if we accept the 4th case.

Why not? Obviously something is wrong in the architecture then, e.g. an 
Extractor accidentally closing the RDFContainer passed to it. I think 
this is rather a feature than a problem :)

In general I believe most objects should refrain from closing 
RDFContainers. Only for DataObject and DataSource implementations it 
makes sense as they can assume that they "own" the RDFContainer. By 
passing it an instance of the appropriate RDFContainer implementation 
class to a DataSource or DataObject constructor "you" (e.g. the 
CrawlerHandler implementor) can influence what the RDFContainer.dispose 
actually does internally.

Maybe this discussion is so complicated because of different perceptions 
on what the RDFContainer represents conceptually and who controls it? I 
think of it as a small self-contained piece of RDF, closely related to 
the notion of CBD graphs and similar concepts. That's why it has a 
notion of a described URI for example and are in my view so tightly 
bound to a DataObject or DataSource. If RDFContainers somehow do some 
trickery and share underlying data structures with other RDFContainers, 
that should remain hidden to the users of the RDFContainer.

> We could introduce a DataSource.dispose() method that would be a 
> convenience wrapper for configuration.close(). But DataObject.dispose() 
> would NOT invoke it.

I would actually *expect* DataSource.dispose to invoke config.dispose 
and DataObject.dispose not having anything to do with it.

I'm really curious about what the others are thinking about all of this. 
Guess we will hear from them next week :)

> If I get the green light, I could implement it right away. Then I would 
> modify the tests and examples to use this approach. After that we could 
> make a merge. I adjusted all Repository-using classes to the new sesame 
> interface. Right now all classes from the RDF2Go branch compile 
> perfectly, SesameRDFContainer became a convenience wrapper around a 
> ModelImplSesame, (actually a wrapper around a RDF2GoRDFContainer that in 
> turns wraps a ModelImplSesame :-) ). RepositoryUtil seems to work, so 
> does RepositoryAccessData the fileinspector examples work too.

Good to hear! So this is all based on Sesame 2 alpha 4 already?


Regards,

Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Fri Nov 10 10:20:59 2006
X-Account-Key: account3
X-UIDL: 0000ed5603b821da
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:8344 "EHLO
	lists-outbound.sourceforge.net") by ps25.test.onet.pl with ESMTP
	id <S4157471AbWKITaB>; Thu, 9 Nov 2006 20:30:01 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 261E2161AE; Thu,  9 Nov 2006 11:29:18 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiFXa-0005Jt-Jo for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 11:26:22 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiFXa-0001tQ-53
	for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 11:26:23 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kA9JQ6bq023239 for <aperture-devel@lists.sourceforge.net>;
	Thu, 9 Nov 2006 20:26:06 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kA9JQ5Y05259; Thu, 9 Nov 2006 20:26:05 +0100 (MET)
Received: from [192.168.22.54] (vpn-2204.kl.dfki.de [192.168.22.54])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kA9JQ3WH002164; Thu, 9 Nov 2006 20:26:04 +0100 (CET)
Message-ID: <455380BD.6050600@dfki.de>
Date:	Thu, 09 Nov 2006 20:25:49 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
References: <45533FC5.5020505@dfki.uni-kl.de>
In-Reply-To: <45533FC5.5020505@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Hi,
good work antoni,
that is the way I also expected it to somehow come out.

Es begab sich aber da Antoni Mylka zur rechten Zeit 09.11.2006 15:48 
folgendes schrieb:
> I've gone through some tutorials and I see it as follows.
>
> We would need one core aperture bundle. It would contain all interfaces 
> and vocabulary classes. I would exclude following packages from this 
> core bundle:
> accessor.file
> accessor.http
> addressbook
> crawler.filesystem
> crawler.ical
> crawler.imap
> crawler.web
> datasource.filesystem
> datasource.ical
> datasource.imap
> datasource.web
> all extractor subpackages except extractor.impl
> hypertext.linkextractor.html
> mime.identifier.magic
> opener.file
> opener.http
> outlook
>
> Security, util and vocabulary could stay. This core bundle would 
> register following services:
> DataAccessorRegistry
> CrawlerRegistry
> DataSourceRegistry
> ExtractorRegistry
> LinkExtractorRegistry
> MimeTypeIdentifierRegistry
> DataOpenerRegistry
>   

yes, correct
> The implementations of these interfaces could all be placed in one big 
> bundle, or in separate bundles, even if each bundle would contain a 
> single class. The activators of these implementation bundles would 
> register all implementations with appropriate registries.
>   
please do it as several bundles for:
* Microsoft Outlook (is needed to be separate)
* IMAP crawling (I think this should be separate)
* everything else

> There remains the issue of RDFContainer creation. We should provide some 
> factory of RDF2GoRDFContainers, that would accept models. It's methods 
> would be exactly equivalent to the current set of constructors in the 
> RDF2GoRDFContainer class.
>   
no idea how to do this - just suggest something
> We should also have a bundle that would expose the core RDF2Go 
> interfaces, and a bundle that would be a factory of ModelImplSesame... 
> this one would need to have access to the ModelImplSesame jar and to the 
> sesame onejar. (Is it at all possible in OSGI for the bundles to use 
> classes from external jars, or export interfaces from external jars?)
>   
the bundles Export classpaths/packages, and you can instantiate the 
classes from any ohter bundle if you correclty import these 
dependencies. try to import bundles or features instead of importing 
packages - see the eclipse plugin-editor (whcih equals to a bundle 
editor) for a gui to edit manifest files.

best greetings
good work
Leo

> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Fri Nov 10 11:56:57 2006
X-Account-Key: account3
X-UIDL: 0000ed5603ba8964
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:4775 "EHLO
	lists-outbound.sourceforge.net") by ps29.test.onet.pl with ESMTP
	id <S5139932AbWKJKcY>; Fri, 10 Nov 2006 11:32:24 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 586FD129F4; Fri, 10 Nov 2006 02:32:23 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiTgK-0005Nt-7r for aperture-devel@lists.sourceforge.net;
	Fri, 10 Nov 2006 02:32:20 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiTgK-00076K-Sk
	for aperture-devel@lists.sourceforge.net;
	Fri, 10 Nov 2006 02:32:21 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kAAAWCTH016686; Fri, 10 Nov 2006 11:32:12 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kAAAWCY17452; Fri, 10 Nov 2006 11:32:12 +0100 (MET)
Received: from [192.168.41.94] (gast-4104.kl.dfki.de [192.168.41.94])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kAAAWAHk029097; Fri, 10 Nov 2006 11:32:10 +0100 (CET)
Message-ID: <4554552E.1000201@dfki.uni-kl.de>
Date:	Fri, 10 Nov 2006 11:32:14 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F3C76.5060307@dfki.uni-kl.de>	<4551FAF4.5080309@aduna-software.com>	<45533875.30002@dfki.uni-kl.de>
	<45535399.5070600@aduna-software.com>
In-Reply-To: <45535399.5070600@aduna-software.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kAAAWCTH016686
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Q2hyaXN0aWFhbiBGbHVpdCBuYXBpc2HFgihhKToKPj4gSW50cm9kdWNlIHRoZSBjb25jZXB0IG9m
IGEgTW9kZWwgYmVpbmcgb3duZWQgYnkgdGhlIGNvbnRhaW5lciB2cy4KPj4gbW9kZWwgYmVpbmcg
c2hhcmVkIGJldHdlZW4gY29udGFpbmVycy4gV2UgY291bGQgYWRkIHR3byBhZGRpdGlvbmFsCj4+
IG1ldGhvZHMgaXNNb2RlbFNoYXJlZCB2cy4gc2V0TW9kZWxTaGFyZWQuIEFsc28sIHdlIGNvdWxk
IHByb3ZpZGUKPj4gYW4gYWRkaXRpb25hbCBwYXJhbWV0ZXIgaW4gdGhlIGNvbnN0cnVjdG9ycy4g
VGhlIGltcGxlbWVudGF0aW9uCj4+IGNvdWxkIHVzZSB0aGlzIHBhcmFtZXRlciB0byBkZXRlcm1p
bmUgaWYgYSBtb2RlbCBzaG91bGQgYmUgY2xvc2VkCj4+IG9uIGRpcG9zYWwgb3Igbm90Cj4gCj4g
SW50cm9kdWNlIHRoZSBjb25jZXB0IHdoZXJlPyBJbiB3aGljaCBBUEk/Cj4gCj4gSSBtYWlubHkg
c2VlIHRoaXMgYXMgc29tZXRoaW5nIGZvciB0aGUgQ3Jhd2xlckhhbmRsZXIgaW1wbGVtZW50b3Ig
dG8gCj4gd29ycnkgYWJvdXQsIGFsdGhvdWdoIEkgY2FuIHVuZGVyc3RhbmQgdGhhdCB5b3Ugd2Fu
dCB0byBvZmZlciBiYXNpYyAKPiBSREZDb250YWluZXIgaW1wbGVtZW50YXRpb25zIHJlYWR5IGZv
ciBnZW5lcmFsIHVzZS4gSSB3b3VsZG4ndCBhZGQgYW55IAo+IG1ldGhvZHMgcmVsYXRlZCB0byBz
aGFyZWQgb3IgdW5zaGFyZWQgdW5kZXJseWluZyBtb2RlbHMgaW4gCj4gUkRGQ29udGFpbmVyJ3Mg
QVBJIGlmIHRoYXQncyB3aGF0IHlvdSBwcm9wb3NlLiBJIGJlbGlldmUgdGhpcyBzaG91bGQgYmUg
Cj4gZW50aXJlbHkgdHJhbnNwYXJlbnQgYW5kIGVuY2Fwc3VsYXRlZCBieSB0aGUgaW1wbGVtZW50
aW5nIGNsYXNzLgo+IAoKSSBpbnRlbmRlZCB0byBpbnRyb2R1Y2UgaXQgaW50byBvdXIgb3duIFJE
RjJHb1JERkNvbnRhaW5lciBjbGFzcy4gTm90IGluIAp0aGUgUkRGQ29udGFpbmVyIGludGVyZmFj
ZSBpdHNlbGYuCgo+PiAuLi4KPj4gNC4gU2luZ2xlIENvbnRhaW5lciByZXR1cm5lZCBtdWx0aXBs
ZSB0aW1lcy4KPj4gLi4uCj4+IEkgY29uc2lkZXJlZCBoYXZpbmcgdGhlIFJERjJHb1JERkNvbnRh
aW5lciB0aHJvdyBhbiAKPj4gSWxsZWdhbFN0YXRlRXhjZXB0aW9uIGlmIGl0IHdvdWxkIGJlIHVz
ZWQgYWZ0ZXIgYmVpbmcgZGlzcG9zZWQuIEl0IGlzIAo+PiBub3QgYSBnb29kIGlkZWEgdGhvdWdo
IGlmIHdlIGFjY2VwdCB0aGUgNHRoIGNhc2UuCj4gCj4gV2h5IG5vdD8gT2J2aW91c2x5IHNvbWV0
aGluZyBpcyB3cm9uZyBpbiB0aGUgYXJjaGl0ZWN0dXJlIHRoZW4sIGUuZy4gYW4gCj4gRXh0cmFj
dG9yIGFjY2lkZW50YWxseSBjbG9zaW5nIHRoZSBSREZDb250YWluZXIgcGFzc2VkIHRvIGl0LiBJ
IHRoaW5rIAo+IHRoaXMgaXMgcmF0aGVyIGEgZmVhdHVyZSB0aGFuIGEgcHJvYmxlbSA6KQoKT0su
IFJERjJHb1JERkNvbnRhaW5lciB3aWxsIHRocm93IGFuIElsbGVnYWxTdGF0ZUV4Y2VwdGlvbiBh
ZnRlciBiZWluZyAKZGlzcG9zZWQuIFdlIG1ha2UgdGhlIGZvdXJ0aCBjYXNlIGlsbGVnYWwuIEFk
ZCBzb21lIG5vdGUgaW4gdGhlIGRvY3MKZXZlcnkgUkRGQ29udGFpbmVyRmFjdG9yeSBzaG91bGQg
cmV0dXJuIE5FVyBpbnN0YW5jZXMgb2YgUkRGQ29udGFpbmVyLgpJdCBpcyB1cCB0byB0aGUgaW1w
bGVtZW50b3IgaWYgdGhleSB3aWxsIHVzZSBhIHNoYXJlZCBtb2RlbCBvciBub3QuCgo+IEluIGdl
bmVyYWwgSSBiZWxpZXZlIG1vc3Qgb2JqZWN0cyBzaG91bGQgcmVmcmFpbiBmcm9tIGNsb3Npbmcg
Cj4gUkRGQ29udGFpbmVycy4gT25seSBmb3IgRGF0YU9iamVjdCBhbmQgRGF0YVNvdXJjZSBpbXBs
ZW1lbnRhdGlvbnMgaXQgCj4gbWFrZXMgc2Vuc2UgYXMgdGhleSBjYW4gYXNzdW1lIHRoYXQgdGhl
eSAib3duIiB0aGUgUkRGQ29udGFpbmVyLiBCeSAKPiBwYXNzaW5nIGl0IGFuIGluc3RhbmNlIG9m
IHRoZSBhcHByb3ByaWF0ZSBSREZDb250YWluZXIgaW1wbGVtZW50YXRpb24gCj4gY2xhc3MgdG8g
YSBEYXRhU291cmNlIG9yIERhdGFPYmplY3QgY29uc3RydWN0b3IgInlvdSIgKGUuZy4gdGhlIAo+
IENyYXdsZXJIYW5kbGVyIGltcGxlbWVudG9yKSBjYW4gaW5mbHVlbmNlIHdoYXQgdGhlIFJERkNv
bnRhaW5lci5kaXNwb3NlIAo+IGFjdHVhbGx5IGRvZXMgaW50ZXJuYWxseS4KCk9LCgo+PiBXZSBj
b3VsZCBpbnRyb2R1Y2UgYSBEYXRhU291cmNlLmRpc3Bvc2UoKSBtZXRob2QgdGhhdCB3b3VsZCBi
ZSBhIAo+PiBjb252ZW5pZW5jZSB3cmFwcGVyIGZvciBjb25maWd1cmF0aW9uLmNsb3NlKCkuIEJ1
dCBEYXRhT2JqZWN0LmRpc3Bvc2UoKSAKPj4gd291bGQgTk9UIGludm9rZSBpdC4KPiAKPiBJIHdv
dWxkIGFjdHVhbGx5ICpleHBlY3QqIERhdGFTb3VyY2UuZGlzcG9zZSB0byBpbnZva2UgY29uZmln
LmRpc3Bvc2UgCj4gYW5kIERhdGFPYmplY3QuZGlzcG9zZSBub3QgaGF2aW5nIGFueXRoaW5nIHRv
IGRvIHdpdGggaXQuCj4gCgpPSy4gSSB0aG91Z2h0IHNvIHRvby4KClNvLi4uIChsaXN0IGFmdGVy
IHN1Z2dlc3Rpb25zKQoxLiBBZGQgYSBkaXNwb3NlKCkgbWV0aG9kIHRvIHRoZSBSREZDb250YWlu
ZXIuCjIuIEFkZCBhIGRpc3Bvc2UoKSBtZXRob2QgdG8gdGhlIERhdGFTb3VyY2UKMy4gSGF2ZSBE
YXRhT2JqZWN0LmRpc3Bvc2UoKSBpbnZva2UgbWV0YWRhdGEuZGlzcG9zZSwgYnV0IG5vdCAKc291
cmNlLmRpc3Bvc2UoKQo0LiBNb2RpZnkgdGhlIGRlZmF1bHQgUkRGMkdvUkRGQ29udGFpbmVyIGlt
cGxlbWVudGF0aW9uLgogICAgYS4gaW50cm9kdWNlIGEgaXNNb2RlbFNoYXJlZCBhdHRyaWJ1dGUg
KHdpdGggZ2V0dGVyIGFuZCBzZXR0ZXIpCiAgICAgICBtYWtlIGl0IE5PVCBzaGFyZWQgYnkgZGVm
YXVsdAogICAgYi4gaW1wbGVtZW50IHRoZSBkaXNwb3NlKCkgbWV0aG9kIGluIGEgd2F5IHRoYXQg
aXQgd291bGQgY2xvc2UKICAgICAgIHRoZSBtb2RlbCBpZiBpdCdzIE5PVCBzaGFyZWQsIGFuZCBE
T04nVCBjbG9zZSBpdCBpZiBpdCdzIHNoYXJlZAogICAgYy4gYWRkIGFkZGl0aW9uYWwgcGFyYW1l
dGVyIHRvIHRoZSBjb25zdHJ1Y3RvcnMsIHRoYXQgd291bGQgc2V0IGlmCiAgICAgICB0aGUgbW9k
ZWwgaXMgc2hhcmVkIG9yIG5vdC4KICAgIGQuIEhhdmUgYWxsIG1ldGhvZHMgY2hlY2sgaWYgYSBt
b2RlbCBoYXMgYWxyZWFkeSBiZWVuIGNsb3NlZCBhbmQKICAgICAgIHRocm93IGFuIElsbGVnYWxT
dGF0ZUV4Y2VwdGlvbiBpZiBpdCBoYXMuCjUuIE1vZGlmeSB0aGUgc3BlY2lmaWMgU2VzYW1lUkRG
Q29udGFpbmVyIC0gbGV0IHRoZSB1c2VyIGRlY2lkZSBpZiB0aGUKICAgIHVuZGVybHlpbmcgbW9k
ZWwgaXMgdG8gYmUgc2hhcmVkIG9yIG5vdC4KNi4gTW9kaWZ5IHRoZSB0ZXN0cyBhbmQgZXhhbXBs
ZXMgdG8gdXNlIHRoaXMgYXBwcm9hY2guCgogPgo+IEdvb2QgdG8gaGVhciEgU28gdGhpcyBpcyBh
bGwgYmFzZWQgb24gU2VzYW1lIDIgYWxwaGEgNCBhbHJlYWR5Pwo+IAoKWWVzLiBCZW5qYW1pbiBI
ZWl0bWFubiBoYXMgdXBkYXRlZCB0aGUgcmRmMmdvIGRyaXZlciBmb3IgdGhlIGFscGhhNC4gSSAK
ZGlkIHRoZSBzYW1lIHdpdGggdGhlIHNlc2FtZS1kZXBlbmRlbnQgcGFydHMgb2YgYXBlcnR1cmUu
IFRoZSBkZWNpc2lvbiAKaXMgc3RpbGwgdG8gYmUgbWFkZSBpZiB3ZSB3b3VsZCBsaWtlIHRvIGxl
YXZlIHRoZSBSZXBvc2l0b3J5QWNjZXNzRGF0YSAKYW5kIFJlcG9zaXRvcnlVdGlsIGlmIHdlIGFs
cmVhZHkgaGF2ZSB0aGUgTW9kZWxBY2Nlc3NEYXRhIGFuZCBNb2RlbFV0aWwuIApMaWtld2lzZSwg
dGhlIHF1ZXN0aW9uIHJlbWFpbnMgaWYgd2UgbGVhdmUgdGhlIGZpbGVpbnNwZWN0b3Igc3dpbmcg
CmV4YW1wbGUgYXMgaXQgaXMsIG9yIHRyeSB0byByZXdyaXRlIGl0IHRvIHVzZSByZGYyZ28uLi4K
CkkgaG9wZSB0byBkbyBpdCBhbGwgdG9kYXkuIFdlIGNvdWxkIG1ha2UgYSBiaWcgbWVyZ2UgbmV4
dCB3ZWVrIGFuZCAKY29udGludWUgd29ya2luZyBvbiBPU0dJLgoKQW50b25pIE15bGthCmFudG9u
aS5teWxrYUBkZmtpLnVuaS1rbC5kZQoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQpVc2luZyBUb21jYXQgYnV0
IG5lZWQgdG8gZG8gbW9yZT8gTmVlZCB0byBzdXBwb3J0IHdlYiBzZXJ2aWNlcywgc2VjdXJpdHk/
CkdldCBzdHVmZiBkb25lIHF1aWNrbHkgd2l0aCBwcmUtaW50ZWdyYXRlZCB0ZWNobm9sb2d5IHRv
IG1ha2UgeW91ciBqb2IgZWFzaWVyCkRvd25sb2FkIElCTSBXZWJTcGhlcmUgQXBwbGljYXRpb24g
U2VydmVyIHYuMS4wLjEgYmFzZWQgb24gQXBhY2hlIEdlcm9uaW1vCmh0dHA6Ly9zZWwuYXMtdXMu
ZmFsa2FnLm5ldC9zZWw/Y21kPWxuayZraWQ9MTIwNzA5JmJpZD0yNjMwNTcmZGF0PTEyMTY0Mgpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpBcGVydHVyZS1k
ZXZlbCBtYWlsaW5nIGxpc3QKQXBlcnR1cmUtZGV2ZWxAbGlzdHMuc291cmNlZm9yZ2UubmV0Cmh0
dHBzOi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL2FwZXJ0dXJlLWRldmVs
Cg==

From - Fri Nov 10 11:56:57 2006
X-Account-Key: account3
X-UIDL: 0000ed5603ba8bb6
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:54444 "EHLO
	lists-outbound.sourceforge.net") by ps28.test.onet.pl with ESMTP
	id <S2250252AbWKJKgj>; Fri, 10 Nov 2006 11:36:39 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 1336212B45; Fri, 10 Nov 2006 02:36:38 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiTkR-0005ip-2K for aperture-devel@lists.sourceforge.net;
	Fri, 10 Nov 2006 02:36:35 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiTkR-0008M4-KU
	for aperture-devel@lists.sourceforge.net;
	Fri, 10 Nov 2006 02:36:36 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kAAAaWFZ018712; Fri, 10 Nov 2006 11:36:32 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kAAAaWY17582; Fri, 10 Nov 2006 11:36:32 +0100 (MET)
Received: from [192.168.41.94] (gast-4104.kl.dfki.de [192.168.41.94])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kAAAaVJK029385; Fri, 10 Nov 2006 11:36:31 +0100 (CET)
Message-ID: <45545633.30809@dfki.uni-kl.de>
Date:	Fri, 10 Nov 2006 11:36:35 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Leo Sauermann <leo.sauermann@dfki.de>,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45533FC5.5020505@dfki.uni-kl.de> <455380BD.6050600@dfki.de>
In-Reply-To: <455380BD.6050600@dfki.de>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kAAAaWFZ018712
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

TGVvIFNhdWVybWFubiBuYXBpc2HFgihhKToKPj4oSXMgaXQgYXQgYWxsIHBvc3NpYmxlIGluIE9T
R0kgZm9yIHRoZSBidW5kbGVzIHRvIHVzZQo+PiBjbGFzc2VzIGZyb20gZXh0ZXJuYWwgamFycywg
b3IgZXhwb3J0IGludGVyZmFjZXMgZnJvbSBleHRlcm5hbCBqYXJzPykKPj4gICAKPiB0aGUgYnVu
ZGxlcyBFeHBvcnQgY2xhc3NwYXRocy9wYWNrYWdlcywgYW5kIHlvdSBjYW4gaW5zdGFudGlhdGUg
dGhlIAo+IGNsYXNzZXMgZnJvbSBhbnkgb2h0ZXIgYnVuZGxlIGlmIHlvdSBjb3JyZWNsdHkgaW1w
b3J0IHRoZXNlIAo+IGRlcGVuZGVuY2llcy4gdHJ5IHRvIGltcG9ydCBidW5kbGVzIG9yIGZlYXR1
cmVzIGluc3RlYWQgb2YgaW1wb3J0aW5nIAo+IHBhY2thZ2VzIC0gc2VlIHRoZSBlY2xpcHNlIHBs
dWdpbi1lZGl0b3IgKHdoY2loIGVxdWFscyB0byBhIGJ1bmRsZSAKPiBlZGl0b3IpIGZvciBhIGd1
aSB0byBlZGl0IG1hbmlmZXN0IGZpbGVzLgo+IAoKSSBrbm93LiBJIG9ubHkgd2FudGVkIHRvIGZp
bmQgb3V0IGlmIHdlIGFyZSB0byBtYWtlIGFuIE9TR0kgYnVuZGxlIGZyb20gCnJkZjJnby5qYXIs
IHJkZjJnby1zZXNhbWUuamFyIGFuZCBzZXNhbWUtMi4wLW9uZWphci5qYXI/IEFsbCBvZiB0aGVt
IAp3b3VsZCBiZSBuZWNlc3NhcnkgZm9yIHRlc3RpbmcuLi4KCkFudG9uaSBNeWxrYQphbnRvbmku
bXlsa2FAZGZraS51bmkta2wuZGUKCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KVXNpbmcgVG9tY2F0IGJ1dCBu
ZWVkIHRvIGRvIG1vcmU/IE5lZWQgdG8gc3VwcG9ydCB3ZWIgc2VydmljZXMsIHNlY3VyaXR5PwpH
ZXQgc3R1ZmYgZG9uZSBxdWlja2x5IHdpdGggcHJlLWludGVncmF0ZWQgdGVjaG5vbG9neSB0byBt
YWtlIHlvdXIgam9iIGVhc2llcgpEb3dubG9hZCBJQk0gV2ViU3BoZXJlIEFwcGxpY2F0aW9uIFNl
cnZlciB2LjEuMC4xIGJhc2VkIG9uIEFwYWNoZSBHZXJvbmltbwpodHRwOi8vc2VsLmFzLXVzLmZh
bGthZy5uZXQvc2VsP2NtZD1sbmsma2lkPTEyMDcwOSZiaWQ9MjYzMDU3JmRhdD0xMjE2NDIKX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQXBlcnR1cmUtZGV2
ZWwgbWFpbGluZyBsaXN0CkFwZXJ0dXJlLWRldmVsQGxpc3RzLnNvdXJjZWZvcmdlLm5ldApodHRw
czovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9hcGVydHVyZS1kZXZlbAo=

From - Fri Nov 10 13:03:33 2006
X-Account-Key: account3
X-UIDL: 0000ed5603baa204
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:35970 "EHLO
	lists-outbound.sourceforge.net") by ps8.test.onet.pl with ESMTP
	id <S5625873AbWKJLQ2>; Fri, 10 Nov 2006 12:16:28 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 7005312225; Fri, 10 Nov 2006 03:16:27 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiUMy-0000pj-Ol for aperture-devel@lists.sourceforge.net;
	Fri, 10 Nov 2006 03:16:24 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiUMz-0001dK-Mm
	for aperture-devel@lists.sourceforge.net;
	Fri, 10 Nov 2006 03:16:26 -0800
Received: (qmail 11463 invoked from network); 10 Nov 2006 12:16:18 +0100
Received: from 5353a894.cable.casema.nl (HELO ?83.83.168.148?) (83.83.168.148)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	10 Nov 2006 12:16:18 +0100
Message-ID: <45545F80.6020409@aduna-software.com>
Date:	Fri, 10 Nov 2006 12:16:16 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45533FC5.5020505@dfki.uni-kl.de>
In-Reply-To: <45533FC5.5020505@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

What I see here is a proposal for organizing stuff in bundles but what 
is lacking IMHO is a rationale for why you draw the lines there. If I 
understand you correctly, all Aperture APIs and related stuff would go 
into a single bundle, right? But what does a MimeTypeIdentifier API have 
to do with a Crawler API, except that they are both part of the Aperture 
project? Why not put them into their own bundles?

To be honest, I don't feel like I have very strong ammunition to shoot 
at your proposal with ;) or solid, undeniable arguments for my own 
proposal. I actually start to feel that the chosen granularity might 
depend a lot on your application, how much you use of Aperture, to which 
extent you want to be able to tweak your installed application, etc. As 
long as the code and build scripts are neatly organized, I expect people 
can always create a different setup of bundles for their own use if they 
want to.

Just one more argument for fine-grained bundles ;) : each bundle can 
have its own private classpath. This makes it possible to e.g. create an 
extractor for a specific MIME type that contains all its third party 
dependencies, without necessarily exposing those dependencies to the 
rest of the application. This may prevent certain class loading 
conflicts. For example the bibtex2rdf stuff we've seen last week bundles 
its own XML parser, I believe including classes that implement core Java 
factory interfaces (SAX factories, etc.). Imagine that for some reason 
you want to use this jar as is, adding such a jar file to a regular Java 
application may cause a lot of hard to debug problems when for example 
the bundled XML parser is buggy and gets transparently used in other 
parts of the application as well. Seeing how Aperture's third party 
dependencies are expanding and that itself is still meant to be part of 
a bigger application, this may become an issue in the future.

However, more important IMO are the BundleActivators, as they require 
some programming as well as intimate knowledge of Aperture's internals 
and therefore you want to create them once and for all. Am I right in 
that the construction of the BundleActivators does not depend on the 
bundle granularity that you choose? Or can a bundle only have a single 
BundleActivator? In that case, perhaps BundleActivators can be chained, 
so that for example you have a single ExtractorsBundleActivator that on 
its turn invokes a HtmlBundleActivator, a PdfBundleActivator, etc.? This 
would then support both the "1 extractor impl bundle" strategy and the 
"1 bundle per extractor impl" strategy.

Again, my knowledge of OSGi is limited so feel free to say that this is 
all nonsense or has all been solved before.

Chris
--

Antoni Mylka wrote:
> I've gone through some tutorials and I see it as follows.
> 
> We would need one core aperture bundle. It would contain all interfaces 
> and vocabulary classes. I would exclude following packages from this 
> core bundle:
> accessor.file
> accessor.http
> addressbook
> crawler.filesystem
> crawler.ical
> crawler.imap
> crawler.web
> datasource.filesystem
> datasource.ical
> datasource.imap
> datasource.web
> all extractor subpackages except extractor.impl
> hypertext.linkextractor.html
> mime.identifier.magic
> opener.file
> opener.http
> outlook
> 
> Security, util and vocabulary could stay. This core bundle would 
> register following services:
> DataAccessorRegistry
> CrawlerRegistry
> DataSourceRegistry
> ExtractorRegistry
> LinkExtractorRegistry
> MimeTypeIdentifierRegistry
> DataOpenerRegistry
> 
> The implementations of these interfaces could all be placed in one big 
> bundle, or in separate bundles, even if each bundle would contain a 
> single class. The activators of these implementation bundles would 
> register all implementations with appropriate registries.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Fri Nov 10 13:56:01 2006
X-Account-Key: account3
X-UIDL: 0000ed5603baddcd
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:22146 "EHLO
	lists-outbound.sourceforge.net") by ps23.test.onet.pl with ESMTP
	id <S5854198AbWKJMpA>; Fri, 10 Nov 2006 13:45:00 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 42DCB12F70; Fri, 10 Nov 2006 04:44:56 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiVkb-0000bI-FI for aperture-devel@lists.sourceforge.net;
	Fri, 10 Nov 2006 04:44:53 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiVkc-0000Bs-5Y
	for aperture-devel@lists.sourceforge.net;
	Fri, 10 Nov 2006 04:44:54 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kAACinP3009388; Fri, 10 Nov 2006 13:44:49 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kAACinY24232; Fri, 10 Nov 2006 13:44:49 +0100 (MET)
Received: from [192.168.41.94] (gast-4104.kl.dfki.de [192.168.41.94])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kAACilkB005193; Fri, 10 Nov 2006 13:44:47 +0100 (CET)
Message-ID: <45547444.6080703@dfki.uni-kl.de>
Date:	Fri, 10 Nov 2006 13:44:52 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45533FC5.5020505@dfki.uni-kl.de>
	<45545F80.6020409@aduna-software.com>
In-Reply-To: <45545F80.6020409@aduna-software.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kAACinP3009388
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Q2hyaXN0aWFhbiBGbHVpdCBuYXBpc2HFgihhKToKPiBXaGF0IEkgc2VlIGhlcmUgaXMgYSBwcm9w
b3NhbCBmb3Igb3JnYW5pemluZyBzdHVmZiBpbiBidW5kbGVzIGJ1dCB3aGF0IAo+IGlzIGxhY2tp
bmcgSU1ITyBpcyBhIHJhdGlvbmFsZSBmb3Igd2h5IHlvdSBkcmF3IHRoZSBsaW5lcyB0aGVyZS4g
SWYgSSAKPiB1bmRlcnN0YW5kIHlvdSBjb3JyZWN0bHksIGFsbCBBcGVydHVyZSBBUElzIGFuZCBy
ZWxhdGVkIHN0dWZmIHdvdWxkIGdvIAo+IGludG8gYSBzaW5nbGUgYnVuZGxlLCByaWdodD8gQnV0
IHdoYXQgZG9lcyBhIE1pbWVUeXBlSWRlbnRpZmllciBBUEkgaGF2ZSAKPiB0byBkbyB3aXRoIGEg
Q3Jhd2xlciBBUEksIGV4Y2VwdCB0aGF0IHRoZXkgYXJlIGJvdGggcGFydCBvZiB0aGUgQXBlcnR1
cmUgCj4gcHJvamVjdD8gV2h5IG5vdCBwdXQgdGhlbSBpbnRvIHRoZWlyIG93biBidW5kbGVzPwoK
MS4gTGV0J3MgYXNzdW1lIHdlIGRvIGFzIHlvdSB3cml0ZToKYS4gd2Ugc3RpbGwgbmVlZCBhIGNv
cmUgYnVuZGxlIHdpdGggUkRGQ29udGFpbmVyICh1c2VkIGJ5IGFsbCksIApWb2NhYnVsYXJ5IChB
dCBsZWFzdCBEQVRBKSwgRGF0YVNvdXJjZSwgVXRpbHMsIHNlY3VyaXR5IGV0Yy4KYi4gYXJvdW5k
IHRoaXMgb25lLCB3ZSB3b3VsZCBuZWVkIHNldmVuICdodWInIGJ1bmRsZXMgdGhhdCB3b3VsZCBj
b250YWluIAp0d28gb3IgdGhyZWUgY2xhc3NlcyBhbmQgZXhwb3NlIHJlZ2lzdHJpZXM6CiA+PiBE
YXRhQWNjZXNzb3JSZWdpc3RyeQogPj4gQ3Jhd2xlclJlZ2lzdHJ5CiA+PiBEYXRhU291cmNlUmVn
aXN0cnkKID4+IEV4dHJhY3RvclJlZ2lzdHJ5CiA+PiBMaW5rRXh0cmFjdG9yUmVnaXN0cnkKID4+
IE1pbWVUeXBlSWRlbnRpZmllclJlZ2lzdHJ5CiA+PiBEYXRhT3BlbmVyUmVnaXN0cnkKCmMuIGFy
b3VuZCBldmVyeSAnaHViJyBidW5kbGUgd2UnZCBuZWVkIGEgc2V0IG9mIGltcGxlbWVudGF0aW9u
IGJ1bmRsZXMuIApTb21lIG9mIHRoZW0gd291bGQgZGVwZW5kIG9ubHkgb24gY29yZSBhbmQgdGhl
IGFwcHJvcHJpYXRlICdodWInIGJ1dCAKc29tZSAobGlrZSB0aGUgRmlsZVN5c3RlbUNyYXdsZXIp
IHdvdWxkIGRlcGVuZCBvbiB0aGUgY29yZSBhbmQgQUxMIAoobWF5YmUgZXhjZXB0IGRhdGFPcGVu
ZXIgcmVnaXN0cnkpLiBUaGUgRGVwZW5kZW5jeSBncmFwaCB3b3VsZCBsb29rIGxpa2UgCnNwYWdo
ZXR0aS4KCk5vdyBsZXQncyBhc3N1bWUgd2Ugd2FudCB0byB3cml0ZSBhIEZpbGVTeXN0ZW1DcmF3
bGVyIGFuZCBpbXBsZW1lbnQgaXQgCmFzIGEgc2VwYXJhdGUgYnVuZGxlLiBJIHdpbGwgYmUgbXVj
aCBtb3JlIGNvbXBsaWNhdGVkIHRoYW4gaXQgaXMgbm93LCAKYmVjYXVzZSBpdCB3b24ndCBiZSBh
YmxlIHRvIGFzc3VtZSB0aGF0IEFjY2Vzc29yUmVnaXN0cmllcyBhbmQgRXh0cmFjdG9yIApSZWdp
c3RyaWVzIGFyZSBhdmFpbGFibGUuIEl0IHdpbGwgaGF2ZSB0byBoYW5kbGUgY2FzZXMgd2hlbiBh
biBFeHRyYWN0b3IgClJlZ2lzdHJ5IGJlY29tZXMgdW5hdmFpbGFibGUgaW4gdGhlIG1pZGRsZSBv
ZiBjcmF3bGluZy4gSXQgd291bGQgbmVlZCB0byAKaW1wbGVtZW50IGF0IGxlYXN0IHR3byBTZXJ2
aWNlVHJhY2tlcnMgYW5kIGhhbmRsZSBhcmJpdHJhcnkgaW50ZXJhY3Rpb25zIApiZXR3ZWVuIHNl
cnZpY2VzIGFwcGVhcmluZyBhbmQgZGlzYXBwZWFyaW5nLiBBbiBhcHBsaWNhdGlvbiB0aGF0IHdv
dWxkIApsaWtlIHRvIHVzZSB0d28gb3IgdGhyZWUgZWxlbWVudHMgb2YgYXBlcnR1cmUgKHRoYXQg
aXMgQWNjZXNzb3IgYW5kIApFeHRyYWN0b3IsIG9yIGEgQ3Jhd2xlciB0aGF0IHVzZXMgQWNjZXNz
b3JzIG9yIEV4dHJhY3RvcnMpIHdvdWxkIG5lZWQgdG8gCmJlIHN1cmUgdGhhdCBhbGwgb2YgdGhl
c2UgYXJlIHByZXNlbnQuCgpJdCB3b3VsZCBiZSBtdWNoIGVhc2llciBmb3IgYWxsIHRvIGJlIGFi
bGUgdG8gYXNzdW1lIHRoYXQgYWxsIHJlZ2lzdHJpZXMgCmFyZSBwcmVzZW50IGF0IGFsbCB0aW1l
cy4gKG9yIG5vdCA6LSkgV3JpdGluZyBjcmF3bGVycyB0aGF0IHVzZSAKQWNjZXNzb3JzLCBFeHRy
YWN0b3JzIG9yIExpbmtFeHRyYWN0b3JzIHdvdWxkIGJlIG11Y2ggZWFzaWVyLiBUaGUgCm1hbmFn
ZW1lbnQgb2YgZGVwZW5kZW5jaWVzIHdvdWxkIGJlIGVhc2llci4KCj4gSnVzdCBvbmUgbW9yZSBh
cmd1bWVudCBmb3IgZmluZS1ncmFpbmVkIGJ1bmRsZXMgOykgOiBlYWNoIGJ1bmRsZSBjYW4gCj4g
aGF2ZSBpdHMgb3duIHByaXZhdGUgY2xhc3NwYXRoLiBUaGlzIG1ha2VzIGl0IHBvc3NpYmxlIHRv
IGUuZy4gY3JlYXRlIGFuIAo+IGV4dHJhY3RvciBmb3IgYSBzcGVjaWZpYyBNSU1FIHR5cGUgdGhh
dCBjb250YWlucyBhbGwgaXRzIHRoaXJkIHBhcnR5IAo+IGRlcGVuZGVuY2llcywgd2l0aG91dCBu
ZWNlc3NhcmlseSBleHBvc2luZyB0aG9zZSBkZXBlbmRlbmNpZXMgdG8gdGhlIAo+IHJlc3Qgb2Yg
dGhlIGFwcGxpY2F0aW9uLiAKClN1cmUuIEV2ZXJ5IGltcGxlbWVudGF0aW9uIG9mIGEgY3Jhd2xl
ciwgZXh0cmFjdG9yIG9yIHdoYXRldmVyIGNvdWxkIApzaGlwIGFzIGEgc2VwYXJhdGUgYnVuZGxl
IHdpdGggaXQncyBkZXBlbmRlbmNpZXMgaW5jbHVkZWQuIEFzIHN1Y2ggd2UgCmNvdWxkIG1hbmFn
ZSB0aGUgc2V0IG9mIGF2YWlsYWJsZSBpbXBsZW1lbnRhdGlvbnMgYXQgd2lsbC4gCkltcGxlbWVu
dGF0aW9ucyBjb3VsZCBiZSB1cGRhdGVkIGluZGVwZW5kZW50bHkuIFRoZSBjb3JlIGJ1bmRsZSBj
b3VsZCAKcmVtYWluIHN0YWJsZS4gVGhlIGNvcmUgaW50ZXJmYWNlcyB3b3VsZG4ndCBjaGFuZ2Ug
dGhhdCBvZnRlbi4KCldlIHdvdWxkIGdldCBhIHNpbXBsZSwgc3Rhci1saWtlIGRlcGVuZGVuY3kg
Z3JhcGguIFdpdGggY29yZSwgcmRmMmdvIGFuZCAKc29tZSBjb250YWluZXIgb3IgTW9kZWwgZmFj
dG9yeSBpbiB0aGUgbWlkZGxlLgoKPiBIb3dldmVyLCBtb3JlIGltcG9ydGFudCBJTU8gYXJlIHRo
ZSBCdW5kbGVBY3RpdmF0b3JzLCBhcyB0aGV5IHJlcXVpcmUgCj4gc29tZSBwcm9ncmFtbWluZyBh
cyB3ZWxsIGFzIGludGltYXRlIGtub3dsZWRnZSBvZiBBcGVydHVyZSdzIGludGVybmFscyAKPiBh
bmQgdGhlcmVmb3JlIHlvdSB3YW50IHRvIGNyZWF0ZSB0aGVtIG9uY2UgYW5kIGZvciBhbGwuIEFt
IEkgcmlnaHQgaW4gCj4gdGhhdCB0aGUgY29uc3RydWN0aW9uIG9mIHRoZSBCdW5kbGVBY3RpdmF0
b3JzIGRvZXMgbm90IGRlcGVuZCBvbiB0aGUgCj4gYnVuZGxlIGdyYW51bGFyaXR5IHRoYXQgeW91
IGNob29zZT8gT3IgY2FuIGEgYnVuZGxlIG9ubHkgaGF2ZSBhIHNpbmdsZSAKPiBCdW5kbGVBY3Rp
dmF0b3I/IEluIHRoYXQgY2FzZSwgcGVyaGFwcyBCdW5kbGVBY3RpdmF0b3JzIGNhbiBiZSBjaGFp
bmVkLCAKPiBzbyB0aGF0IGZvciBleGFtcGxlIHlvdSBoYXZlIGEgc2luZ2xlIEV4dHJhY3RvcnNC
dW5kbGVBY3RpdmF0b3IgdGhhdCBvbiAKPiBpdHMgdHVybiBpbnZva2VzIGEgSHRtbEJ1bmRsZUFj
dGl2YXRvciwgYSBQZGZCdW5kbGVBY3RpdmF0b3IsIGV0Yy4/IFRoaXMgCj4gd291bGQgdGhlbiBz
dXBwb3J0IGJvdGggdGhlICIxIGV4dHJhY3RvciBpbXBsIGJ1bmRsZSIgc3RyYXRlZ3kgYW5kIHRo
ZSAKPiAiMSBidW5kbGUgcGVyIGV4dHJhY3RvciBpbXBsIiBzdHJhdGVneS4KCkkgYWN0dWFsbHkg
dGhpbmsgaXQgaXMgYSBnb29kIGlkZWEuCgo+IEFnYWluLCBteSBrbm93bGVkZ2Ugb2YgT1NHaSBp
cyBsaW1pdGVkIHNvIGZlZWwgZnJlZSB0byBzYXkgdGhhdCB0aGlzIGlzIAo+IGFsbCBub25zZW5z
ZSBvciBoYXMgYWxsIGJlZW4gc29sdmVkIGJlZm9yZS4KPiAKTXkga25vd2xlZGdlIGlzIGxpbWl0
ZWQgdG8gYSAyNS1wYWdlIHR1dG9yaWFsIDotKS4gSSB3b3VsZCBnbGFkbHkgaGVhciAKZnJvbSB0
aG9zZSwgd2hvIGhhdmUgbW9yZSBleHBlcmllbmNlIHdpdGggT1NHSS4KCkFudG9uaSBNeWxrYQph
bnRvbmkubXlsa2FAZGZraS51bmkta2wuZGUKCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KVXNpbmcgVG9tY2F0
IGJ1dCBuZWVkIHRvIGRvIG1vcmU/IE5lZWQgdG8gc3VwcG9ydCB3ZWIgc2VydmljZXMsIHNlY3Vy
aXR5PwpHZXQgc3R1ZmYgZG9uZSBxdWlja2x5IHdpdGggcHJlLWludGVncmF0ZWQgdGVjaG5vbG9n
eSB0byBtYWtlIHlvdXIgam9iIGVhc2llcgpEb3dubG9hZCBJQk0gV2ViU3BoZXJlIEFwcGxpY2F0
aW9uIFNlcnZlciB2LjEuMC4xIGJhc2VkIG9uIEFwYWNoZSBHZXJvbmltbwpodHRwOi8vc2VsLmFz
LXVzLmZhbGthZy5uZXQvc2VsP2NtZD1sbmsma2lkPTEyMDcwOSZiaWQ9MjYzMDU3JmRhdD0xMjE2
NDIKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQXBlcnR1
cmUtZGV2ZWwgbWFpbGluZyBsaXN0CkFwZXJ0dXJlLWRldmVsQGxpc3RzLnNvdXJjZWZvcmdlLm5l
dApodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9hcGVydHVyZS1k
ZXZlbAo=

From - Sat Nov 11 13:06:09 2006
X-Account-Key: account3
X-UIDL: 0000ed5603bb8cd6
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:3268 "EHLO
	lists-outbound.sourceforge.net") by ps18.test.onet.pl with ESMTP
	id <S6154423AbWKJKwE>; Fri, 10 Nov 2006 11:52:04 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id D09C012A95; Fri, 10 Nov 2006 02:51:57 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiTzG-00072D-KL for aperture-devel@lists.sourceforge.net;
	Fri, 10 Nov 2006 02:51:54 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiTzG-0003tG-Jb
	for aperture-devel@lists.sourceforge.net;
	Fri, 10 Nov 2006 02:51:55 -0800
Received: (qmail 11000 invoked from network); 10 Nov 2006 11:51:43 +0100
Received: from 5353a894.cable.casema.nl (HELO ?83.83.168.148?) (83.83.168.148)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	10 Nov 2006 11:51:43 +0100
Message-ID: <455459BE.5070909@aduna-software.com>
Date:	Fri, 10 Nov 2006 11:51:42 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F3C76.5060307@dfki.uni-kl.de>	<4551FAF4.5080309@aduna-software.com>	<45533875.30002@dfki.uni-kl.de>
	<45535399.5070600@aduna-software.com>
	<4554552E.1000201@dfki.uni-kl.de>
In-Reply-To: <4554552E.1000201@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Antoni Mylka wrote:
> So... (list after suggestions)
> 1. Add a dispose() method to the RDFContainer.
> 2. Add a dispose() method to the DataSource
> 3. Have DataObject.dispose() invoke metadata.dispose, but not 
> source.dispose()
> 4. Modify the default RDF2GoRDFContainer implementation.
>    a. introduce a isModelShared attribute (with getter and setter)
>       make it NOT shared by default
>    b. implement the dispose() method in a way that it would close
>       the model if it's NOT shared, and DON'T close it if it's shared
>    c. add additional parameter to the constructors, that would set if
>       the model is shared or not.
>    d. Have all methods check if a model has already been closed and
>       throw an IllegalStateException if it has.
> 5. Modify the specific SesameRDFContainer - let the user decide if the
>    underlying model is to be shared or not.
> 6. Modify the tests and examples to use this approach.

Sounds great! Perhaps await Leo's and Gunnar's replies to see what they 
have to say but I'm rather confident that this approach will fit 
everyone's purposes.

> I hope to do it all today. We could make a big merge next week

Would be very nice, we would pick up the new code very soon and update 
our code to the latest Aperture and Sesame alpha 4, so it will get 
thoroughly tested soon after.


Chris
--


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Nov 13 02:23:28 2006
X-Account-Key: account3
X-UIDL: 0000ed5603c2f033
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:60862 "EHLO
	lists-outbound.sourceforge.net") by ps2.test.onet.pl with ESMTP
	id <S1572708AbWKLSNk>; Sun, 12 Nov 2006 19:13:40 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id EECA812911; Sun, 12 Nov 2006 10:13:30 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GjJpO-0002Xs-CC for aperture-devel@lists.sourceforge.net;
	Sun, 12 Nov 2006 10:13:10 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GjJpF-0006kV-Nv
	for aperture-devel@lists.sourceforge.net;
	Sun, 12 Nov 2006 10:13:11 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kACICu0d008604; Sun, 12 Nov 2006 19:12:56 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kACICuY20358; Sun, 12 Nov 2006 19:12:56 +0100 (MET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kACICre5015688; Sun, 12 Nov 2006 19:12:55 +0100 (CET)
Message-ID: <45576422.7030300@dfki.de>
Date:	Sun, 12 Nov 2006 19:12:50 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <45533FC5.5020505@dfki.uni-kl.de>
	<45545F80.6020409@aduna-software.com>
In-Reply-To: <45545F80.6020409@aduna-software.com>
X-Spam-Score: 0.3 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.3 HTML_10_20             BODY: Message is 10% to 20% HTML
	0.0 HTML_TITLE_EMPTY       BODY: HTML title contains no text
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1573299981=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============1573299981==
Content-Type: multipart/alternative;
	boundary="------------060503050005080802000408"

This is a multi-part message in MIME format.
--------------060503050005080802000408
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

It depends on the application,
and bundling each mimetype detector is much too granular. putting single 
classes in bundles is out of question.

you may want to view it from the aperture user's side, not from the 
aperture developers side

for the aperture user, he is only interested in getting aperture and 
make it run, so the understanding of the details inside the impl is not 
needed there.

The activators: they usually contain only a few lines of code and should 
be simple to understand.
Stacking them or combining them adds just another framework of a framework.

We will go for the simple way first, if we find problems we worry then.

as we all don't know much about OSGI, I would keep it as simple as possible.



greetings
Leo


Es begab sich aber da Christiaan Fluit zur rechten Zeit 10.11.2006 12:16 
folgendes schrieb:
> What I see here is a proposal for organizing stuff in bundles but what 
> is lacking IMHO is a rationale for why you draw the lines there. If I 
> understand you correctly, all Aperture APIs and related stuff would go 
> into a single bundle, right? But what does a MimeTypeIdentifier API have 
> to do with a Crawler API, except that they are both part of the Aperture 
> project? Why not put them into their own bundles?
>
> To be honest, I don't feel like I have very strong ammunition to shoot 
> at your proposal with ;) or solid, undeniable arguments for my own 
> proposal. I actually start to feel that the chosen granularity might 
> depend a lot on your application, how much you use of Aperture, to which 
> extent you want to be able to tweak your installed application, etc. As 
> long as the code and build scripts are neatly organized, I expect people 
> can always create a different setup of bundles for their own use if they 
> want to.
>
> Just one more argument for fine-grained bundles ;) : each bundle can 
> have its own private classpath. This makes it possible to e.g. create an 
> extractor for a specific MIME type that contains all its third party 
> dependencies, without necessarily exposing those dependencies to the 
> rest of the application. This may prevent certain class loading 
> conflicts. For example the bibtex2rdf stuff we've seen last week bundles 
> its own XML parser, I believe including classes that implement core Java 
> factory interfaces (SAX factories, etc.). Imagine that for some reason 
> you want to use this jar as is, adding such a jar file to a regular Java 
> application may cause a lot of hard to debug problems when for example 
> the bundled XML parser is buggy and gets transparently used in other 
> parts of the application as well. Seeing how Aperture's third party 
> dependencies are expanding and that itself is still meant to be part of 
> a bigger application, this may become an issue in the future.
>
> However, more important IMO are the BundleActivators, as they require 
> some programming as well as intimate knowledge of Aperture's internals 
> and therefore you want to create them once and for all. Am I right in 
> that the construction of the BundleActivators does not depend on the 
> bundle granularity that you choose? Or can a bundle only have a single 
> BundleActivator? In that case, perhaps BundleActivators can be chained, 
> so that for example you have a single ExtractorsBundleActivator that on 
> its turn invokes a HtmlBundleActivator, a PdfBundleActivator, etc.? This 
> would then support both the "1 extractor impl bundle" strategy and the 
> "1 bundle per extractor impl" strategy.
>
> Again, my knowledge of OSGi is limited so feel free to say that this is 
> all nonsense or has all been solved before.
>
> Chris
> --
>
> Antoni Mylka wrote:
>   
>> I've gone through some tutorials and I see it as follows.
>>
>> We would need one core aperture bundle. It would contain all interfaces 
>> and vocabulary classes. I would exclude following packages from this 
>> core bundle:
>> accessor.file
>> accessor.http
>> addressbook
>> crawler.filesystem
>> crawler.ical
>> crawler.imap
>> crawler.web
>> datasource.filesystem
>> datasource.ical
>> datasource.imap
>> datasource.web
>> all extractor subpackages except extractor.impl
>> hypertext.linkextractor.html
>> mime.identifier.magic
>> opener.file
>> opener.http
>> outlook
>>
>> Security, util and vocabulary could stay. This core bundle would 
>> register following services:
>> DataAccessorRegistry
>> CrawlerRegistry
>> DataSourceRegistry
>> ExtractorRegistry
>> LinkExtractorRegistry
>> MimeTypeIdentifierRegistry
>> DataOpenerRegistry
>>
>> The implementations of these interfaces could all be placed in one big 
>> bundle, or in separate bundles, even if each bundle would contain a 
>> single class. The activators of these implementation bundles would 
>> register all implementations with appropriate registries.
>>     
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------060503050005080802000408
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
It depends on the application,<br>
and bundling each mimetype detector is much too granular. putting
single classes in bundles is out of question.<br>
<br>
you may want to view it from the aperture user's side, not from the
aperture developers side<br>
<br>
for the aperture user, he is only interested in getting aperture and
make it run, so the understanding of the details inside the impl is not
needed there.<br>
<br>
The activators: they usually contain only a few lines of code and
should be simple to understand.<br>
Stacking them or combining them adds just another framework of a
framework.<br>
<br>
We will go for the simple way first, if we find problems we worry then.<br>
<br>
as we all don't know much about OSGI, I would keep it as simple as
possible.<br>
<br>
<br>
<br>
greetings<br>
Leo<br>
<br>
<br>
Es begab sich aber da Christiaan Fluit zur rechten Zeit 10.11.2006
12:16 folgendes schrieb:
<blockquote cite="mid45545F80.6020409@aduna-software.com" type="cite">
  <pre wrap="">What I see here is a proposal for organizing stuff in bundles but what 
is lacking IMHO is a rationale for why you draw the lines there. If I 
understand you correctly, all Aperture APIs and related stuff would go 
into a single bundle, right? But what does a MimeTypeIdentifier API have 
to do with a Crawler API, except that they are both part of the Aperture 
project? Why not put them into their own bundles?

To be honest, I don't feel like I have very strong ammunition to shoot 
at your proposal with ;) or solid, undeniable arguments for my own 
proposal. I actually start to feel that the chosen granularity might 
depend a lot on your application, how much you use of Aperture, to which 
extent you want to be able to tweak your installed application, etc. As 
long as the code and build scripts are neatly organized, I expect people 
can always create a different setup of bundles for their own use if they 
want to.

Just one more argument for fine-grained bundles ;) : each bundle can 
have its own private classpath. This makes it possible to e.g. create an 
extractor for a specific MIME type that contains all its third party 
dependencies, without necessarily exposing those dependencies to the 
rest of the application. This may prevent certain class loading 
conflicts. For example the bibtex2rdf stuff we've seen last week bundles 
its own XML parser, I believe including classes that implement core Java 
factory interfaces (SAX factories, etc.). Imagine that for some reason 
you want to use this jar as is, adding such a jar file to a regular Java 
application may cause a lot of hard to debug problems when for example 
the bundled XML parser is buggy and gets transparently used in other 
parts of the application as well. Seeing how Aperture's third party 
dependencies are expanding and that itself is still meant to be part of 
a bigger application, this may become an issue in the future.

However, more important IMO are the BundleActivators, as they require 
some programming as well as intimate knowledge of Aperture's internals 
and therefore you want to create them once and for all. Am I right in 
that the construction of the BundleActivators does not depend on the 
bundle granularity that you choose? Or can a bundle only have a single 
BundleActivator? In that case, perhaps BundleActivators can be chained, 
so that for example you have a single ExtractorsBundleActivator that on 
its turn invokes a HtmlBundleActivator, a PdfBundleActivator, etc.? This 
would then support both the "1 extractor impl bundle" strategy and the 
"1 bundle per extractor impl" strategy.

Again, my knowledge of OSGi is limited so feel free to say that this is 
all nonsense or has all been solved before.

Chris
--

Antoni Mylka wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">I've gone through some tutorials and I see it as follows.

We would need one core aperture bundle. It would contain all interfaces 
and vocabulary classes. I would exclude following packages from this 
core bundle:
accessor.file
accessor.http
addressbook
crawler.filesystem
crawler.ical
crawler.imap
crawler.web
datasource.filesystem
datasource.ical
datasource.imap
datasource.web
all extractor subpackages except extractor.impl
hypertext.linkextractor.html
mime.identifier.magic
opener.file
opener.http
outlook

Security, util and vocabulary could stay. This core bundle would 
register following services:
DataAccessorRegistry
CrawlerRegistry
DataSourceRegistry
ExtractorRegistry
LinkExtractorRegistry
MimeTypeIdentifierRegistry
DataOpenerRegistry

The implementations of these interfaces could all be placed in one big 
bundle, or in separate bundles, even if each bundle would contain a 
single class. The activators of these implementation bundles would 
register all implementations with appropriate registries.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
<a class="moz-txt-link-freetext" href="http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642">http://sel.as-us.falkag.net/sel?cmd=lnk&amp;kid=120709&amp;bid=263057&amp;dat=121642</a>
_______________________________________________
Aperture-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aperture-devel@lists.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listinfo/aperture-devel</a>
  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
____________________________________________________
DI Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------060503050005080802000408--


--===============1573299981==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--===============1573299981==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============1573299981==--


From - Mon Nov 13 02:23:28 2006
X-Account-Key: account3
X-UIDL: 0000ed5603c30277
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:25482 "EHLO
	lists-outbound.sourceforge.net") by ps24.test.onet.pl with ESMTP
	id <S4845858AbWKLSmj>; Sun, 12 Nov 2006 19:42:39 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 5C99812982; Sun, 12 Nov 2006 10:13:06 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GjJp4-0002R5-02 for aperture-devel@lists.sourceforge.net;
	Sun, 12 Nov 2006 10:12:50 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GjJp2-0006df-7Y
	for aperture-devel@lists.sourceforge.net;
	Sun, 12 Nov 2006 10:12:51 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kACICaO7008501; Sun, 12 Nov 2006 19:12:36 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kACICaY20348; Sun, 12 Nov 2006 19:12:36 +0100 (MET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kACICVBN015682; Sun, 12 Nov 2006 19:12:33 +0100 (CET)
Message-ID: <4557640C.9030505@dfki.de>
Date:	Sun, 12 Nov 2006 19:12:28 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <454F3C76.5060307@dfki.uni-kl.de>	<4551FAF4.5080309@aduna-software.com>	<45533875.30002@dfki.uni-kl.de>	<45535399.5070600@aduna-software.com>	<4554552E.1000201@dfki.uni-kl.de>
	<455459BE.5070909@aduna-software.com>
In-Reply-To: <455459BE.5070909@aduna-software.com>
X-Spam-Score: 0.1 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.1 HTML_30_40             BODY: Message is 30% to 40% HTML
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.0 HTML_TITLE_EMPTY       BODY: HTML title contains no text
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0847452242=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============0847452242==
Content-Type: multipart/alternative;
	boundary="------------020006020705040209040802"

This is a multi-part message in MIME format.
--------------020006020705040209040802
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Es begab sich aber da Christiaan Fluit zur rechten Zeit 10.11.2006 11:51 
folgendes schrieb:
> Antoni Mylka wrote:
>   
>> So... (list after suggestions)
>> 1. Add a dispose() method to the RDFContainer.
>> 2. Add a dispose() method to the DataSource
>> 3. Have DataObject.dispose() invoke metadata.dispose, but not 
>> source.dispose()
>> 4. Modify the default RDF2GoRDFContainer implementation.
>>    a. introduce a isModelShared attribute (with getter and setter)
>>       make it NOT shared by default
>>    b. implement the dispose() method in a way that it would close
>>       the model if it's NOT shared, and DON'T close it if it's shared
>>    c. add additional parameter to the constructors, that would set if
>>       the model is shared or not.
>>    d. Have all methods check if a model has already been closed and
>>       throw an IllegalStateException if it has.
>> 5. Modify the specific SesameRDFContainer - let the user decide if the
>>    underlying model is to be shared or not.
>> 6. Modify the tests and examples to use this approach.
>>     
>
> Sounds great! Perhaps await Leo's and Gunnar's replies to see what they 
> have to say but I'm rather confident that this approach will fit 
> everyone's purposes.
>   

dispose at RDFContainer is good.
dispose at DataSource - don't know, Is it needed? Usually datasource 
should only hold config data. I wish we had a automatically disposing 
RDFContainer that behaves like a HashSet... so, add dispose().

otherwise, go for it.


>   
>> I hope to do it all today. We could make a big merge next week
>>     
>
> Would be very nice, we would pick up the new code very soon and update 
> our code to the latest Aperture and Sesame alpha 4, so it will get 
> thoroughly tested soon after.
>
>
> Chris
> --
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------020006020705040209040802
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Es begab sich aber da Christiaan Fluit zur rechten Zeit 10.11.2006
11:51 folgendes schrieb:
<blockquote cite="mid455459BE.5070909@aduna-software.com" type="cite">
  <pre wrap="">Antoni Mylka wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">So... (list after suggestions)
1. Add a dispose() method to the RDFContainer.
2. Add a dispose() method to the DataSource
3. Have DataObject.dispose() invoke metadata.dispose, but not 
source.dispose()
4. Modify the default RDF2GoRDFContainer implementation.
   a. introduce a isModelShared attribute (with getter and setter)
      make it NOT shared by default
   b. implement the dispose() method in a way that it would close
      the model if it's NOT shared, and DON'T close it if it's shared
   c. add additional parameter to the constructors, that would set if
      the model is shared or not.
   d. Have all methods check if a model has already been closed and
      throw an IllegalStateException if it has.
5. Modify the specific SesameRDFContainer - let the user decide if the
   underlying model is to be shared or not.
6. Modify the tests and examples to use this approach.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Sounds great! Perhaps await Leo's and Gunnar's replies to see what they 
have to say but I'm rather confident that this approach will fit 
everyone's purposes.
  </pre>
</blockquote>
<br>
dispose at RDFContainer is good.<br>
dispose at DataSource - don't know, Is it needed? Usually datasource
should only hold config data. I wish we had a automatically disposing
RDFContainer that behaves like a HashSet... so, add dispose().<br>
<br>
otherwise, go for it.<br>
<br>
<br>
<blockquote cite="mid455459BE.5070909@aduna-software.com" type="cite">
  <pre wrap="">
  </pre>
  <blockquote type="cite">
    <pre wrap="">I hope to do it all today. We could make a big merge next week
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Would be very nice, we would pick up the new code very soon and update 
our code to the latest Aperture and Sesame alpha 4, so it will get 
thoroughly tested soon after.


Chris
--


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
<a class="moz-txt-link-freetext" href="http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642">http://sel.as-us.falkag.net/sel?cmd=lnk&amp;kid=120709&amp;bid=263057&amp;dat=121642</a>
_______________________________________________
Aperture-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aperture-devel@lists.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listinfo/aperture-devel</a>
  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
____________________________________________________
DI Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------020006020705040209040802--


--===============0847452242==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--===============0847452242==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============0847452242==--


From - Mon Nov 13 02:23:31 2006
X-Account-Key: account3
X-UIDL: 0000ed5603c3c3e5
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:2276 "EHLO
	lists-outbound.sourceforge.net") by ps26.test.onet.pl with ESMTP
	id <S4856421AbWKMAuA>; Mon, 13 Nov 2006 01:50:00 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id B5C1DF865; Sun, 12 Nov 2006 10:37:02 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GjKC8-0004rV-5t for aperture-devel@lists.sourceforge.net;
	Sun, 12 Nov 2006 10:36:40 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GjKC7-0004au-6S
	for aperture-devel@lists.sourceforge.net;
	Sun, 12 Nov 2006 10:36:41 -0800
Received: (qmail 16332 invoked from network); 12 Nov 2006 19:36:31 +0100
Received: from 5353a894.cable.casema.nl (HELO ?83.83.168.148?) (83.83.168.148)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	12 Nov 2006 19:36:30 +0100
Message-ID: <455769AC.4000800@aduna-software.com>
Date:	Sun, 12 Nov 2006 19:36:28 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45533FC5.5020505@dfki.uni-kl.de>
	<45545F80.6020409@aduna-software.com> <45576422.7030300@dfki.de>
In-Reply-To: <45576422.7030300@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Leo Sauermann wrote:
> you may want to view it from the aperture user's side, not from the 
> aperture developers side
> 
> for the aperture user, he is only interested in getting aperture and 
> make it run, so the understanding of the details inside the impl is not 
> needed there.

I think you misunderstand me. I'm exactly viewing it from an Aperture's 
user side. It's the Aperture user who apparently wants to run Aperture 
inside an OSGi framework and, depending on his needs, different bundle 
granularities may be appropriate.

If he really would only be interested in "getting Aperture and making it 
run", a single Aperture bundle containing everything would be enough.

However, other users may want to have more fine-grained control over 
what implementations are used in his system and it would be a pity if he 
would have to redo all bundling work from scratch. Perhaps this 
shouldn't be the default bundle setup but just keep this in mind when 
creating BundleActivators.

> The activators: they usually contain only a few lines of code and should 
> be simple to understand.
> Stacking them or combining them adds just another framework of a framework.

I don't see this as another framework of a framework, just a way to 
organize your BundleActivators. Its exactly the necessity of having to 
understand the details of the implementations for whoever wants to 
create a different bundle setup that I want to prevent. I.e. *we* should 
worry about BundleActivators, Aperture users ideally shouldn't. Coding 
them carefully could make this happen.

> We will go for the simple way first, if we find problems we worry then.
> 
> as we all don't know much about OSGI, I would keep it as simple as possible.

Would be ok for me, for now.


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov  9 08:39:01 2006
X-Account-Key: account6
X-UIDL: 453c769a00000055
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Delivery-Date: Wed, 08 Nov 2006 18:35:32 +0100
Received: from dfki-2203.dfki.uni-kl.de (root@gate-3114 [192.168.31.254])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id kA8HZV98005131
	for <mylka@serv-3100.kl.dfki.de>; Wed, 8 Nov 2006 18:35:31 +0100 (CET)
Received: from mailgw2.uni-kl.de (isg-2202.kl.dfki.de [192.168.22.192])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id kA8HZWC09211
	for <antoni.mylka@dfki.uni-kl.de>; Wed, 8 Nov 2006 18:35:32 +0100 (MET)
Received: from mail.dfki.de (corp-206.dfki.uni-sb.de [134.96.188.26])
	by mailgw2.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id kA8HZTLE026034
	for <antoni.mylka@dfki.uni-kl.de>; Wed, 8 Nov 2006 18:35:29 +0100
Received: by mail.dfki.de (Postfix)
	id 65A5CE4A04; Wed,  8 Nov 2006 18:35:29 +0100 (CET)
Delivered-To: antoni.mylka@dfki.de
Received: from mail.dfki.de (localhost.dfki.uni-sb.de [127.0.0.1])
	by localhost (Postfix) with ESMTP id 39F66E4ABB
	for <Antoni.Mylka@dfki.de>; Wed,  8 Nov 2006 18:35:29 +0100 (CET)
Received: from www4.aduna-software.com (www4.aduna-software.com [66.98.176.99])
	by mail.dfki.de (Postfix) with ESMTP id B24E4E4A04
	for <Antoni.Mylka@dfki.de>; Wed,  8 Nov 2006 18:35:28 +0100 (CET)
Received: (qmail 26400 invoked from network); 8 Nov 2006 18:35:24 +0100
Received: from 5353a894.cable.casema.nl (HELO ?83.83.168.148?) (83.83.168.148)
  by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 8 Nov 2006 18:35:24 +0100
Message-ID: <45521557.6080105@aduna-software.com>
Date: Wed, 08 Nov 2006 18:35:19 +0100
From: Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Arjohn Kampman <arjohn.kampman@aduna-software.com>
Cc: Antoni Mylka <Antoni.Mylka@dfki.de>
Subject: Re: [Aperture-devel] Closing vs. disposing
References: <454F3C76.5060307@dfki.uni-kl.de>	<4551FAF4.5080309@aduna-software.com> <45520125.7080904@aduna-software.com>
In-Reply-To: <45520125.7080904@aduna-software.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Status:  O

Arjohn Kampman wrote:
>> Not just because of the sesameConnection, in Sesame 2 alpha 3 the 
>> MemoryStore also printed a warning when you didn't close it (which I 
>> find awkward for an in-memory representation, but ok).
> 
> Note that memory stores are not necessarily volatile, they can use data
> files for persistence.

I'm taking this off the list...

Why not print a warning only for MemoryStores that have been configured 
to be persistent?

I guess that in the end this is actually very subjective. I think of a 
MemoryStore as just another Java data structure, of which I can get rid 
of by removing all references to it and letting it be garbage collected. 
If you think of it as just another persistent RDF store with an 
in-memory implementation, it becomes different.

But is the reason for this warning just to inform users of an incorrect 
implementation? One could argue than the reverse might be expected 
instead: a warning when I *do* a shutdown on it while no file is 
configured on the store, as then I might also lose data.


Chris
--

From - Thu Nov  9 08:39:01 2006
X-Account-Key: account6
X-UIDL: 453c769a00000058
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Delivery-Date: Wed, 08 Nov 2006 20:45:33 +0100
Received: from dfki-2203.dfki.uni-kl.de (root@gate-3114 [192.168.31.254])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id kA8JjWhK009416
	for <mylka@serv-3100.kl.dfki.de>; Wed, 8 Nov 2006 20:45:32 +0100 (CET)
Received: from mailgw2.uni-kl.de (isg-2202.kl.dfki.de [192.168.22.192])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id kA8JjXC15368
	for <antoni.mylka@dfki.uni-kl.de>; Wed, 8 Nov 2006 20:45:33 +0100 (MET)
Received: from mail.dfki.de (corp-206.dfki.uni-sb.de [134.96.188.26])
	by mailgw2.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id kA8JjOhH009413
	for <antoni.mylka@dfki.uni-kl.de>; Wed, 8 Nov 2006 20:45:24 +0100
Received: by mail.dfki.de (Postfix)
	id 4CE88E4ABD; Wed,  8 Nov 2006 20:45:24 +0100 (CET)
Delivered-To: antoni.mylka@dfki.de
Received: from mail.dfki.de (localhost.dfki.uni-sb.de [127.0.0.1])
	by localhost (Postfix) with ESMTP id 2244BE4ABE
	for <Antoni.Mylka@dfki.de>; Wed,  8 Nov 2006 20:45:24 +0100 (CET)
Received: from www4.aduna-software.com (www4.aduna-software.com [66.98.176.99])
	by mail.dfki.de (Postfix) with ESMTP id A7066E4ABD
	for <Antoni.Mylka@dfki.de>; Wed,  8 Nov 2006 20:45:23 +0100 (CET)
Received: (qmail 29635 invoked from network); 8 Nov 2006 20:45:19 +0100
Received: from ip22-165-208-87.adsl2.versatel.nl (HELO ?192.168.1.6?) (87.208.165.22)
  by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 8 Nov 2006 20:45:18 +0100
Message-ID: <455233C9.9080701@aduna-software.com>
Date: Wed, 08 Nov 2006 20:45:13 +0100
From: Arjohn Kampman <arjohn.kampman@aduna-software.com>
Organization: Aduna BV
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Christiaan Fluit <christiaan.fluit@aduna-software.com>
Cc: Antoni Mylka <Antoni.Mylka@dfki.de>
Subject: Re: [Aperture-devel] Closing vs. disposing
References: <454F3C76.5060307@dfki.uni-kl.de>	<4551FAF4.5080309@aduna-software.com> <45520125.7080904@aduna-software.com> <45521557.6080105@aduna-software.com>
In-Reply-To: <45521557.6080105@aduna-software.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Status:  O

Christiaan Fluit wrote:
> Arjohn Kampman wrote:
>>> Not just because of the sesameConnection, in Sesame 2 alpha 3 the 
>>> MemoryStore also printed a warning when you didn't close it (which I 
>>> find awkward for an in-memory representation, but ok).
>>
>> Note that memory stores are not necessarily volatile, they can use data
>> files for persistence.
> 
> I'm taking this off the list...
> 
> Why not print a warning only for MemoryStores that have been configured 
> to be persistent?

I agree that the current logging is too trigger happpy. It could be a
little more relaxed in situations where it doesn't matter if resources
are closed properly.

> I guess that in the end this is actually very subjective. I think of a 
> MemoryStore as just another Java data structure, of which I can get rid 
> of by removing all references to it and letting it be garbage collected. 
> If you think of it as just another persistent RDF store with an 
> in-memory implementation, it becomes different.
> 
> But is the reason for this warning just to inform users of an incorrect 
> implementation? One could argue than the reverse might be expected 
> instead: a warning when I *do* a shutdown on it while no file is 
> configured on the store, as then I might also lose data.

I don't agree with the latter as it does away with the transparency that
the API offers. It should be possible to replace a MemoryStore with
another RDF store implementation without affecting the calling code. In
this sense, the MemoryStore is "just another RDF store".

Note that the underlying problem of the strict connection closing issue
is a lack of transaction isolation in the RDF stores. When this is
improved, closing connections is not such a big issue anymore as it
won't affect other connections.

Arjohn


-- 
Arjohn Kampman, Senior Software Engineer
Aduna - Guided Exploration
www.aduna-software.com

From - Fri Nov 10 10:20:55 2006
X-Account-Key: account6
X-UIDL: 453c769a0000005a
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Delivery-Date: Thu, 09 Nov 2006 20:26:07 +0100
Received: from dfki-2203.dfki.uni-kl.de (root@gate-3114 [192.168.31.254])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id kA9JQ6ew002179
	for <mylka@serv-3100.kl.dfki.de>; Thu, 9 Nov 2006 20:26:06 +0100 (CET)
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id kA9JQ5Y05259;
	Thu, 9 Nov 2006 20:26:05 +0100 (MET)
Received: from [192.168.22.54] (vpn-2204.kl.dfki.de [192.168.22.54])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id kA9JQ3WH002164;
	Thu, 9 Nov 2006 20:26:04 +0100 (CET)
Message-ID: <455380BD.6050600@dfki.de>
Date: Thu, 09 Nov 2006 20:25:49 +0100
From: Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
CC: Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] OSGI
References: <45533FC5.5020505@dfki.uni-kl.de>
In-Reply-To: <45533FC5.5020505@dfki.uni-kl.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Status:  O

Hi,
good work antoni,
that is the way I also expected it to somehow come out.

Es begab sich aber da Antoni Mylka zur rechten Zeit 09.11.2006 15:48 
folgendes schrieb:
> I've gone through some tutorials and I see it as follows.
>
> We would need one core aperture bundle. It would contain all interfaces 
> and vocabulary classes. I would exclude following packages from this 
> core bundle:
> accessor.file
> accessor.http
> addressbook
> crawler.filesystem
> crawler.ical
> crawler.imap
> crawler.web
> datasource.filesystem
> datasource.ical
> datasource.imap
> datasource.web
> all extractor subpackages except extractor.impl
> hypertext.linkextractor.html
> mime.identifier.magic
> opener.file
> opener.http
> outlook
>
> Security, util and vocabulary could stay. This core bundle would 
> register following services:
> DataAccessorRegistry
> CrawlerRegistry
> DataSourceRegistry
> ExtractorRegistry
> LinkExtractorRegistry
> MimeTypeIdentifierRegistry
> DataOpenerRegistry
>   

yes, correct
> The implementations of these interfaces could all be placed in one big 
> bundle, or in separate bundles, even if each bundle would contain a 
> single class. The activators of these implementation bundles would 
> register all implementations with appropriate registries.
>   
please do it as several bundles for:
* Microsoft Outlook (is needed to be separate)
* IMAP crawling (I think this should be separate)
* everything else

> There remains the issue of RDFContainer creation. We should provide some 
> factory of RDF2GoRDFContainers, that would accept models. It's methods 
> would be exactly equivalent to the current set of constructors in the 
> RDF2GoRDFContainer class.
>   
no idea how to do this - just suggest something
> We should also have a bundle that would expose the core RDF2Go 
> interfaces, and a bundle that would be a factory of ModelImplSesame... 
> this one would need to have access to the ModelImplSesame jar and to the 
> sesame onejar. (Is it at all possible in OSGI for the bundles to use 
> classes from external jars, or export interfaces from external jars?)
>   
the bundles Export classpaths/packages, and you can instantiate the 
classes from any ohter bundle if you correclty import these 
dependencies. try to import bundles or features instead of importing 
packages - see the eclipse plugin-editor (whcih equals to a bundle 
editor) for a gui to edit manifest files.

best greetings
good work
Leo

> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


From - Mon Nov 13 15:49:00 2006
X-Account-Key: account6
X-UIDL: 453c769a00000067
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Delivery-Date: Mon, 13 Nov 2006 15:26:39 +0100
Received: from dfki-2203.dfki.uni-kl.de (root@gate-3114 [192.168.31.254])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id kADEQchB009750
	for <mylka@serv-3100.kl.dfki.de>; Mon, 13 Nov 2006 15:26:38 +0100 (CET)
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id kADEQcY19381;
	Mon, 13 Nov 2006 15:26:38 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id kADEQad2009743;
	Mon, 13 Nov 2006 15:26:36 +0100 (CET)
Message-ID: <45588094.9040603@dfki.de>
Date: Mon, 13 Nov 2006 15:26:28 +0100
From: Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
CC: Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] OSGI Bundles
References: <45587625.4000608@dfki.uni-kl.de>
In-Reply-To: <45587625.4000608@dfki.uni-kl.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Status: RO

Ok,

I reviewed this wikipage and think it conforms to the ideas of Nepomuk,
I changed a few lines there.

from my side: go ahead.

only that we already have a bundle for Sesame2, done by Mikhail Kotelnikov,
we may want to use that for Aperture, but I have no clue how to get this 
arranged within these days,
if you can somehow bundle sesame2 "as antoni likes" that would work good 
for us.
Later on, we can put the "antoni bundled" sesame2 into nepomuk, 
replacing Mikhail's and nothing should break, because OSGI rocks.

same with rdf2go - just bundle it.

for sesame2, please use this bundle name:
org.openrdf.sesame2


here is the manifest file of the current wrapping by mikhail 
(Eclipse-plugin way of OSGI manifests, should be easy to understand):
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %pluginName
Bundle-SymbolicName: org.openrdf.sesame2
Bundle-Version: 2.0.0.4
Bundle-ClassPath: 
sparql-tests.jar,openrdf-model.jar,openrdf-util.jar,rio.jar,sesame.jar,sparql-core.jar,sparql-sesame.jar
Bundle-Vendor: %pluginProvider
Bundle-Localization: plugin
Export-Package: .,
 name.levering.ryan.sparql,
 name.levering.ryan.sparql.common,
 name.levering.ryan.sparql.common.impl,
 name.levering.ryan.sparql.logic,
 name.levering.ryan.sparql.logic.expression,
 name.levering.ryan.sparql.logic.function,
 name.levering.ryan.sparql.model,
 name.levering.ryan.sparql.model.data,
 name.levering.ryan.sparql.model.logic,
 name.levering.ryan.sparql.parser,
 name.levering.ryan.sparql.parser.model,
 org.openrdf.model,
 org.openrdf.model.impl,
 org.openrdf.model.vocabulary,
 org.openrdf.rio,
 org.openrdf.rio.helpers,
 org.openrdf.rio.n3,
 org.openrdf.rio.ntriples,
 org.openrdf.rio.rdfxml,
 org.openrdf.rio.trix,
 org.openrdf.rio.turtle,
 org.openrdf.sesame,
 org.openrdf.sesame.query,
 org.openrdf.sesame.query.helpers,
 org.openrdf.sesame.query.serql,
 org.openrdf.sesame.query.sparql,
 org.openrdf.sesame.repository,
 org.openrdf.sesame.repository.helpers,
 org.openrdf.sesame.sail,
 org.openrdf.sesame.sail.query,
 org.openrdf.sesame.sail.util,
 org.openrdf.sesame.sailimpl.inferencer,
 org.openrdf.sesame.sailimpl.memory,
 org.openrdf.sesame.sailimpl.memory.model,
 org.openrdf.sesame.sailimpl.mysql,
 org.openrdf.sesame.sailimpl.mysql.model,
 org.openrdf.sesame.sailimpl.nativerdf,
 org.openrdf.sesame.sailimpl.nativerdf.btree,
 org.openrdf.sesame.sailimpl.nativerdf.datastore,
 org.openrdf.sesame.sailimpl.nativerdf.model,
 org.openrdf.sesame.server,
 org.openrdf.sesame.server.config,
 org.openrdf.sesame.server.http,
 org.openrdf.sesame.tools,
 org.openrdf.util,
 org.openrdf.util.http,
 org.openrdf.util.io,
 org.openrdf.util.iterator,
 org.openrdf.util.jdbc,
 org.openrdf.util.locking,
 org.openrdf.util.log,
 org.openrdf.util.uri,
 org.openrdf.util.xml,
 org.openrdf.util.xml.datatypes,
 test_cases,
 test_cases.alternatives,
 test_cases.alternatives.data,
 test_cases.alternatives.query,
 test_cases.alternatives.result,
 test_cases.bugs,
 test_cases.bugs.data,
 test_cases.bugs.query,
 test_cases.bugs.result,
 test_cases.dataset,
 test_cases.dataset.data,
 test_cases.dataset.query,
 test_cases.dataset.result,
 test_cases.forms,
 test_cases.forms.data,
 test_cases.forms.query,
 test_cases.forms.result,
 test_cases.literals,
 test_cases.literals.data,
 test_cases.literals.query,
 test_cases.literals.result,
 test_cases.optional,
 test_cases.optional.data,
 test_cases.optional.query,
 test_cases.optional.result,
 test_cases.patterns,
 test_cases.patterns.data,
 test_cases.patterns.query,
 test_cases.patterns.result,
 test_cases.simple,
 test_cases.simple.data,
 test_cases.simple.query,
 test_cases.simple.result,
 test_cases.specifying,
 test_cases.specifying.data,
 test_cases.specifying.query,
 test_cases.specifying.result,
 test_cases.stress,
 test_cases.stress.data,
 test_cases.stress.query,
 test_cases.stress.result,
 test_cases.values,
 test_cases.values.data,
 test_cases.values.query,
 test_cases.values.result
Import-Package: javax.servlet;version="2.1.0";resolution:=optional,
 javax.servlet.http;version="2.1.0";resolution:=optional,
 org.apache.commons.logging,
 org.apache.log4j


greetings
Leo

Es begab sich aber da Antoni Mylka zur rechten Zeit 13.11.2006 14:41 
folgendes schrieb:
> I've been working on it today. It seems to me that we could do it in 
> three bundles.
>
> 1. Core - contains interfaces and exposes registries
>
> 2. impl - contains implementations (factories that are registered with 
> registries from bundle 1. This bundle could be split into as many parts 
> as necessary (separate extractors, crawlers, or even every 
> extractor/crawler in it's own bundle with it's own dependencies). I 
> actually think that chaining Activators might not be a bad idea.
>
> 3. Aperture-rdf2go. This would simply expose all rdf2go interfaces and 
> make them available to all. I could create it from the rdf2go sources 
> and exclude the implementation classes. (Either way the full rdf2go.jar 
> will have to be included in every 'client' application)
>
> Apart from that every application would depend on three elements:
> a. Aperture-helpers.jar The jar that contains basic implementation 
> classes ready to use off-the shelf. (RDF2GoRDFContainer, AccessData, 
> base classes etc.). It will need to be included in the classpath of the 
> core bundle and on the classpath of every 'client' bundle. I can't find 
> any way to avoid this duplication without significant changes in the code.
>
> b. full rdf2go.jar
>
> c. rdf2go-sesame.jar The sesame rdf2go driver,
>
> d. Release of sesame.
>
> c and d can be substituted with any other model implementation. I 
> assumed that the client will provide the Models.
>
> I made an exact listing and put in on the wiki page:
>
> https://gnowsis.opendfki.de/wiki/ApertureOSGi
>
> I intend to do it this way. Any comments welcome.
>
> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


From - Tue Nov 14 10:50:04 2006
X-Account-Key: account3
X-UIDL: 0000ed5603c5e706
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:46746 "EHLO
	lists-outbound.sourceforge.net") by ps4.test.onet.pl with ESMTP
	id <S3648443AbWKMSjU>; Mon, 13 Nov 2006 19:39:20 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 065AEE582; Mon, 13 Nov 2006 05:42:55 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gjc4e-0002B5-BI for aperture-devel@lists.sourceforge.net;
	Mon, 13 Nov 2006 05:42:08 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gjc4d-0000EY-2j
	for aperture-devel@lists.sourceforge.net;
	Mon, 13 Nov 2006 05:42:09 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kADDfvTC028593 for <aperture-devel@lists.sourceforge.net>;
	Mon, 13 Nov 2006 14:41:57 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kADDfvY16850 for <aperture-devel@lists.sourceforge.net>;
	Mon, 13 Nov 2006 14:41:57 +0100 (MET)
Received: from [192.168.41.93] (gast-4103.kl.dfki.de [192.168.41.93])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kADDfudD028655 for <aperture-devel@lists.sourceforge.net>;
	Mon, 13 Nov 2006 14:41:57 +0100 (CET)
Message-ID: <45587625.4000608@dfki.uni-kl.de>
Date:	Mon, 13 Nov 2006 14:41:57 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] OSGI Bundles
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

I've been working on it today. It seems to me that we could do it in 
three bundles.

1. Core - contains interfaces and exposes registries

2. impl - contains implementations (factories that are registered with 
registries from bundle 1. This bundle could be split into as many parts 
as necessary (separate extractors, crawlers, or even every 
extractor/crawler in it's own bundle with it's own dependencies). I 
actually think that chaining Activators might not be a bad idea.

3. Aperture-rdf2go. This would simply expose all rdf2go interfaces and 
make them available to all. I could create it from the rdf2go sources 
and exclude the implementation classes. (Either way the full rdf2go.jar 
will have to be included in every 'client' application)

Apart from that every application would depend on three elements:
a. Aperture-helpers.jar The jar that contains basic implementation 
classes ready to use off-the shelf. (RDF2GoRDFContainer, AccessData, 
base classes etc.). It will need to be included in the classpath of the 
core bundle and on the classpath of every 'client' bundle. I can't find 
any way to avoid this duplication without significant changes in the code.

b. full rdf2go.jar

c. rdf2go-sesame.jar The sesame rdf2go driver,

d. Release of sesame.

c and d can be substituted with any other model implementation. I 
assumed that the client will provide the Models.

I made an exact listing and put in on the wiki page:

https://gnowsis.opendfki.de/wiki/ApertureOSGi

I intend to do it this way. Any comments welcome.

Antoni Mylka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Tue Nov 14 10:50:07 2006
X-Account-Key: account3
X-UIDL: 0000ed5603c65f33
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:63453 "EHLO
	lists-outbound.sourceforge.net") by ps23.test.onet.pl with ESMTP
	id <S5856583AbWKMXXa>; Tue, 14 Nov 2006 00:23:30 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 3292312EA4; Mon, 13 Nov 2006 06:27:25 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gjclo-0006Zt-Pl for aperture-devel@lists.sourceforge.net;
	Mon, 13 Nov 2006 06:26:44 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gjclp-0005yY-5E
	for aperture-devel@lists.sourceforge.net;
	Mon, 13 Nov 2006 06:26:46 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kADEQcPP023029 for <aperture-devel@lists.sourceforge.net>;
	Mon, 13 Nov 2006 15:26:38 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kADEQcY19381; Mon, 13 Nov 2006 15:26:38 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kADEQad2009743; Mon, 13 Nov 2006 15:26:36 +0100 (CET)
Message-ID: <45588094.9040603@dfki.de>
Date:	Mon, 13 Nov 2006 15:26:28 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
References: <45587625.4000608@dfki.uni-kl.de>
In-Reply-To: <45587625.4000608@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] OSGI Bundles
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Ok,

I reviewed this wikipage and think it conforms to the ideas of Nepomuk,
I changed a few lines there.

from my side: go ahead.

only that we already have a bundle for Sesame2, done by Mikhail Kotelnikov,
we may want to use that for Aperture, but I have no clue how to get this 
arranged within these days,
if you can somehow bundle sesame2 "as antoni likes" that would work good 
for us.
Later on, we can put the "antoni bundled" sesame2 into nepomuk, 
replacing Mikhail's and nothing should break, because OSGI rocks.

same with rdf2go - just bundle it.

for sesame2, please use this bundle name:
org.openrdf.sesame2


here is the manifest file of the current wrapping by mikhail 
(Eclipse-plugin way of OSGI manifests, should be easy to understand):
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %pluginName
Bundle-SymbolicName: org.openrdf.sesame2
Bundle-Version: 2.0.0.4
Bundle-ClassPath: 
sparql-tests.jar,openrdf-model.jar,openrdf-util.jar,rio.jar,sesame.jar,sparql-core.jar,sparql-sesame.jar
Bundle-Vendor: %pluginProvider
Bundle-Localization: plugin
Export-Package: .,
 name.levering.ryan.sparql,
 name.levering.ryan.sparql.common,
 name.levering.ryan.sparql.common.impl,
 name.levering.ryan.sparql.logic,
 name.levering.ryan.sparql.logic.expression,
 name.levering.ryan.sparql.logic.function,
 name.levering.ryan.sparql.model,
 name.levering.ryan.sparql.model.data,
 name.levering.ryan.sparql.model.logic,
 name.levering.ryan.sparql.parser,
 name.levering.ryan.sparql.parser.model,
 org.openrdf.model,
 org.openrdf.model.impl,
 org.openrdf.model.vocabulary,
 org.openrdf.rio,
 org.openrdf.rio.helpers,
 org.openrdf.rio.n3,
 org.openrdf.rio.ntriples,
 org.openrdf.rio.rdfxml,
 org.openrdf.rio.trix,
 org.openrdf.rio.turtle,
 org.openrdf.sesame,
 org.openrdf.sesame.query,
 org.openrdf.sesame.query.helpers,
 org.openrdf.sesame.query.serql,
 org.openrdf.sesame.query.sparql,
 org.openrdf.sesame.repository,
 org.openrdf.sesame.repository.helpers,
 org.openrdf.sesame.sail,
 org.openrdf.sesame.sail.query,
 org.openrdf.sesame.sail.util,
 org.openrdf.sesame.sailimpl.inferencer,
 org.openrdf.sesame.sailimpl.memory,
 org.openrdf.sesame.sailimpl.memory.model,
 org.openrdf.sesame.sailimpl.mysql,
 org.openrdf.sesame.sailimpl.mysql.model,
 org.openrdf.sesame.sailimpl.nativerdf,
 org.openrdf.sesame.sailimpl.nativerdf.btree,
 org.openrdf.sesame.sailimpl.nativerdf.datastore,
 org.openrdf.sesame.sailimpl.nativerdf.model,
 org.openrdf.sesame.server,
 org.openrdf.sesame.server.config,
 org.openrdf.sesame.server.http,
 org.openrdf.sesame.tools,
 org.openrdf.util,
 org.openrdf.util.http,
 org.openrdf.util.io,
 org.openrdf.util.iterator,
 org.openrdf.util.jdbc,
 org.openrdf.util.locking,
 org.openrdf.util.log,
 org.openrdf.util.uri,
 org.openrdf.util.xml,
 org.openrdf.util.xml.datatypes,
 test_cases,
 test_cases.alternatives,
 test_cases.alternatives.data,
 test_cases.alternatives.query,
 test_cases.alternatives.result,
 test_cases.bugs,
 test_cases.bugs.data,
 test_cases.bugs.query,
 test_cases.bugs.result,
 test_cases.dataset,
 test_cases.dataset.data,
 test_cases.dataset.query,
 test_cases.dataset.result,
 test_cases.forms,
 test_cases.forms.data,
 test_cases.forms.query,
 test_cases.forms.result,
 test_cases.literals,
 test_cases.literals.data,
 test_cases.literals.query,
 test_cases.literals.result,
 test_cases.optional,
 test_cases.optional.data,
 test_cases.optional.query,
 test_cases.optional.result,
 test_cases.patterns,
 test_cases.patterns.data,
 test_cases.patterns.query,
 test_cases.patterns.result,
 test_cases.simple,
 test_cases.simple.data,
 test_cases.simple.query,
 test_cases.simple.result,
 test_cases.specifying,
 test_cases.specifying.data,
 test_cases.specifying.query,
 test_cases.specifying.result,
 test_cases.stress,
 test_cases.stress.data,
 test_cases.stress.query,
 test_cases.stress.result,
 test_cases.values,
 test_cases.values.data,
 test_cases.values.query,
 test_cases.values.result
Import-Package: javax.servlet;version="2.1.0";resolution:=optional,
 javax.servlet.http;version="2.1.0";resolution:=optional,
 org.apache.commons.logging,
 org.apache.log4j


greetings
Leo

Es begab sich aber da Antoni Mylka zur rechten Zeit 13.11.2006 14:41 
folgendes schrieb:
> I've been working on it today. It seems to me that we could do it in 
> three bundles.
>
> 1. Core - contains interfaces and exposes registries
>
> 2. impl - contains implementations (factories that are registered with 
> registries from bundle 1. This bundle could be split into as many parts 
> as necessary (separate extractors, crawlers, or even every 
> extractor/crawler in it's own bundle with it's own dependencies). I 
> actually think that chaining Activators might not be a bad idea.
>
> 3. Aperture-rdf2go. This would simply expose all rdf2go interfaces and 
> make them available to all. I could create it from the rdf2go sources 
> and exclude the implementation classes. (Either way the full rdf2go.jar 
> will have to be included in every 'client' application)
>
> Apart from that every application would depend on three elements:
> a. Aperture-helpers.jar The jar that contains basic implementation 
> classes ready to use off-the shelf. (RDF2GoRDFContainer, AccessData, 
> base classes etc.). It will need to be included in the classpath of the 
> core bundle and on the classpath of every 'client' bundle. I can't find 
> any way to avoid this duplication without significant changes in the code.
>
> b. full rdf2go.jar
>
> c. rdf2go-sesame.jar The sesame rdf2go driver,
>
> d. Release of sesame.
>
> c and d can be substituted with any other model implementation. I 
> assumed that the client will provide the Models.
>
> I made an exact listing and put in on the wiki page:
>
> https://gnowsis.opendfki.de/wiki/ApertureOSGi
>
> I intend to do it this way. Any comments welcome.
>
> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov 15 09:32:59 2006
X-Account-Key: account3
X-UIDL: 0000ed5603c9cdb5
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:7645 "EHLO
	lists-outbound.sourceforge.net") by ps19.test.onet.pl with ESMTP
	id <S8040262AbWKMOdH>; Mon, 13 Nov 2006 15:33:07 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 3810512F86; Mon, 13 Nov 2006 06:05:25 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GjcQV-0004P4-42 for aperture-devel@lists.sourceforge.net;
	Mon, 13 Nov 2006 06:04:43 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GjcQV-0007na-2F
	for aperture-devel@lists.sourceforge.net;
	Mon, 13 Nov 2006 06:04:44 -0800
Received: (qmail 9656 invoked from network); 13 Nov 2006 15:04:36 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	13 Nov 2006 15:04:35 +0100
Message-ID: <45587B71.5080800@aduna-software.com>
Date:	Mon, 13 Nov 2006 15:04:33 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45587625.4000608@dfki.uni-kl.de>
In-Reply-To: <45587625.4000608@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI Bundles
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Antoni Mylka wrote:
> a. Aperture-helpers.jar The jar that contains basic implementation 
> classes ready to use off-the shelf. (RDF2GoRDFContainer, AccessData, 
> base classes etc.). It will need to be included in the classpath of the 
> core bundle and on the classpath of every 'client' bundle. I can't find 
> any way to avoid this duplication without significant changes in the code.

This is the only part I didn't understand: what kind of duplication do 
you mean? Just some lines in the manifest of these bundles or something 
else? And why does the core bundle depend on them? I would expect it the 
other way around, if at all.

For the rest everything looks fine to me.


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov 15 12:41:45 2006
X-Account-Key: account3
X-UIDL: 0000ed5603ca9994
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:44764 "EHLO
	lists-outbound.sourceforge.net") by ps23.test.onet.pl with ESMTP
	id <S5854472AbWKOLWI>; Wed, 15 Nov 2006 12:22:08 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 1402013286; Tue, 14 Nov 2006 08:49:35 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gk1TX-0007yT-M9 for aperture-devel@lists.sourceforge.net;
	Tue, 14 Nov 2006 08:49:32 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gk1TX-0001n3-0y
	for aperture-devel@lists.sourceforge.net;
	Tue, 14 Nov 2006 08:49:32 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kAEGnMu2026041 for <aperture-devel@lists.sourceforge.net>;
	Tue, 14 Nov 2006 17:49:22 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kAEGnLY10138 for <aperture-devel@lists.sourceforge.net>;
	Tue, 14 Nov 2006 17:49:21 +0100 (MET)
Received: from [192.168.41.93] (gast-4103.kl.dfki.de [192.168.41.93])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kAEGnKIO026843 for <aperture-devel@lists.sourceforge.net>;
	Tue, 14 Nov 2006 17:49:20 +0100 (CET)
Message-ID: <4559F393.20303@dfki.uni-kl.de>
Date:	Tue, 14 Nov 2006 17:49:23 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] RDF2Go has been merged into the main trunk.
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

I have merged the RDF2Go branch with the main trunk. I intend to 
continue working from there. I made a Tag right before the merge. It is 
called aperture-before-rdf2go-merge. If some problems occur, we could 
use it to restore the previous state.

It was a major change. Almost every file has been affected. Every 
alteration may have introduced a bug, so it may take some time before 
this code can be considered mature.

For those that didn't follow the discussions here are the highlights.

1. Whole aperture uses RDF-store-indepent RDF2Go interfaces (URI, 
Literal, etc.)
2. RDFContainer wraps a RDF2Go Model. If one needs 'direct' access to 
RDF (e.g. for querying), the getModel() method from the RDFContainer 
returns the underlying model.
3. All rdf elements (URIs, Literals, Statements etc.) are to be built by 
a newly introduced ValueFactory interface. It mimmicks the ValueFactory 
from Sesame. Provided for convenience.
4. RDF2Go made aperture independent from any concrete RDF-store 
implementation. We don't create models anywhere ourselves, It is up to 
the user to provide a Model implementation. (With the exception of 
AppleAddressbookCrawler that still relies on ModelImplSesame).
5. It all works under the newest sesame-2.0-alpha4. It operates on 
connections. Every connection has to be closed properly. That's why 
every ModelImplSesame has to be closed properly. That made it necessary 
to introduce a dispose() method to the RDFContainer. The default 
container implementation can be configured to close the model on 
disposal or not.
6. Disposing RDFContainers made it necessary to dispose DataSources and 
DataObjects. DataObject.dispose() invokes a metadata.dispose(), and 
DataSource.dispose() invokes a configuration.dispose(). (At least in the 
default implementations).

Potential sources of problems might include:
1. Context support in RDF2Go. I might have ommited contexts in some 
places. RDF2Go is basically a triple-store and contexts aren't 'natural' 
to it. It is not much of our problem though. The application developer 
will have to provide models with proper contexts.
2. Performance. ModelImplSesame seems to support manual commits. I 
didn't use it though. It shouldn't be much of a problem since it would 
only affect the tests and examples. Every real application would have to 
take this into account.
3. ... and many more :-)

Have fun!

Antoni Mylka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
SF.net email is sponsored by: A Better Job is Waiting for You - Find it Now.
Check out Slashdot's new job board. Browse through tons of technical jobs
posted by companies looking to hire people just like you.
http://jobs.slashdot.org/
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov 15 16:04:12 2006
X-Account-Key: account3
X-UIDL: 0000ed5603cad052
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:26066 "EHLO
	lists-outbound.sourceforge.net") by ps23.test.onet.pl with ESMTP
	id <S290737AbWKOMjh>; Wed, 15 Nov 2006 13:39:37 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id CC1541238E; Wed, 15 Nov 2006 04:39:35 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GkK3A-0003sB-M3 for aperture-devel@lists.sourceforge.net;
	Wed, 15 Nov 2006 04:39:32 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GkK39-0006FH-G5
	for aperture-devel@lists.sourceforge.net;
	Wed, 15 Nov 2006 04:39:34 -0800
Received: (qmail 22824 invoked from network); 15 Nov 2006 13:39:20 +0100
Received: from e80143.upc-e.chello.nl (HELO ?10.73.5.3?) (213.93.80.143)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	15 Nov 2006 13:39:20 +0100
Message-ID: <455B0A81.6010705@aduna-software.com>
Date:	Wed, 15 Nov 2006 13:39:29 +0100
From:	Herko ter Horst <herko.ter.horst@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45587625.4000608@dfki.uni-kl.de>	<45587B71.5080800@aduna-software.com>
	<455ADD99.5070308@dfki.uni-kl.de>
In-Reply-To: <455ADD99.5070308@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI Bundles
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

 > The question of  whether it is possible to use the helpers bundle as
 > if it were a jar on the classpath or not is quite fundamental.
> 
> If it isn't:
>     -  we will have to include some of the helpers classes in the impl
>        bundle
>     -  every client application would need to include:
>        - aperture-helpers.jar as an 'aperture client'
>        - rdf2go.jar (required by all rdf2go drivers)
>        - rdf2go driver and all jars that it requires (separate copies).
> 
> OR
> 
>     - everything into real OSGI bundles with real services like
>        - rdf2go interfaces,
>        - rdf2gosesameModelfactory,
>        - ModelAccessDataFactory,
>        - ConfigurationUtilService,
>        - sesame2-osgi-service etc.
> 
> The first option would mean lots of duplication, the other would mean 
> lots of work...
> 
> Any comments are welcome
> 
> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de

First of all, Leo is right: OSGi doesn't enforce the use of services for 
everything (luckily). It is perfectly ok for a bundle to deliver just 
API or implementation, regardless of services.

So there is no need for -helpers.jar to be included in the classpath of 
every client bundle. In fact, I see no reason for -helpers.jar at all, 
because I think those classes should either be included in the core, or 
be made available as separate bundles.

I think it is important to first and foremost think about bundles in 
terms of the API and services they expose, or in terms of the service 
implementation they provide. Second, think about whether or not the 
bundle exposes an API or service that could be useful when use 
stand-alone, or whether it provides an implementation that could be 
optional and/or easy to replace (because of size or quality concerns).

As an example, consider the MimeTypeIdentifier service and its 
implementation based on MimeMagic. The MTI service is a very useful 
service, even when used stand-alone outside of Aperture, so it would 
make sense to deliver it as a separate bundle, instead of integrated 
into one big Aperture bundle. MimeMagic is only one possible 
implementation, so it should be separate as well. However, it does not 
make much sense to split up the MimeMagic implementation further using a 
registry/factory pattern for different mime-types. In fact, the 
MimeMagic for each mime-type is so simple, it can be encoded in a 
configuration file.

Taking the above into account, I would probably split up the bundles a 
bit differently, based on what combination of packages constitutes a 
useful stand-alone API, implementation or service. Of course, there is 
no "law" on where to draw the line, so there are probably several 
"correct" ways to do this. Having said that, below is what I would 
consider a reasonable separation of bundles:


CORE API bundles (1) (only exports API)
----------------
vocabulary


CORE SERVICE bundles (6) (API + services)
--------------------
accessor
accessor.base
accessor.impl (factory implementation, not exported)

crawler
crawler.base
crawler.impl (factory implementation, not exported)

datasource
datasource.base
datasource.config
datasource.impl (factory implementation, not exported)

extractor
extractor.impl (factory implementation, not exported)

opener
opener.impl (factory implementation, not exported)

rdf
rdf.rdf2go (factory implementation, not exported, should be impl?)


SUPPORTING SERVICE bundles (4) (API + services used by CORE)
--------------------------
hypertext.linkextractor
hypertext.linkextractor.impl (factory implementation, not exported)

mime.identifier
mime.identifier.impl (factory implementation, not exported)

security.trustdecider
security.trustdecider.impl (factory implementation, not exported)

security.trustmanager
security.trustmanger.impl (factory implementation, not exported)


SUPPORTING API (1) (only exports API)
--------------
util


CORE SERVICE IMPLEMENTATION bundles (6) (service implementations only)
-----------------------------------
accessor.* (all impls combined is ok for now, should be split)

crawler.* (all impls combined is ok for now, should be split)

datasource.* (all impls combined is ok for now, should be split)

extractor.* (all impls combined is ok for now, should be split)
extractor.util (REVIEW: doesn't seem to have clean dependencies)

opener.* (all impls combined is ok for now, should be split)

rdf.sesame


SUPPORTING SERVICE IMPLEMENTATION bundles (4) (service impls only)
-----------------------------------------
html.linkextractor.html

mime.identifier.magic

security.trustdecider.dialog

security.trustmanager.standard


3RD PARTY API bundles (2)
---------------------
rdf2go (packaged as a bundle)

sesame (packaged as one bundle for now, multiple bundles later)


"Typical" Aperture client applications whould only depend directly on 
CORE API and CORE SERVICES bundles, but would of course need to install 
all bundles in the OSGi framework at runtime to get full default 
functionality.

Splitting up the CORE SERVICE implementations further would be even 
better from an OSGi point of view, IMO. I realize this would mean that 
some bundles contain only one or two classes, however sometimes a few 
classes drag along a large number of dependencies, which would still 
make it worthwhile IMO. In this case, those 3rd party jars should of 
course be separate bundles if they are shared among several other 
bundles (for example, POI is shared by several extractor bundles, so it 
should be in a bundle of its own, not put on the classpath of each of 
those bundles, IMO).

If this way to split things into bundles is too much work for now, as I 
imagine it might be, I would recommend to create combined bundles based 
on the main categories above, which would result in six Aperture bundles 
(with jar dependencies on their internal classpath) + two 3rd party 
bundles. In any case, I would recommend creating BundleActivators as if 
all bundles were separate (and call them from an extra central 
BundleActivator when using combined bundles).

Hope this helps.

Cheers,

Herko ter Horst
Senior Software Engineer
--
Aduna - Guided Exploration
www.aduna-software.com
Prinses Julianaplein 14-b
3817 CS Amersfoort
The Netherlands
+31-33-4659987 (office)

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov 15 16:21:29 2006
X-Account-Key: account3
X-UIDL: 0000ed5603cb31e6
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:52642 "EHLO
	lists-outbound.sourceforge.net") by ps11.test.onet.pl with ESMTP
	id <S3092366AbWKONCW>; Wed, 15 Nov 2006 14:02:22 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id F334612CE6; Wed, 15 Nov 2006 05:02:15 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GkKP6-000679-9t for aperture-devel@lists.sourceforge.net;
	Wed, 15 Nov 2006 05:02:12 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GkKP6-0005Xc-CM
	for aperture-devel@lists.sourceforge.net;
	Wed, 15 Nov 2006 05:02:13 -0800
Received: (qmail 23562 invoked from network); 15 Nov 2006 14:02:00 +0100
Received: from e80143.upc-e.chello.nl (HELO ?10.73.5.3?) (213.93.80.143)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	15 Nov 2006 14:01:59 +0100
Message-ID: <455B0FD1.9000903@aduna-software.com>
Date:	Wed, 15 Nov 2006 14:02:09 +0100
From:	Herko ter Horst <herko.ter.horst@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	aperture-devel@lists.sourceforge.net
References: <45587625.4000608@dfki.uni-kl.de>	<45587B71.5080800@aduna-software.com>	<455ADD99.5070308@dfki.uni-kl.de>
	<455B0A81.6010705@aduna-software.com>
In-Reply-To: <455B0A81.6010705@aduna-software.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI Bundles
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   


> rdf.sesame

Sorry, I just realized this should be the rdf2go Sesame driver bundle.

Herko

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov 16 09:11:35 2006
X-Account-Key: account3
X-UIDL: 0000ed5603cb7f6a
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:12183 "EHLO
	lists-outbound.sourceforge.net") by ps28.test.onet.pl with ESMTP
	id <S2249937AbWKOQrx>; Wed, 15 Nov 2006 17:47:53 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id A5ED4F9E4; Wed, 15 Nov 2006 01:28:03 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GkH3o-0001EI-EH for aperture-devel@lists.sourceforge.net;
	Wed, 15 Nov 2006 01:28:00 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GkH3o-0006DY-2k
	for aperture-devel@lists.sourceforge.net;
	Wed, 15 Nov 2006 01:28:01 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kAF9Rpwb025397; Wed, 15 Nov 2006 10:27:51 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kAF9RpY02690; Wed, 15 Nov 2006 10:27:51 +0100 (MET)
Received: from [192.168.41.93] (gast-4103.kl.dfki.de [192.168.41.93])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kAF9RoWZ018493; Wed, 15 Nov 2006 10:27:50 +0100 (CET)
Message-ID: <455ADD99.5070308@dfki.uni-kl.de>
Date:	Wed, 15 Nov 2006 10:27:53 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45587625.4000608@dfki.uni-kl.de>
	<45587B71.5080800@aduna-software.com>
In-Reply-To: <45587B71.5080800@aduna-software.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kAF9Rpwb025397
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI Bundles
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Q2hyaXN0aWFhbiBGbHVpdCBuYXBpc2HFgihhKToKPiBBbnRvbmkgTXlsa2Egd3JvdGU6Cj4+IGEu
IEFwZXJ0dXJlLWhlbHBlcnMuamFyIFRoZSBqYXIgdGhhdCBjb250YWlucyBiYXNpYyBpbXBsZW1l
bnRhdGlvbiAKPj4gY2xhc3NlcyByZWFkeSB0byB1c2Ugb2ZmLXRoZSBzaGVsZi4gKFJERjJHb1JE
RkNvbnRhaW5lciwgQWNjZXNzRGF0YSwgCj4+IGJhc2UgY2xhc3NlcyBldGMuKS4gSXQgd2lsbCBu
ZWVkIHRvIGJlIGluY2x1ZGVkIGluIHRoZSBjbGFzc3BhdGggb2YgdGhlIAo+PiBjb3JlIGJ1bmRs
ZSBhbmQgb24gdGhlIGNsYXNzcGF0aCBvZiBldmVyeSAnY2xpZW50JyBidW5kbGUuIEkgY2FuJ3Qg
ZmluZCAKPj4gYW55IHdheSB0byBhdm9pZCB0aGlzIGR1cGxpY2F0aW9uIHdpdGhvdXQgc2lnbmlm
aWNhbnQgY2hhbmdlcyBpbiB0aGUgY29kZS4KPiAKPiBUaGlzIGlzIHRoZSBvbmx5IHBhcnQgSSBk
aWRuJ3QgdW5kZXJzdGFuZDogd2hhdCBraW5kIG9mIGR1cGxpY2F0aW9uIGRvIAo+IHlvdSBtZWFu
PyBKdXN0IHNvbWUgbGluZXMgaW4gdGhlIG1hbmlmZXN0IG9mIHRoZXNlIGJ1bmRsZXMgb3Igc29t
ZXRoaW5nIAo+IGVsc2U/IEFuZCB3aHkgZG9lcyB0aGUgY29yZSBidW5kbGUgZGVwZW5kIG9uIHRo
ZW0/IEkgd291bGQgZXhwZWN0IGl0IHRoZSAKPiBvdGhlciB3YXkgYXJvdW5kLCBpZiBhdCBhbGwu
Cj4gCj4gRm9yIHRoZSByZXN0IGV2ZXJ5dGhpbmcgbG9va3MgZmluZSB0byBtZS4KPiAKCllvdSBh
ZGRyZXNzZWQgYSBxdWVzdGlvbiBJIGNvbnNpZGVyIGZ1bmRhbWVudGFsLiBJdCBzdGVtcyBmcm9t
IG15IGxhY2sgCm9mIE9TR0kga25vd2xlZGdlIGFuZCBoYXMgcHJvZm91bmQgY29uc2VxdWVuY2Vz
LiBGb3JnaXZlIG1lIGZvciBiZWluZyBhIApiaXQgdG9vIGVsYWJvcmF0ZSwgYnV0IEkgdGhpbmsg
aXQgaXMgd29ydGggbWFraW5nIHNvbWUgdGhpbmdzIGNsZWFyLgoKSSBzZWVtIHRvIGhhdmUgbWlz
dW5kZXJzdG9vZCB0aGUgY29uY2VwdCBvZiBidW5kbGUgc2VwYXJhdGlvbiBpbiBPU0dJLiAKTXkg
dmlldyB3YXMgYXMgZm9sbG93czoKCnRoZXJlIGFyZSB0aHJlZSBraW5kcyBvZiBsaW5rcyBiZXR3
ZWVuIGphcnMgaW4gT1NHSS4KICAgIC0gaW1wb3J0L2V4cG9ydCBwYWNrYWdlcwogICAgLSByZXF1
aXJlLWJ1bmRsZSAod2hpY2ggaXMgYWN0dWFsbHkgYW4gZXh0ZW50aW9uIG9mIGltcG9ydCBwYWNr
YWdlcykKICAgIC0gY2xhc3NwYXRoIC0gbGluayBiZXR3ZWVuIGEgYnVuZGxlIGFuZCBleHRlcm5h
bCBqYXJzIHVzZWQgYnkgaXQKICAgICAgdGhvc2UgZXh0ZXJuYWwgamFycyBhcmVuJ3QgdmlzaWJs
ZSBpbiB0aGUgcmVzdCBvZiB0aCBPU0dpCiAgICAgIGZyYW1ld29yaywgdGhleSBhcmUgbm90IGJ1
bmRsZXMuIFNpbmNlIGV2ZXJ5IGJ1bmRsZSBoYXMgaXQncyBvd24KICAgICAgY2xhc3NwYXRoIC0g
aXQgaXMgcG9zc2libGUgZm9yIG11bHRpcGxlIHZlcnNpb25zIG9mIHRoZSBzYW1lCiAgICAgIGxp
YnJhcnkgdG8gY29leGlzdCB3aXRoaW4gdGhlIHNhbWUgZnJhbWV3b3JrCgpJIHRob3VnaHQgdGhh
dCBpZiB0d28gYnVuZGxlcyBhcmUgY29ubmVjdGVkIHRocm91Z2ggJ2ltcG9ydCcgb3IgCidyZXF1
aXJlJywgdGhheSBjYW4gY29tbXVuaWNhdGUgT05MWSB0aHJvdWdoIHNlcnZpY2VzLiBJdCBpcyBp
bXBvc3NpYmxlIApmb3Igb25lIGJ1bmRsZSB0byBpbnN0YW50aWF0ZSBjbGFzc2VzIGZyb20gdGhl
IG90aGVyLCBldmVuIGlmIHRoZSAKcGFja2FnZXMgY29udGFpbmluZyB0aG9zZSBjbGFzc2VzIGFy
ZSBleHBvcnRlZC4gSXQgaXMgdGhlIHBoaWxvc29waHkgb2YgCk9TR2kuIExvb3NlIGNvdXBsaW5n
LgoKSWYgd2UgaGF2ZSBidW5kbGUgQSB0aGF0IGNvbnRhaW5zIHNvbWUgY2xhc3MgQyBhbmQgd2Ug
aGF2ZSBhIGJ1bmRsZSBCIAp0aGF0IHdvdWxkIGxpa2UgdG8gdXNlIGFuIGluc3RhbmNlIG9mIHRo
ZSBjbGFzcyBDLiBXZSB3b3VsZCBoYXZlIHRvIG1ha2UgCkEgcmVnaXN0ZXIgc29tZSBDRmFjdG9y
eVNlcnZpY2UuIFRoZSBCIHdvdWxkIGhhdmUgdG8gdXNlIHRoYXQgc2VydmljZSB0byAKb2J0YWlu
IGFuIGluc3RhbmNlIG9mIEMuCgpUaGlzIGtpbmQgb2Ygc2VwYXJhdGlvbiB3b3VsZCBtYWtlIGl0
IHZlcnkgZGlmZmljdWx0IHRvIGRlY291cGxlIAphcGVydHVyZSBpbnRvIG11bHRpcGxlIGNvbXBv
bmVudHMuIEFsbCBpbXBsZW1lbnRhdGlvbiBjbGFzc2VzIHdvdWxkIGhhdmUgCnRvIGJlIGRpcmVj
dGx5IGluY2x1ZGVkIGluIGFsbCBjbGllbnQgYnVuZGxlcy4gVGhhdCdzIHdoeSBJIGNvaW5lZCB0
aGUgCmlkZWEgb2YgYXBlcnR1cmUtaGVscGVycy5qYXIuIEl0IHdvdWxkIGJlIGEgamFyIHRoYXQg
d291bGQgYmUgaW5jbHVkZWQgCmluIHRoZSBDTEFTU1BBVEggKG5vdCBpbXBvcnRlZC9yZXF1aXJl
ZCkgb2YgZXZlcnkgYnVuZGxlIHRoYXQgd291bGQgbGlrZSAKdG8gdXNlIGFwZXJ0dXJlLiBObyB1
c2VyIGNhbiBiZSBleHBlY3RlZCB0byB1c2UgYXBlcnR1cmUgd2l0aG91dCAKVm9jYWJ1bGFyeSBj
bGFzc2VzLCBDb25maWd1cmF0aW9uVXRpbCBvciBSREYyR29SREZDb250YWluZXIuIFR1cm5pbmcg
CnRoZW0gaW50byBzZXJ2aWNlcyB3b3VsZCBuZWNlc3NpdGF0ZSBhIGNvbXBsZXRlIHJld3JpdGUu
IEhvdyB0byBtYWtlIGEgCnNlcnZpY2UgZnJvbSBhIFZvY2FidWxhcnkgY2xhc3M/CgpMZW8gdG9s
ZCBtZSB0aGF0IEkgd2FzIHdyb25nLiBFdmVuIHRob3VnaCBPU0dpIGVuY291cmFnZXMgbG9vc2Ug
Y291cGxpbmcgCmFuZCBjb21tdW5pY2F0aW9uIHRocm91Z2ggc2VydmljZXMgLSBpdCBhbGxvd3Mg
dGhlIGJ1bmRsZXMgdG8gCmNvbW11bmljYXRlIGRpcmVjdGx5IGFuZCBpbnN0YW50aWF0ZSBlYWNo
IG90aGVyJ3MgY2xhc3NlcyBkaXJlY3RseS4gClRoYXQncyB3aHkgaXQgd2lsbCBiZSBwb3NzaWJs
ZSB0byBwdWJsaXNoIHRoZSBhcGVydHVyZS1oZWxwZXJzLmphciBhcyBhIApidW5kbGUuIFRoZSBk
ZXBlbmRlbmN5IGRpYWdyYW0gd291bGQgbG9vayBhcyBmb2xsb3dzOgoKICAgICAgICAgICAgICAg
ICAgLy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS1cCiAgICAgICAgICAgICAgICAgXHwv
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICAgY29yZSA8LS0t
LS0tLS0gaW1wbCAtLS0tLS0tLT4gaGVscGVycwogICAgICAgICAgICAgICAgIC98XCAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgL3xcCiAgICAgICAgICAgICAgICAgIFwtLS0tLS0tLS0tLWNs
aWVudC0tLS0tLS0tLS0tLS0tLwoKKHRoZSB0aXAgb2YgdGhlIGFycm93IGluZGljYXRlcyB0aGF0
IGhlbHBlcnMgYW5kIGltcGwgZGVwZW5kIG9uICB0aGUgY29yZSkKCkFsbCBvZiB0aGVtIHdvdWxk
IGRlcGVuZCBvbiByZGYyZ28gYnVuZGxlLiBUaGUgY2xpZW50IHdvdWxkIGFsc28gZGVwZW5kIApv
biBhbnkgcmRmMmdvIGltcGxlbWVudGF0aW9uIGJ1bmRsZXMgaXQgd291bGQgbGlrZSB0byB1c2Ug
KGxpa2UgCnJkZjJnby1zZXNhbWUpLgoKVGhpcyBkZXNpZ24gbWF5IG5vdCBiZSB0aGUgZHJlYW0g
b2YgYW4gY29tcG9uZW50LW9yaWVudGVkIApmdW5kYW1lbnRhbGlzdC4gRXhjaGFuZ2luZyBjb3Jl
LCBoZWxwZXJzIG9yIGltcGwgZnJvbSBkaWZmZXJlbnQgdmVyc2lvbnMgCm9mIGFwZXJ0dXJlIG1h
eSBiZSBkaWZmaWN1bHQuIENvcmUgaW50ZXJmYWNlcyBjb3VsZCBiZSBleHBlY3RlZCB0byAKcmVt
YWluIHN0YWJsZSBidXQgbW9zdCBpbXBsZW1lbnRhdGlvbnMgYW5kIGNsaWVudHMgd291bGQgb25s
eSB3b3JrIHdpdGggCmEgc2luZ2xlIHZlcnNpb24gb2YgaGVscGVycy4KCk5ldmVydGhlbGVzcyB0
aGUgbWFpbiBnb2FsIHRoYXQgaXM6IGZpbmUtZ3JhaW5lZCBjb250cm9sIG92ZXIgdGhlIAppbXBs
ZW1lbnRhdGlvbnMgYXZhaWxhYmxlIGluIGFueSBnaXZlbiBpbnN0YWxsYXRpb24gbWF5IGJlIGFj
aGlldmVkLiBBcyAKSSBzYWlkLCB0aGUgaW1wbCBidW5kbGUgY291bGQgYmUgc3BsaXQgaW50byBh
cyBtYW55IGJ1bmRsZXMgYXMgCm5lY2Vzc2FyeS4gQWRkaXRpb25hbCBpbXBsZW1lbnRhdGlvbnMg
Y2FuIGJlIGFkZGVkIGVhc2lseSAod3JpdGUgYSAKYnVuZGxlIHRoYXQgdXNlcyBjb3JlLCBoZWxw
ZXJzIGFuZCByZGYyZ28sIGhhdmUgdGhlIGFjdGl2YXRvciBhZGQgCmFwcHJvcHJpYXRlIGZhY3Rv
cmllcyBpbnRvIHRoZSBhcHByb3ByaWF0ZSByZWdpc3RyeSBhbmQgdm9pbGEuLi4pLgoKSSBndWVz
cyB0aGVyZSdzIHN0aWxsIGEgbG90IHRvIGxlYXJuLi4uIDotKSBUaGUgYWJpbGl0eSB0byBpbnN0
YW50aWF0ZSAKY2xhc3NlcyBmcm9tIG90aGVyIGJ1bmRsZXMgbWlnaHQgaW50cm9kdWNlIG1hbnkg
c3VidGxlIHByb2JsZW1zLCAKZXNwZWNpYWxseSBpZiB0aGUgcHJvdmlkaW5nIGFuZCB1c2luZyBi
dW5kbGUgdXNlIHRoZSBzYW1lIGxpYnJhcnksIGJ1dCAKaW4gZGlmZmVyZW50IHZlcnNpb25zLgoK
SGVya286IHlvdSBzZWVtIHRvIGJlIHRoZSBPU0dpIHNwZWNpYWxpc3Qgb24gdGhpcyBncm91cC4g
VGhlIHF1ZXN0aW9uIG9mIAp3aGV0aGVyIGl0IGlzIHBvc3NpYmxlIHRvIHVzZSB0aGUgaGVscGVy
cyBidW5kbGUgYXMgaWYgaXQgd2VyZSBhIGphciBvbiAKdGhlIGNsYXNzcGF0aCBvciBub3QgaXMg
cXVpdGUgZnVuZGFtZW50YWwuCgpJZiBpdCBpc24ndDoKICAgIC0gIHdlIHdpbGwgaGF2ZSB0byBp
bmNsdWRlIHNvbWUgb2YgdGhlIGhlbHBlcnMgY2xhc3NlcyBpbiB0aGUgaW1wbAogICAgICAgYnVu
ZGxlCiAgICAtICBldmVyeSBjbGllbnQgYXBwbGljYXRpb24gd291bGQgbmVlZCB0byBpbmNsdWRl
OgogICAgICAgLSBhcGVydHVyZS1oZWxwZXJzLmphciBhcyBhbiAnYXBlcnR1cmUgY2xpZW50Jwog
ICAgICAgLSByZGYyZ28uamFyIChyZXF1aXJlZCBieSBhbGwgcmRmMmdvIGRyaXZlcnMpCiAgICAg
ICAtIHJkZjJnbyBkcml2ZXIgYW5kIGFsbCBqYXJzIHRoYXQgaXQgcmVxdWlyZXMgKHNlcGFyYXRl
IGNvcGllcykuCgpPUgoKICAgIC0gZXZlcnl0aGluZyBpbnRvIHJlYWwgT1NHSSBidW5kbGVzIHdp
dGggcmVhbCBzZXJ2aWNlcyBsaWtlCiAgICAgICAtIHJkZjJnbyBpbnRlcmZhY2VzLAogICAgICAg
LSByZGYyZ29zZXNhbWVNb2RlbGZhY3RvcnksCiAgICAgICAtIE1vZGVsQWNjZXNzRGF0YUZhY3Rv
cnksCiAgICAgICAtIENvbmZpZ3VyYXRpb25VdGlsU2VydmljZSwKICAgICAgIC0gc2VzYW1lMi1v
c2dpLXNlcnZpY2UgZXRjLgoKVGhlIGZpcnN0IG9wdGlvbiB3b3VsZCBtZWFuIGxvdHMgb2YgZHVw
bGljYXRpb24sIHRoZSBvdGhlciB3b3VsZCBtZWFuIApsb3RzIG9mIHdvcmsuLi4KCkFueSBjb21t
ZW50cyBhcmUgd2VsY29tZQoKQW50b25pIE15bGthCmFudG9uaS5teWxrYUBkZmtpLnVuaS1rbC5k
ZQoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQpUYWtlIFN1cnZleXMuIEVhcm4gQ2FzaC4gSW5mbHVlbmNlIHRo
ZSBGdXR1cmUgb2YgSVQKSm9pbiBTb3VyY2VGb3JnZS5uZXQncyBUZWNoc2F5IHBhbmVsIGFuZCB5
b3UnbGwgZ2V0IHRoZSBjaGFuY2UgdG8gc2hhcmUgeW91cgpvcGluaW9ucyBvbiBJVCAmIGJ1c2lu
ZXNzIHRvcGljcyB0aHJvdWdoIGJyaWVmIHN1cnZleXMgLSBhbmQgZWFybiBjYXNoCmh0dHA6Ly93
d3cudGVjaHNheS5jb20vZGVmYXVsdC5waHA/cGFnZT1qb2luLnBocCZwPXNvdXJjZWZvcmdlJkNJ
RD1ERVZERVYKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18K
QXBlcnR1cmUtZGV2ZWwgbWFpbGluZyBsaXN0CkFwZXJ0dXJlLWRldmVsQGxpc3RzLnNvdXJjZWZv
cmdlLm5ldApodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9hcGVy
dHVyZS1kZXZlbAo=

From - Thu Nov 16 09:11:35 2006
X-Account-Key: account3
X-UIDL: 0000ed5603cba91b
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:24041 "EHLO
	lists-outbound.sourceforge.net") by ps21.test.onet.pl with ESMTP
	id <S6772896AbWKOPdx>; Wed, 15 Nov 2006 16:33:53 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 2065612B06; Wed, 15 Nov 2006 07:33:49 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GkMlV-00049z-N7 for aperture-devel@lists.sourceforge.net;
	Wed, 15 Nov 2006 07:33:29 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GkMlU-0004aJ-2n
	for aperture-devel@lists.sourceforge.net;
	Wed, 15 Nov 2006 07:33:30 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kAFFXKDc019948 for <aperture-devel@lists.sourceforge.net>;
	Wed, 15 Nov 2006 16:33:20 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kAFFXKY24953 for <aperture-devel@lists.sourceforge.net>;
	Wed, 15 Nov 2006 16:33:20 +0100 (MET)
Received: from [192.168.41.93] (gast-4103.kl.dfki.de [192.168.41.93])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kAFFXImC004407 for <aperture-devel@lists.sourceforge.net>;
	Wed, 15 Nov 2006 16:33:19 +0100 (CET)
Message-ID: <455B3343.1030100@dfki.uni-kl.de>
Date:	Wed, 15 Nov 2006 16:33:23 +0100
From:	Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <45587625.4000608@dfki.uni-kl.de>	<45587B71.5080800@aduna-software.com>	<455ADD99.5070308@dfki.uni-kl.de>
	<455B0A81.6010705@aduna-software.com>
In-Reply-To: <455B0A81.6010705@aduna-software.com>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kAFFXKDc019948
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI Bundles
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

SGVya28gdGVyIEhvcnN0IG5hcGlzYcWCKGEpOgo+IAo+IENPUkUgU0VSVklDRSBidW5kbGVzICg2
KSAoQVBJICsgc2VydmljZXMpCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiBhY2Nlc3Nvcgo+IGFj
Y2Vzc29yLmJhc2UKPiBhY2Nlc3Nvci5pbXBsIChmYWN0b3J5IGltcGxlbWVudGF0aW9uLCBub3Qg
ZXhwb3J0ZWQpCgpZb3UgbWVhbiBSZWdpc3RyeSBpbXBsZW1lbnRhdGlvbiA/Pz8KCkFudG9uaSBN
eWxrYQphbnRvbmkubXlsa2FAZGZraS51bmkta2wuZGUKCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KVGFrZSBT
dXJ2ZXlzLiBFYXJuIENhc2guIEluZmx1ZW5jZSB0aGUgRnV0dXJlIG9mIElUCkpvaW4gU291cmNl
Rm9yZ2UubmV0J3MgVGVjaHNheSBwYW5lbCBhbmQgeW91J2xsIGdldCB0aGUgY2hhbmNlIHRvIHNo
YXJlIHlvdXIKb3BpbmlvbnMgb24gSVQgJiBidXNpbmVzcyB0b3BpY3MgdGhyb3VnaCBicmllZiBz
dXJ2ZXlzIC0gYW5kIGVhcm4gY2FzaApodHRwOi8vd3d3LnRlY2hzYXkuY29tL2RlZmF1bHQucGhw
P3BhZ2U9am9pbi5waHAmcD1zb3VyY2Vmb3JnZSZDSUQ9REVWREVWCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCkFwZXJ0dXJlLWRldmVsIG1haWxpbmcgbGlz
dApBcGVydHVyZS1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKaHR0cHM6Ly9saXN0cy5zb3Vy
Y2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vYXBlcnR1cmUtZGV2ZWwK

From - Thu Nov 16 09:11:36 2006
X-Account-Key: account3
X-UIDL: 0000ed5603cbd1c6
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:35542 "EHLO
	lists-outbound.sourceforge.net") by ps5.test.onet.pl with ESMTP
	id <S4120899AbWKIOu0>; Thu, 9 Nov 2006 15:50:26 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 2CF0112F36; Thu,  9 Nov 2006 06:50:25 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiBEA-0000Nu-FD for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 06:50:03 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiBEA-0006l1-17
	for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 06:50:03 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kA9EmZvN002665 for <aperture-devel@lists.sourceforge.net>;
	Thu, 9 Nov 2006 15:48:37 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kA9EmZY20212 for <aperture-devel@lists.sourceforge.net>;
	Thu, 9 Nov 2006 15:48:35 +0100 (MET)
Received: from [192.168.41.94] (gast-4104.kl.dfki.de [192.168.41.94])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kA9EmXjK013007 for <aperture-devel@lists.sourceforge.net>;
	Thu, 9 Nov 2006 15:48:34 +0100 (CET)
Message-ID: <45533FC5.5020505@dfki.uni-kl.de>
Date:	Thu, 09 Nov 2006 15:48:37 +0100
From:	Antoni Mylka <Antoni.Mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

I've gone through some tutorials and I see it as follows.

We would need one core aperture bundle. It would contain all interfaces 
and vocabulary classes. I would exclude following packages from this 
core bundle:
accessor.file
accessor.http
addressbook
crawler.filesystem
crawler.ical
crawler.imap
crawler.web
datasource.filesystem
datasource.ical
datasource.imap
datasource.web
all extractor subpackages except extractor.impl
hypertext.linkextractor.html
mime.identifier.magic
opener.file
opener.http
outlook

Security, util and vocabulary could stay. This core bundle would 
register following services:
DataAccessorRegistry
CrawlerRegistry
DataSourceRegistry
ExtractorRegistry
LinkExtractorRegistry
MimeTypeIdentifierRegistry
DataOpenerRegistry

The implementations of these interfaces could all be placed in one big 
bundle, or in separate bundles, even if each bundle would contain a 
single class. The activators of these implementation bundles would 
register all implementations with appropriate registries.

There remains the issue of RDFContainer creation. We should provide some 
factory of RDF2GoRDFContainers, that would accept models. It's methods 
would be exactly equivalent to the current set of constructors in the 
RDF2GoRDFContainer class.

We should also have a bundle that would expose the core RDF2Go 
interfaces, and a bundle that would be a factory of ModelImplSesame... 
this one would need to have access to the ModelImplSesame jar and to the 
sesame onejar. (Is it at all possible in OSGI for the bundles to use 
classes from external jars, or export interfaces from external jars?)

Antoni Mylka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov 16 09:11:37 2006
X-Account-Key: account3
X-UIDL: 0000ed5603cc5303
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:36332 "EHLO
	lists-outbound.sourceforge.net") by ps5.test.onet.pl with ESMTP
	id <S4016193AbWKHPay>; Wed, 8 Nov 2006 16:30:54 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id CF58813626; Wed,  8 Nov 2006 07:30:40 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GhpN3-0002GL-Rs for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 07:29:46 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GhpN3-0002vx-KT
	for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 07:29:47 -0800
Received: (qmail 22851 invoked from network); 8 Nov 2006 16:29:17 +0100
Received: from ip22-165-208-87.adsl2.versatel.nl (HELO ?192.168.1.6?)
	(87.208.165.22)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	8 Nov 2006 16:29:15 +0100
Message-ID: <4551F7C7.2080602@aduna-software.com>
Date:	Wed, 08 Nov 2006 16:29:11 +0100
From:	Arjohn Kampman <arjohn.kampman@aduna-software.com>
Organization: Aduna BV
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F2723.8040809@dfki.uni-kl.de>
	<4551F000.5020009@aduna-software.com>
In-Reply-To: <4551F000.5020009@aduna-software.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Progress Report - BibTex crawler - OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Christiaan Fluit wrote:
> I've also looked around and found this Perl script: 
> http://www.cs.vu.nl/%7Emcaklein/bib2rdf/bib2rdf. It's available as an 
> online service: http://www.cs.vu.nl/%7Emcaklein/bib2rdf/ so you can 
> determine its quality. Unfortunately the script is also distributed 
> under GPL. It's part of the OpenAcademia project, of which I know 
> several people. I have no Perl experience but I suspect it is possible 
> to port this script to Java fairly easy. I can ask the authors for 
> permission to do so and distribute the results under a different 
> license. Perhaps this is an option for you?

AFAIK, the perl script is pretty good except for handling non-ASCII
characters. At least, it used to have problems with unicode chars about
a year ago.

Further, MIT's Simile project has a number of RDFizers, one of which
transforms BibTEX to RDF. Might be worth investigating:
http://simile.mit.edu/RDFizers/

--
Arjohn

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov 16 11:15:11 2006
X-Account-Key: account3
X-UIDL: 0000ed5603ce09e5
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:4570 "EHLO
	lists-outbound.sourceforge.net") by ps27.test.onet.pl with ESMTP
	id <S5136858AbWKOQOs>; Wed, 15 Nov 2006 17:14:48 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 5872712585; Wed, 15 Nov 2006 07:40:47 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GkMrt-0004sz-TT for aperture-devel@lists.sourceforge.net;
	Wed, 15 Nov 2006 07:40:06 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GkMrt-0006fJ-O7
	for aperture-devel@lists.sourceforge.net;
	Wed, 15 Nov 2006 07:40:07 -0800
Received: (qmail 27961 invoked from network); 15 Nov 2006 16:39:52 +0100
Received: from e80143.upc-e.chello.nl (HELO ?10.73.5.3?) (213.93.80.143)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	15 Nov 2006 16:39:52 +0100
Message-ID: <455B34D2.9070702@aduna-software.com>
Date:	Wed, 15 Nov 2006 16:40:02 +0100
From:	Herko ter Horst <herko.ter.horst@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
References: <45587625.4000608@dfki.uni-kl.de>	<45587B71.5080800@aduna-software.com>	<455ADD99.5070308@dfki.uni-kl.de>	<455B0A81.6010705@aduna-software.com>
	<455B3343.1030100@dfki.uni-kl.de>
In-Reply-To: <455B3343.1030100@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] OSGI Bundles
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

>> CORE SERVICE bundles (6) (API + services)
>> --------------------
>> accessor
>> accessor.base
>> accessor.impl (factory implementation, not exported)
> 
> You mean Registry implementation ???

Yes, sorry about that.

> Antoni Mylka
> antoni.mylka@dfki.uni-kl.de

Cheers,

Herko ter Horst
Senior Software Engineer
--
Aduna - Guided Exploration
www.aduna-software.com
Prinses Julianaplein 14-b
3817 CS Amersfoort
The Netherlands
+31-33-4659987 (office)

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Sat Nov 18 18:30:23 2006
X-Account-Key: account3
X-UIDL: 0000ed5603d4a94c
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:11926 "EHLO
	lists-outbound.sourceforge.net") by ps25.test.onet.pl with ESMTP
	id <S5053118AbWKQR3P>; Fri, 17 Nov 2006 18:29:15 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id BB6041365F; Fri, 17 Nov 2006 09:29:12 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gl7WW-0006T7-QO for Aperture-devel@lists.sourceforge.net;
	Fri, 17 Nov 2006 09:29:08 -0800
Received: from balboa.ai.sri.com ([130.107.64.135])
	by mail.sourceforge.net with esmtp (Exim 4.44) id 1Gl7WV-0002LC-V9
	for Aperture-devel@lists.sourceforge.net;
	Fri, 17 Nov 2006 09:29:10 -0800
Received: from Balboa.AI.SRI.COM (localhost [127.0.0.1])
	by Balboa.AI.SRI.COM (8.11.7p2+Sun/8.10.1) with SMTP id kAHHT2E12494
	for <Aperture-devel@lists.sourceforge.net>;
	Fri, 17 Nov 2006 09:29:02 -0800 (PST)
Received: from Salt.AI.SRI.COM ([130.107.65.211])
	by Balboa.AI.SRI.COM (SMSSMTP 4.1.9.35) with SMTP id
	M2006111709290101068 for <Aperture-devel@lists.sourceforge.net>;
	Fri, 17 Nov 2006 09:29:01 -0800
Received: from localhost.ai.sri.com
	([127.0.0.1] helo=[130.107.65.21] ident=root)
	by Salt.AI.SRI.COM with asmtp (Exim 3.35 #1 (Debian))
	id 1Gl7WQ-0001OZ-00 for <Aperture-devel@lists.sourceforge.net>;
	Fri, 17 Nov 2006 09:29:02 -0800
Message-ID: <455DF154.9080808@sri.com>
Date:	Fri, 17 Nov 2006 09:28:52 -0800
From:	Jack Park <jack.park@sri.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture-devel@lists.sourceforge.net
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] RabbiT Cache/Proxy
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   


See http://www.khelekore.org/rabbit/
> RabbIT is a web proxy that speeds up web surfing over slow links by doing:
> 
>     * Compress text pages to gzip streams. This reduces size by up to 75%
>     * Compress images to 10% jpeg. This reduces size by up to 95%
>     * Remove advertising
>     * Remove background images
>     * Cache filtered pages and images
>     * Uses keepalive if possible
>     * Easy and powerful configuration
>     * Multi threaded solution written in java
>     * Modular and easily extended
>     * Complete HTTP/1.1 compliance 

Might make a good interloper for harvesting web pages! Look at all the 
stuff it says it can do...
java/bsd

Cheers
Jack

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Sat Nov 18 18:30:24 2006
X-Account-Key: account3
X-UIDL: 0000ed5603d4dd58
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:9128 "EHLO
	lists-outbound.sourceforge.net") by ps24.test.onet.pl with ESMTP
	id <S5062815AbWKQSpa>; Fri, 17 Nov 2006 19:45:30 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 984611387D; Fri, 17 Nov 2006 08:39:15 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gl6kB-0001CP-UU for aperture-devel@lists.sourceforge.net;
	Fri, 17 Nov 2006 08:39:12 -0800
Received: from ug-out-1314.google.com ([66.249.92.174])
	by mail.sourceforge.net with esmtp (Exim 4.44) id 1Gl6kC-0002kI-S8
	for aperture-devel@lists.sourceforge.net;
	Fri, 17 Nov 2006 08:39:13 -0800
Received: by ug-out-1314.google.com with SMTP id z38so730435ugc
	for <aperture-devel@lists.sourceforge.net>;
	Fri, 17 Nov 2006 08:39:11 -0800 (PST)
Received: by 10.78.185.15 with SMTP id i15mr2097449huf.1163781550255;
	Fri, 17 Nov 2006 08:39:10 -0800 (PST)
Received: by 10.78.157.4 with HTTP; Fri, 17 Nov 2006 08:39:10 -0800 (PST)
Message-ID: <97d19f3c0611170839r11a1a1e2s8818032bb2dea4f2@mail.gmail.com>
Date:	Fri, 17 Nov 2006 17:39:10 +0100
From:	"Antoni Mylka" <antoni.mylka@gmail.com>
To:	aperture-devel@lists.sourceforge.net
MIME-Version: 1.0
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.0 RCVD_BY_IP             Received by mail server with no name
Cc:	"Fluit, Christiaan" <christiaan.fluit@aduna-software.net>,
	"Sauermann, Leo" <sauermann@dfki.uni-kl.de>
Subject: [Aperture-devel] Report 17.11.2006
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

I managed to do the following:

1. There is a fourth source folder src/activators. It contains the
BundleActivators. There are almost 50 of them. Each will be
responsible for activating a single bundle. This division will make it
possible to create those fine-grained bundles Christiaan and Herko
spoke of.

2. There are also 'higher-level' activators. They will work with
bundles at higher level of granularity. They work by forwarding the
start and stop events to appropriate elementary activators.

3. The build script has been expanded with selectors. There is one
selector for each elementary bundle. Higher level bundles are handled
by making a union (<or> tag) of an appropriate set of lower-level
selectors. It is quite complicated. I've used a simple a bash-script
to check if all classes are included in the bundles and if there are
no duplicates. I may add it to the repository if you'd like.

4. Targets for jar files of bundles at middle (6) and high (2) levels
of granularity have been provided. They choose appropriate selectors.
They include class files, sources and resources from appropriate
directories. Extra care has been taken to prevent resource files from
being added twice to a jar file (Yes, it is possible to have two files
with the same name in the same directory of a jar file, generates
errors when trying to do something with this jar (like view it in
mc)). All of them are invoked by a single jar.bundles target.

5. Simple manifest files for the above jars have been provided. They
are stored in src/manifest directory. They contain the basic
information.

6. I used the mangen tool to create the import/export statements in
the manifest files of the bundles. I added it to the repository.
(Forgive my boldness at doing it without asking). It seems to do a
good job. I integrated it with the ant build script. The task
mangen.run Compiles the classes, creates the bundles and runs mangen.
As a result the bundles receive manifests with appropriate
import/export statements. It can be customized with rules.

The activators seem to work. (At least those that have already been
written). The only thing that's left is an activator for an
implementation bundle (with an appropriate service tracker, that will
be able support registries appearing and disappearing). Such could be
reused for every implementation bundle. (By copy-paste, i don't want
to introduce additional dependencies by creating some generic
activator and  inheriting from it...)

Best regards
Antoni Mylka
antoni.mylka@dfki.uni-kl.de


-- =

Antoni My=B3ka
antoni.mylka@gmail.com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Sat Nov 18 18:30:49 2006
X-Account-Key: account3
X-UIDL: 0000ed5603d75b0e
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:14491 "EHLO
	lists-outbound.sourceforge.net") by ps11.test.onet.pl with ESMTP
	id <S1608182AbWKQUzO>; Fri, 17 Nov 2006 21:55:14 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id BCA1B1292C; Fri, 17 Nov 2006 12:34:05 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GlAPQ-0007aO-Uj for Aperture-devel@lists.sourceforge.net;
	Fri, 17 Nov 2006 12:34:01 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GlAPO-0005a4-Hm
	for Aperture-devel@lists.sourceforge.net;
	Fri, 17 Nov 2006 12:34:01 -0800
Received: (qmail 5836 invoked from network); 17 Nov 2006 21:33:50 +0100
Received: from ip22-165-208-87.adsl2.versatel.nl (HELO ?192.168.1.6?)
	(87.208.165.22)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	17 Nov 2006 21:33:50 +0100
Message-ID: <455E1CA7.7000501@aduna-software.com>
Date:	Fri, 17 Nov 2006 21:33:43 +0100
From:	Arjohn Kampman <arjohn.kampman@aduna-software.com>
Organization: Aduna BV
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Jack Park <jack.park@sri.com>
References: <455DF154.9080808@sri.com>
In-Reply-To: <455DF154.9080808@sri.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture-devel@lists.sourceforge.net
Subject: Re: [Aperture-devel] RabbiT Cache/Proxy
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Please note that this is not something that can be integrated on the
client, so I don't quite see how this will benefit aperture:

"RabbIT works best if it is run on a computer with a fast link
(typically your ISP). Since every large image is compressed before it is
sent from the ISP to you, surfing becomes much faster at the price of
some decrease in image quality."

Arjohn

Jack Park wrote:
> See http://www.khelekore.org/rabbit/
>> RabbIT is a web proxy that speeds up web surfing over slow links by doing:
>>
>>     * Compress text pages to gzip streams. This reduces size by up to 75%
>>     * Compress images to 10% jpeg. This reduces size by up to 95%
>>     * Remove advertising
>>     * Remove background images
>>     * Cache filtered pages and images
>>     * Uses keepalive if possible
>>     * Easy and powerful configuration
>>     * Multi threaded solution written in java
>>     * Modular and easily extended
>>     * Complete HTTP/1.1 compliance 
> 
> Might make a good interloper for harvesting web pages! Look at all the 
> stuff it says it can do...
> java/bsd



-- 
Arjohn Kampman, Senior Software Engineer
Aduna - Guided Exploration
www.aduna-software.com

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov 29 11:43:50 2006
X-Account-Key: account3
X-UIDL: 0000ed56040394c1
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:30876 "EHLO
	lists-outbound.sourceforge.net") by ps18.test.onet.pl with ESMTP
	id <S7937997AbWK2KQo>; Wed, 29 Nov 2006 11:16:44 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 717831322C; Wed, 29 Nov 2006 01:49:47 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GpM4V-0000Jk-Rp for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 01:49:43 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GpM4S-0007TM-Hw
	for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 01:49:45 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kAT9nXgB001390 for <aperture-devel@lists.sourceforge.net>;
	Wed, 29 Nov 2006 10:49:33 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kAT9nWY11608; Wed, 29 Nov 2006 10:49:32 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kAT9nVkX023538; Wed, 29 Nov 2006 10:49:31 +0100 (CET)
Message-ID: <456D5798.2020205@dfki.de>
Date:	Wed, 29 Nov 2006 10:49:12 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
References: <456C7961.7020108@dfki.uni-kl.de>
In-Reply-To: <456C7961.7020108@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] OSGI packaging.
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

very good!

could you copy your text into the /doc/ folder, in some html about 
OSGIaperturte
and link to it from the main doc page?

we can then update the doc on the sf website.

best
Leo

Es begab sich aber da Antoni Mylka zur rechten Zeit 28.11.2006 19:01 
folgendes schrieb:
> After two weeks of learning, researching and programming, I am pleased
> to present the OSGI incarnation of Aperture...
>
> What is done:
>
> * 6 'Middle-grained' Bundles: *
>
> 1. Core services
> 2. Supporting services
> 3. Vocabulary
> 4. Util
> 5. Core implementations
> 6. Supporting implementations
>
> * 2. 'Coarse-grained' bundles *
>
> 1. Core ( 1-4 taken together )
> 2. Impl ( 5-6 taken together )
>
> 52 Activators
> - Service activators - register a service (e.g. Extractor Registry). Use 
> a service tracker to detect all incoming factories. If factories 
> thisappear, they are also automatically unregistered. This assumes that 
> every factory registers an osgi service on it's own under the generic 
> name of an interface (e.g. 
> org.semanticdesktop.aperture.accessor.DataAccessorFactory).
>
> - Implementation activators. Register factories as OSGI services (which 
> are in turn detected by registries).
>
> The activators are chained one for every 'elementary' bundle. There
> is a set of broader activators, that simply start and stop appropriate
> elementary activators.
>
> Activators are stored in a separate directory.
>
> Build infrastructure
>   * build.xml - Is more than 1000 lines longer than it used to be. Every
>     'elementary' bundle has it's own selector. It selects the source
>     the generated classes, all resources and libraries needed by every
>     elementary bundle. Every 'elementary' selector could potentially be
>     used as a basis for an 'elementary' jar file. (If we wanted to split
>     aperture into 40 bundles).
>   * 8 manifest files. Only two actually work. I didn't manage to persuade
>     mangen into doing what I wanted it to do. I wrote them by myself.
>     Mangen is disabled in the build script and could safely be deleted
>     from the CVS. The necessity to determine the required bundles,
>     imports and exports manually took too much time. I haven't managed
>     to make the six 'middle-grained' bundles work. I disabled their
>     creation in the build script. They can easily be re-enabled.
>
> We could use eclipse PDE. Every bundle could be a separate project that 
> imports source files from the aperture directory (with the help of the 
> eclipse include/exclude facility). We would loose the possibility of 
> automatic builds though. It wouldn't solve the problem of having to 
> maintain 40 manifests either. This is the only problem.
>
> Conclusion:
>
> If you really think about dividing aperture into the smallest possible 
> units, some kind of automatic manifest-generating facility is necessary.
>
> Issues:
>
> I moved the MailUtil class from the util package because it would
> introduce a dependency on mail....jar for the core bundle
>
> All classes from the core bundle that refer directly to org.openrdf
> will not work (that is: RepositoryUtil, RepositoryAccessData etc.) This 
> would introduce a dependency on sesame.
>
> The ResourceUtil methods got a second argument (that is a class that
> originates the request). It didn't work under OSGI since every bundle
> has it's own classloader and the resource lookup wouldn't work.
>
> 7. Added an OutlookAccessorFactory
>
> -------------------------------------------------------------------------
>
> EXAMPLE:
>
> I've written a simple example of the FileSystemCrawler. It doesn't have
> any interface (yet...) the path to the root directory and to the
> repository file is hard-coded in:
>
> src/examples/org/semanticdesktop/aperture/examples/osgi/ExampleFileCrawlerActivator.java
>
> line number 66.
>
> If you want to see it in action do the following:
>
> 1. download the 'distribution' from
> http://www.dfki.uni-kl.de/~mylka/aperture-20061128.zip. It contains two 
> full-featured execution environments - Equinox and Knopflerfish. This 
> example works under Equinox but fails under Knopflerfish. I have been 
> unable to find out why.
>
> 2. Unpack it and edit the file mentioned above.
> 3. type 'ant osgi.dist'
> 4. Go to the directory build/dist/bundles
> 5. run the run.aperture.sh script (I did it on linux, it shouldn't be
> too difficult to adjust it to work under windows
> 6. When the osgi prompt appears, type 'ss' to show the list of bundles.
> There should be 10 started bundles and the 11'th one should be the
> aperture-example.
> 7. type start 11. The example will start to crawl the given directory
> and will store the rdf in the given file. (Hopefully)
>
> Any comments welcome
>
> Antoni Mylka
> antoni.mylka@dkfi.de
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov 29 20:04:59 2006
X-Account-Key: account3
X-UIDL: 0000ed560404e090
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:27790 "EHLO
	lists-outbound.sourceforge.net") by ps6.test.onet.pl with ESMTP
	id <S6267645AbWK2RsG>; Wed, 29 Nov 2006 18:48:06 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 079AD134A5; Wed, 29 Nov 2006 06:44:49 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GpQcg-0005HU-0Y for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 06:41:18 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GpQcc-0001Ka-1I
	for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 06:41:15 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kATEf83l016270; Wed, 29 Nov 2006 15:41:08 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kATEf8Y14686; Wed, 29 Nov 2006 15:41:08 +0100 (MET)
Received: from [192.168.41.35] (port-4125.kl.dfki.de [192.168.41.35])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kATEf7fb027303; Wed, 29 Nov 2006 15:41:07 +0100 (CET)
Message-ID: <456D9C05.2030504@dfki.uni-kl.de>
Date:	Wed, 29 Nov 2006 15:41:09 +0100
From:	Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Leo Sauermann <leo.sauermann@dfki.de>
References: <456D68B2.8030208@dfki.uni-kl.de> <456D87F8.30006@dfki.de>
In-Reply-To: <456D87F8.30006@dfki.de>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kATEf83l016270
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Dublin core vocabulary
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Leo Sauermann napisa=B3(a):
> Hey,
>
> could you just add the DCES, DCTERMs and DCTYPE proerpties and classes =

> into the DATA vocabulary,
> possibly by doing subclasses or sub-interfaces?
>
> having four imports in each file (import org....dc, import =

> org...dcterms, import org....DATA) is exactly the "over-engineered" =

> approach that most python hackers will laugh at :-)
Did as you said. Had to alter VocabularyWriter a little. Now it creates =

Interfaces (not classes) and the CLASS_NAME.NS field is now called =

CLASS_NAME.NS_CLASS_NAME. This allows for a class to implement multiple =

interfaces (as long as field names don't overlap). DATA class implements =

four interfaces now: (DATA_GEN, DCES_GEN, DCTERMS_GEN and DCTYPE_GEN.

Antoni My=B3ka
antoni.mylka@dfki.de

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov 29 20:05:01 2006
X-Account-Key: account3
X-UIDL: 0000ed560404fe55
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:6074 "EHLO
	lists-outbound.sourceforge.net") by ps15.test.onet.pl with ESMTP
	id <S14157014AbWK2Rf0>; Wed, 29 Nov 2006 18:35:26 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id E06B113893; Wed, 29 Nov 2006 09:35:17 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GpTL0-0000Gz-GI for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 09:35:14 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GpTL0-0001vx-Am
	for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 09:35:15 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kATHZ2WO029705 for <aperture-devel@lists.sourceforge.net>;
	Wed, 29 Nov 2006 18:35:02 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kATHZ2Y24267; Wed, 29 Nov 2006 18:35:02 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kATHZ1Ls018417; Wed, 29 Nov 2006 18:35:01 +0100 (CET)
Message-ID: <456DC4B2.3040303@dfki.de>
Date:	Wed, 29 Nov 2006 18:34:42 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
References: <456D68B2.8030208@dfki.uni-kl.de> <456D87F8.30006@dfki.de>
	<456D9C05.2030504@dfki.uni-kl.de>
In-Reply-To: <456D9C05.2030504@dfki.uni-kl.de>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kATHZ2WO029705
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Dublin core vocabulary
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Hi Antoni,

just to check:
do you agree with this approach, is it better for the developers?
or was the idea not so good because of some drawback I forgot.

Es begab sich aber da Antoni Mylka zur rechten Zeit 29.11.2006 15:41 =

folgendes schrieb:
> Leo Sauermann napisa=B3(a):
>> Hey,
>>
>> could you just add the DCES, DCTERMs and DCTYPE proerpties and =

>> classes into the DATA vocabulary,
>> possibly by doing subclasses or sub-interfaces?
>>
>> having four imports in each file (import org....dc, import =

>> org...dcterms, import org....DATA) is exactly the "over-engineered" =

>> approach that most python hackers will laugh at :-)
> Did as you said. Had to alter VocabularyWriter a little. Now it =

> creates Interfaces (not classes) and the CLASS_NAME.NS field is now =

> called CLASS_NAME.NS_CLASS_NAME. This allows for a class to implement =

> multiple interfaces (as long as field names don't overlap). DATA class =

> implements four interfaces now: (DATA_GEN, DCES_GEN, DCTERMS_GEN and =

> DCTYPE_GEN.
>
> Antoni My=B3ka
> antoni.mylka@dfki.de


-- =

____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann =

DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Nov 29 20:05:02 2006
X-Account-Key: account3
X-UIDL: 0000ed560405090e
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:30647 "EHLO
	lists-outbound.sourceforge.net") by ps27.test.onet.pl with ESMTP
	id <S5724390AbWK2Spk>; Wed, 29 Nov 2006 19:45:40 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id EE402138E3; Wed, 29 Nov 2006 10:45:37 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GpUR4-0007uo-2K for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 10:45:34 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GpUR0-0000aU-Au
	for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 10:45:32 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kATIjK31025001; Wed, 29 Nov 2006 19:45:20 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kATIjJY27976; Wed, 29 Nov 2006 19:45:19 +0100 (MET)
Received: from [192.168.41.35] (port-4125.kl.dfki.de [192.168.41.35])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kATIjIAv003821; Wed, 29 Nov 2006 19:45:19 +0100 (CET)
Message-ID: <456DD541.7090405@dfki.uni-kl.de>
Date:	Wed, 29 Nov 2006 19:45:21 +0100
From:	Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Leo Sauermann <leo.sauermann@dfki.de>,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <456C7961.7020108@dfki.uni-kl.de> <456D5798.2020205@dfki.de>
In-Reply-To: <456D5798.2020205@dfki.de>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kATIjK31025001
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] OSGI packaging.
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

TGVvIFNhdWVybWFubiBuYXBpc2HFgihhKToKPiB2ZXJ5IGdvb2QhCj4gCj4gY291bGQgeW91IGNv
cHkgeW91ciB0ZXh0IGludG8gdGhlIC9kb2MvIGZvbGRlciwgaW4gc29tZSBodG1sIGFib3V0IAo+
IE9TR0lhcGVydHVydGUKPiBhbmQgbGluayB0byBpdCBmcm9tIHRoZSBtYWluIGRvYyBwYWdlPwo+
IAo+IHdlIGNhbiB0aGVuIHVwZGF0ZSB0aGUgZG9jIG9uIHRoZSBzZiB3ZWJzaXRlLgo+IAo+IGJl
c3QKPiBMZW8KPiAKCkkndmUgd3JpdHRlbiBhIHRleHQuIEl0IGlzIGluIHRoZSBkb2MvdHV0b3Jp
YWwvb3NnaS5odG1sLiBQdWJsaXNoaW5nIGl0IApvbiB0aGUgd2Vic2l0ZSB3b3VsZCBub3QgYmUg
YSBnb29kIGlkZWEsIHNpbmNlIGl0IHJlZmVycyB0byB0aGUgQ1ZTIApzbmFwc2hvdCwgbm90IHRo
ZSBjdXJyZW50IHJlbGVhc2UuCgpJZiB3ZSB3ZXJlIHRvIG1ha2UgYSBuZXcgcmVsZWFzZSBiZWZv
cmUgY2hyaXN0bWFzLCBlbnRpcmUgZG9jdW1lbnRhdGlvbiAKd291bGQgbmVlZCB0byBiZSByZXdv
cmtlZCwgc29tZSBub3RlIGFib3V0IFJERjJHbyBzaG91bGQgYmUgYWRkZWQsIApleGFtcGxlcyBz
aG91bGQgYmUgcmV3cml0dGVuLiBJdCB3b3VsZCBhbHNvIGJlIGEgZ29vZCBvcG9ydHVuaXR5IHRv
IApjb252ZXJ0IHRoZSBkb2NzIHRvIHNvbWUgbW9yZSBnZW5lcmljIGZvcm1hdCAoTGF0ZXgsIERv
Y2Jvb2ssIHdoYXRldmVyKSAKdG8gbWFrZSBpdCBwb3NzaWJsZSB0byBnZW5lcmF0ZSBuaWNlLWxv
b2tpbmcgSFRNTCBhbmQgUERGIHZlcnNpb25zLgoKQW50b25pIE15bGthCmFudG9uaS5teWxrYUBk
ZmtpLmRlCgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tClRha2UgU3VydmV5cy4gRWFybiBDYXNoLiBJbmZsdWVu
Y2UgdGhlIEZ1dHVyZSBvZiBJVApKb2luIFNvdXJjZUZvcmdlLm5ldCdzIFRlY2hzYXkgcGFuZWwg
YW5kIHlvdSdsbCBnZXQgdGhlIGNoYW5jZSB0byBzaGFyZSB5b3VyCm9waW5pb25zIG9uIElUICYg
YnVzaW5lc3MgdG9waWNzIHRocm91Z2ggYnJpZWYgc3VydmV5cyAtIGFuZCBlYXJuIGNhc2gKaHR0
cDovL3d3dy50ZWNoc2F5LmNvbS9kZWZhdWx0LnBocD9wYWdlPWpvaW4ucGhwJnA9c291cmNlZm9y
Z2UmQ0lEPURFVkRFVgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXwpBcGVydHVyZS1kZXZlbCBtYWlsaW5nIGxpc3QKQXBlcnR1cmUtZGV2ZWxAbGlzdHMuc291
cmNlZm9yZ2UubmV0Cmh0dHBzOi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZv
L2FwZXJ0dXJlLWRldmVsCg==

From - Thu Nov 30 09:34:43 2006
X-Account-Key: account3
X-UIDL: 0000ed560405b727
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:37091 "EHLO
	lists-outbound.sourceforge.net") by ps8.test.onet.pl with ESMTP
	id <S5655871AbWK2NUc>; Wed, 29 Nov 2006 14:20:32 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id A6449134BD; Wed, 29 Nov 2006 05:20:28 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GpPIB-00055c-4o for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 05:16:03 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GpPI9-0001VP-J9
	for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 05:16:04 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kATDFukR009079 for <aperture-devel@lists.sourceforge.net>;
	Wed, 29 Nov 2006 14:15:56 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kATDFuY09798; Wed, 29 Nov 2006 14:15:56 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kATDFtZS004666; Wed, 29 Nov 2006 14:15:55 +0100 (CET)
Message-ID: <456D87F8.30006@dfki.de>
Date:	Wed, 29 Nov 2006 14:15:36 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
References: <456D68B2.8030208@dfki.uni-kl.de>
In-Reply-To: <456D68B2.8030208@dfki.uni-kl.de>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kATDFukR009079
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] Dublin core vocabulary
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Hey,

could you just add the DCES, DCTERMs and DCTYPE proerpties and classes =

into the DATA vocabulary,
possibly by doing subclasses or sub-interfaces?

having four imports in each file (import org....dc, import =

org...dcterms, import org....DATA) is exactly the "over-engineered" =

approach that most python hackers will laugh at :-)

I would see the aperture-Java class "DATA" as the vocubulary class that =

gathers all NEEDED vocabularies, so that developers don't have to search =

three files to see which properties and classes are endorsed by aperture =

- think of people:
* I write an extractor, I want to know what properties / classes I can =

use to describe extracted data - what do I do? I open DATA.java and have =

all of them
* I write a user interface, showing search results. Something comes =

back, a property "http://....dc/title" - what does this mean? I open =

DATA.java and see what it is about.

best
Leo

Es begab sich aber da Antoni Mylka zur rechten Zeit 29.11.2006 12:02 =

folgendes schrieb:
> 1. I have added six classes generated from dublin core schemas:
>
> DCES (Dublin Core Metadata Element Set http://purl.org/dc/elements/1.1/)
> DCTERMS (Other elements, Refinements etc. http://purl.org/dc/terms/)
> DCTYPE (DCMI Type Vocabulary http://purl.org/dc/dcmitype/)
>
> 2. Removed the following properties from the data ontology (and the DATA =

> Vocabulary class)
>
> created
> creator
> date
> description
> language
> modified
> subject
> title
>
> Replaced all occurences of those properties with references to =

> appropriate DC vocabularies.
>
> Antoni My=B3ka
> antoni.mylka@dfki.uni-kl.de
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>
>   =



-- =

____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann =

DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov 30 09:34:43 2006
X-Account-Key: account3
X-UIDL: 0000ed560405d14b
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:19425 "EHLO
	lists-outbound.sourceforge.net") by ps27.test.onet.pl with ESMTP
	id <S4990975AbWK1SBZ>; Tue, 28 Nov 2006 19:01:25 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 715D812660; Tue, 28 Nov 2006 10:01:24 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gp7Gg-0000MD-Di for aperture-devel@lists.sourceforge.net;
	Tue, 28 Nov 2006 10:01:18 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gp7Gf-0004er-3G
	for aperture-devel@lists.sourceforge.net;
	Tue, 28 Nov 2006 10:01:19 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kASI16Aj016738 for <aperture-devel@lists.sourceforge.net>;
	Tue, 28 Nov 2006 19:01:06 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kASI15Y26070 for <aperture-devel@lists.sourceforge.net>;
	Tue, 28 Nov 2006 19:01:05 +0100 (MET)
Received: from [192.168.41.35] (port-4125.kl.dfki.de [192.168.41.35])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kASI14ss029163 for <aperture-devel@lists.sourceforge.net>;
	Tue, 28 Nov 2006 19:01:04 +0100 (CET)
Message-ID: <456C7961.7020108@dfki.uni-kl.de>
Date:	Tue, 28 Nov 2006 19:01:05 +0100
From:	Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] OSGI packaging.
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

After two weeks of learning, researching and programming, I am pleased
to present the OSGI incarnation of Aperture...

What is done:

* 6 'Middle-grained' Bundles: *

1. Core services
2. Supporting services
3. Vocabulary
4. Util
5. Core implementations
6. Supporting implementations

* 2. 'Coarse-grained' bundles *

1. Core ( 1-4 taken together )
2. Impl ( 5-6 taken together )

52 Activators
- Service activators - register a service (e.g. Extractor Registry). Use 
a service tracker to detect all incoming factories. If factories 
thisappear, they are also automatically unregistered. This assumes that 
every factory registers an osgi service on it's own under the generic 
name of an interface (e.g. 
org.semanticdesktop.aperture.accessor.DataAccessorFactory).

- Implementation activators. Register factories as OSGI services (which 
are in turn detected by registries).

The activators are chained one for every 'elementary' bundle. There
is a set of broader activators, that simply start and stop appropriate
elementary activators.

Activators are stored in a separate directory.

Build infrastructure
  * build.xml - Is more than 1000 lines longer than it used to be. Every
    'elementary' bundle has it's own selector. It selects the source
    the generated classes, all resources and libraries needed by every
    elementary bundle. Every 'elementary' selector could potentially be
    used as a basis for an 'elementary' jar file. (If we wanted to split
    aperture into 40 bundles).
  * 8 manifest files. Only two actually work. I didn't manage to persuade
    mangen into doing what I wanted it to do. I wrote them by myself.
    Mangen is disabled in the build script and could safely be deleted
    from the CVS. The necessity to determine the required bundles,
    imports and exports manually took too much time. I haven't managed
    to make the six 'middle-grained' bundles work. I disabled their
    creation in the build script. They can easily be re-enabled.

We could use eclipse PDE. Every bundle could be a separate project that 
imports source files from the aperture directory (with the help of the 
eclipse include/exclude facility). We would loose the possibility of 
automatic builds though. It wouldn't solve the problem of having to 
maintain 40 manifests either. This is the only problem.

Conclusion:

If you really think about dividing aperture into the smallest possible 
units, some kind of automatic manifest-generating facility is necessary.

Issues:

I moved the MailUtil class from the util package because it would
introduce a dependency on mail....jar for the core bundle

All classes from the core bundle that refer directly to org.openrdf
will not work (that is: RepositoryUtil, RepositoryAccessData etc.) This 
would introduce a dependency on sesame.

The ResourceUtil methods got a second argument (that is a class that
originates the request). It didn't work under OSGI since every bundle
has it's own classloader and the resource lookup wouldn't work.

7. Added an OutlookAccessorFactory

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

EXAMPLE:

I've written a simple example of the FileSystemCrawler. It doesn't have
any interface (yet...) the path to the root directory and to the
repository file is hard-coded in:

src/examples/org/semanticdesktop/aperture/examples/osgi/ExampleFileCrawlerActivator.java

line number 66.

If you want to see it in action do the following:

1. download the 'distribution' from
http://www.dfki.uni-kl.de/~mylka/aperture-20061128.zip. It contains two 
full-featured execution environments - Equinox and Knopflerfish. This 
example works under Equinox but fails under Knopflerfish. I have been 
unable to find out why.

2. Unpack it and edit the file mentioned above.
3. type 'ant osgi.dist'
4. Go to the directory build/dist/bundles
5. run the run.aperture.sh script (I did it on linux, it shouldn't be
too difficult to adjust it to work under windows
6. When the osgi prompt appears, type 'ss' to show the list of bundles.
There should be 10 started bundles and the 11'th one should be the
aperture-example.
7. type start 11. The example will start to crawl the given directory
and will store the rdf in the given file. (Hopefully)

Any comments welcome

Antoni Mylka
antoni.mylka@dkfi.de

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov 30 11:49:46 2006
X-Account-Key: account3
X-UIDL: 0000ed56040730cb
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:48103 "EHLO
	lists-outbound.sourceforge.net") by ps4.test.onet.pl with ESMTP
	id <S3954504AbWK2ShN>; Wed, 29 Nov 2006 19:37:13 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 46FA0139A0; Wed, 29 Nov 2006 09:39:05 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GpTOf-0000cQ-Lt for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 09:39:01 -0800
Received: from balboa.ai.sri.com ([130.107.64.135])
	by mail.sourceforge.net with esmtp (Exim 4.44) id 1GpTOf-0001cY-Ob
	for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 09:39:03 -0800
Received: from Balboa.AI.SRI.COM (localhost [127.0.0.1])
	by Balboa.AI.SRI.COM (8.11.7p2+Sun/8.10.1) with SMTP id kATHcpS08551
	for <aperture-devel@lists.sourceforge.net>;
	Wed, 29 Nov 2006 09:38:51 -0800 (PST)
Received: from Salt.AI.SRI.COM ([130.107.65.211])
	by Balboa.AI.SRI.COM (SMSSMTP 4.1.9.35) with SMTP id
	M2006112909385012795 for <aperture-devel@lists.sourceforge.net>;
	Wed, 29 Nov 2006 09:38:50 -0800
Received: from localhost.ai.sri.com
	([127.0.0.1] helo=[130.107.65.21] ident=root)
	by Salt.AI.SRI.COM with asmtp (Exim 3.35 #1 (Debian))
	id 1GpTOU-00035y-00 for <aperture-devel@lists.sourceforge.net>;
	Wed, 29 Nov 2006 09:38:50 -0800
Message-ID: <456DC5A5.6080605@sri.com>
Date:	Wed, 29 Nov 2006 09:38:45 -0800
From:	Jack Park <jack.park@sri.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <456D68B2.8030208@dfki.uni-kl.de> <456D87F8.30006@dfki.de>
	<456D9C05.2030504@dfki.uni-kl.de> <456DC4B2.3040303@dfki.de>
In-Reply-To: <456DC4B2.3040303@dfki.de>
X-MIME-Autoconverted: from 8bit to quoted-printable by Balboa.AI.SRI.COM id
	kATHcpS08551
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Dublin core vocabulary
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Seems to me that "self documenting" at the interface level, no matter =

how the implementation takes place is always useful.

+1 on moving to standardized properties.

Cheers
Jack

Leo Sauermann wrote:
> Hi Antoni,
> =

> just to check:
> do you agree with this approach, is it better for the developers?
> or was the idea not so good because of some drawback I forgot.
> =

> Es begab sich aber da Antoni Mylka zur rechten Zeit 29.11.2006 15:41 =

> folgendes schrieb:
>> Leo Sauermann napisa=B3(a):
>>> Hey,
>>>
>>> could you just add the DCES, DCTERMs and DCTYPE proerpties and =

>>> classes into the DATA vocabulary,
>>> possibly by doing subclasses or sub-interfaces?
>>>
>>> having four imports in each file (import org....dc, import =

>>> org...dcterms, import org....DATA) is exactly the "over-engineered" =

>>> approach that most python hackers will laugh at :-)
>> Did as you said. Had to alter VocabularyWriter a little. Now it =

>> creates Interfaces (not classes) and the CLASS_NAME.NS field is now =

>> called CLASS_NAME.NS_CLASS_NAME. This allows for a class to implement =

>> multiple interfaces (as long as field names don't overlap). DATA class =

>> implements four interfaces now: (DATA_GEN, DCES_GEN, DCTERMS_GEN and =

>> DCTYPE_GEN.
>>
>> Antoni My=B3ka
>> antoni.mylka@dfki.de
> =

> =



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Nov 30 11:49:46 2006
X-Account-Key: account3
X-UIDL: 0000ed560407401f
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:52430 "EHLO
	lists-outbound.sourceforge.net") by ps4.test.onet.pl with ESMTP
	id <S4444439AbWK2SyC>; Wed, 29 Nov 2006 19:54:02 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 5F57C12234; Wed, 29 Nov 2006 10:23:19 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GpU5U-0005NH-Si for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 10:23:17 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GpU5T-00015I-MH
	for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 10:23:18 -0800
Received: (qmail 25291 invoked from network); 29 Nov 2006 19:23:04 +0100
Received: from 5353a894.cable.casema.nl (HELO ?83.83.168.148?) (83.83.168.148)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	29 Nov 2006 19:23:04 +0100
Message-ID: <456DD005.2000003@aduna-software.com>
Date:	Wed, 29 Nov 2006 19:23:01 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <456D68B2.8030208@dfki.uni-kl.de>
	<456D87F8.30006@dfki.de>	<456D9C05.2030504@dfki.uni-kl.de>
	<456DC4B2.3040303@dfki.de> <456DC5A5.6080605@sri.com>
In-Reply-To: <456DC5A5.6080605@sri.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Dublin core vocabulary
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

I also agree, sounds like a good balance between maintainability at our =

side and developer ease. Furthermore certain Extractor implementations =

can now be simplified as their corresponding document formats already =

use DC, e.g. OpenDocument and Open XML.

Chris
--

Jack Park wrote:
> Seems to me that "self documenting" at the interface level, no matter =

> how the implementation takes place is always useful.
> =

> +1 on moving to standardized properties.
> =

> Cheers
> Jack
> =

> Leo Sauermann wrote:
>> Hi Antoni,
>>
>> just to check:
>> do you agree with this approach, is it better for the developers?
>> or was the idea not so good because of some drawback I forgot.
>>
>> Es begab sich aber da Antoni Mylka zur rechten Zeit 29.11.2006 15:41 =

>> folgendes schrieb:
>>> Leo Sauermann napisa=B3(a):
>>>> Hey,
>>>>
>>>> could you just add the DCES, DCTERMs and DCTYPE proerpties and =

>>>> classes into the DATA vocabulary,
>>>> possibly by doing subclasses or sub-interfaces?
>>>>
>>>> having four imports in each file (import org....dc, import =

>>>> org...dcterms, import org....DATA) is exactly the "over-engineered" =

>>>> approach that most python hackers will laugh at :-)
>>> Did as you said. Had to alter VocabularyWriter a little. Now it =

>>> creates Interfaces (not classes) and the CLASS_NAME.NS field is now =

>>> called CLASS_NAME.NS_CLASS_NAME. This allows for a class to implement =

>>> multiple interfaces (as long as field names don't overlap). DATA class =

>>> implements four interfaces now: (DATA_GEN, DCES_GEN, DCTERMS_GEN and =

>>> DCTYPE_GEN.
>>>
>>> Antoni My=B3ka
>>> antoni.mylka@dfki.de
>>
> =

> =

> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel


Met vriendelijke groet,

Christiaan Fluit
-- =

Aduna - Guided Exploration
www.aduna-software.com

Prinses Julianaplein 14-b
3817 CS Amersfoort
The Netherlands
+31-33-4659987 (office)

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Dec  4 09:03:14 2006
X-Account-Key: account3
X-UIDL: 0000ed56040bb137
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:57272 "EHLO
	lists-outbound.sourceforge.net") by ps25.test.onet.pl with ESMTP
	id <S5635776AbWK2LEV>; Wed, 29 Nov 2006 12:04:21 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 57F701349C; Wed, 29 Nov 2006 03:04:16 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GpNCg-00086c-6C for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 03:02:14 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GpNCf-0006jf-Ui
	for aperture-devel@lists.sourceforge.net;
	Wed, 29 Nov 2006 03:02:15 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kATB29tE013524 for <aperture-devel@lists.sourceforge.net>;
	Wed, 29 Nov 2006 12:02:09 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kATB28Y16661 for <aperture-devel@lists.sourceforge.net>;
	Wed, 29 Nov 2006 12:02:09 +0100 (MET)
Received: from [192.168.41.35] (port-4125.kl.dfki.de [192.168.41.35])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kATB27ED016951 for <aperture-devel@lists.sourceforge.net>;
	Wed, 29 Nov 2006 12:02:08 +0100 (CET)
Message-ID: <456D68B2.8030208@dfki.uni-kl.de>
Date:	Wed, 29 Nov 2006 12:02:10 +0100
From:	Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kATB29tE013524
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] Dublin core vocabulary
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

1. I have added six classes generated from dublin core schemas:

DCES (Dublin Core Metadata Element Set http://purl.org/dc/elements/1.1/)
DCTERMS (Other elements, Refinements etc. http://purl.org/dc/terms/)
DCTYPE (DCMI Type Vocabulary http://purl.org/dc/dcmitype/)

2. Removed the following properties from the data ontology (and the DATA =

Vocabulary class)

created
creator
date
description
language
modified
subject
title

Replaced all occurences of those properties with references to =

appropriate DC vocabularies.

Antoni My=B3ka
antoni.mylka@dfki.uni-kl.de

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Dec  4 09:03:17 2006
X-Account-Key: account3
X-UIDL: 0000ed56040c3f7b
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:6539 "EHLO
	lists-outbound.sourceforge.net") by ps5.test.onet.pl with ESMTP
	id <S3794096AbWLAE7u>; Fri, 1 Dec 2006 05:59:50 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 313741229C; Thu, 30 Nov 2006 20:01:00 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GpzZO-0007AF-SV for aperture-devel@lists.sourceforge.net;
	Thu, 30 Nov 2006 20:00:14 -0800
Received: from smtp1.rz.uni-karlsruhe.de ([129.13.185.217] ident=Debian-exim)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GpzZM-00083s-WB
	for aperture-devel@lists.sourceforge.net;
	Thu, 30 Nov 2006 20:00:16 -0800
Received: from ontoware.org (aifbontoware.aifb.uni-karlsruhe.de
	[172.22.131.111])
	by smtp1.rz.uni-karlsruhe.de with esmtp (Exim 4.50 #1)
	id 1GpzZG-0000aO-PM; Fri, 01 Dec 2006 05:00:06 +0100
Received: from [127.0.0.1] (helo=aifbontoware.aifb.uni-karlsruhe.de)
	by ontoware.org with esmtp (Exim 4.63)
	(envelope-from <mailman-bounces@ontoware.org>) id 1GpzZF-0005F4-SK
	for aperture-devel@lists.sourceforge.net;
	Fri, 01 Dec 2006 05:00:05 +0100
MIME-Version: 1.0
From:	mailman-owner@ontoware.org
To:	aperture-devel@lists.sourceforge.net
X-No-Archive: yes
Message-ID: <mailman.32.1164945602.19981.mailman@ontoware.org>
Date:	Fri, 01 Dec 2006 05:00:02 +0100
Precedence: bulk
X-BeenThere: mailman@ontoware.org
X-Mailman-Version: 2.1.7
X-List-Administrivia: yes
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.2 NO_REAL_NAME           From: does not include a real name
	1.0 FORGED_RCVD_HELO       Received: contains a forged HELO
Subject: [Aperture-devel] ontoware.org mailing list memberships reminder
X-BeenThere: aperture-devel@lists.sourceforge.net
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a reminder, sent out once a month, about your ontoware.org
mailing list memberships.  It includes your subscription info and how
to use it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ontoware.org) containing just
the word 'help' in the message body, and an email message will be sent
to you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ontoware.org.  Thanks!

Passwords for aperture-devel@lists.sourceforge.net:

List                                     Password // URL
----                                     --------  
rdf2go-devel@ontoware.org                esdukaan  
http://ontoware.org/mailman/options/rdf2go-devel/aperture-devel%40lists.sourceforge.net

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Dec  4 09:57:45 2006
X-Account-Key: account3
X-UIDL: 0000ed56041358c2
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:62168 "EHLO
	lists-outbound.sourceforge.net") by ps15.test.onet.pl with ESMTP
	id <S13709356AbWLDItc>; Mon, 4 Dec 2006 09:49:32 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 4614512BE3; Mon,  4 Dec 2006 00:49:30 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Gr9Vv-0001iT-78 for aperture-devel@lists.sourceforge.net;
	Mon, 04 Dec 2006 00:49:27 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Gr9Vu-0007rD-TF
	for aperture-devel@lists.sourceforge.net;
	Mon, 04 Dec 2006 00:49:28 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kB48nLeW026684 for <aperture-devel@lists.sourceforge.net>;
	Mon, 4 Dec 2006 09:49:21 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kB48nLY16308; Mon, 4 Dec 2006 09:49:21 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kB48nJxl018509; Mon, 4 Dec 2006 09:49:20 +0100 (CET)
Message-ID: <4573E0F4.7020704@dfki.de>
Date:	Mon, 04 Dec 2006 09:48:52 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
References: <456C7961.7020108@dfki.uni-kl.de> <456D5798.2020205@dfki.de>
	<456DD541.7090405@dfki.uni-kl.de>
In-Reply-To: <456DD541.7090405@dfki.uni-kl.de>
X-Spam-Score: 0.1 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.1 HTML_30_40             BODY: Message is 30% to 40% HTML
	0.0 HTML_MESSAGE           BODY: HTML included in message
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] doc / bibtex / release
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0467782663=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============0467782663==
Content-Type: multipart/alternative;
	boundary="------------070002070003010206040209"

This is a multi-part message in MIME format.
--------------070002070003010206040209
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kB48nLeW026684

Hi Guys,

looking at our workload at DFKI (Nepomuk's first deliverables are due=20
12/2006),
I think a release would be too much now.
end of january?

Btw: does anyone (Jack?) have time to make a bibtex datasource and crawle=
r?

doc:
the sesame guys use docbook XML to create their docs, maybe we should=20
use that.
I don't fancy these systems very much, html and a good CSS should do it,
but surely docbook is better than nothing.
we can give it a try .. when?

best
Leo

Es begab sich aber da Antoni Mylka zur rechten Zeit 29.11.2006 19:45=20
folgendes schrieb:
> Leo Sauermann napisa=C5=82(a):
>  =20
>> very good!
>>
>> could you copy your text into the /doc/ folder, in some html about=20
>> OSGIaperturte
>> and link to it from the main doc page?
>>
>> we can then update the doc on the sf website.
>>
>> best
>> Leo
>>
>>    =20
>
> I've written a text. It is in the doc/tutorial/osgi.html. Publishing it=
=20
> on the website would not be a good idea, since it refers to the CVS=20
> snapshot, not the current release.
>
> If we were to make a new release before christmas, entire documentation=
=20
> would need to be reworked, some note about RDF2Go should be added,=20
> examples should be rewritten. It would also be a good oportunity to=20
> convert the docs to some more generic format (Latex, Docbook, whatever)=
=20
> to make it possible to generate nice-looking HTML and PDF versions.
>
> Antoni Mylka
> antoni.mylka@dfki.de
>
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share=
 your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>
>  =20


--=20
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann=20
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------070002070003010206040209
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	kB48nLeW026684

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"=
>
</head>
<body bgcolor=3D"#ffffff" text=3D"#000000">
Hi Guys,<br>
<br>
looking at our workload at DFKI (Nepomuk's first deliverables are due
12/2006),<br>
I think a release would be too much now.<br>
end of january?<br>
<br>
Btw: does anyone (Jack?) have time to make a bibtex datasource and
crawler?<br>
<br>
doc:<br>
the sesame guys use docbook XML to create their docs, maybe we should
use that.<br>
I don't fancy these systems very much, html and a good CSS should do it,<=
br>
but surely docbook is better than nothing.<br>
we can give it a try .. when?<br>
<br>
best<br>
Leo<br>
<br>
Es begab sich aber da Antoni Mylka zur rechten Zeit 29.11.2006 19:45
folgendes schrieb:
<blockquote cite=3D"mid456DD541.7090405@dfki.uni-kl.de" type=3D"cite">
  <pre wrap=3D"">Leo Sauermann napisa=C5=82(a):
  </pre>
  <blockquote type=3D"cite">
    <pre wrap=3D"">very good!

could you copy your text into the /doc/ folder, in some html about=20
OSGIaperturte
and link to it from the main doc page?

we can then update the doc on the sf website.

best
Leo

    </pre>
  </blockquote>
  <pre wrap=3D""><!---->
I've written a text. It is in the doc/tutorial/osgi.html. Publishing it=20
on the website would not be a good idea, since it refers to the CVS=20
snapshot, not the current release.

If we were to make a new release before christmas, entire documentation=20
would need to be reworked, some note about RDF2Go should be added,=20
examples should be rewritten. It would also be a good oportunity to=20
convert the docs to some more generic format (Latex, Docbook, whatever)=20
to make it possible to generate nice-looking HTML and PDF versions.

Antoni Mylka
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:antoni.mylka@dfki.de=
">antoni.mylka@dfki.de</a>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
opinions on IT &amp; business topics through brief surveys - and earn cas=
h
<a class=3D"moz-txt-link-freetext" href=3D"http://www.techsay.com/default=
.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV">http://www.techsay.com=
/default.php?page=3Djoin.php&amp;p=3Dsourceforge&amp;CID=3DDEVDEV</a>
_______________________________________________
Aperture-devel mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Aperture-devel@lists=
.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.sourceforge.net/=
lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listin=
fo/aperture-devel</a>

  </pre>
</blockquote>
<br>
<br>
<pre class=3D"moz-signature" cols=3D"72">--=20
____________________________________________________
DI Leo Sauermann       <a class=3D"moz-txt-link-freetext" href=3D"http://=
www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a>=20
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class=3D"moz-txt-link-abbreviated" href=3D=
"mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------070002070003010206040209--


--===============0467782663==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--===============0467782663==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============0467782663==--


From - Tue Dec  5 09:28:51 2006
X-Account-Key: account3
X-UIDL: 0000ed560415f427
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:12247 "EHLO
	lists-outbound.sourceforge.net") by ps23.test.onet.pl with ESMTP
	id <S4848929AbWLEIZ2>; Tue, 5 Dec 2006 09:25:28 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 01468FAEB; Tue,  5 Dec 2006 00:25:26 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GrVcB-0001ZO-FY for aperture-devel@lists.sourceforge.net;
	Tue, 05 Dec 2006 00:25:23 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GrVcA-0001ro-Ij
	for aperture-devel@lists.sourceforge.net;
	Tue, 05 Dec 2006 00:25:24 -0800
Received: (qmail 31342 invoked from network); 5 Dec 2006 09:25:10 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	5 Dec 2006 09:25:09 +0100
Message-ID: <45752CE2.4000204@aduna-software.com>
Date:	Tue, 05 Dec 2006 09:25:06 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <456C7961.7020108@dfki.uni-kl.de>
	<456D5798.2020205@dfki.de>	<456DD541.7090405@dfki.uni-kl.de>
	<4573E0F4.7020704@dfki.de> <4574D287.3070308@sri.com>
In-Reply-To: <4574D287.3070308@sri.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] doc / bibtex / release
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Jack Park wrote:
> My own comment is that, while I don't want to start a flame war, I have 
> this intuition that the XML format in Open Office might be a better XML 
> to persist to than would be OpenDoc. That format just went ISO standard. 
> I am not saying OpenDoc is inadequate. I will say that it has been 
> really tough finding a decent editor for it; all of the OpenIRIS 
> documents were formatted in OpenDoc and the apache fop project, which we 
> used, is buggy, needed patching, and is also nolonger developed. I'd 
> much rather just use OpenOffice to do this kind of work. Perhaps an OO 
> template for biblio representations either exists or could be created.

I don't see your point exactly but perhaps I misunderstood.

First of all, does your comment relate to Leo's question about a bibtex 
crawler of to the choice for a documentation framework? I assume it's 
the latter but as you refer to "biblio representations" at the end, I 
got confused.

With "the XML format in Open Office" you mean the older XML-based 
formats used by OpenOffice 1.x? As OpenDocument is the primary document 
format of OpenOffice 2.x, why not use that? Besides OpenOffice there are 
other editors available for it as well and since it has been 
standardized, I would expect that in the end more tools will support 
OpenDocument than the older format.


Chris
--

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Tue Dec  5 13:49:34 2006
X-Account-Key: account3
X-UIDL: 0000ed5604164c66
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:29323 "EHLO
	lists-outbound.sourceforge.net") by ps19.test.onet.pl with ESMTP
	id <S781714AbWLEB7r>; Tue, 5 Dec 2006 02:59:47 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 9C83D12013; Mon,  4 Dec 2006 17:59:45 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GrPaw-0005V5-SF for aperture-devel@lists.sourceforge.net;
	Mon, 04 Dec 2006 17:59:42 -0800
Received: from alnrmhc12.comcast.net ([204.127.225.92])
	by mail.sourceforge.net with esmtp (Exim 4.44) id 1GrPaw-00081n-2C
	for aperture-devel@lists.sourceforge.net;
	Mon, 04 Dec 2006 17:59:44 -0800
Received: from [192.168.1.100]
	(c-69-181-79-170.hsd1.ca.comcast.net[69.181.79.170])
	by comcast.net (alnrmhc12) with ESMTP
	id <20061205015934b1200t1rnge>; Tue, 5 Dec 2006 01:59:34 +0000
Message-ID: <4574D287.3070308@sri.com>
Date:	Mon, 04 Dec 2006 17:59:35 -0800
From:	Jack Park <jack.park@sri.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.0.4) Gecko/20060516 SeaMonkey/1.0.2
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <456C7961.7020108@dfki.uni-kl.de> <456D5798.2020205@dfki.de>
	<456DD541.7090405@dfki.uni-kl.de> <4573E0F4.7020704@dfki.de>
In-Reply-To: <4573E0F4.7020704@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] doc / bibtex / release
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

SmFjayAoYydlc3QgbW9pKSB3aWxsIGJlIG91dCBvZiB0aGUgY291bnRyeSBvdmVyIG11Y2ggb2Yg
RGVjZW1iZXIgYW5kIApzd2FtcGVkIHdoZW4gaGUgZ2V0cyBiYWNrLiBOb3QgdG9vIG11Y2ggY2hh
bmNlIG9mIGNvbnRyaWJ1dGluZyBhIGJpYnRleCAKZGF0YXNvdXJjZSBhbnl0aW1lIHNvb24sIGJ1
dCB3b3VsZCBsb3ZlIHRvIGRvIHNvIGxhdGVyIGlmICBpdCdzIG5vdCAKc2F0aXNmaWVkIHlldC4K
Ck15IG93biBjb21tZW50IGlzIHRoYXQsIHdoaWxlIEkgZG9uJ3Qgd2FudCB0byBzdGFydCBhIGZs
YW1lIHdhciwgSSBoYXZlIAp0aGlzIGludHVpdGlvbiB0aGF0IHRoZSBYTUwgZm9ybWF0IGluIE9w
ZW4gT2ZmaWNlIG1pZ2h0IGJlIGEgYmV0dGVyIFhNTCAKdG8gcGVyc2lzdCB0byB0aGFuIHdvdWxk
IGJlIE9wZW5Eb2MuIFRoYXQgZm9ybWF0IGp1c3Qgd2VudCBJU08gc3RhbmRhcmQuIApJIGFtIG5v
dCBzYXlpbmcgT3BlbkRvYyBpcyBpbmFkZXF1YXRlLiBJIHdpbGwgc2F5IHRoYXQgaXQgaGFzIGJl
ZW4gCnJlYWxseSB0b3VnaCBmaW5kaW5nIGEgZGVjZW50IGVkaXRvciBmb3IgaXQ7IGFsbCBvZiB0
aGUgT3BlbklSSVMgCmRvY3VtZW50cyB3ZXJlIGZvcm1hdHRlZCBpbiBPcGVuRG9jIGFuZCB0aGUg
YXBhY2hlIGZvcCBwcm9qZWN0LCB3aGljaCB3ZSAKdXNlZCwgaXMgYnVnZ3ksIG5lZWRlZCBwYXRj
aGluZywgYW5kIGlzIGFsc28gbm9sb25nZXIgZGV2ZWxvcGVkLiBJJ2QgCm11Y2ggcmF0aGVyIGp1
c3QgdXNlIE9wZW5PZmZpY2UgdG8gZG8gdGhpcyBraW5kIG9mIHdvcmsuIFBlcmhhcHMgYW4gT08g
CnRlbXBsYXRlIGZvciBiaWJsaW8gcmVwcmVzZW50YXRpb25zIGVpdGhlciBleGlzdHMgb3IgY291
bGQgYmUgY3JlYXRlZC4KCkp1c3QgYSBoYWxmIEVVUk8uLi4KQ2hlZXJzCkphY2sKCkxlbyBTYXVl
cm1hbm4gd3JvdGU6Cj4gSGkgR3V5cywKPiAKPiBsb29raW5nIGF0IG91ciB3b3JrbG9hZCBhdCBE
RktJIChOZXBvbXVrJ3MgZmlyc3QgZGVsaXZlcmFibGVzIGFyZSBkdWUgCj4gMTIvMjAwNiksCj4g
SSB0aGluayBhIHJlbGVhc2Ugd291bGQgYmUgdG9vIG11Y2ggbm93Lgo+IGVuZCBvZiBqYW51YXJ5
Pwo+IAo+IEJ0dzogZG9lcyBhbnlvbmUgKEphY2s/KSBoYXZlIHRpbWUgdG8gbWFrZSBhIGJpYnRl
eCBkYXRhc291cmNlIGFuZCBjcmF3bGVyPwo+IAo+IGRvYzoKPiB0aGUgc2VzYW1lIGd1eXMgdXNl
IGRvY2Jvb2sgWE1MIHRvIGNyZWF0ZSB0aGVpciBkb2NzLCBtYXliZSB3ZSBzaG91bGQgCj4gdXNl
IHRoYXQuCj4gSSBkb24ndCBmYW5jeSB0aGVzZSBzeXN0ZW1zIHZlcnkgbXVjaCwgaHRtbCBhbmQg
YSBnb29kIENTUyBzaG91bGQgZG8gaXQsCj4gYnV0IHN1cmVseSBkb2Nib29rIGlzIGJldHRlciB0
aGFuIG5vdGhpbmcuCj4gd2UgY2FuIGdpdmUgaXQgYSB0cnkgLi4gd2hlbj8KPiAKPiBiZXN0Cj4g
TGVvCj4gCj4gRXMgYmVnYWIgc2ljaCBhYmVyIGRhIEFudG9uaSBNeWxrYSB6dXIgcmVjaHRlbiBa
ZWl0IDI5LjExLjIwMDYgMTk6NDUgCj4gZm9sZ2VuZGVzIHNjaHJpZWI6Cj4+IExlbyBTYXVlcm1h
bm4gbmFwaXNhxYIoYSk6Cj4+ICAgCj4+PiB2ZXJ5IGdvb2QhCj4+Pgo+Pj4gY291bGQgeW91IGNv
cHkgeW91ciB0ZXh0IGludG8gdGhlIC9kb2MvIGZvbGRlciwgaW4gc29tZSBodG1sIGFib3V0IAo+
Pj4gT1NHSWFwZXJ0dXJ0ZQo+Pj4gYW5kIGxpbmsgdG8gaXQgZnJvbSB0aGUgbWFpbiBkb2MgcGFn
ZT8KPj4+Cj4+PiB3ZSBjYW4gdGhlbiB1cGRhdGUgdGhlIGRvYyBvbiB0aGUgc2Ygd2Vic2l0ZS4K
Pj4+Cj4+PiBiZXN0Cj4+PiBMZW8KPj4+Cj4+PiAgICAgCj4+Cj4+IEkndmUgd3JpdHRlbiBhIHRl
eHQuIEl0IGlzIGluIHRoZSBkb2MvdHV0b3JpYWwvb3NnaS5odG1sLiBQdWJsaXNoaW5nIGl0IAo+
PiBvbiB0aGUgd2Vic2l0ZSB3b3VsZCBub3QgYmUgYSBnb29kIGlkZWEsIHNpbmNlIGl0IHJlZmVy
cyB0byB0aGUgQ1ZTIAo+PiBzbmFwc2hvdCwgbm90IHRoZSBjdXJyZW50IHJlbGVhc2UuCj4+Cj4+
IElmIHdlIHdlcmUgdG8gbWFrZSBhIG5ldyByZWxlYXNlIGJlZm9yZSBjaHJpc3RtYXMsIGVudGly
ZSBkb2N1bWVudGF0aW9uIAo+PiB3b3VsZCBuZWVkIHRvIGJlIHJld29ya2VkLCBzb21lIG5vdGUg
YWJvdXQgUkRGMkdvIHNob3VsZCBiZSBhZGRlZCwgCj4+IGV4YW1wbGVzIHNob3VsZCBiZSByZXdy
aXR0ZW4uIEl0IHdvdWxkIGFsc28gYmUgYSBnb29kIG9wb3J0dW5pdHkgdG8gCj4+IGNvbnZlcnQg
dGhlIGRvY3MgdG8gc29tZSBtb3JlIGdlbmVyaWMgZm9ybWF0IChMYXRleCwgRG9jYm9vaywgd2hh
dGV2ZXIpIAo+PiB0byBtYWtlIGl0IHBvc3NpYmxlIHRvIGdlbmVyYXRlIG5pY2UtbG9va2luZyBI
VE1MIGFuZCBQREYgdmVyc2lvbnMuCj4+Cj4+IEFudG9uaSBNeWxrYQo+PiBhbnRvbmkubXlsa2FA
ZGZraS5kZQo+Pgo+IAo+IC0tIAo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KPiBESSBMZW8gU2F1ZXJtYW5uICAgICAgIGh0dHA6Ly93d3cuZGZr
aS5kZS9+c2F1ZXJtYW5uIAo+IERGS0kgR21iSAo+IFAuTy4gQm94IDIwODAgICAgICAgICAgRm9u
OiAgICs0OSA2MzEgMjA1LTM1MDMKPiA2NzYwOCBLYWlzZXJzbGF1dGVybiAgIEZheDogICArNDkg
NjMxIDIwNS0zNDcyCj4gR2VybWFueSAgICAgICAgICAgICAgICBNYWlsOiAgbGVvLnNhdWVybWFu
bkBkZmtpLmRlCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwo+IAo+IAoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQpUYWtlIFN1cnZleXMuIEVhcm4gQ2FzaC4g
SW5mbHVlbmNlIHRoZSBGdXR1cmUgb2YgSVQKSm9pbiBTb3VyY2VGb3JnZS5uZXQncyBUZWNoc2F5
IHBhbmVsIGFuZCB5b3UnbGwgZ2V0IHRoZSBjaGFuY2UgdG8gc2hhcmUgeW91cgpvcGluaW9ucyBv
biBJVCAmIGJ1c2luZXNzIHRvcGljcyB0aHJvdWdoIGJyaWVmIHN1cnZleXMgLSBhbmQgZWFybiBj
YXNoCmh0dHA6Ly93d3cudGVjaHNheS5jb20vZGVmYXVsdC5waHA/cGFnZT1qb2luLnBocCZwPXNv
dXJjZWZvcmdlJkNJRD1ERVZERVYKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18KQXBlcnR1cmUtZGV2ZWwgbWFpbGluZyBsaXN0CkFwZXJ0dXJlLWRldmVsQGxp
c3RzLnNvdXJjZWZvcmdlLm5ldApodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9s
aXN0aW5mby9hcGVydHVyZS1kZXZlbAo=

From - Tue Dec  5 14:41:22 2006
X-Account-Key: account3
X-UIDL: 0000ed560416a8d0
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:51600 "EHLO
	lists-outbound.sourceforge.net") by ps25.test.onet.pl with ESMTP
	id <S4821903AbWLENdJ>; Tue, 5 Dec 2006 14:33:09 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id A2A1E121B7; Tue,  5 Dec 2006 05:33:08 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GraPw-0008LF-Hg for aperture-devel@lists.sourceforge.net;
	Tue, 05 Dec 2006 05:33:04 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GraPr-00014S-Ny
	for aperture-devel@lists.sourceforge.net;
	Tue, 05 Dec 2006 05:33:05 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kB5DWqsU005909; Tue, 5 Dec 2006 14:32:52 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kB5DWqY17614; Tue, 5 Dec 2006 14:32:52 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kB5DWnWl026632; Tue, 5 Dec 2006 14:32:49 +0100 (CET)
Message-ID: <457574FE.8000000@dfki.de>
Date:	Tue, 05 Dec 2006 14:32:46 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <456C7961.7020108@dfki.uni-kl.de>	<456D5798.2020205@dfki.de>	<456DD541.7090405@dfki.uni-kl.de>	<4573E0F4.7020704@dfki.de>
	<4574D287.3070308@sri.com> <45752CE2.4000204@aduna-software.com>
In-Reply-To: <45752CE2.4000204@aduna-software.com>
X-Spam-Score: 0.5 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.5 HTML_20_30             BODY: Message is 20% to 30% HTML
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] doc / bibtex / release
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0951112736=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============0951112736==
Content-Type: multipart/alternative;
	boundary="------------020708030301030303010801"

This is a multi-part message in MIME format.
--------------020708030301030303010801
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


the question was on DOC - documentation
and I suggested to do the same as the sesames with docbook XML

and Jack said that they had problems with opendoc (don't know what that 
is) and that open office is better.

true - I don't know of any editor for the docbook xml :-|

we search for something to write docs

Es begab sich aber da Christiaan Fluit zur rechten Zeit 05.12.2006 09:25 
folgendes schrieb:
> Jack Park wrote:
>   
>> My own comment is that, while I don't want to start a flame war, I have 
>> this intuition that the XML format in Open Office might be a better XML 
>> to persist to than would be OpenDoc. That format just went ISO standard. 
>> I am not saying OpenDoc is inadequate. I will say that it has been 
>> really tough finding a decent editor for it; all of the OpenIRIS 
>> documents were formatted in OpenDoc and the apache fop project, which we 
>> used, is buggy, needed patching, and is also nolonger developed. I'd 
>> much rather just use OpenOffice to do this kind of work. Perhaps an OO 
>> template for biblio representations either exists or could be created.
>>     
>
> I don't see your point exactly but perhaps I misunderstood.
>
> First of all, does your comment relate to Leo's question about a bibtex 
> crawler of to the choice for a documentation framework? I assume it's 
> the latter but as you refer to "biblio representations" at the end, I 
> got confused.
>
> With "the XML format in Open Office" you mean the older XML-based 
> formats used by OpenOffice 1.x? As OpenDocument is the primary document 
> format of OpenOffice 2.x, why not use that? Besides OpenOffice there are 
> other editors available for it as well and since it has been 
> standardized, I would expect that in the end more tools will support 
> OpenDocument than the older format.
>
>
> Chris
> --
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------020708030301030303010801
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
the question was on DOC - documentation<br>
and I suggested to do the same as the sesames with docbook XML<br>
<br>
and Jack said that they had problems with opendoc (don't know what that
is) and that open office is better.<br>
<br>
true - I don't know of any editor for the docbook xml :-|<br>
<br>
we search for something to write docs<br>
<br>
Es begab sich aber da Christiaan Fluit zur rechten Zeit 05.12.2006
09:25 folgendes schrieb:
<blockquote cite="mid45752CE2.4000204@aduna-software.com" type="cite">
  <pre wrap="">Jack Park wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">My own comment is that, while I don't want to start a flame war, I have 
this intuition that the XML format in Open Office might be a better XML 
to persist to than would be OpenDoc. That format just went ISO standard. 
I am not saying OpenDoc is inadequate. I will say that it has been 
really tough finding a decent editor for it; all of the OpenIRIS 
documents were formatted in OpenDoc and the apache fop project, which we 
used, is buggy, needed patching, and is also nolonger developed. I'd 
much rather just use OpenOffice to do this kind of work. Perhaps an OO 
template for biblio representations either exists or could be created.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I don't see your point exactly but perhaps I misunderstood.

First of all, does your comment relate to Leo's question about a bibtex 
crawler of to the choice for a documentation framework? I assume it's 
the latter but as you refer to "biblio representations" at the end, I 
got confused.

With "the XML format in Open Office" you mean the older XML-based 
formats used by OpenOffice 1.x? As OpenDocument is the primary document 
format of OpenOffice 2.x, why not use that? Besides OpenOffice there are 
other editors available for it as well and since it has been 
standardized, I would expect that in the end more tools will support 
OpenDocument than the older format.


Chris
--

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT &amp; business topics through brief surveys - and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&amp;p=sourceforge&amp;CID=DEVDEV</a>
_______________________________________________
Aperture-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aperture-devel@lists.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listinfo/aperture-devel</a>
  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
____________________________________________________
DI Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------020708030301030303010801--


--===============0951112736==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--===============0951112736==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============0951112736==--


From - Tue Dec  5 15:28:19 2006
X-Account-Key: account3
X-UIDL: 0000ed560416c02c
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:48317 "EHLO
	lists-outbound.sourceforge.net") by ps2.test.onet.pl with ESMTP
	id <S1412182AbWLEOQB>; Tue, 5 Dec 2006 15:16:01 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 8CEEBE571; Tue,  5 Dec 2006 06:15:59 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Grb5P-0004I5-UP for aperture-devel@lists.sourceforge.net;
	Tue, 05 Dec 2006 06:15:56 -0800
Received: from sccrmhc13.comcast.net ([63.240.77.83])
	by mail.sourceforge.net with esmtp (Exim 4.44) id 1Grb5P-000505-LK
	for aperture-devel@lists.sourceforge.net;
	Tue, 05 Dec 2006 06:15:57 -0800
Received: from [192.168.1.100]
	(c-69-181-79-170.hsd1.ca.comcast.net[69.181.79.170])
	by comcast.net (sccrmhc13) with ESMTP
	id <2006120514154701300ln46re>; Tue, 5 Dec 2006 14:15:47 +0000
Message-ID: <45757F15.9050107@sri.com>
Date:	Tue, 05 Dec 2006 06:15:49 -0800
From:	Jack Park <jack.park@sri.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.0.4) Gecko/20060516 SeaMonkey/1.0.2
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <456C7961.7020108@dfki.uni-kl.de> <456D5798.2020205@dfki.de>
	<456DD541.7090405@dfki.uni-kl.de> <4573E0F4.7020704@dfki.de>
	<4574D287.3070308@sri.com> <45752CE2.4000204@aduna-software.com>
	<457574FE.8000000@dfki.de>
In-Reply-To: <457574FE.8000000@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] doc / bibtex / release
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

The problems with opendoc have been that it is undersupported in Java. 
the apache FOP project seems dead, not developed in a long time (though 
it might have picked up in the last year; I haven't checked in a long 
time). OpenDoc, itself, is a well-supported and even popular product. I 
simply think it is time to move on to something that is much larger in 
scope yet still satisfies the same need as OpenDoc. At least you can use 
OpenOffice to edit it, eventually even MS Word (it says here).

Jack

Leo Sauermann wrote:
> 
> the question was on DOC - documentation
> and I suggested to do the same as the sesames with docbook XML
> 
> and Jack said that they had problems with opendoc (don't know what that 
> is) and that open office is better.
> 
> true - I don't know of any editor for the docbook xml :-|
> 
> we search for something to write docs
> 
> Es begab sich aber da Christiaan Fluit zur rechten Zeit 05.12.2006 09:25 
> folgendes schrieb:
>> Jack Park wrote:
>>   
>>> My own comment is that, while I don't want to start a flame war, I have 
>>> this intuition that the XML format in Open Office might be a better XML 
>>> to persist to than would be OpenDoc. That format just went ISO standard. 
>>> I am not saying OpenDoc is inadequate. I will say that it has been 
>>> really tough finding a decent editor for it; all of the OpenIRIS 
>>> documents were formatted in OpenDoc and the apache fop project, which we 
>>> used, is buggy, needed patching, and is also nolonger developed. I'd 
>>> much rather just use OpenOffice to do this kind of work. Perhaps an OO 
>>> template for biblio representations either exists or could be created.
>>>     
>>
>> I don't see your point exactly but perhaps I misunderstood.
>>
>> First of all, does your comment relate to Leo's question about a bibtex 
>> crawler of to the choice for a documentation framework? I assume it's 
>> the latter but as you refer to "biblio representations" at the end, I 
>> got confused.
>>
>> With "the XML format in Open Office" you mean the older XML-based 
>> formats used by OpenOffice 1.x? As OpenDocument is the primary document 
>> format of OpenOffice 2.x, why not use that? Besides OpenOffice there are 
>> other editors available for it as well and since it has been 
>> standardized, I would expect that in the end more tools will support 
>> OpenDocument than the older format.
>>
>>
>> Chris
>> --
>>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Dec 14 14:37:25 2006
X-Account-Key: account3
X-UIDL: 0000ed560418e52a
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:38635 "EHLO
	lists-outbound.sourceforge.net") by ps11.test.onet.pl with ESMTP
	id <S1001925AbWLFI5U>; Wed, 6 Dec 2006 09:57:20 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 84608FC3D; Wed,  6 Dec 2006 00:57:18 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GrsYU-0000fd-NF for aperture-devel@lists.sourceforge.net;
	Wed, 06 Dec 2006 00:55:06 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GrsYU-0001Bs-0Y
	for aperture-devel@lists.sourceforge.net;
	Wed, 06 Dec 2006 00:55:08 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-210.dfki.uni-kl.de
	[131.246.241.70])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	kB68svkF005201; Wed, 6 Dec 2006 09:54:57 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	kB68svY12331; Wed, 6 Dec 2006 09:54:57 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	kB68stph018867; Wed, 6 Dec 2006 09:54:56 +0100 (CET)
Message-ID: <45768559.8000601@dfki.de>
Date:	Wed, 06 Dec 2006 09:54:49 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Jack Park <jack.park@sri.com>
References: <456C7961.7020108@dfki.uni-kl.de>
	<456D5798.2020205@dfki.de>	<456DD541.7090405@dfki.uni-kl.de>
	<4573E0F4.7020704@dfki.de>	<4574D287.3070308@sri.com>
	<45752CE2.4000204@aduna-software.com>	<457574FE.8000000@dfki.de>
	<45757F15.9050107@sri.com>
In-Reply-To: <45757F15.9050107@sri.com>
X-Spam-Score: 0.5 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.5 HTML_20_30             BODY: Message is 20% to 30% HTML
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] doc / bibtex / release
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0639454948=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============0639454948==
Content-Type: multipart/alternative;
	boundary="------------060303000303010201020102"

This is a multi-part message in MIME format.
--------------060303000303010201020102
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi All,

to be more "uri-centered", here is the opendocument we are talking about:
http://en.wikipedia.org/wiki/OpenDocument

NOT to be mixed with the deprecated Xerox/Apple opendoc (Jack, watch 
your words!)
http://en.wikipedia.org/wiki/OpenDoc

Antoni,
next year when we have more oxygen here to breath,
could you look at OpenOffice 2.x and see if anybody else on the planet 
uses opendocument / .odt files to write Software documentation?
if yes, I see no problem also doing it.
The clear advantage is availability of a good editor (openoffice) and 
the possibility that other people may write converters for HTML output.

best
Leo

Es begab sich aber da Jack Park zur rechten Zeit 05.12.2006 15:15 
folgendes schrieb:
> The problems with opendoc have been that it is undersupported in Java. 
> the apache FOP project seems dead, not developed in a long time (though 
> it might have picked up in the last year; I haven't checked in a long 
> time). OpenDoc, itself, is a well-supported and even popular product. I 
> simply think it is time to move on to something that is much larger in 
> scope yet still satisfies the same need as OpenDoc. At least you can use 
> OpenOffice to edit it, eventually even MS Word (it says here).
>
> Jack
>
> Leo Sauermann wrote:
>   
>> the question was on DOC - documentation
>> and I suggested to do the same as the sesames with docbook XML
>>
>> and Jack said that they had problems with opendoc (don't know what that 
>> is) and that open office is better.
>>
>> true - I don't know of any editor for the docbook xml :-|
>>
>> we search for something to write docs
>>
>> Es begab sich aber da Christiaan Fluit zur rechten Zeit 05.12.2006 09:25 
>> folgendes schrieb:
>>     
>>> Jack Park wrote:
>>>   
>>>       
>>>> My own comment is that, while I don't want to start a flame war, I have 
>>>> this intuition that the XML format in Open Office might be a better XML 
>>>> to persist to than would be OpenDoc. That format just went ISO standard. 
>>>> I am not saying OpenDoc is inadequate. I will say that it has been 
>>>> really tough finding a decent editor for it; all of the OpenIRIS 
>>>> documents were formatted in OpenDoc and the apache fop project, which we 
>>>> used, is buggy, needed patching, and is also nolonger developed. I'd 
>>>> much rather just use OpenOffice to do this kind of work. Perhaps an OO 
>>>> template for biblio representations either exists or could be created.
>>>>     
>>>>         
>>> I don't see your point exactly but perhaps I misunderstood.
>>>
>>> First of all, does your comment relate to Leo's question about a bibtex 
>>> crawler of to the choice for a documentation framework? I assume it's 
>>> the latter but as you refer to "biblio representations" at the end, I 
>>> got confused.
>>>
>>> With "the XML format in Open Office" you mean the older XML-based 
>>> formats used by OpenOffice 1.x? As OpenDocument is the primary document 
>>> format of OpenOffice 2.x, why not use that? Besides OpenOffice there are 
>>> other editors available for it as well and since it has been 
>>> standardized, I would expect that in the end more tools will support 
>>> OpenDocument than the older format.
>>>
>>>
>>> Chris
>>> --
>>>
>>>       
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------060303000303010201020102
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi All,<br>
<br>
to be more "uri-centered", here is the opendocument we are talking
about:<br>
<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/OpenDocument">http://en.wikipedia.org/wiki/OpenDocument</a><br>
<br>
NOT to be mixed with the deprecated Xerox/Apple opendoc (Jack, watch
your words!)<br>
<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/OpenDoc">http://en.wikipedia.org/wiki/OpenDoc</a><br>
<br>
Antoni, <br>
next year when we have more oxygen here to breath, <br>
could you look at OpenOffice 2.x and see if anybody else on the planet
uses opendocument / .odt files to write Software documentation?<br>
if yes, I see no problem also doing it.<br>
The clear advantage is availability of a good editor (openoffice) and
the possibility that other people may write converters for HTML output.<br>
<br>
best<br>
Leo<br>
<br>
Es begab sich aber da Jack Park zur rechten Zeit 05.12.2006 15:15
folgendes schrieb:
<blockquote cite="mid45757F15.9050107@sri.com" type="cite">
  <pre wrap="">The problems with opendoc have been that it is undersupported in Java. 
the apache FOP project seems dead, not developed in a long time (though 
it might have picked up in the last year; I haven't checked in a long 
time). OpenDoc, itself, is a well-supported and even popular product. I 
simply think it is time to move on to something that is much larger in 
scope yet still satisfies the same need as OpenDoc. At least you can use 
OpenOffice to edit it, eventually even MS Word (it says here).

Jack

Leo Sauermann wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">the question was on DOC - documentation
and I suggested to do the same as the sesames with docbook XML

and Jack said that they had problems with opendoc (don't know what that 
is) and that open office is better.

true - I don't know of any editor for the docbook xml :-|

we search for something to write docs

Es begab sich aber da Christiaan Fluit zur rechten Zeit 05.12.2006 09:25 
folgendes schrieb:
    </pre>
    <blockquote type="cite">
      <pre wrap="">Jack Park wrote:
  
      </pre>
      <blockquote type="cite">
        <pre wrap="">My own comment is that, while I don't want to start a flame war, I have 
this intuition that the XML format in Open Office might be a better XML 
to persist to than would be OpenDoc. That format just went ISO standard. 
I am not saying OpenDoc is inadequate. I will say that it has been 
really tough finding a decent editor for it; all of the OpenIRIS 
documents were formatted in OpenDoc and the apache fop project, which we 
used, is buggy, needed patching, and is also nolonger developed. I'd 
much rather just use OpenOffice to do this kind of work. Perhaps an OO 
template for biblio representations either exists or could be created.
    
        </pre>
      </blockquote>
      <pre wrap="">I don't see your point exactly but perhaps I misunderstood.

First of all, does your comment relate to Leo's question about a bibtex 
crawler of to the choice for a documentation framework? I assume it's 
the latter but as you refer to "biblio representations" at the end, I 
got confused.

With "the XML format in Open Office" you mean the older XML-based 
formats used by OpenOffice 1.x? As OpenDocument is the primary document 
format of OpenOffice 2.x, why not use that? Besides OpenOffice there are 
other editors available for it as well and since it has been 
standardized, I would expect that in the end more tools will support 
OpenDocument than the older format.


Chris
--

      </pre>
    </blockquote>
  </blockquote>
  <pre wrap=""><!---->
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT &amp; business topics through brief surveys - and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&amp;p=sourceforge&amp;CID=DEVDEV</a>
_______________________________________________
Aperture-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aperture-devel@lists.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listinfo/aperture-devel</a>
  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
____________________________________________________
DI Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------060303000303010201020102--


--===============0639454948==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--===============0639454948==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============0639454948==--


From - Thu Dec 14 14:37:27 2006
X-Account-Key: account3
X-UIDL: 0000ed56041925b9
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:58060 "EHLO
	lists-outbound.sourceforge.net") by ps20.test.onet.pl with ESMTP
	id <S4822048AbWLFKTd>; Wed, 6 Dec 2006 11:19:33 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id E88DD120DF; Wed,  6 Dec 2006 02:19:31 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Grts8-0000O4-J7 for aperture-devel@lists.sourceforge.net;
	Wed, 06 Dec 2006 02:19:28 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Grts8-0001T4-Mg
	for aperture-devel@lists.sourceforge.net;
	Wed, 06 Dec 2006 02:19:30 -0800
Received: (qmail 5800 invoked from network); 6 Dec 2006 11:19:18 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	6 Dec 2006 11:19:18 +0100
Message-ID: <45769922.3090702@aduna-software.com>
Date:	Wed, 06 Dec 2006 11:19:14 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <456C7961.7020108@dfki.uni-kl.de>	<456D5798.2020205@dfki.de>	<456DD541.7090405@dfki.uni-kl.de>	<4573E0F4.7020704@dfki.de>	<4574D287.3070308@sri.com>	<45752CE2.4000204@aduna-software.com>	<457574FE.8000000@dfki.de>	<45757F15.9050107@sri.com>
	<45768559.8000601@dfki.de>
In-Reply-To: <45768559.8000601@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] doc / bibtex / release
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Leo Sauermann wrote:
> next year when we have more oxygen here to breath,
> could you look at OpenOffice 2.x and see if anybody else on the planet 
> uses opendocument / .odt files to write Software documentation?

We do :)

Whenever you see us use something else, it's probably because we haven't 
ported it to OpenDocument yet. When asking Arjohn about the use of 
Docbook for Sesame he noted that he would now also consider using 
OpenDocument if he had to do it all over again.

But truth be told, so far we have only used it to generate PDFs of our 
documentation. Docbook has facilities for exporting to several 
HTML-based formats (e.g. all in 1 file, split across multiple files with 
fancy tables of contents, etc.). I don't know whether there are any 
tools that can do the same for OpenDocument or whether OpenOffice can do 
that.

> if yes, I see no problem also doing it.
> The clear advantage is availability of a good editor (openoffice)

This I really like, so I would be in favor of OpenDocument.


Chris
--


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Thu Dec 14 14:37:35 2006
X-Account-Key: account3
X-UIDL: 0000ed56041a5034
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:27090 "EHLO
	lists-outbound.sourceforge.net") by ps22.test.onet.pl with ESMTP
	id <S4817184AbWLFS0A>; Wed, 6 Dec 2006 19:26:00 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 728CD129EA; Wed,  6 Dec 2006 08:23:14 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GrzTh-0003pJ-2V for aperture-devel@lists.sourceforge.net;
	Wed, 06 Dec 2006 08:18:37 -0800
Received: from balboa.ai.sri.com ([130.107.64.135])
	by mail.sourceforge.net with esmtp (Exim 4.44) id 1GrzTh-0003IA-Fd
	for aperture-devel@lists.sourceforge.net;
	Wed, 06 Dec 2006 08:18:38 -0800
Received: from Balboa.AI.SRI.COM (localhost [127.0.0.1])
	by Balboa.AI.SRI.COM (8.11.7p2+Sun/8.10.1) with SMTP id kB6GIMw08618
	for <aperture-devel@lists.sourceforge.net>;
	Wed, 6 Dec 2006 08:18:22 -0800 (PST)
Received: from Salt.AI.SRI.COM ([130.107.65.211])
	by Balboa.AI.SRI.COM (SMSSMTP 4.1.9.35) with SMTP id
	M2006120608182215519 for <aperture-devel@lists.sourceforge.net>;
	Wed, 06 Dec 2006 08:18:22 -0800
Received: from localhost.ai.sri.com
	([127.0.0.1] helo=[130.107.65.21] ident=root)
	by Salt.AI.SRI.COM with asmtp (Exim 3.35 #1 (Debian))
	id 1GrzTS-0004sQ-00 for <aperture-devel@lists.sourceforge.net>;
	Wed, 06 Dec 2006 08:18:22 -0800
Message-ID: <4576ED49.7050109@sri.com>
Date:	Wed, 06 Dec 2006 08:18:17 -0800
From:	Jack Park <jack.park@sri.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <456C7961.7020108@dfki.uni-kl.de> <456D5798.2020205@dfki.de>
	<456DD541.7090405@dfki.uni-kl.de> <4573E0F4.7020704@dfki.de>
	<4574D287.3070308@sri.com> <45752CE2.4000204@aduna-software.com>
	<457574FE.8000000@dfki.de> <45757F15.9050107@sri.com>
	<45768559.8000601@dfki.de>
In-Reply-To: <45768559.8000601@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] doc / bibtex / release
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

My bad. When I said "opendoc" (perhaps a wisp of wishful thinking that 
Apple's opendoc still lives), I meant DocBook.

You can turn the lights back on now...
Jack

Leo Sauermann wrote:
> Hi All,
> 
> to be more "uri-centered", here is the opendocument we are talking about:
> http://en.wikipedia.org/wiki/OpenDocument
> 
> NOT to be mixed with the deprecated Xerox/Apple opendoc (Jack, watch 
> your words!)
> http://en.wikipedia.org/wiki/OpenDoc
> 
> Antoni,
> next year when we have more oxygen here to breath,
> could you look at OpenOffice 2.x and see if anybody else on the planet 
> uses opendocument / .odt files to write Software documentation?
> if yes, I see no problem also doing it.
> The clear advantage is availability of a good editor (openoffice) and 
> the possibility that other people may write converters for HTML output.
> 
> best
> Leo
> 
> Es begab sich aber da Jack Park zur rechten Zeit 05.12.2006 15:15 
> folgendes schrieb:
>> The problems with opendoc have been that it is undersupported in Java. 
>> the apache FOP project seems dead, not developed in a long time (though 
>> it might have picked up in the last year; I haven't checked in a long 
>> time). OpenDoc, itself, is a well-supported and even popular product. I 
>> simply think it is time to move on to something that is much larger in 
>> scope yet still satisfies the same need as OpenDoc. At least you can use 
>> OpenOffice to edit it, eventually even MS Word (it says here).
>>
>> Jack
>>
>> Leo Sauermann wrote:
>>   
>>> the question was on DOC - documentation
>>> and I suggested to do the same as the sesames with docbook XML
>>>
>>> and Jack said that they had problems with opendoc (don't know what that 
>>> is) and that open office is better.
>>>
>>> true - I don't know of any editor for the docbook xml :-|
>>>
>>> we search for something to write docs
>>>
>>> Es begab sich aber da Christiaan Fluit zur rechten Zeit 05.12.2006 09:25 
>>> folgendes schrieb:
>>>     
>>>> Jack Park wrote:
>>>>   
>>>>       
>>>>> My own comment is that, while I don't want to start a flame war, I have 
>>>>> this intuition that the XML format in Open Office might be a better XML 
>>>>> to persist to than would be OpenDoc. That format just went ISO standard. 
>>>>> I am not saying OpenDoc is inadequate. I will say that it has been 
>>>>> really tough finding a decent editor for it; all of the OpenIRIS 
>>>>> documents were formatted in OpenDoc and the apache fop project, which we 
>>>>> used, is buggy, needed patching, and is also nolonger developed. I'd 
>>>>> much rather just use OpenOffice to do this kind of work. Perhaps an OO 
>>>>> template for biblio representations either exists or could be created.
>>>>>     
>>>>>         
>>>> I don't see your point exactly but perhaps I misunderstood.
>>>>
>>>> First of all, does your comment relate to Leo's question about a bibtex 
>>>> crawler of to the choice for a documentation framework? I assume it's 
>>>> the latter but as you refer to "biblio representations" at the end, I 
>>>> got confused.
>>>>
>>>> With "the XML format in Open Office" you mean the older XML-based 
>>>> formats used by OpenOffice 1.x? As OpenDocument is the primary document 
>>>> format of OpenOffice 2.x, why not use that? Besides OpenOffice there are 
>>>> other editors available for it as well and since it has been 
>>>> standardized, I would expect that in the end more tools will support 
>>>> OpenDocument than the older format.
>>>>
>>>>
>>>> Chris
>>>> --
>>>>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Dec  4 09:57:38 2006
X-Account-Key: account6
X-UIDL: 453c769a000000c7
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Delivery-Date: Mon, 04 Dec 2006 09:49:23 +0100
Received: from dfki-2203.dfki.uni-kl.de (root@gate-3114 [192.168.31.254])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id kB48nMna018518
	for <mylka@serv-3100.kl.dfki.de>; Mon, 4 Dec 2006 09:49:22 +0100 (CET)
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id kB48nLY16308;
	Mon, 4 Dec 2006 09:49:21 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id kB48nJxl018509;
	Mon, 4 Dec 2006 09:49:20 +0100 (CET)
Message-ID: <4573E0F4.7020704@dfki.de>
Date: Mon, 04 Dec 2006 09:48:52 +0100
From: Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
CC: Aperture Developers <aperture-devel@lists.sourceforge.net>
Subject: Re: [Aperture-devel] doc / bibtex / release
References: <456C7961.7020108@dfki.uni-kl.de> <456D5798.2020205@dfki.de> <456DD541.7090405@dfki.uni-kl.de>
In-Reply-To: <456DD541.7090405@dfki.uni-kl.de>
Content-Type: multipart/alternative;
 boundary="------------070002070003010206040209"
Status:  O

This is a multi-part message in MIME format.
--------------070002070003010206040209
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Guys,

looking at our workload at DFKI (Nepomuk's first deliverables are due 
12/2006),
I think a release would be too much now.
end of january?

Btw: does anyone (Jack?) have time to make a bibtex datasource and crawler?

doc:
the sesame guys use docbook XML to create their docs, maybe we should 
use that.
I don't fancy these systems very much, html and a good CSS should do it,
but surely docbook is better than nothing.
we can give it a try .. when?

best
Leo

Es begab sich aber da Antoni Mylka zur rechten Zeit 29.11.2006 19:45 
folgendes schrieb:
> Leo Sauermann napisał(a):
>   
>> very good!
>>
>> could you copy your text into the /doc/ folder, in some html about 
>> OSGIaperturte
>> and link to it from the main doc page?
>>
>> we can then update the doc on the sf website.
>>
>> best
>> Leo
>>
>>     
>
> I've written a text. It is in the doc/tutorial/osgi.html. Publishing it 
> on the website would not be a good idea, since it refers to the CVS 
> snapshot, not the current release.
>
> If we were to make a new release before christmas, entire documentation 
> would need to be reworked, some note about RDF2Go should be added, 
> examples should be rewritten. It would also be a good oportunity to 
> convert the docs to some more generic format (Latex, Docbook, whatever) 
> to make it possible to generate nice-looking HTML and PDF versions.
>
> Antoni Mylka
> antoni.mylka@dfki.de
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------070002070003010206040209
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Guys,<br>
<br>
looking at our workload at DFKI (Nepomuk's first deliverables are due
12/2006),<br>
I think a release would be too much now.<br>
end of january?<br>
<br>
Btw: does anyone (Jack?) have time to make a bibtex datasource and
crawler?<br>
<br>
doc:<br>
the sesame guys use docbook XML to create their docs, maybe we should
use that.<br>
I don't fancy these systems very much, html and a good CSS should do it,<br>
but surely docbook is better than nothing.<br>
we can give it a try .. when?<br>
<br>
best<br>
Leo<br>
<br>
Es begab sich aber da Antoni Mylka zur rechten Zeit 29.11.2006 19:45
folgendes schrieb:
<blockquote cite="mid456DD541.7090405@dfki.uni-kl.de" type="cite">
  <pre wrap="">Leo Sauermann napisał(a):
  </pre>
  <blockquote type="cite">
    <pre wrap="">very good!

could you copy your text into the /doc/ folder, in some html about 
OSGIaperturte
and link to it from the main doc page?

we can then update the doc on the sf website.

best
Leo

    </pre>
  </blockquote>
  <pre wrap=""><!---->
I've written a text. It is in the doc/tutorial/osgi.html. Publishing it 
on the website would not be a good idea, since it refers to the CVS 
snapshot, not the current release.

If we were to make a new release before christmas, entire documentation 
would need to be reworked, some note about RDF2Go should be added, 
examples should be rewritten. It would also be a good oportunity to 
convert the docs to some more generic format (Latex, Docbook, whatever) 
to make it possible to generate nice-looking HTML and PDF versions.

Antoni Mylka
<a class="moz-txt-link-abbreviated" href="mailto:antoni.mylka@dfki.de">antoni.mylka@dfki.de</a>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT &amp; business topics through brief surveys - and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&amp;p=sourceforge&amp;CID=DEVDEV</a>
_______________________________________________
Aperture-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aperture-devel@lists.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listinfo/aperture-devel</a>

  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
____________________________________________________
DI Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------070002070003010206040209--

From - Wed Jan  3 15:37:25 2007
X-Account-Key: account3
X-UIDL: 0000ed56043ada36
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:177 "EHLO
	lists-outbound.sourceforge.net") by ps3.test.onet.pl with ESMTP
	id <S4001052AbWKHO5K>; Wed, 8 Nov 2006 15:57:10 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id DF93212CDF; Wed,  8 Nov 2006 06:57:08 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Ghoql-0007Xz-JB for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 06:56:23 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Ghoqg-0004Uz-UQ
	for aperture-devel@lists.sourceforge.net;
	Wed, 08 Nov 2006 06:56:24 -0800
Received: (qmail 21854 invoked from network); 8 Nov 2006 15:56:04 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	8 Nov 2006 15:56:04 +0100
Message-ID: <4551F000.5020009@aduna-software.com>
Date:	Wed, 08 Nov 2006 15:56:00 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F2723.8040809@dfki.uni-kl.de>
In-Reply-To: <454F2723.8040809@dfki.uni-kl.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Progress Report - BibTex crawler - OSGI
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Antoni Mylka wrote:
> 1. Take care of proper closing of all rdf models. The underlying sesame2 
> implementation uses a sesameConnection. It has to be properly closed. 
> Max Volkel included the open() and close() methods in the model 
> interface. Benjamin Hartman implemented them in ModelImplSesame. I must 
> take a look at this and see what problems would it pose in the current 
> aperture architecture.

Sounds all ok.

Some thoughts I'd like to share: please keep in mind that some 
applications may use a dedicated RDF data structure (a Sesame Repository 
or whatever) per RDFContainer, whereas others may use a single data 
structure that is shared among a number of RDFContainers.

For example, is for some reason you want your extracted metadata to be 
stored *directly* in a single native store, you want to use 
RDFContainers that all reference the same shared repository.

Please take care that in the revised API such designs remain possible. 
Not that I suspect that your changes will immediately make this 
impossible (the integrator creating the CrawlerHandler can always use 
his own RDFContainer/Rdf2go driver/whatever implementations, we're 
already doing so in AutoFocus), but it may be a good thought experiment 
to see if it is still possible. What you don't want is a close() on a 
data structure that accidentally makes further operation of its siblings 
impossible. I believe the described flexibility is one of the key 
advantages of Aperture.

> BibTeX Crawler
> 
> I did some investigation into available solutions. Apart from the 
> converter made by Wolf Siberski there is one by Peter Haase and Bjorn 
> Schnitzler from AIFB. It uses the same java-bib BibTeX parser. It's 
> advantage is that it is GPL. It's disadvantage is that it is really 

Is GPL really an advantage? As far as I understand this license, we can 
only use GPL software in Aperture when Aperture itself is also 
distributed under the GPL. This on its turn would pose the same 
restriction on all apps using Aperture. Without trying to start a 
discussion on the legal interpretation of the GPL, this is the 
perception of a lot of people on how the GPL works and would therefore 
make Aperture less attractive for them. At Aduna we have quite some 
experience with licensing by now and even the more liberal LGPL gave us 
more headaches than expected. So unless you can convince me otherwise, I 
believe we should refrain from using such GPL-licensed libraries in 
Aperture.

Too bad this is an issue though...

> crappy. Works with string concatenation, generates ugly XML, creates 
> URIs for all resources by concatenating some magic hard-coded prefix:
> 
> swap://urn.jxta.uuid-59616261646162614A7874615032503319973678153643E581589E1EC4A2ED4E03.jxta
> 
> with a hash and some integer. I guess that trying to convert it to use 
> RDF2Go would be more unnerving than it's worth. The other option is to 
> use the java-bib to create our own crawler from scratch - and use the 
> experience from the ical crawler, they would be similar in many respects.

Sounds like a good approach but java-bib is also GPL-licensed software.

What's wrong with Wolf Siberski's library? Except for that its jar file 
*embeds* all its third party dependencies (please do not include this 
jar file in this state in Aperture), I see that it's licensed under the 
Apache license and the third party licenses did not freak me out either. 
  You say it depends on the (GPL-ed) java-bib but I couldn't see any 
references to it. If you can even specify the mapping from Bibtex 
elements to properties, what else is missing? Oh wait, it depends on 
Jena... That explains the large download ;)

I've also looked around and found this Perl script: 
http://www.cs.vu.nl/%7Emcaklein/bib2rdf/bib2rdf. It's available as an 
online service: http://www.cs.vu.nl/%7Emcaklein/bib2rdf/ so you can 
determine its quality. Unfortunately the script is also distributed 
under GPL. It's part of the OpenAcademia project, of which I know 
several people. I have no Perl experience but I suspect it is possible 
to port this script to Java fairly easy. I can ask the authors for 
permission to do so and distribute the results under a different 
license. Perhaps this is an option for you?

> I must admit that I'm completely new to OSGI. So if I am to implement 
> the code, that would enable aperture to be used as a set of OSGI bundles 
> - it would be easier for me to know the decision concerning the level of 
> granularity...
> What would it mean 'both' - two editions? aperture-fine-grained.zip and 
> aperture-coarse-grained.zip ?????

I interpret this as: two build targets, creating different sets of 
bundles. Probably also two trees in src/, next to java/, examples/ and 
test/, each containing a different set of BundleActivators (I assume 
it's a good idea to let the BundleActivators live in a separate source 
tree, similar to src/test?)

>  > This is fine for some purposes, but not for all. I would also like to
>  > see the possibility for a more fine-grained approach.
> 
> Could you provide some more specific suggestions?

OSGi is fairly new for me as well but I'll give it a shot...

A use case for the approach where you either have a single Aperture 
bundle or only a small number of bundles (e.g. an API bundle and a 
bundle containing all API implementations) is those applications that 
just want to use Aperture "as is" in an OSGi environment, e.g. because 
they use the Eclipse Rich Client Platform. That is, I assume the Eclipse 
RCP requires the use of OSGi bundles. In short: it's for people that 
already use an OSGi platform and just want to incorporate Aperture.

A use case for the approach with a bundle per single implementation 
(e.g. a FileSystemCrawler bundle, a PdfExtractor bundle, etc.) is an 
application where you need to create tailor-made versions of an 
application with diverse requirements on which implementations are 
available in an application, perhaps even to the extent that this may 
vary between end users.

This granularity may for example allow the following scenario:

- user gets a signal from the app that an updated set of Extractors is 
available

- user sees the list of new and/or updated Extractors

- user selects which new ones he wants to download ("yes! MP3 support! 
finally!"), which ones he wants to upgrade ("PDF support is really 
sloppy, I'll try the new one"), perhaps even which ones he may wish to 
downgrade once *we* get sloppy ;)

- user clicks OK, app downloads these bundles, add them to/replaces them 
in the list of used bundles and >>boom<< the application is upgraded at 
runtime.

The likeliness of this scenario depends on your application: how much 
control do you want to give to your end users or administrators, can you 
expect them to understand the consequences of picking or skipping 
certain bundles, how much bundles will there be to choose from (being 
able to manage hundreds of bundles may freak them out), do you want your 
application to be able to alter current functionality or is 
functionality extension enough (you can always add fine-grained bundles 
to an existing set of coarse-grained bundles), etc.

Herko: could it be that the decision of which granularity we choose only 
determines the set of jar files and Manifests (i.e., build script magic) 
but does not influence which BundleActivators we need to create?

>  > This is why it is very important to provide a stable API defined in
>  > terms of interfaces, which I think we have now.

We're getting close indeed! One thing I would still like to change 
before a final Aperture release is a way to pass Files to Extractors, so 
that we can properly use all those ID3 tag extraction libraries out 
there. I've given this some thought lately, I'll put it on the Aperture 
wiki or post it here soon.

> I'll dig into OSGi. I hope I will my questions weren't completely 
> nonsense. :-)

Absolutely not! :)


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Jan  3 15:37:36 2007
X-Account-Key: account3
X-UIDL: 0000ed56043b0231
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:54687 "EHLO
	lists-outbound.sourceforge.net") by ps3.test.onet.pl with ESMTP
	id <S4145173AbWKIRkh>; Thu, 9 Nov 2006 18:40:37 +0100
Received: from sc8-sf-list2-new.sourceforge.net (unknown [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 6F07D13B42; Thu,  9 Nov 2006 09:40:36 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GiDnY-0001Pf-P9 for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 09:34:44 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GiDnX-0004uy-Gw
	for aperture-devel@lists.sourceforge.net;
	Thu, 09 Nov 2006 09:34:46 -0800
Received: (qmail 24760 invoked from network); 9 Nov 2006 18:34:31 +0100
Received: from 5353a894.cable.casema.nl (HELO ?83.83.168.148?) (83.83.168.148)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	9 Nov 2006 18:34:31 +0100
Message-ID: <455366A6.20404@aduna-software.com>
Date:	Thu, 09 Nov 2006 18:34:30 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <454F3C76.5060307@dfki.uni-kl.de>	<4551FAF4.5080309@aduna-software.com>	<45533875.30002@dfki.uni-kl.de>
	<45535399.5070600@aduna-software.com>
In-Reply-To: <45535399.5070600@aduna-software.com>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: Re: [Aperture-devel] Closing vs. disposing
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Christiaan Fluit wrote:
>> Introduce the concept of a Model being owned by the container vs. 
>> model being shared between containers. We could add two additional 
>> methods isModelShared vs. setModelShared. Also, we could provide an
>> additional parameter in the constructors. The implementation could
>> use this parameter to determine if a model should be closed on
>> diposal or not
> ... I wouldn't add any methods related to shared or unshared
> underlying models in RDFContainer's API if that's what you propose. I
> believe this should be entirely transparent and encapsulated by the
> implementing class.

Wait, I see that this *is* actually what you propose. Sorry, I misread
your proposal, my mistake :)


Chris
--

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Jan  3 15:38:22 2007
X-Account-Key: account3
X-UIDL: 0000ed5604415ebe
X-Mozilla-Status: 0001
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:16010 "EHLO
	lists-outbound.sourceforge.net") by ps14.test.onet.pl with ESMTP
	id <S17147585AbWL1RUF>; Thu, 28 Dec 2006 18:20:05 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 3B2F512D29; Thu, 28 Dec 2006 07:06:55 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1GzwqG-0008Ju-SN for aperture-devel@lists.sourceforge.net;
	Thu, 28 Dec 2006 07:06:50 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GzwqI-0007MX-5X
	for aperture-devel@lists.sourceforge.net;
	Thu, 28 Dec 2006 07:06:50 -0800
Received: (qmail 29848 invoked from network); 28 Dec 2006 16:06:43 +0100
Received: from 5353ad89.cable.casema.nl (HELO ?83.83.173.137?) (83.83.173.137)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	28 Dec 2006 16:06:43 +0100
Message-ID: <4593DD7C.7010204@aduna-software.com>
Date:	Thu, 28 Dec 2006 16:06:36 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
Content-Type: multipart/mixed; boundary="------------090801010307000606010807"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Subject: [Aperture-devel] [Fwd: MagicMimeTypeIdentifier]
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--------------090801010307000606010807
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

... just so you know ;)

Chris
--

--------------090801010307000606010807
Content-Type: message/rfc822;
 name="MagicMimeTypeIdentifier"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="MagicMimeTypeIdentifier"

Return-Path: <nobody@sourceforge.net>
Delivered-To: 5-christiaan.fluit@aduna.biz
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on 
	www4.aduna-software.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=7.0 tests=BAYES_00 autolearn=ham 
	version=3.1.0
Received: (qmail 27966 invoked from network); 28 Dec 2006 14:44:05 +0100
Received: from lists.sourceforge.net (HELO mail.sourceforge.net)
	(66.35.250.206)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	28 Dec 2006 14:44:05 +0100
Received: from sc8-sf-web1-b.sourceforge.net ([10.3.1.71]
	helo=sc8-sf-web1.sourceforge.net)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1GzvYC-0004SF-3n
	for cfmfluit@users.sourceforge.net; Thu, 28 Dec 2006 05:44:04 -0800
Received: from nobody by sc8-sf-web1.sourceforge.net with local (Exim 4.43)
	id 1GzvYB-0007vV-Bo
	for cfmfluit@users.sourceforge.net; Thu, 28 Dec 2006 05:44:03 -0800
To: cfmfluit@users.sourceforge.net
From: "Fred Eaker" <feaker@users.sourceforge.net>
Subject: MagicMimeTypeIdentifier
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Message-Id: <E1GzvYB-0007vV-Bo@sc8-sf-web1.sourceforge.net>
Sender: Nobody <nobody@sc8-sf-web1.sourceforge.net>
Date: Thu, 28 Dec 2006 05:44:03 -0800


Message body follows:

I recently completed some testing that revealed your
MagicMimeTypeIdentifier code to be a superior means in
identifying a file's type. You can read the article here:
http://fredeaker.blogspot.com/2006/12/file-type-mime-detection.html

Thanks for your great work!

Fred Eaker

--
This message has been sent to you, a registered SourceForge.net user,
by another site user, through the SourceForge.net site.  This message
has been delivered to your SourceForge.net mail alias.  You may reply
to this message using the "Reply" feature of your email client, or
using the messaging facility of SourceForge.net at:
https://sourceforge.net/sendmessage.php?touser=1396191


--------------090801010307000606010807
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--------------090801010307000606010807
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--------------090801010307000606010807--


From - Wed Jan  3 15:38:31 2007
X-Account-Key: account3
X-UIDL: 0000ed5604431bf0
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:18875 "EHLO
	lists-outbound.sourceforge.net") by ps15.test.onet.pl with ESMTP
	id <S9587427AbXAAEA0>; Mon, 1 Jan 2007 05:00:26 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 3F196F96F; Sun, 31 Dec 2006 20:00:21 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1H1ELR-0001sS-Tu for aperture-devel@lists.sourceforge.net;
	Sun, 31 Dec 2006 20:00:18 -0800
Received: from smtp1.rz.uni-karlsruhe.de ([129.13.185.217] ident=Debian-exim)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1H1ELQ-0005xb-9n
	for aperture-devel@lists.sourceforge.net;
	Sun, 31 Dec 2006 20:00:19 -0800
Received: from ontoware.org (aifbontoware.aifb.uni-karlsruhe.de
	[172.22.131.111])
	by smtp1.rz.uni-karlsruhe.de with esmtp (Exim 4.63 #1)
	id 1H1ELF-0000nq-KH; Mon, 01 Jan 2007 05:00:05 +0100
Received: from [127.0.0.1] (helo=aifbontoware.aifb.uni-karlsruhe.de)
	by ontoware.org with esmtp (Exim 4.63)
	(envelope-from <mailman-bounces@ontoware.org>) id 1H1ELE-0001iC-IX
	for aperture-devel@lists.sourceforge.net;
	Mon, 01 Jan 2007 05:00:04 +0100
MIME-Version: 1.0
From:	mailman-owner@ontoware.org
To:	aperture-devel@lists.sourceforge.net
X-No-Archive: yes
Message-ID: <mailman.32.1167624002.6437.mailman@ontoware.org>
Date:	Mon, 01 Jan 2007 05:00:02 +0100
Precedence: bulk
X-BeenThere: mailman@ontoware.org
X-Mailman-Version: 2.1.7
X-List-Administrivia: yes
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.2 NO_REAL_NAME           From: does not include a real name
	1.0 FORGED_RCVD_HELO       Received: contains a forged HELO
Subject: [Aperture-devel] ontoware.org mailing list memberships reminder
X-BeenThere: aperture-devel@lists.sourceforge.net
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a reminder, sent out once a month, about your ontoware.org
mailing list memberships.  It includes your subscription info and how
to use it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ontoware.org) containing just
the word 'help' in the message body, and an email message will be sent
to you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ontoware.org.  Thanks!

Passwords for aperture-devel@lists.sourceforge.net:

List                                     Password // URL
----                                     --------  
rdf2go-devel@ontoware.org                esdukaan  
http://ontoware.org/mailman/options/rdf2go-devel/aperture-devel%40lists.sourceforge.net

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Wed Jan  3 15:38:34 2007
X-Account-Key: account3
X-UIDL: 0000ed560443cd9b
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:16108 "EHLO
	lists-outbound.sourceforge.net") by ps10.test.onet.pl with ESMTP
	id <S100728457AbXABKcy>; Tue, 2 Jan 2007 11:32:54 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 57ED2FE0F; Tue,  2 Jan 2007 01:30:45 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1H1fyi-0002TT-O5 for aperture-devel@lists.sourceforge.net;
	Tue, 02 Jan 2007 01:30:40 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1H1fyh-0006IS-F6
	for aperture-devel@lists.sourceforge.net;
	Tue, 02 Jan 2007 01:30:42 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-209.dfki.uni-kl.de
	[131.246.241.69])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	l029UR5O010531; Tue, 2 Jan 2007 10:30:27 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	l029UR114226; Tue, 2 Jan 2007 10:30:27 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	l029UPWV012584; Tue, 2 Jan 2007 10:30:25 +0100 (CET)
Message-ID: <459A2627.2050407@dfki.de>
Date:	Tue, 02 Jan 2007 10:30:15 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>,
	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <4593DD7C.7010204@aduna-software.com>
In-Reply-To: <4593DD7C.7010204@aduna-software.com>
X-Spam-Score: 0.3 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.2 HTML_TAG_EXIST_TBODY   BODY: HTML has "tbody" tag
	0.1 HTML_50_60             BODY: Message is 50% to 60% HTML
Subject: Re: [Aperture-devel] [Fwd: MagicMimeTypeIdentifier]
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1109221975=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============1109221975==
Content-Type: multipart/alternative;
	boundary="------------030203080407080207000306"

This is a multi-part message in MIME format.
--------------030203080407080207000306
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hey, this rocks

good code, Chris!

Es begab sich aber da Christiaan Fluit zur rechten Zeit 28.12.2006 16:06 
folgendes schrieb:
> ... just so you know ;)
>
> Chris
> -- 
>
> ------------------------------------------------------------------------
>
> Betreff:
> MagicMimeTypeIdentifier
> Von:
> "Fred Eaker" <feaker@users.sourceforge.net>
> Datum:
> Thu, 28 Dec 2006 05:44:03 -0800
> An:
> cfmfluit@users.sourceforge.net
>
> An:
> cfmfluit@users.sourceforge.net
>
>
> Message body follows:
>
> I recently completed some testing that revealed your
> MagicMimeTypeIdentifier code to be a superior means in
> identifying a file's type. You can read the article here:
> http://fredeaker.blogspot.com/2006/12/file-type-mime-detection.html
>
> Thanks for your great work!
>
> Fred Eaker
>
> --
> This message has been sent to you, a registered SourceForge.net user,
> by another site user, through the SourceForge.net site.  This message
> has been delivered to your SourceForge.net mail alias.  You may reply
> to this message using the "Reply" feature of your email client, or
> using the messaging facility of SourceForge.net at:
> https://sourceforge.net/sendmessage.php?touser=1396191
>
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>   


-- 
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------030203080407080207000306
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hey, this rocks<br>
<br>
good code, Chris!<br>
<br>
Es begab sich aber da Christiaan Fluit zur rechten Zeit 28.12.2006
16:06 folgendes schrieb:
<blockquote cite="mid4593DD7C.7010204@aduna-software.com" type="cite">...
just so you know ;)
  <br>
  <br>
Chris
  <br>
--
  <br>
  <br>
  <hr size="4" width="90%"><br>
  <table class="header-part1" border="0" cellpadding="0" cellspacing="0"
 width="100%">
    <tbody>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Betreff:
        </div>
MagicMimeTypeIdentifier</td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Von: </div>
"Fred Eaker" <a class="moz-txt-link-rfc2396E" href="mailto:feaker@users.sourceforge.net">&lt;feaker@users.sourceforge.net&gt;</a></td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Datum: </div>
Thu, 28 Dec 2006 05:44:03 -0800</td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">An: </div>
<a class="moz-txt-link-abbreviated" href="mailto:cfmfluit@users.sourceforge.net">cfmfluit@users.sourceforge.net</a></td>
      </tr>
    </tbody>
  </table>
  <table class="header-part2" border="0" cellpadding="0" cellspacing="0"
 width="100%">
    <tbody>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">An: </div>
<a class="moz-txt-link-abbreviated" href="mailto:cfmfluit@users.sourceforge.net">cfmfluit@users.sourceforge.net</a></td>
      </tr>
    </tbody>
  </table>
  <br>
  <pre wrap="">Message body follows:

I recently completed some testing that revealed your
MagicMimeTypeIdentifier code to be a superior means in
identifying a file's type. You can read the article here:
<a class="moz-txt-link-freetext" href="http://fredeaker.blogspot.com/2006/12/file-type-mime-detection.html">http://fredeaker.blogspot.com/2006/12/file-type-mime-detection.html</a>

Thanks for your great work!

Fred Eaker

--
This message has been sent to you, a registered SourceForge.net user,
by another site user, through the SourceForge.net site.  This message
has been delivered to your SourceForge.net mail alias.  You may reply
to this message using the "Reply" feature of your email client, or
using the messaging facility of SourceForge.net at:
<a class="moz-txt-link-freetext" href="https://sourceforge.net/sendmessage.php?touser=1396191">https://sourceforge.net/sendmessage.php?touser=1396191</a>

  </pre>
  <pre wrap="">
<hr size="4" width="90%">
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT &amp; business topics through brief surveys - and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&amp;p=sourceforge&amp;CID=DEVDEV</a></pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Aperture-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aperture-devel@lists.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listinfo/aperture-devel</a>
  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
____________________________________________________
DI Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------030203080407080207000306--


--===============1109221975==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--===============1109221975==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============1109221975==--


From - Fri Jan  5 15:21:13 2007
X-Account-Key: account3
X-UIDL: 0000ed560446967e
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:10212 "EHLO
	lists-outbound.sourceforge.net") by ps3.test.onet.pl with ESMTP
	id <S3409837AbXAEN3v>; Fri, 5 Jan 2007 14:29:51 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 9E74BFBA9; Fri,  5 Jan 2007 04:56:52 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1H2oaZ-0005Sw-HU for aperture-devel@lists.sourceforge.net;
	Fri, 05 Jan 2007 04:54:27 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1H2oaX-0008Rs-E2
	for aperture-devel@lists.sourceforge.net;
	Fri, 05 Jan 2007 04:54:29 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-209.dfki.uni-kl.de
	[131.246.241.69])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	l05CsJ1c010006; Fri, 5 Jan 2007 13:54:20 +0100
Received: from serv-4100.kl.dfki.de (serv-4100.kl.dfki.de [192.168.41.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	l05CsJ101387; Fri, 5 Jan 2007 13:54:19 +0100 (MET)
Received: from [192.168.31.133] (pc-3113 [192.168.31.133])
	by serv-4100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	l05CsIVb012673; Fri, 5 Jan 2007 13:54:18 +0100 (CET)
Message-ID: <459E4B5A.3000108@dfki.de>
Date:	Fri, 05 Jan 2007 13:58:02 +0100
From:	Gunnar Aastrand Grimnes <gunnar.grimnes@dfki.de>
User-Agent: Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
X-Enigmail-Version: 0.94.0.0
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	reuschling@dfki.uni-kl.de, Heinz.Kirchmann@dfki.de
Subject: [Aperture-devel] crawling files containing dataobjects
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

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

Hello everyone,

We recently came across a problem with crawling some special XML files. These
files contain several "things" that we would like to have mapped to several
data-objects.

This is analogous to the problem of archive files, this problem I have
previously discussed with Chris. I.e. when the fileSystemCrawler finds a
zip-file we might want to crawl the content of the file, not just the file
itself. Currently the architecture makes kinda tricky. The FileSystemCrawler
will find one file, and only in the crawlerHandler.reportNew do we find the
mime-type of the file, and only then do we invoke the appropriate extractor to
get the contents.

The main problem with the current setup is that  The extractor method "extract"
gets a single RDFContainer, and a single ID, there is no way for it to report
other data-objects.

One solution is of course to hard-code zip/tar/rar/whatever support into the
FileSystemCrawler, but that's kinda crappy, cause you would like to be able to
crawl zip files as email attachments as well.

This problem also arises for things like thunderbird addressbooks (a single file
on disk), or iCal files, etc. but it's not as natural to crawl these as a part
of a file-system crawl - and these are solved by having dedicated crawlers for
these.

Leo just pointed me to this link, where this was discussed previously:
http://gnowsis.opendfki.de/wiki/ApertureArchives

Has anyone got any good ideas about this? :)
- --
Gunnar Aastrand Grimnes
gunnar.grimnes [AT] dfki.de

DFKI GmbH
Knowledge Management
Erwin-Schroedinger-Strasse
D-67663 Kaiserslautern
Germany

Office: +49 631 205 3438
Mobile: +49 177 277 4397


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFnktafD15aMgAOfcRAoVYAJ94EvqWGrOt15kUr8oXjyhmhhHKzwCfbVTs
cbnM9Ilc2fY893+9/dAndcY=
=9lk+
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Jan  8 10:07:50 2007
X-Account-Key: account3
X-UIDL: 0000ed560446e3b9
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:16293 "EHLO
	lists-outbound.sourceforge.net") by ps28.test.onet.pl with ESMTP
	id <S2421895AbXAETl0>; Fri, 5 Jan 2007 20:41:26 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 3691C12C57; Fri,  5 Jan 2007 05:33:29 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1H2pAF-0000ds-KG for aperture-devel@lists.sourceforge.net;
	Fri, 05 Jan 2007 05:31:20 -0800
Received: from www4.aduna-software.com ([66.98.176.99])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1H2pAC-0002Bn-02
	for aperture-devel@lists.sourceforge.net;
	Fri, 05 Jan 2007 05:31:18 -0800
Received: (qmail 27166 invoked from network); 5 Jan 2007 14:31:07 +0100
Received: from home.aduna-software.com (HELO ?10.1.0.11?) (213.84.59.34)
	by www4.aduna-software.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	5 Jan 2007 14:31:07 +0100
Message-ID: <459E5313.2040806@aduna-software.com>
Date:	Fri, 05 Jan 2007 14:30:59 +0100
From:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To:	Aperture Developers <aperture-devel@lists.sourceforge.net>
References: <459E4B5A.3000108@dfki.de>
In-Reply-To: <459E4B5A.3000108@dfki.de>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
Cc:	reuschling@dfki.uni-kl.de, Heinz.Kirchmann@dfki.de
Subject: Re: [Aperture-devel] crawling files containing dataobjects
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

Gunnar Aastrand Grimnes wrote:
> Has anyone got any good ideas about this? :)

Some rough ideas (partially repeats stuff I wrote in 
http://gnowsis.opendfki.de/wiki/ApertureArchives):

* I think this calls for another major API, next to Crawler and 
Extractor, as it seems to be something altogether different. I call it 
CompoundObjectProcessor for now, still looking for a better name. 
Typical processing in AutoFocus or Gnowsis would then be:

- apply a Crawler on a DataSource, producing a queue of DataObjects.
- for every DataObject in this set:
     - determine the MIME type of the stream
     - see if there is a CompoundObjectProcessor impl for this MIME type.
       if yes:
          - apply the CompoundObjectProcessor on this DataObject and put
            all resulting DataObjects in the queue
       if no:
          - see if there is an Extractor impl for this MIME type and
            if so, apply it on the DataObject

The CompoundObjectProcessor could be given an AccessData instance, just 
like Crawler, to make incremental crawling of such objects possible. We 
have seen cases where zip files were *adapted* periodically, e.g. backup 
archives or dumps of a document management system. Also, IMAP supports 
editing of existing messages (removing attachments, for example), MSN 
Messenger puts all the logs for all sessions in a single file per 
contact, etc. This means that when incrementally crawling a zip file to 
which a single file was added, the latter file would be reported as new, 
the zip file itself as changed and all the other files in the zip file 
as unchanged.

Giving the CompoundObjectProcessor a DataObject rather than, say, an 
InputStream allows it to add container-specific metadata for the archive 
itself (#entries, uncompressed size, etc) and to retrieve metadata it 
may require (e.g. the name of the archive file).

* Alternative: find a way to generalize the Crawler and Extractor APIs 
into one XYZ API: you put a source description in and it produces 
DataObjects that get processed recursively and exhaustively. Feels a bit 
tricky and over-generalization to me but I wanted to mention it, perhaps 
someone has good ideas in this direction.

* Arjohn recently referred me to the Commons VFS project 
(http://jakarta.apache.org/commons/vfs/). From the 1.0 release notes:

"Commons VFS provides a single API for accessing various different file
systems. It presents a uniform view of the files from various different
sources, such as the files on local disk, on an HTTP server, or inside a
Zip archive. For example, you can use filenames like 
"tar:gz:http://anyhost/dir/mytar.tar.gz!/mytar.tar!/path/in/tar/README.txt"
to access a compressed tar file located on a web server."

Could be useful, they seem to handle multiple schemes, multiple archive 
formats and infinite nesting. I didn't look at it in detail thus far. 
It's not clear to me right now how Aperture and Commons VFS would be 
integrated.


Chris
--

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

From - Mon Jan  8 11:33:59 2007
X-Account-Key: account3
X-UIDL: 0000ed5604489a0f
X-Mozilla-Status: 0011
X-Mozilla-Status2: 10000000
Received: from lists-outbound.sourceforge.net ([66.35.250.225]:62417 "EHLO
	lists-outbound.sourceforge.net") by ps6.test.onet.pl with ESMTP
	id <S6211030AbXAHJTR>; Mon, 8 Jan 2007 10:19:17 +0100
Received: from sc8-sf-list2-new.sourceforge.net (sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 8B97912AE6; Mon,  8 Jan 2007 01:19:15 -0800 (PST)
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1H3qet-0000c3-F4 for aperture-devel@lists.sourceforge.net;
	Mon, 08 Jan 2007 01:19:11 -0800
Received: from mailgw1.uni-kl.de ([131.246.120.220])
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1H3qer-0006qI-KP
	for aperture-devel@lists.sourceforge.net;
	Mon, 08 Jan 2007 01:19:13 -0800
Received: from dfki-2203.dfki.uni-kl.de (pc-209.dfki.uni-kl.de
	[131.246.241.69])
	by mailgw1.uni-kl.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	l089IxED024361; Mon, 8 Jan 2007 10:18:59 +0100
Received: from serv-3100.kl.dfki.de (serv-3100.kl.dfki.de [192.168.31.180])
	by dfki-2203.dfki.uni-kl.de (8.11.7p3+Sun/8.11.4) with ESMTP id
	l089Ix111379; Mon, 8 Jan 2007 10:18:59 +0100 (MET)
Received: from [192.168.31.36] (port-3126.kl.dfki.de [192.168.31.36])
	by serv-3100.kl.dfki.de (8.13.7+Sun/8.13.7) with ESMTP id
	l089IviM018032; Mon, 8 Jan 2007 10:18:57 +0100 (CET)
Message-ID: <45A20C76.6060404@dfki.de>
Date:	Mon, 08 Jan 2007 10:18:46 +0100
From:	Leo Sauermann <leo.sauermann@dfki.de>
Organization: DFKI GmbH
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To:	Christiaan Fluit <christiaan.fluit@aduna-software.com>
References: <459E4B5A.3000108@dfki.de> <459E5313.2040806@aduna-software.com>
In-Reply-To: <459E5313.2040806@aduna-software.com>
X-Spam-Score: 0.1 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	0.1 HTML_30_40             BODY: Message is 30% to 40% HTML
	0.0 HTML_MESSAGE           BODY: HTML included in message
Cc:	Aperture Developers <aperture-devel@lists.sourceforge.net>,
	reuschling@dfki.uni-kl.de, Heinz.Kirchmann@dfki.de
Subject: Re: [Aperture-devel] crawling files containing dataobjects
X-BeenThere: aperture-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <aperture-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=aperture-devel>
List-Post: <mailto:aperture-devel@lists.sourceforge.net>
List-Help: <mailto:aperture-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe:	<https://lists.sourceforge.net/lists/listinfo/aperture-devel>, 
	<mailto:aperture-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0819959470=="
Sender:	aperture-devel-bounces@lists.sourceforge.net
Errors-To: aperture-devel-bounces@lists.sourceforge.net
X-OnetAntySpam: NIE, to nie jest SPAM
X-OrigFrom: aperture-devel-bounces@lists.sourceforge.net
X-ZA0: unknown (-1,0)
Status:   

This is a multi-part message in MIME format.
--===============0819959470==
Content-Type: multipart/alternative;
	boundary="------------040600050702020007000000"

This is a multi-part message in MIME format.
--------------040600050702020007000000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgw1.uni-kl.de id
	l089IxED024361

Ok,

I have updated the wiki-page with pro/con votes,
please continue the discussion both via e-mail and on the wiki, so that=20
we can read it monthsl later also.

Here my feedback:

Solutions:


    CompoundObjectProcessor?
    <https://gnowsis.opendfki.de/wiki/CompoundObjectProcessor> =B6
    <https://gnowsis.opendfki.de/wiki/ApertureArchives#CompoundObjectProc=
essor>

Leo: how about naming it "Sub-Crawler" or "MicroCrawler?=20
<https://gnowsis.opendfki.de/wiki/MicroCrawler>". This is, a crawler=20
that is crawling inside a bigger crawl process to crawl sub-resources.

    * apply a Crawler on a DataSource?
      <https://gnowsis.opendfki.de/wiki/DataSource>, producing a queue
      of DataObjects? <https://gnowsis.opendfki.de/wiki/DataObjects>.
    * for every DataObject?
      <https://gnowsis.opendfki.de/wiki/DataObject> in this set:
          o determine the MIME type of the stream
          o see if there is a CompoundObjectProcessor?
            <https://gnowsis.opendfki.de/wiki/CompoundObjectProcessor>
            impl for this MIME type. if yes:
                + apply the CompoundObjectProcessor?
                  <https://gnowsis.opendfki.de/wiki/CompoundObjectProcess=
or>
                  on this DataObject?
                  <https://gnowsis.opendfki.de/wiki/DataObject> and put
                  all resulting DataObjects?
                  <https://gnowsis.opendfki.de/wiki/DataObjects> in the
                  queue
          o if no:
                + see if there is an Extractor impl for this MIME type
                  and if so, apply it on the DataObject?
                  <https://gnowsis.opendfki.de/wiki/DataObject>

The CompoundObjectProcessor?=20
<https://gnowsis.opendfki.de/wiki/CompoundObjectProcessor> could be=20
given an AccessData? <https://gnowsis.opendfki.de/wiki/AccessData>=20
instance, just like Crawler, to make incremental crawling of such=20
objects possible.

Giving the CompoundObjectProcessor?=20
<https://gnowsis.opendfki.de/wiki/CompoundObjectProcessor> a DataObject?=20
<https://gnowsis.opendfki.de/wiki/DataObject> rather than, say, an=20
InputStream? <https://gnowsis.opendfki.de/wiki/InputStream> allows it to=20
add container-specific metadata for the archive itself (#entries,=20
uncompressed size, etc) and to retrieve metadata it may require (e.g.=20
the name of the archive file).

Pro:

    * Leo: could handle most prolbems

Con:

    * Leo: When you have the file extension ".xml", there is a billion
      choices how to extract the info from it.

Vote:

    * Leo: +


    Merge Crawler and Exctractor =B6
    <https://gnowsis.opendfki.de/wiki/ApertureArchives#MergeCrawlerandExc=
tractor>

Alternative: find a way to generalize the Crawler and Extractor APIs=20
into one XYZ API: you put a source description in and it produces=20
DataObjects? <https://gnowsis.opendfki.de/wiki/DataObjects> that get=20
processed recursively and exhaustively. Feels a bit tricky and=20
over-generalization to me but I wanted to mention it, perhaps someone=20
has good ideas in this direction.

Pro:

Con:

    * Leo: that would make it soo generic that it is useless.

Vote:

    * Leo: -


    Let Extractor do more =B6
    <https://gnowsis.opendfki.de/wiki/ApertureArchives#LetExtractordomore=
>

The Extractor interface was designed to return more than one resource=20
anyway. It can do that by wrapping them inside the RDFContainer, we have=20
done that with addresses in e-mails already, using anonymous nodes or=20
URI nodes in between (for sender/cc).

Extractor can return a bigger RDF graph inside one RDF Container (which=20
works already), but the RDFContainer could be extended with a list of=20
resources contained within. The list can be done either using RDF=20
metadata (x aperture:isContainedIn y) or with a Java list.

Pro:

    * Leo: works today

Con:

    * Leo: hard to optimize Lucene index afterwards



Es begab sich aber da Christiaan Fluit zur rechten Zeit 05.01.2007 14:30=20
folgendes schrieb:
> Gunnar Aastrand Grimnes wrote:
>  =20
>> Has anyone got any good ideas about this? :)
>>    =20
>
> Some rough ideas (partially repeats stuff I wrote in=20
> http://gnowsis.opendfki.de/wiki/ApertureArchives):
>
> * I think this calls for another major API, next to Crawler and=20
> Extractor, as it seems to be something altogether different. I call it=20
> CompoundObjectProcessor for now, still looking for a better name.=20
> Typical processing in AutoFocus or Gnowsis would then be:
>
> - apply a Crawler on a DataSource, producing a queue of DataObjects.
> - for every DataObject in this set:
>      - determine the MIME type of the stream
>      - see if there is a CompoundObjectProcessor impl for this MIME typ=
e.
>        if yes:
>           - apply the CompoundObjectProcessor on this DataObject and pu=
t
>             all resulting DataObjects in the queue
>        if no:
>           - see if there is an Extractor impl for this MIME type and
>             if so, apply it on the DataObject
>
> The CompoundObjectProcessor could be given an AccessData instance, just=
=20
> like Crawler, to make incremental crawling of such objects possible. We=
=20
> have seen cases where zip files were *adapted* periodically, e.g. backu=
p=20
> archives or dumps of a document management system. Also, IMAP supports=20
> editing of existing messages (removing attachments, for example), MSN=20
> Messenger puts all the logs for all sessions in a single file per=20
> contact, etc. This means that when incrementally crawling a zip file to=
=20
> which a single file was added, the latter file would be reported as new=
,=20
> the zip file itself as changed and all the other files in the zip file=20
> as unchanged.
>
> Giving the CompoundObjectProcessor a DataObject rather than, say, an=20
> InputStream allows it to add container-specific metadata for the archiv=
e=20
> itself (#entries, uncompressed size, etc) and to retrieve metadata it=20
> may require (e.g. the name of the archive file).
>
> * Alternative: find a way to generalize the Crawler and Extractor APIs=20
> into one XYZ API: you put a source description in and it produces=20
> DataObjects that get processed recursively and exhaustively. Feels a bi=
t=20
> tricky and over-generalization to me but I wanted to mention it, perhap=
s=20
> someone has good ideas in this direction.
>
> * Arjohn recently referred me to the Commons VFS project=20
> (http://jakarta.apache.org/commons/vfs/). From the 1.0 release notes:
>
> "Commons VFS provides a single API for accessing various different file
> systems. It presents a uniform view of the files from various different
> sources, such as the files on local disk, on an HTTP server, or inside =
a
> Zip archive. For example, you can use filenames like=20
> "tar:gz:http://anyhost/dir/mytar.tar.gz!/mytar.tar!/path/in/tar/README.=
txt"
> to access a compressed tar file located on a web server."
>
> Could be useful, they seem to handle multiple schemes, multiple archive=
=20
> formats and infinite nesting. I didn't look at it in detail thus far.=20
> It's not clear to me right now how Aperture and Commons VFS would be=20
> integrated.
>
>
> Chris
> --
>
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share=
 your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Aperture-devel mailing list
> Aperture-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aperture-devel
>  =20


--=20
____________________________________________________
DI Leo Sauermann       http://www.dfki.de/~sauermann=20
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  leo.sauermann@dfki.de
____________________________________________________


--------------040600050702020007000000
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ok, <br>
<br>
I have updated the wiki-page with pro/con votes,<br>
please continue the discussion both via e-mail and on the wiki, so that
we can read it monthsl later also.<br>
<br>
Here my feedback:<br>
<p>Solutions:
</p>
<h2 id="CompoundObjectProcessor"><a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/CompoundObjectProcessor"
 rel="nofollow">CompoundObjectProcessor?</a><a
 title="Link to this section" class="anchor"
 href="https://gnowsis.opendfki.de/wiki/ApertureArchives#CompoundObjectProcessor">
&para;</a></h2>
<p>
Leo: how about naming it "Sub-Crawler" or "<a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/MicroCrawler" rel="nofollow">MicroCrawler?</a>".
This is, a crawler that is crawling inside a bigger crawl process to
crawl sub-resources.
</p>
<ul>
  <li>apply a Crawler on a <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/DataSource" rel="nofollow">DataSource?</a>,
producing a queue of <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/DataObjects" rel="nofollow">DataObjects?</a>.
  </li>
  <li>for every <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/DataObject" rel="nofollow">DataObject?</a>
in this set:
    <ul>
      <li>determine the MIME type of the stream
      </li>
      <li>see if there is a <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/CompoundObjectProcessor"
 rel="nofollow">CompoundObjectProcessor?</a> impl for this MIME type.
if yes:
        <ul>
          <li>apply the <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/CompoundObjectProcessor"
 rel="nofollow">CompoundObjectProcessor?</a> on this <a
 class="missing wiki" href="https://gnowsis.opendfki.de/wiki/DataObject"
 rel="nofollow">DataObject?</a> and put
all resulting <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/DataObjects" rel="nofollow">DataObjects?</a>
in the queue
          </li>
        </ul>
      </li>
      <li>if no:
        <ul>
          <li>see if there is an Extractor impl for this MIME type and
if so, apply it on the <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/DataObject" rel="nofollow">DataObject?</a>
          </li>
        </ul>
      </li>
    </ul>
  </li>
</ul>
<p>The <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/CompoundObjectProcessor"
 rel="nofollow">CompoundObjectProcessor?</a> could be given an <a
 class="missing wiki" href="https://gnowsis.opendfki.de/wiki/AccessData"
 rel="nofollow">AccessData?</a> instance, just like Crawler, to make
incremental crawling of such objects possible. </p>
<p>
Giving the <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/CompoundObjectProcessor"
 rel="nofollow">CompoundObjectProcessor?</a> a <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/DataObject" rel="nofollow">DataObject?</a>
rather than, say, an <a class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/InputStream" rel="nofollow">InputStream?</a>
allows it to add container-specific metadata for the archive itself
(#entries, uncompressed size, etc) and to retrieve metadata it may
require (e.g. the name of the archive file).
</p>
<p>
Pro: </p>
<ul>
  <li>Leo: could handle most prolbems
  </li>
</ul>
<p>Con:
</p>
<ul>
  <li>Leo: When you have the file extension ".xml", there is a billion
choices how to extract the info from it. </li>
</ul>
<p>Vote:
</p>
<ul>
  <li>Leo: +
  </li>
</ul>
<h2 id="MergeCrawlerandExctractor">Merge Crawler and Exctractor<a
 title="Link to this section" class="anchor"
 href="https://gnowsis.opendfki.de/wiki/ApertureArchives#MergeCrawlerandExctractor">
&para;</a></h2>
<p>
Alternative: find a way to generalize the Crawler and Extractor APIs
into one XYZ API: you put a source description in and it produces <a
 class="missing wiki"
 href="https://gnowsis.opendfki.de/wiki/DataObjects" rel="nofollow">DataObjects?</a>
that get processed recursively and exhaustively. Feels a bit tricky and
over-generalization to me but I wanted to mention it, perhaps someone
has good ideas in this direction.
</p>
<p>
Pro:
</p>
<p>
Con:
</p>
<ul>
  <li>Leo: that would make it soo generic that it is useless.
  </li>
</ul>
<p>Vote:
</p>
<ul>
  <li>Leo: - </li>
</ul>
<h2 id="LetExtractordomore">Let Extractor do more<a
 title="Link to this section" class="anchor"
 href="https://gnowsis.opendfki.de/wiki/ApertureArchives#LetExtractordomore">
&para;</a></h2>
<p>
The Extractor interface was designed to return more than one resource
anyway.
It can do that by wrapping them inside the RDFContainer, we have done
that with addresses in e-mails already, using anonymous nodes or URI
nodes in between (for sender/cc).
</p>
<p>
Extractor can return a bigger RDF graph inside one RDF Container (which
works already),
but the RDFContainer could be extended with a list of resources
contained within.
The list can be done either using RDF metadata (x
aperture:isContainedIn y)
or with a Java list.
</p>
<p>
Pro:
</p>
<ul>
  <li>Leo: works today
  </li>
</ul>
<p>Con:
</p>
<ul>
  <li>Leo: hard to optimize Lucene index afterwards
  </li>
</ul>
<br>
<br>
Es begab sich aber da Christiaan Fluit zur rechten Zeit 05.01.2007
14:30 folgendes schrieb:
<blockquote cite="mid459E5313.2040806@aduna-software.com" type="cite">
  <pre wrap="">Gunnar Aastrand Grimnes wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Has anyone got any good ideas about this? :)
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Some rough ideas (partially repeats stuff I wrote in 
<a class="moz-txt-link-freetext" href="http://gnowsis.opendfki.de/wiki/ApertureArchives">http://gnowsis.opendfki.de/wiki/ApertureArchives</a>):

* I think this calls for another major API, next to Crawler and 
Extractor, as it seems to be something altogether different. I call it 
CompoundObjectProcessor for now, still looking for a better name. 
Typical processing in AutoFocus or Gnowsis would then be:

- apply a Crawler on a DataSource, producing a queue of DataObjects.
- for every DataObject in this set:
     - determine the MIME type of the stream
     - see if there is a CompoundObjectProcessor impl for this MIME type.
       if yes:
          - apply the CompoundObjectProcessor on this DataObject and put
            all resulting DataObjects in the queue
       if no:
          - see if there is an Extractor impl for this MIME type and
            if so, apply it on the DataObject

The CompoundObjectProcessor could be given an AccessData instance, just 
like Crawler, to make incremental crawling of such objects possible. We 
have seen cases where zip files were *adapted* periodically, e.g. backup 
archives or dumps of a document management system. Also, IMAP supports 
editing of existing messages (removing attachments, for example), MSN 
Messenger puts all the logs for all sessions in a single file per 
contact, etc. This means that when incrementally crawling a zip file to 
which a single file was added, the latter file would be reported as new, 
the zip file itself as changed and all the other files in the zip file 
as unchanged.

Giving the CompoundObjectProcessor a DataObject rather than, say, an 
InputStream allows it to add container-specific metadata for the archive 
itself (#entries, uncompressed size, etc) and to retrieve metadata it 
may require (e.g. the name of the archive file).

* Alternative: find a way to generalize the Crawler and Extractor APIs 
into one XYZ API: you put a source description in and it produces 
DataObjects that get processed recursively and exhaustively. Feels a bit 
tricky and over-generalization to me but I wanted to mention it, perhaps 
someone has good ideas in this direction.

* Arjohn recently referred me to the Commons VFS project 
(<a class="moz-txt-link-freetext" href="http://jakarta.apache.org/commons/vfs/">http://jakarta.apache.org/commons/vfs/</a>). From the 1.0 release notes:

"Commons VFS provides a single API for accessing various different file
systems. It presents a uniform view of the files from various different
sources, such as the files on local disk, on an HTTP server, or inside a
Zip archive. For example, you can use filenames like 
"tar:gz:<a class="moz-txt-link-freetext" href="http://anyhost/dir/mytar.tar.gz!/mytar.tar!/path/in/tar/README.txt">http://anyhost/dir/mytar.tar.gz!/mytar.tar!/path/in/tar/README.txt</a>"
to access a compressed tar file located on a web server."

Could be useful, they seem to handle multiple schemes, multiple archive 
formats and infinite nesting. I didn't look at it in detail thus far. 
It's not clear to me right now how Aperture and Commons VFS would be 
integrated.


Chris
--

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT &amp; business topics through brief surveys - and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&amp;p=sourceforge&amp;CID=DEVDEV</a>
_______________________________________________
Aperture-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aperture-devel@lists.sourceforge.net">Aperture-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/aperture-devel">https://lists.sourceforge.net/lists/listinfo/aperture-devel</a>
  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
____________________________________________________
DI Leo Sauermann       <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> 
DFKI GmbH
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern   Fax:   +49 631 205-3472
Germany                Mail:  <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a>
____________________________________________________
</pre>
</body>
</html>

--------------040600050702020007000000--


--===============0819959470==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--===============0819959470==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aperture-devel mailing list
Aperture-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aperture-devel

--===============0819959470==--