Yep, I've already implemented support for this in the as yet unavailable
client code I've been working (rather slowly, unfortunately) to clean up.
- James
Bob Wyman wrote:
> James M Snell mentioned his Apache Project...
>
> It would be *very* nice if you could see your way to implementing
> "RF
James M Snell mentioned his Apache Project...
It would be *very* nice if you could see your way to implementing
"RFC3229+feed"[1] support in your implementation. As I think you know, the
use of this mechanism results in massive reductions in the bandwidth and
client-side processing required in fe
On 5/23/06, James M Snell <[EMAIL PROTECTED]> wrote:
We made a mistake calling our stuff a "reference implementation"
It's OK. We're used to this kind of thing coming from your direction.
--
Robert Sayre
On May 23, 2006, at 8:35 AM, James M Snell wrote:
The goal is to have a reference implementation that is also usable.
However, I do have to be careful here, the IETF doesn't really do
reference implemenations so the naming of this project is a bit wrong.
We really shouldn't be calling it a "ref
Sylvain Hellegouarch wrote:
Demokritos might be quite well advanced but unfortunately Python code
is not very suited for us poor souls who still have to struggle with
java environments ;-)
I guess I kind of got that as well. That being said, it will be nice of
the project at some point can
That sounds good to me.
Please not though that I didn't care about the language, my only
questions were:
1. Why not using an existing project?
2. How interoperable had you planned to be?
It seems these questions have more or less been answered so I'm fine :)
- Sylvain
Right. IETF specs ca
Right. IETF specs cannot have an official reference implementation. The
best we can do, in this case, is to have a number of implementations
available that strive to a) implement the spec as completely as possible
and b) interoperate with one another as best as possible. The
"reference implement
FWIW, I removed the term "reference implemenation" from the proposal to
properly reflect the nature of the implementation.
Ugo Cei wrote:
>
> at
> On May 23, 2006, at 4:53 PM, Walter Underwood wrote:
>
>> The goal is a reference implementation. The goal is to be exactly
>> correct.
>> Being in
* Sylvain Hellegouarch <[EMAIL PROTECTED]> [2006-05-23 17:20]:
> As we have already seen on this list, RFC4287 lacks of
> precision in some context, therefore I wonder what being
> "exactly correct" represents.
Did I miss something? I remember several oversights of omission,
but none of imprecisi
at
On May 23, 2006, at 4:53 PM, Walter Underwood wrote:
The goal is a reference implementation. The goal is to be exactly
correct.
Being in a particular language, or even being fast enough to be
usable,
is beside the point. In particular, a reference implementation should
always choose code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Elliotte Harold wrote:
> Of course, this requires the reference implementation to be developed
> with the same authority that the spec writers have. That's not at all
> the case here, so I suspect "reference implementation" is a false
> statement. Thi
I don't really want to get into a lot of detail here (it's not the
proper forum for it). The project will provide a Java-language Atom
parser, APP client, and some APP server side code with the goal of
providing as complete an implementation as possible.
And regarding the choice of the XML parser
In this particular case, it means providing an implementation that
allows, as closely as possible, everything that the spec allows. For
instance, if you look at the code, the Link element is marked as being
extensible and as allowing string content, both of which are explicitly
allowed by RFC4287
The goal is to have a reference implementation that is also usable.
However, I do have to be careful here, the IETF doesn't really do
reference implemenations so the naming of this project is a bit wrong.
We really shouldn't be calling it a "reference implementation" although
that is the kind of t
Sylvain Hellegouarch wrote:
I'm sorry to ask but I'm not sure to understand the meaning of having an
implementation which is exactly correct. As we have already seen on this
list, RFC4287 lacks of precision in some context, therefore I wonder what
being "exactly correct" represents. I believe J
> I believe Jigsaw [1] is a an example of what you mean.
Jigsaw: http://www.w3.org/Jigsaw/
But you all knew that. ;)
- Sylvain
> The goal is a reference implementation. The goal is to be exactly correct.
> Being in a particular language, or even being fast enough to be usable,
> is beside the point. In particular, a reference implementation should
> always choose code readability over speed.
Fair enough.
>
> If the goa
--On May 23, 2006 3:18:18 PM +0200 Ugo Cei <[EMAIL PROTECTED]> wrote:
Demokritos might be quite well advanced but unfortunately Python code is not
very suited for us poor souls who still have to struggle with java
environments ;-)
The goal is a reference implementation. The goal is to be ex
I could certainly do with more of a critical mass of users /
contributors / people-on-the-mailing-list
James
On 23/05/2006, at 8:59 AM, Sylvain Hellegouarch wrote:
It seems to be good idea to do such promotion. However I wonder why
you
have not considerated using an existing project suc
> Demokritos might be quite well advanced but unfortunately Python code
> is not very suited for us poor souls who still have to struggle with
> java environments ;-)
>
I guess I kind of got that as well. That being said, it will be nice of
the project at some point can state exactly how it will
On May 23, 2006, at 2:59 PM, Sylvain Hellegouarch wrote:
It seems to be good idea to do such promotion. However I wonder why
you
have not considerated using an existing project such as demokritos [1]
which is quite well advanced.
Demokritos might be quite well advanced but unfortunately Py
>
> James M Snell wrote:
>> Just an FYI,
>>
>> http://wiki.apache.org/incubator/AriProposal
>> http://www.snellspace.com/wp/?p=323
>> http://www.snellspace.com/public/ari.tar.gz
>>
>> We are proposing the creation of an Atom Reference Implementation
>> project at Apache and have donated source to
James M Snell wrote:
Just an FYI,
http://wiki.apache.org/incubator/AriProposal
http://www.snellspace.com/wp/?p=323
http://www.snellspace.com/public/ari.tar.gz
We are proposing the creation of an Atom Reference Implementation
project at Apache and have donated source to kick things off.
I'm
James M Snell wrote:
We are proposing the creation of an Atom Reference Implementation
project at Apache and have donated source to kick things off.
What minimum Java version are you targetting? 1.2? 1.4? 5?
--
Elliotte Rusty Harold [EMAIL PROTECTED]
XML in a Nutshell 3rd Edition Just Pub
James M Snell wrote:
We are proposing the creation of an Atom Reference Implementation
project at Apache and have donated source to kick things off. Currently
the source fully implements RFC4287 and includes preliminary support for
parsing APP introspection documents and the Feed Thread Extens
25 matches
Mail list logo
