Draft for XML_Atom

Hello everyone,

After the comments that I received for Services_RPCBlogging,
it seems
that one package to handle all kinds of blog services is
what is
required. In order to relaise that, we need a pear package
that can
communicate with servers using the Atom publishing protocol.

The draft for XML_Atom
(http://pear.php.net/pepr/pepr-proposal-show.php?id=376
) is a step in
that direction. I wish to announce this draft to the
community and
invite anyone interested to contribute in whatever way they
can.

Creating this package is not going to be easy, and so I
definitely need
help. Especially because the protocol itself is an IETF
draft; which
means that some of the specifications are incomplete and
many are open
to interpretation.

Thank you for your time.

Best Regards,
-- 
Anant

Find Freedom, Go Open Source!
http://www.kix.in/

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Please rename it to APP and fix the broken links on the
proposal page.

I'd gladly help out in any way I can. I've been throwing
around ideas
in my head how to write APP package for some time now -
buuut, I
recently broke my hand... 

- Hannes

On 3/21/06, Anant Narayanan <anantkix.in> wrote:
> Hello everyone,
>
> After the comments that I received for
Services_RPCBlogging, it seems
> that one package to handle all kinds of blog services
is what is
> required. In order to relaise that, we need a pear
package that can
> communicate with servers using the Atom publishing
protocol.
>
> The draft for XML_Atom
> (http://pear.php.net/pepr/pepr-proposal-show.php?id=376
) is a step in
> that direction. I wish to announce this draft to the
community and
> invite anyone interested to contribute in whatever way
they can.
>
> Creating this package is not going to be easy, and so I
definitely need
> help. Especially because the protocol itself is an IETF
draft; which
> means that some of the specifications are incomplete
and many are open
> to interpretation.
>
> Thank you for your time.
>
> Best Regards,
> --
> Anant
>
> Find Freedom, Go Open Source!
> http://www.kix.in/
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub
.php
>
>

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

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

I did not read the draft but on the principle it is probably
a good idea
to have an atom package.

Arnaud.

Anant Narayanan wrote:
> Hello everyone,
> 
> After the comments that I received for
Services_RPCBlogging, it seems
> that one package to handle all kinds of blog services
is what is
> required. In order to relaise that, we need a pear
package that can
> communicate with servers using the Atom publishing
protocol.
> 
> The draft for XML_Atom
> (http://pear.php.net/pepr/pepr-proposal-show.php?id=376
) is a step in
> that direction. I wish to announce this draft to the
community and
> invite anyone interested to contribute in whatever way
they can.
> 
> Creating this package is not going to be easy, and so I
definitely need
> help. Especially because the protocol itself is an IETF
draft; which
> means that some of the specifications are incomplete
and many are open
> to interpretation.
> 
> Thank you for your time.
> 
> Best Regards,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFEIHIQpaCRa4qsdSIRAq4FAJ9xSiFSnpfJy+nP9yJDNb7aXyDFpgCc
DTIL
gfl06LCZeLrJyMIMfINvRwA=
=i8Lm
-----END PGP SIGNATURE-----

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Hi Hannes,

Sorry for the late reponse!

> Please rename it to APP and fix the broken links on the
proposal page.

I fixed the links. IMHO, we can change the name later,
sometime around
the proposal phase, because we may receive some more
suggestions about
what we should call it.

> I'd gladly help out in any way I can. I've been
throwing around ideas
> in my head how to write APP package for some time now -
buuut, I
> recently broke my hand... 

Thanks for you support. You can see what I've already done
on the
proposal page. Here's what we need to do:

- Complete the XML_Atom_Response class that will provide
methods to
extract information from the response that is sent by the
Atom server
(response code, content etc). This complements the
XML_Atom_Request
class that is already half built.

- Create an XML_Atom_Feed class that will enable generation
and parsing
of Atom feeds according to the specifications provided by
the IETF.

- Provide methods in the XML_Atom class that uses
XML_Atom_Request to
generate requests to the Atom server, and returns an
XML_Atom_Response
object to the user.

- I've added support for HTTP Basic authentication.
Probably, we should
also support more stronger types of authentication that Atom
also supports.

Feel free to work on any of these, or something else that
you feel is
important. I don't think we are allowed to use the PHP CVS
repository
for collaboration right now, because this is just a draft.
However, it's
just the two of us, so you can just let me know what part
you're doing
so that we don't duplicate work.

Thanks and Regards,
-- 
Anant

Find Freedom, Go Open Source!
http://www.kix.in/

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Hi Anant

> > Please rename it to APP and fix the broken links
on the proposal page.
>
> I fixed the links. IMHO, we can change the name later,
sometime around
> the proposal phase, because we may receive some more
suggestions about
> what we should call it.
The Atom Syndication format is usually referred to as
"Atom" but the
Atom Publishing Protocol is referred to as APP. Calling the
package
Atom *will* create unnecessary confusing.

> - Create an XML_Atom_Feed class that will enable
generation and parsing
> of Atom feeds according to the specifications provided
by the IETF.
AFAIK there are some guys working on XML_Feed_Writer which
will most
likely include support for Atom 1.0.

> Feel free to work on any of these
As I said, I only got one hand available, did try to code
with one
hand few days ago.. ..not going through that hell again for
the next
couple of weeks.

I'll be in contact ASAP 

-Hannes

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

On Mar 22, 2006, at 12:28 PM, Anant Narayanan wrote:
> - Create an XML_Atom_Feed class that will enable
generation and  
> parsing
> of Atom feeds according to the specifications provided
by the IETF.

Is there a particular reason you couldn't use
XML_Feed_Parser for the  
parsing? I've tried as much as possible to comply with the
RFC,  
having tracked it through several iterations before
releasing the  
package.

As I said the other day, it would be good to ensure these
two  
packages can interoperate, and perhaps to see if anyone
wants to  
resuscitate the XML_Feed_Writer proposal to complete that
part of the  
puzzle.

James.

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Hi James,

> Is there a particular reason you couldn't use
XML_Feed_Parser for the
> parsing? I've tried as much as possible to comply with
the RFC, having
> tracked it through several iterations before releasing
the package.

Yes, I did intend to use XML_Feed_Parser for parsing. The
methods in
XML_Atom_Feed are just a wrapper over yours 

> As I said the other day, it would be good to ensure
these two packages
> can interoperate, and perhaps to see if anyone wants to
resuscitate the
> XML_Feed_Writer proposal to complete that part of the
puzzle.

Agreed. I'll see if I can do something about
XML_Feed_Writer. I wanted
to write one for XML_Atom anyway, might as well generalize
it and make a
package out of it.

Best Regards,
-- 
Anant

Find Freedom, Go Open Source!
http://www.kix.in/

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php