You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xindice-dev@xml.apache.org by Kimbro Staken <ks...@xmldatabases.org> on 2002/08/18 03:13:07 UTC
[VOTE] New contributions and committers
OK, for this we're actually voting on two things. First if we want to
accept the contributions and second if we want to accept the people as new
committers. I'm proposing that we accept all of them.
Contributions: Observable code (in CVS already), Meta-data implementation,
linking implementation and a few other things. See the archives for more
details, the code is attached to a couple messages from David Viner in the
thread "proposal for metadata storage in xindice".
People: David Viner and David Ku
Contribution: XNode API. This is an alternative Java API originally
developed at Sun that also adds meta-data support. The API docs are
available. http://kmi.open.ac.uk/projects/ceryle/docs/api/org/apache/xnode/
package-summary.html
Person: Murray Altheim
Kimbro Staken
Java and XML Software, Consulting and Writing http://www.xmldatabases.org/
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org
Re: [VOTE] New contributions and committers
Posted by Gianugo Rabellino <gi...@apache.org>.
Kimbro Staken wrote:
> OK, for this we're actually voting on two things. First if we want to
> accept the contributions and second if we want to accept the people as
> new committers. I'm proposing that we accept all of them.
Sorry for the delay, I was on vacation. +1 for everything, and welcome
aboard!
Ciao,
--
Gianugo Rabellino
>
> Contributions: Observable code (in CVS already), Meta-data implementation,
> linking implementation and a few other things. See the archives for
> more details, the code is attached to a couple messages from David Viner
> in the thread "proposal for metadata storage in xindice".
> People: David Viner and David Ku
>
> Contribution: XNode API. This is an alternative Java API originally
> developed at Sun that also adds meta-data support. The API docs are
> available. http://kmi.open.ac.uk/projects/ceryle/docs/api/org/apache/xnode/
> package-summary.html
> Person: Murray Altheim
>
> Kimbro Staken
> Java and XML Software, Consulting and Writing http://www.xmldatabases.org/
> Apache Xindice native XML database http://xml.apache.org/xindice
> XML:DB Initiative http://www.xmldb.org
>
Re: [VOTE] New contributions and committers
Posted by Kurt Ward <ku...@yahoo.com>.
+1 for all. I have worked with David Viner on the PHP XML-RPC client
and have also applied at least one of David Ku's older patches in the CVS
tree
some time back. Glad to see them here!!
Kurt
----- Original Message -----
From: "David Viner" <dv...@yahoo-inc.com>
To: <xi...@xml.apache.org>
Sent: Monday, August 19, 2002 7:32 PM
Subject: RE: [VOTE] New contributions and committers
> obviously, i'd vote in favor of this :)
>
> dave
>
> -----Original Message-----
> From: Kimbro Staken [mailto:kstaken@xmldatabases.org]
> Sent: Saturday, August 17, 2002 6:13 PM
> To: xindice-dev@xml.apache.org
> Subject: [VOTE] New contributions and committers
>
>
> OK, for this we're actually voting on two things. First if we want to
> accept the contributions and second if we want to accept the people as new
> committers. I'm proposing that we accept all of them.
>
> Contributions: Observable code (in CVS already), Meta-data implementation,
> linking implementation and a few other things. See the archives for more
> details, the code is attached to a couple messages from David Viner in the
> thread "proposal for metadata storage in xindice".
> People: David Viner and David Ku
>
> Contribution: XNode API. This is an alternative Java API originally
> developed at Sun that also adds meta-data support. The API docs are
> available.
http://kmi.open.ac.uk/projects/ceryle/docs/api/org/apache/xnode/
> package-summary.html
> Person: Murray Altheim
>
> Kimbro Staken
> Java and XML Software, Consulting and Writing http://www.xmldatabases.org/
> Apache Xindice native XML database http://xml.apache.org/xindice
> XML:DB Initiative http://www.xmldb.org
>
RE: [VOTE] New contributions and committers
Posted by David Viner <dv...@yahoo-inc.com>.
obviously, i'd vote in favor of this :)
dave
-----Original Message-----
From: Kimbro Staken [mailto:kstaken@xmldatabases.org]
Sent: Saturday, August 17, 2002 6:13 PM
To: xindice-dev@xml.apache.org
Subject: [VOTE] New contributions and committers
OK, for this we're actually voting on two things. First if we want to
accept the contributions and second if we want to accept the people as new
committers. I'm proposing that we accept all of them.
Contributions: Observable code (in CVS already), Meta-data implementation,
linking implementation and a few other things. See the archives for more
details, the code is attached to a couple messages from David Viner in the
thread "proposal for metadata storage in xindice".
People: David Viner and David Ku
Contribution: XNode API. This is an alternative Java API originally
developed at Sun that also adds meta-data support. The API docs are
available. http://kmi.open.ac.uk/projects/ceryle/docs/api/org/apache/xnode/
package-summary.html
Person: Murray Altheim
Kimbro Staken
Java and XML Software, Consulting and Writing http://www.xmldatabases.org/
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org
Re: [VOTE] New contributions and committers
Posted by Murray Altheim <m....@open.ac.uk>.
Fernando Padilla wrote:
[...]
> Well, I'm not saying that one is not as good as the other. They are both
> competent implementations of meta-data extensions for XML:DB. But my
> design principles have always been to strive for simplicity and
> consistency.
>
> I can just see that at somepoint in the future this functionality is to be
> folded into Xindice core - so that the system can maintain its meta-data,
> like last modified, mime-type and whether a Resource is Binary or XML.
> At that point having two implementations will go against simplicity and
> consistency and we'll have to come up with one implementation to go with,
> even if it'll look nothing like what we have today.
>
> So I'm leaning towards folding in both implementations, but having them
> share a common api so the implementation is configurable...
Fernado,
Sounds reasonable to me. Since the other metadata API is just being
developed, might I ask that its developers look at the XNode API to
see how close it might be to their in this respect? Since we published
XNode about a year ago (to my memory) there may be people out there
besides myself using it, so it'd be less work to change their code
if there was some similarity in the APIs (I'd not considered the idea
of using one API for both prior to your message).
Ciao,
Murray
......................................................................
Murray Altheim <http://kmi.open.ac.uk/people/murray/>
Knowledge Media Institute
The Open University, Milton Keynes, Bucks, MK7 6AA, UK
One of the sad things about corporations is that despite
their name they have no corpora, no body responsible for
their actions. They are therefore free to do whatever is
the will of those who control them, and can transmogrify
as necessary, like ghosts, to thwart those who might try.
--ma
Re: [VOTE] New contributions and committers
Posted by Fernando Padilla <fe...@interdimensions.com>.
On Wed, 21 Aug 2002, Murray Altheim wrote:
> Fernando Padilla wrote:
>
> > +0
> >
> > Make them committers. And I guess integrate in the meta-data
> > implementations until we have a better idea of what we're doing. :) Then
> > we can refactor out the one that is not as desirable later. :)
>
>
> Perhaps one consideration: there's no need to have only one
> API here. The two metadata proposals are complimentary, different
> approaches to metadata in Xindice. If perhaps one or both are in
> the end poorly designed, not suitable, etc. then certainly pull
> them out, but please consider these alternatives as the SAX and
> DOM of metadata APIs, not competitors.
>
> Also, I'm perfectly happy if XNode becomes an add-on module, a
> jar file available as a supplement to the Xindice download. The
> code is pretty small, but even so it doesn't need to be on
> everyone's machine unless it's believe that the API should be
> available universally (I can't see a good reason for that).
>
> Thanks for the vote of confidence (or at least curiousity), btw.
:)
Well, I'm not saying that one is not as good as the other. They are both
competent implementations of meta-data extensions for XML:DB. But my
design principles have always been to strive for simplicity and
consistency.
I can just see that at somepoint in the future this functionality is to be
folded into Xindice core - so that the system can maintain its meta-data,
like last modified, mime-type and whether a Resource is Binary or XML.
At that point having two implementations will go against simplicity and
consistency and we'll have to come up with one implementation to go with,
even if it'll look nothing like what we have today.
So I'm leaning towards folding in both implementations, but having them
share a common api so the implementation is configurable...
fernado
Re: [VOTE] New contributions and committers
Posted by Murray Altheim <m....@open.ac.uk>.
Fernando Padilla wrote:
> +0
>
> Make them committers. And I guess integrate in the meta-data
> implementations until we have a better idea of what we're doing. :) Then
> we can refactor out the one that is not as desirable later. :)
Perhaps one consideration: there's no need to have only one
API here. The two metadata proposals are complimentary, different
approaches to metadata in Xindice. If perhaps one or both are in
the end poorly designed, not suitable, etc. then certainly pull
them out, but please consider these alternatives as the SAX and
DOM of metadata APIs, not competitors.
Also, I'm perfectly happy if XNode becomes an add-on module, a
jar file available as a supplement to the Xindice download. The
code is pretty small, but even so it doesn't need to be on
everyone's machine unless it's believe that the API should be
available universally (I can't see a good reason for that).
Thanks for the vote of confidence (or at least curiousity), btw.
Murray
......................................................................
Murray Altheim <http://kmi.open.ac.uk/people/murray/>
Knowledge Media Institute
The Open University, Milton Keynes, Bucks, MK7 6AA, UK
One of the sad things about corporations is that despite
their name they have no corpora, no body responsible for
their actions. They are therefore free to do whatever is
the will of those who control them, and can transmogrify
as necessary, like ghosts, to thwart those who might try.
--ma
Re: [VOTE] New contributions and committers
Posted by Fernando Padilla <fe...@interdimensions.com>.
yes.
On Tue, 20 Aug 2002, Kimbro Staken wrote:
> So can we say this is +1 for the committers and +0 on the code?
>
> On Tuesday, August 20, 2002, at 02:58 PM, Fernando Padilla wrote:
>
> >
> > +0
> >
> > Make them committers. And I guess integrate in the meta-data
> > implementations until we have a better idea of what we're doing. :) Then
> > we can refactor out the one that is not as desirable later. :)
Re: [VOTE] New contributions and committers
Posted by Kimbro Staken <ks...@xmldatabases.org>.
So can we say this is +1 for the committers and +0 on the code?
On Tuesday, August 20, 2002, at 02:58 PM, Fernando Padilla wrote:
>
> +0
>
> Make them committers. And I guess integrate in the meta-data
> implementations until we have a better idea of what we're doing. :) Then
> we can refactor out the one that is not as desirable later. :)
>
>
>
> On Sat, 17 Aug 2002, Kimbro Staken wrote:
>
>> OK, for this we're actually voting on two things. First if we want to
>> accept the contributions and second if we want to accept the people as
>> new
>> committers. I'm proposing that we accept all of them.
>>
>> Contributions: Observable code (in CVS already), Meta-data
>> implementation,
>> linking implementation and a few other things. See the archives for
>> more
>> details, the code is attached to a couple messages from David Viner in
>> the
>> thread "proposal for metadata storage in xindice".
>> People: David Viner and David Ku
>>
>> Contribution: XNode API. This is an alternative Java API originally
>> developed at Sun that also adds meta-data support. The API docs are
>> available.
>> http://kmi.open.ac.uk/projects/ceryle/docs/api/org/apache/xnode/
>> package-summary.html
>> Person: Murray Altheim
>>
Kimbro Staken
Java and XML Software, Consulting and Writing http://www.xmldatabases.org/
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org
>>
>>
>
Re: [VOTE] New contributions and committers
Posted by Fernando Padilla <fe...@interdimensions.com>.
+0
Make them committers. And I guess integrate in the meta-data
implementations until we have a better idea of what we're doing. :) Then
we can refactor out the one that is not as desirable later. :)
On Sat, 17 Aug 2002, Kimbro Staken wrote:
> OK, for this we're actually voting on two things. First if we want to
> accept the contributions and second if we want to accept the people as new
> committers. I'm proposing that we accept all of them.
>
> Contributions: Observable code (in CVS already), Meta-data implementation,
> linking implementation and a few other things. See the archives for more
> details, the code is attached to a couple messages from David Viner in the
> thread "proposal for metadata storage in xindice".
> People: David Viner and David Ku
>
> Contribution: XNode API. This is an alternative Java API originally
> developed at Sun that also adds meta-data support. The API docs are
> available. http://kmi.open.ac.uk/projects/ceryle/docs/api/org/apache/xnode/
> package-summary.html
> Person: Murray Altheim
>
> Kimbro Staken
> Java and XML Software, Consulting and Writing http://www.xmldatabases.org/
> Apache Xindice native XML database http://xml.apache.org/xindice
> XML:DB Initiative http://www.xmldb.org
>
>